2010/8/1 Justin M. Forbes <[email protected]>: > 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/
Are these drivers unsigned/selfsigned/signed? Eg. will Windows 2008/2008R2 accept them? Thanks, Kenni _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
