qemu-kvm-0.14.x regression - windows 2K8 R2 stopped booting
Hello,
after I tried updating our production host to 0.14.0 or 0.14.1, our windows terminal server stopped booting. Here's BSOD screen:
http://nik.lbox.cz/public/wincrash.png
reverting to 0.13.5 fixes the problem.
I can't reproduce this on testing hardware though :(
exact guest version:
Microsoft Windows Server 2008 R2 Enterprise
6.1.7600 build 7600x86_64, 4GB RAM, 1CPU
host is currently running 2.6.38.7 (but I had the problem also with 2.6.37) it's 8core intel E5310 with 16GB RAM
since the hosts on which I'm experiencing this problem are production machines, my possibilities of testing are a bit limited (bisecting this will be quite problematic), but I'll do what I can to help fix this... Could somebody please have a look on it?
thanks a lot in advance!
n.
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 7 lines · Nikola Ciprich
Hello,
after I tried updating our production host to 0.14.0 or 0.14.1, our windows terminal server stopped booting. Here's BSOD screen:
http://nik.lbox.cz/public/wincrash.png
reverting to 0.13.5 fixes the problem.
I can't reproduce this on testing hardware though :(
Quoted 8 lines
exact guest version:
Microsoft Windows Server 2008 R2 Enterprise
6.1.7600 build 7600x86_64, 4GB RAM, 1CPUhost is currently running 2.6.38.7 (but I had the problem also with 2.6.37) it's 8core intel E5310 with 16GB RAM
What is you command line?
Quoted 3 lines
since the hosts on which I'm experiencing this problem are production machines, my possibilities of testing are a bit limited (bisecting this will be quite problematic), but I'll do what I can to help fix this... Could somebody please have a look on it?
thanks a lot in advance!
You can make a copy from your production image, install 0.14 version in different place from 0.13 and experiment.
--
Gleb.
Hello Gleb!
Quoted 1 line
What is you command line?
currently it's:/usr/bin/qemu-kvm -S -M pc-0.13 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmwts02 -uuid 1e501300-dc48-11df-a690-00304834195b -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmwts02.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmwts02-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive 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 -netdev tap,fd=15,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:61:01:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:30802 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 but this is with 0.13.5 (so it's running well). it's started using libvirt, I guess with 0.14.0 the command line should be very similar. (I can provide it later if needed).
Quoted 2 lines
You can make a copy from your production image, install 0.14 version in different place from 0.13 and experiment.
yup, I think I've tried it also with exact copy and wasn't able to reproduce it, but I'll try it again and report soon. n.
Quoted 9 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 3 lines · Nikola Ciprich
Quoted 2 lines
You can make a copy from your production image, install 0.14 version in different place from 0.13 and experiment.
yup, I think I've tried it also with exact copy and wasn't able to reproduce it, but I'll try it again and report soon.
Then check image file permission please.
--
Gleb.
OK, I tried copying the whole image to my test box running 0.14.0 again and it crashes with exactly the same BSOD! So now I have the test environment to play with...
What should I check/try now?
n.
PS: I'm not sure what You mean by permissions, but I'm using LVM partitions and qemu-kvm is started by root user anyways..
Quoted 13 lines · Gleb Natapov
Quoted 3 lines · Nikola Ciprich
Quoted 2 lines
You can make a copy from your production image, install 0.14 version in different place from 0.13 and experiment.
yup, I think I've tried it also with exact copy and wasn't able to reproduce it, but I'll try it again and report soon.
Then check image file permission please.
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 6 lines · Nikola Ciprich
OK, I tried copying the whole image to my test box running 0.14.0 again and it crashes with exactly the same BSOD! So now I have the test environment to play with...
What should I check/try now?
n.
PS: I'm not sure what You mean by permissions, but I'm using LVM partitions and qemu-kvm is started by root user anyways..
This BSOD usually indicates that Windows can't write to the boot disk. This is usually happens if qemu has no permission to write to the image file. But if you are starting qemu as a root this is probably is not the case. So what is your 0.14 command line?
Quoted 7 lines · Gleb Natapov
Quoted 6 lines · Nikola Ciprich
Quoted 3 lines
Quoted 2 lines
You can make a copy from your production image, install 0.14 version in different place from 0.13 and experiment.
yup, I think I've tried it also with exact copy and wasn't able to reproduce it, but I'll try it again and report soon.
Then check image file permission please.
Quoted 23 lines
Quoted 7 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlSignature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
--
Gleb.
Quoted 3 lines
This BSOD usually indicates that Windows can't write to the boot disk. This is usually happens if qemu has no permission to write to the image file. But if you are starting qemu as a root this is probably is not the
OK, I see.
Quoted 1 line
case. So what is your 0.14 command line?
here it goes:/usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid 1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmtst04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=14,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:18:04:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:24104 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
Quoted 41 lines
Quoted 8 lines · Gleb Natapov
Quoted 6 lines · Nikola Ciprich
Quoted 3 lines
Quoted 2 lines
You can make a copy from your production image, install 0.14 version in different place from 0.13 and experiment.
yup, I think I've tried it also with exact copy and wasn't able to reproduce it, but I'll try it again and report soon.
Then check image file permission please.
Quoted 23 lines
Quoted 7 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlSignature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] ---------------------------------------
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 4 lines · Nikola Ciprich
Quoted 3 lines
This BSOD usually indicates that Windows can't write to the boot disk. This is usually happens if qemu has no permission to write to the image file. But if you are starting qemu as a root this is probably is not the
OK, I see.
May be libvirt does something funny with selinux.
Quoted 3 lines
Quoted 1 line
case. So what is your 0.14 command line?
here it goes:
/usr/bin/qemu-kvm-S -M pc-0.14 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid 1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmtst04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=14,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:18:04:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:24104 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
Try to run with -M pc-0.13.
--
Gleb.
Quoted 1 line
May be libvirt does something funny with selinux.
it shouldn't, I don't have selinux enabled in host kernel at all..
Quoted 1 line
Try to run with -M pc-0.13.
tried now, same result...
Quoted 8 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 7 lines · Nikola Ciprich
Quoted 1 line
May be libvirt does something funny with selinux.
it shouldn't, I don't have selinux enabled in host kernel at all..
Quoted 1 line
Try to run with -M pc-0.13.
tried now, same result...
Hmm. And what if you start qemu directly (without using libvirt) with 0.13 command line?
--
Gleb.
Quoted 2 lines
Hmm. And what if you start qemu directly (without using libvirt) with 0.13 command line?
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104
same result...
Quoted 8 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 6 lines · Nikola Ciprich
Quoted 2 lines
Hmm. And what if you start qemu directly (without using libvirt) with 0.13 command line?
/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104same result...
Should be more like that one with correct image path:
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096
-smp 1,sockets=1,cores=1,threads=1 -name vmwts02 -uuid 1e501300-dc48-11df-a690-00304834195b -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmwts02.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline
-rtc base=localtime -boot c -drive file=/dev/vgshared/vmwts02-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive 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 -netdev user,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:61:01:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:30802 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
--
Gleb.
Quoted 1 line
Should be more like that one with correct image path:
huh, now I got a bit lost :)
I tried running both:/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid 1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev socket,id=char
monitor,path=/var/lib/libvirt/qemu/vmtst04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=14,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:18:04:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:24104 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
and simplified:/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,driv
e=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104 /usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104
where /dev/vgshared/vmtst04-1 is the copy of windows volume from production server. so is this ok?
n.
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 6 lines · Nikola Ciprich
Quoted 1 line
Should be more like that one with correct image path:
huh, now I got a bit lost :)
I tried running both:/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid 1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev socket,id=char
monitor,path=/var/lib/libvirt/qemu/vmtst04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=14,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:18:04:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:24104 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
That one should fail to start.
Quoted 6 lines
and simplified:
/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,driv
e=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104where
/dev/vgshared/vmtst04-1is the copy of windows volume from production server. so is this ok?
No, try to run the one I gave you. Just replace the image file path. I do no have much hope it will work though, but worth trying.
--
Gleb.
Quoted 2 lines
No, try to run the one I gave you. Just replace the image file path. I do no have much hope it will work though, but worth trying.
OK, I tried, I just had to remove the monitor device. Still, it fails the same way... n.
Quoted 8 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 3 lines · Nikola Ciprich
Quoted 2 lines
No, try to run the one I gave you. Just replace the image file path. I do no have much hope it will work though, but worth trying.
OK, I tried, I just had to remove the monitor device. Still, it fails the same way...
According to this:
http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/09aae527-ff6d-4003-9e59-962d73d409ed
such bsod happens because Windows can't access boot device. Your boot device is IDE. Nothing changed in this area from 13 to 14. Are you sure your image was copied correctly and is not corrupted?
--
Gleb.
Quoted 5 lines
According to this:
http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/09aae527-ff6d-4003-9e59-962d73d409ed
such bsod happens because Windows can't access boot device. Your boot device is IDE. Nothing changed in this area from 13 to 14. Are you sure your image was copied correctly and is not corrupted?
definitly. I just tried downgrading qemu-kvm to 0.13.0 and it works again... n.
Quoted 8 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 6 lines · Nikola Ciprich
Quoted 5 lines
According to this:
http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/09aae527-ff6d-4003-9e59-962d73d409ed
such bsod happens because Windows can't access boot device. Your boot device is IDE. Nothing changed in this area from 13 to 14. Are you sure your image was copied correctly and is not corrupted?definitly. I just tried downgrading qemu-kvm to 0.13.0 and it works again...
In this case I am very puzzled :)
--
Gleb.
Quoted 1 line
In this case I am very puzzled :)
well, so am I :)
but at least, I now know there seems to be problem with disk access. I'll ask some of our windows guys to try some failsave mode or something and find out what is going on... I'll report when I know something.
thanks for Your help!
n.
Quoted 8 lines
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 10 lines · Nikola Ciprich
Quoted 1 line
Should be more like that one with correct image path:
huh, now I got a bit lost :)
I tried running both:/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid 1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev socket,id=char
monitor,path=/var/lib/libvirt/qemu/vmtst04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=14,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:18:04:00,bus=pci.0,addr=0x3 -usb -vnc 0.0.0.0:24104 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4and simplified:
/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -rtc base=localtime -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,driv
e=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104/usr/bin/qemu-kvm-M pc-0.13 -enable-kvm -m 4096 -boot c -drive file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -vnc 0.0.0.0:24104
Try appending ,cache=none to the -drive parameter?
Maybe we have a regression with writethrough block devices (a bad idea anyway).
Signature · 2 lines
I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.
Hello Avi,
Quoted 1 line
Try appending ,cache=none to the -drive parameter?
nope, unfortunately same result :(
n.
Quoted 13 lines
Maybe we have a regression with writethrough block devices (a bad idea anyway).
Signature · 7 lines
I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Quoted 5 lines · Nikola Ciprich
Hello Avi,
Quoted 1 line
Try appending ,cache=none to the -drive parameter?
nope, unfortunately same result :(
n.
Does installing the same guest software into a new image work?
Signature · 1 line
error compiling committee.c: too many arguments to function
Hello Avi,
sorry, I've been off for vacation for few days now. I think even "clean" preinstalled guest worked properly, only the one particular production machine didn't. I'll confirm during this week.
n.
Quoted 5 lines
Does installing the same guest software into a new image work?
Signature · 1 line
error compiling committee.c: too many arguments to function
Signature · 13 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
So we've finally confirmed, that on cleanly installed guest, (or previously created image of w2k8) we can't reproduce the problem, only with this one particular image. I'd not worry about it anymore, I'll just have this one reinstalled.
thanks for Your time and sorry for delays
nik
Quoted 25 lines · Nikola Ciprich
Hello Avi,
sorry, I've been off for vacation for few days now. I think even "clean" preinstalled guest worked properly, only the one particular production machine didn't. I'll confirm during this week.
n.Quoted 5 lines
Does installing the same guest software into a new image work?
Signature · 1 line
error compiling committee.c: too many arguments to functionSignature · 13 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------
Signature · 14 lines
------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: [email protected] -------------------------------------