Control: severity -1 normal Control: tags -1 + moreinfo 08.10.2012 15:20, Josquin DEHAENE wrote: > Package: qemu-kvm > Version: 1.1.2+dfsg-2~bpo60+1 > Severity: important > > Hi, > > We have different kind of VMs running on this host. All of them boot normaly > after update to 1.1.2 expect Win2k8 64b wich make BSOD on 0x00..07E error. > Note that Win2k8 srv 32b boot normaly. > Downgrade to 1.0.0 make VMs to boot normaly.
I don't have access to Win2K8 installation media, so can't test it. > See attach file for detail VM definition. This VM definition does not help me, unfortunately. Qemu/kvm does not understand xml. It will help if you can show the kvm command line used instead. However after a brief look at the provided .xml (with my limited understanding of it) I noticed that there's no particular qemu/kvm machine version specified in there, -- and as far as I understand, it means that when you upgrade, it is okay to present slightly different virtual devices configuration than was in previous versions, -- qemu defaults to "current" hardware version without any specific value. In particular, it might present slightly different variants of built-in devices, with slightly different properties. The option/argument in question is -machine (or -M), which is, by default, "pc" which means "the latest PC", or it can be "pc-1.0" for example, to mean the hardware which was emulated by qemu-kvm-1.0, etc. With this in mind, it is unrealistic for qemu to provide compatible virtual hardware across versions for every guest OS variant possible, and it is not realistic to ask qemu why a particular OS or driver version does not work with one variant of qemu hardware and does not work with another. We don't control windows drivers. Another thing to have in mind is that virtual ide controller, while works, is quite a bit slow, and is not recommended for production use. There is a native "device", virtio-block, with corresponding guest driver for windows available, and that one will work across upgrades - at least this is something we can control. Having said that, I'm downgrading severity of this bugreport from "important" to "normal" while I'm waiting for the qemu/kvm command line I asked above - and if my suspicious is right, and you don't specify -M/-machine of any particular version, that will be a wontfix. Thanks, /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
