centos 6.4 kvm, can't install windows 2008r2
Hello!
My colleague tries to install 64bit windows 2008r2 on centos 6.4 server:
here is kernel version:
# uname -a Linux gesar 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
during setup ( at early stage ) he got:
driver_irql_not_less_or_equal stop
code is 0x000000d1
But he successefully installed windows 2003 on this server....
Any ideas about which driver can cause this and how to fix?
Thank you!
Quoted 13 lines · Dmitry Melekhov
Hello!
My colleague tries to install 64bit windows 2008r2 on centos 6.4 server:
here is kernel version:
# uname -a Linux gesar 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linuxduring setup ( at early stage ) he got:
Quoted 8 lines
driver_irql_not_less_or_equalstopcode is
0x000000d1But he successefully installed windows 2003 on this server....
Any ideas about which driver can cause this and how to fix?
It is better to report problems with vendor kernel to the vendor, but you will have to tell us much more. Did he use libvirt or qemu directly. What is qemu command line. Did he installed virtio drivers? What is the host cpu?
--
Gleb.
13.11.2013 11:29, Gleb Natapov пишет:
Quoted 16 lines · Dmitry Melekhov
Quoted 15 lines
Hello!
My colleague tries to install 64bit windows 2008r2 on centos 6.4 server:
here is kernel version:
# uname -a Linux gesar 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linuxduring setup ( at early stage ) he got:
driver_irql_not_less_or_equalstop
Quoted 7 lines
Quoted 6 lines
code is
0x000000d1But he successefully installed windows 2003 on this server....
Any ideas about which driver can cause this and how to fix?
It is better to report problems with vendor kernel to the vendor,
Absolutely agree, I already posted the same question to centos mail list, but looks like nobody had such problem before.
Quoted 2 lines
but you will have to tell us much more. Did he use libvirt or qemu directly. What is qemu command line. Did he installed virtio drivers?
he use libvirt.
resulted command line is
0:18 /usr/libexec/qemu-kvm -name lubsan -S -M rhel6.4.0 -cpu Penryn,+osxsave,+xsave,+dca,+pdcm,+xtpr,+tm2,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -no-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -uuid 9d95c8bf-0888-ac58-da16-85944e450ea9 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/lubsan.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/mapper/mpathc,if=none,id=drive-ide0-0-1,format=raw,cache=none,aio=native -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=2 -drive file=/opt/iso/ru_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_vl_build_x64_dvd_617421.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -vnc 127.0.0.1:1 -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
cpu type is not default because we tried to do something and changed it, result is the same.
There are no virtio drivers installed.
Quoted 3 lines
What is the host cpu?
This is xeon E5405
Thank you!
Quoted 27 lines · Dmitry Melekhov
13.11.2013 11:29, Gleb Natapov пишет:
Quoted 16 lines · Dmitry Melekhov
Quoted 15 lines
Hello!
My colleague tries to install 64bit windows 2008r2 on centos 6.4 server:
here is kernel version:
# uname -a Linux gesar 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linuxduring setup ( at early stage ) he got:
driver_irql_not_less_or_equalstopQuoted 7 lines
Quoted 6 lines
code is
0x000000d1But he successefully installed windows 2003 on this server....
Any ideas about which driver can cause this and how to fix?
It is better to report problems with vendor kernel to the vendor,
Absolutely agree, I already posted the same question to centos mail list, but looks like nobody had such problem before.
Quoted 8 lines
Quoted 2 lines
but you will have to tell us much more. Did he use libvirt or qemu directly. What is qemu command line. Did he installed virtio drivers?
he use libvirt.
resulted command line is
0:18
/usr/libexec/qemu-kvm-name lubsan -S -M rhel6.4.0 -cpu Penryn,+osxsave,+xsave,+dca,+pdcm,+xtpr,+tm2,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -no-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -uuid
Why no-kvm?
Quoted 14 lines
9d95c8bf-0888-ac58-da16-85944e450ea9 -nodefconfig -nodefaults
(quoted diff) +0
-2-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/lubsan.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtcbase=localtime,driftfix=slew -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/mapper/mpathc,if=none,id=drive-ide0-0-1,format=raw,cache=none,aio=native(quoted diff) +0
-4-device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=2 -drive file=/opt/iso/ru_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_vl_build_x64_dvd_617421.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -vnc 127.0.0.1:1 -vga std -devicevirtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
cpu type is not default because we tried to do something and changed it, result is the same.
Quoted 8 lines
There are no virtio drivers installed.
Quoted 3 lines
What is the host cpu?
This is xeon E5405
Thank you!
--
Gleb.
13.11.2013 11:48, Gleb Natapov пишет:
Quoted 7 lines
resulted command line is
0:18
/usr/libexec/qemu-kvm-name lubsan -S -M rhel6.4.0 -cpu Penryn,+osxsave,+xsave,+dca,+pdcm,+xtpr,+tm2,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -no-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -uuid
Why no-kvm?
Thank you!
That's problem.
hardware support was disabled in bios.
My colleague didn't find this because he created VM in virt-manager and now for some reason it shows virtualization type in advanced, which is hidden by default and all other (newer) servers have hardware support on by default. On the other hand I thought he checked everything before calling me.
Anyway, now I know why we are only who had this problem- we are more stupid then anyone else ;-)