On Thu, May 26, 2011 at 01:50:35PM +0200, Nikola Ciprich wrote: > 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? > On Thu, May 26, 2011 at 01:22:37PM +0300, Gleb Natapov wrote: > > On Thu, May 26, 2011 at 12:20:56PM +0200, Nikola Ciprich wrote: > > > > 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 majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > ------------------------------------- > 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: servis@xxxxxxxxxxx > ------------------------------------- -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
