I've had a Windows XP KVM running through several fedora upgrades and updates, and I just tried starting it for the first time since getting the libvirt-0.8.2-1.fc13.x86_64 update, and now it bluescreens.
I had been running the redhat virtio disk and network drivers inside the KVM, have they gone incompatible on me? (I guess I could try switching the KVM back to IDE emulation and see if it starts working).
On 01/08/10 15:40, Tom Horsley wrote:
I've had a Windows XP KVM running through several fedora upgrades and updates, and I just tried starting it for the first time since getting the libvirt-0.8.2-1.fc13.x86_64 update, and now it bluescreens.
Ah, so it's not just me then...
I had been running the redhat virtio disk and network drivers inside the KVM, have they gone incompatible on me? (I guess I could try switching the KVM back to IDE emulation and see if it starts working).
It's virtio I suspect. That was certainly what I found, that switching back to IDE fixed it.
I thought I had ruled out all likely changes (ie updates to kernel and/or qemu) though so had pretty much decided that Windows had just decided to start objecting to the driver for some reason.
It's only booting that seems to be a problem - if you hot add a virtio disk while Windows is running then it can access it just fine.
Tom
On Sun, 2010-08-01 at 15:54 +0100, Tom Hughes wrote:
On 01/08/10 15:40, Tom Horsley wrote:
I've had a Windows XP KVM running through several fedora upgrades and updates, and I just tried starting it for the first time since getting the libvirt-0.8.2-1.fc13.x86_64 update, and now it bluescreens.
Ah, so it's not just me then...
I had been running the redhat virtio disk and network drivers inside the KVM, have they gone incompatible on me? (I guess I could try switching the KVM back to IDE emulation and see if it starts working).
It's virtio I suspect. That was certainly what I found, that switching back to IDE fixed it.
I thought I had ruled out all likely changes (ie updates to kernel and/or qemu) though so had pretty much decided that Windows had just decided to start objecting to the driver for some reason.
It's only booting that seems to be a problem - if you hot add a virtio disk while Windows is running then it can access it just fine.
Are you using the Fedora virtio-win drivers from:
http://alt.fedoraproject.org/pub/alt/virtio-win/13/
Jusitn
On 01/08/10 17:49, Justin M. Forbes wrote:
On Sun, 2010-08-01 at 15:54 +0100, Tom Hughes wrote:
It's virtio I suspect. That was certainly what I found, that switching back to IDE fixed it.
I thought I had ruled out all likely changes (ie updates to kernel and/or qemu) though so had pretty much decided that Windows had just decided to start objecting to the driver for some reason.
It's only booting that seems to be a problem - if you hot add a virtio disk while Windows is running then it can access it just fine.
Are you using the Fedora virtio-win drivers from:
No I think mine are older than that. I did Google but couldn't turn up anything newer than what I already had.
I'll give those a go tomorrow.
Tom
On 01/08/10 17:51, Tom Hughes wrote:
On 01/08/10 17:49, Justin M. Forbes wrote:
Are you using the Fedora virtio-win drivers from:
No I think mine are older than that. I did Google but couldn't turn up anything newer than what I already had.
Well what I actually have is 5.3.0.17241 dated 10/10/2009 and it doesn't look like that ISO is any newer, or at least Windows is saying it can't find any drivers that are a better match when searching that ISO.
I am running XP64 though, and the storage drivers on that ISO don't seem to include an amd64 build in the WXp folder (unlike the network drivers) so I had to use the Wnet ones which I believe are Windows Server 2003 which is basically the same as XP64 anyway.
Tom
On Sun, 01 Aug 2010 11:49:18 -0500 Justin M. Forbes wrote:
Are you using the Fedora virtio-win drivers from:
I'll have to dig the version up from inside the KVM if I get things working again, but I'm pretty sure they were from a redhat site, not a fedora site, and they are fairly old these days.
On Sun, 1 Aug 2010 13:13:02 -0400 Tom Horsley wrote:
I'll have to dig the version up from inside the KVM if I get things working again
OK, switched to IDE and was able to boot. The virtio driver I was using identifies itself as:
Redhat VirtIO SCSI driver 5.0.1.1 9/24/2009
Unfortunately Windows also wants me to reactivate now, but I'll try the new virtio drivers before I do anything that drastic...
2010/8/1 Justin M. Forbes jmforbes@linuxtx.org:
On Sun, 2010-08-01 at 15:54 +0100, Tom Hughes wrote:
On 01/08/10 15:40, Tom Horsley wrote:
I've had a Windows XP KVM running through several fedora upgrades and updates, and I just tried starting it for the first time since getting the libvirt-0.8.2-1.fc13.x86_64 update, and now it bluescreens.
Ah, so it's not just me then...
I had been running the redhat virtio disk and network drivers inside the KVM, have they gone incompatible on me? (I guess I could try switching the KVM back to IDE emulation and see if it starts working).
It's virtio I suspect. That was certainly what I found, that switching back to IDE fixed it.
I thought I had ruled out all likely changes (ie updates to kernel and/or qemu) though so had pretty much decided that Windows had just decided to start objecting to the driver for some reason.
It's only booting that seems to be a problem - if you hot add a virtio disk while Windows is running then it can access it just fine.
Are you using the Fedora virtio-win drivers from:
Are these drivers unsigned/selfsigned/signed? Eg. will Windows 2008/2008R2 accept them?
Thanks, Kenni
On 08/01/2010 10:40 AM, Tom Horsley wrote:
I've had a Windows XP KVM running through several fedora upgrades and updates, and I just tried starting it for the first time since getting the libvirt-0.8.2-1.fc13.x86_64 update, and now it bluescreens.
Only updated libvirt, and not qemu-*? Can you provide /var/log/libvirt/qemu/$VMNAME.log, particularly interested in the libvirt-0.7* generated cmdline vs. the libvirt-0.8* generated command line.
Actually, best to just open a bug report and we can follow up there.
- Cole
I had been running the redhat virtio disk and network drivers inside the KVM, have they gone incompatible on me? (I guess I could try switching the KVM back to IDE emulation and see if it starts working). _______________________________________________ virt mailing list virt@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
-
Cole Robinson -
Justin Forbes -
Kenni Lund -
Tom Horsley -
Tom Hughes