On 08/04/10 16:04, Gerrit van der Kolk wrote: > On Wed, 2010-08-04 at 14:53 +0200, Gerrit van der Kolk wrote: >> I managed to get libvirtd out of the loop. I'm starting the vm with: >> qemu-kvm -S -M fedora-13 -enable-kvm -m 2048 -smp 2,sockets=1,cores=2,threads=1 -name test -uuid 5ffc03bf-3562-1c90-9543-a64b2416a4a1 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/test.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=localtime -boot dc -drive file=/var/lib/libvirt/images/test-1.img,if=ide,boot=on,format=raw -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vga std -drive file=/var/lib/libvirt/images/test-3.img,if=virtio,format=raw >> >> host os is a fully updated fedora13 system with kernel 2.6.33.6-147.2.4.fc13.x86_64. Guestos is windows 2003 SP2 x86 with miniport hotfix KB932755 applied. Didn't solve the problem either. >> >> Anyone out there where the virtio storage does work with windows? I'm a little out of ideas at the moment. >> > Hi, Gerrit. > > Code 10 usually indicates a problem in FindAdapter routine. > It could be one of two reasons for that: > - invalid HW resources reported to guest; > - version mismatch between viostor driver and qemu. > Best regards, > Vadim. > > Hi Vadim, > > I understand, but how do I find out what HW resources are reported and how do I find out what version of the driver I should use on which qemu version? I have qemu 0.12.3 Geert, Did you check what it says in the device manager in windows? If this is during install, you could try a test install using IDE for the root drive and just use viostor for the second drive, then check in the device manager what is there. Cheers, Jes -- 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
