unable to load viostor driver in w2k3 x86

unable to load viostor driver in w2k3 x86

[Gerrit van der Kolk]

Hello,

I've been trying to use kvm with viostor, but the driver fails to load(Code 10). I'm using version 4.3.0.17241 of the driver.

Info pci @ the qemu console gives: (qemu) info pci
info pci
  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc000 [0xc00f].
      id ""
  Bus  0, device   1, function 2:
    USB controller: PCI device 8086:7020
      IRQ 11.
      BAR4: I/O at 0xc020 [0xc03f].
      id ""
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1234:1111
      BAR0: 32 bit prefetchable memory at 0xf0000000 [0xf0ffffff].
      id ""
  Bus  0, device   3, function 0:
    RAM controller: PCI device 1af4:1002
      IRQ 11.
      BAR0: I/O at 0xc040 [0xc05f].
      id "balloon0"
  Bus  0, device   4, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xffffffffffffffff [0x003e].
      BAR1: 32 bit memory at 0xffffffffffffffff [0x00000ffe].
      id "virtio-disk0"
  Bus  0, device   7, function 0:
    Ethernet controller: PCI device 1af4:1000
      IRQ 5.
      BAR0: I/O at 0xc0c0 [0xc0df].
      BAR1: 32 bit memory at 0xf1001000 [0xf1001fff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id "net0"

Windows detects the controller and finds the driver automatically. But after this there is the yellow exclamation mark with the code 10.
I'm using libvirt with kvm. The configuration is:

<domain type='kvm'>
  <name>base</name>
  <uuid>d6d143d6-387f-8252-f7b0-419a76d4c609</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type arch='x86_64' machine='fedora-13'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu match='exact'>
    <model>core2duo</model>
    <feature policy='force' name='x2apic'/>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/libvirt/images/base.qcow2'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/gvdkolk/Downloads/NetKVM-and-viostor.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' unit='0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/test.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:78:dd:89'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </interface>
    <input type='tablet' bus='usb'>
    </input>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
    <video>
      <model type='vga' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
  </devices>
  <seclabel type='dynamic' model='selinux'/>
</domain>

Does anyone have any idea what is going on here?

Regards,

Gerrit van der Kolk

The information contained in this communication is confidential, intended solely for the use of the individual or entity to whom it is addressed and may be legally privileged and protected by professional secrecy. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This email does not constitute any commitment from Cordys Holding BV or any of its subsidiaries except when expressly agreed in a written agreement between the intended recipient and Cordys Holding BV or its subsidiaries. Cordys is neither liable for the proper
  and complete transmission of the information contained in this communication nor for any delay in its receipt. Cordys does not guarantee that the integrity of this communication has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies.

RE: unable to load viostor driver in w2k3 x86

[Gerrit van der Kolk]

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.

Regards,

Gerrit

-----Original Message-----
From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On Behalf Of Gerrit van der Kolk
Sent: Monday, August 02, 2010 3:44 PM
To: 'kvm@vger.kernel.org'
Subject: unable to load viostor driver in w2k3 x86

Hello,

I've been trying to use kvm with viostor, but the driver fails to load(Code 10). I'm using version 4.3.0.17241 of the driver.

Info pci @ the qemu console gives: (qemu) info pci
info pci
  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc000 [0xc00f].
      id ""
  Bus  0, device   1, function 2:
    USB controller: PCI device 8086:7020
      IRQ 11.
      BAR4: I/O at 0xc020 [0xc03f].
      id ""
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1234:1111
      BAR0: 32 bit prefetchable memory at 0xf0000000 [0xf0ffffff].
      id ""
  Bus  0, device   3, function 0:
    RAM controller: PCI device 1af4:1002
      IRQ 11.
      BAR0: I/O at 0xc040 [0xc05f].
      id "balloon0"
  Bus  0, device   4, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xffffffffffffffff [0x003e].
      BAR1: 32 bit memory at 0xffffffffffffffff [0x00000ffe].
      id "virtio-disk0"
  Bus  0, device   7, function 0:
    Ethernet controller: PCI device 1af4:1000
      IRQ 5.
      BAR0: I/O at 0xc0c0 [0xc0df].
      BAR1: 32 bit memory at 0xf1001000 [0xf1001fff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id "net0"

Windows detects the controller and finds the driver automatically. But after this there is the yellow exclamation mark with the code 10.
I'm using libvirt with kvm. The configuration is:

<domain type='kvm'>
  <name>base</name>
  <uuid>d6d143d6-387f-8252-f7b0-419a76d4c609</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type arch='x86_64' machine='fedora-13'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu match='exact'>
    <model>core2duo</model>
    <feature policy='force' name='x2apic'/>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/libvirt/images/base.qcow2'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/gvdkolk/Downloads/NetKVM-and-viostor.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' unit='0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/test.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:78:dd:89'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </interface>
    <input type='tablet' bus='usb'>
    </input>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
    <video>
      <model type='vga' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
  </devices>
  <seclabel type='dynamic' model='selinux'/>
</domain>

Does anyone have any idea what is going on here?

Regards,

Gerrit van der Kolk

The information contained in this communication is confidential, intended solely for the use of the individual or entity to whom it is addressed and may be legally privileged and protected by professional secrecy. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This email does not constitute any commitment from Cordys Holding BV or any of its subsidiaries except when expressly agreed in a written agreement between the intended recipient and Cordys Holding BV or its subsidiaries. Cordys is neither liable for the proper
  and complete transmission of the information contained in this communication nor for any delay in its receipt. Cordys does not guarantee that the integrity of this communication has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: unable to load viostor driver in w2k3 x86

[Vadim Rozenfeld]

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.
  
> Regards,
> 
> Gerrit
> 
> -----Original Message-----
> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On Behalf Of Gerrit van der Kolk
> Sent: Monday, August 02, 2010 3:44 PM
> To: 'kvm@vger.kernel.org'
> Subject: unable to load viostor driver in w2k3 x86
> 
> Hello,
> 
> I've been trying to use kvm with viostor, but the driver fails to load(Code 10). I'm using version 4.3.0.17241 of the driver.
> 
> Info pci @ the qemu console gives: (qemu) info pci
> info pci
>   Bus  0, device   0, function 0:
>     Host bridge: PCI device 8086:1237
>       id ""
>   Bus  0, device   1, function 0:
>     ISA bridge: PCI device 8086:7000
>       id ""
>   Bus  0, device   1, function 1:
>     IDE controller: PCI device 8086:7010
>       BAR4: I/O at 0xc000 [0xc00f].
>       id ""
>   Bus  0, device   1, function 2:
>     USB controller: PCI device 8086:7020
>       IRQ 11.
>       BAR4: I/O at 0xc020 [0xc03f].
>       id ""
>   Bus  0, device   1, function 3:
>     Bridge: PCI device 8086:7113
>       IRQ 9.
>       id ""
>   Bus  0, device   2, function 0:
>     VGA controller: PCI device 1234:1111
>       BAR0: 32 bit prefetchable memory at 0xf0000000 [0xf0ffffff].
>       id ""
>   Bus  0, device   3, function 0:
>     RAM controller: PCI device 1af4:1002
>       IRQ 11.
>       BAR0: I/O at 0xc040 [0xc05f].
>       id "balloon0"
>   Bus  0, device   4, function 0:
>     SCSI controller: PCI device 1af4:1001
>       IRQ 10.
>       BAR0: I/O at 0xffffffffffffffff [0x003e].
>       BAR1: 32 bit memory at 0xffffffffffffffff [0x00000ffe].
>       id "virtio-disk0"
>   Bus  0, device   7, function 0:
>     Ethernet controller: PCI device 1af4:1000
>       IRQ 5.
>       BAR0: I/O at 0xc0c0 [0xc0df].
>       BAR1: 32 bit memory at 0xf1001000 [0xf1001fff].
>       BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
>       id "net0"
> 
> Windows detects the controller and finds the driver automatically. But after this there is the yellow exclamation mark with the code 10.
> I'm using libvirt with kvm. The configuration is:
> 
> <domain type='kvm'>
>   <name>base</name>
>   <uuid>d6d143d6-387f-8252-f7b0-419a76d4c609</uuid>
>   <memory>2097152</memory>
>   <currentMemory>2097152</currentMemory>
>   <vcpu>2</vcpu>
>   <os>
>     <type arch='x86_64' machine='fedora-13'>hvm</type>
>     <boot dev='cdrom'/>
>     <boot dev='hd'/>
>   </os>
>   <features>
>     <acpi/>
>     <apic/>
>     <pae/>
>   </features>
>   <cpu match='exact'>
>     <model>core2duo</model>
>     <feature policy='force' name='x2apic'/>
>   </cpu>
>   <clock offset='localtime'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>restart</on_crash>
>   <devices>
>     <emulator>/usr/bin/qemu-kvm</emulator>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='qcow2' cache='none'/>
>       <source file='/var/lib/libvirt/images/base.qcow2'/>
>       <target dev='hda' bus='ide'/>
>       <address type='drive' controller='0' bus='0' unit='0'/>
>     </disk>
>     <disk type='file' device='cdrom'>
>       <driver name='qemu' type='raw'/>
>       <source file='/home/gvdkolk/Downloads/NetKVM-and-viostor.iso'/>
>       <target dev='hdc' bus='ide'/>
>       <readonly/>
>       <address type='drive' controller='0' bus='1' unit='0'/>
>     </disk>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='raw'/>
>       <source file='/var/lib/libvirt/images/test.img'/>
>       <target dev='vda' bus='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>     </disk>
>     <controller type='ide' index='0'>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>     </controller>
>     <interface type='bridge'>
>       <mac address='52:54:00:78:dd:89'/>
>       <source bridge='br0'/>
>       <target dev='vnet0'/>
>       <model type='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
>     </interface>
>     <input type='tablet' bus='usb'>
>     </input>
>     <input type='mouse' bus='ps2'/>
>     <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
>     <video>
>       <model type='vga' vram='9216' heads='1'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>     </video>
>   </devices>
>   <seclabel type='dynamic' model='selinux'/>
> </domain>
> 
> Does anyone have any idea what is going on here?
> 
> Regards,
> 
> Gerrit van der Kolk
> 
> The information contained in this communication is confidential, intended solely for the use of the individual or entity to whom it is addressed and may be legally privileged and protected by professional secrecy. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This email does not constitute any commitment from Cordys Holding BV or any of its subsidiaries except when expressly agreed in a written agreement between the intended recipient and Cordys Holding BV or its subsidiaries. Cordys is neither liable for the prop
 er and complete transmission of the information contained in this communication nor for any delay in its receipt. Cordys does not guarantee that the integrity of this communication has been!
  m!
>  aintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: unable to load viostor driver in w2k3 x86

[Gerrit van der Kolk]

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

Regards,

Gerrit


> Regards,
>
> Gerrit
>
> -----Original Message-----
> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On Behalf Of Gerrit van der Kolk
> Sent: Monday, August 02, 2010 3:44 PM
> To: 'kvm@vger.kernel.org'
> Subject: unable to load viostor driver in w2k3 x86
>
> Hello,
>
> I've been trying to use kvm with viostor, but the driver fails to load(Code 10). I'm using version 4.3.0.17241 of the driver.
>
> Info pci @ the qemu console gives: (qemu) info pci
> info pci
>   Bus  0, device   0, function 0:
>     Host bridge: PCI device 8086:1237
>       id ""
>   Bus  0, device   1, function 0:
>     ISA bridge: PCI device 8086:7000
>       id ""
>   Bus  0, device   1, function 1:
>     IDE controller: PCI device 8086:7010
>       BAR4: I/O at 0xc000 [0xc00f].
>       id ""
>   Bus  0, device   1, function 2:
>     USB controller: PCI device 8086:7020
>       IRQ 11.
>       BAR4: I/O at 0xc020 [0xc03f].
>       id ""
>   Bus  0, device   1, function 3:
>     Bridge: PCI device 8086:7113
>       IRQ 9.
>       id ""
>   Bus  0, device   2, function 0:
>     VGA controller: PCI device 1234:1111
>       BAR0: 32 bit prefetchable memory at 0xf0000000 [0xf0ffffff].
>       id ""
>   Bus  0, device   3, function 0:
>     RAM controller: PCI device 1af4:1002
>       IRQ 11.
>       BAR0: I/O at 0xc040 [0xc05f].
>       id "balloon0"
>   Bus  0, device   4, function 0:
>     SCSI controller: PCI device 1af4:1001
>       IRQ 10.
>       BAR0: I/O at 0xffffffffffffffff [0x003e].
>       BAR1: 32 bit memory at 0xffffffffffffffff [0x00000ffe].
>       id "virtio-disk0"
>   Bus  0, device   7, function 0:
>     Ethernet controller: PCI device 1af4:1000
>       IRQ 5.
>       BAR0: I/O at 0xc0c0 [0xc0df].
>       BAR1: 32 bit memory at 0xf1001000 [0xf1001fff].
>       BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
>       id "net0"
>
> Windows detects the controller and finds the driver automatically. But after this there is the yellow exclamation mark with the code 10.
> I'm using libvirt with kvm. The configuration is:
>
> <domain type='kvm'>
>   <name>base</name>
>   <uuid>d6d143d6-387f-8252-f7b0-419a76d4c609</uuid>
>   <memory>2097152</memory>
>   <currentMemory>2097152</currentMemory>
>   <vcpu>2</vcpu>
>   <os>
>     <type arch='x86_64' machine='fedora-13'>hvm</type>
>     <boot dev='cdrom'/>
>     <boot dev='hd'/>
>   </os>
>   <features>
>     <acpi/>
>     <apic/>
>     <pae/>
>   </features>
>   <cpu match='exact'>
>     <model>core2duo</model>
>     <feature policy='force' name='x2apic'/>
>   </cpu>
>   <clock offset='localtime'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>restart</on_crash>
>   <devices>
>     <emulator>/usr/bin/qemu-kvm</emulator>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='qcow2' cache='none'/>
>       <source file='/var/lib/libvirt/images/base.qcow2'/>
>       <target dev='hda' bus='ide'/>
>       <address type='drive' controller='0' bus='0' unit='0'/>
>     </disk>
>     <disk type='file' device='cdrom'>
>       <driver name='qemu' type='raw'/>
>       <source file='/home/gvdkolk/Downloads/NetKVM-and-viostor.iso'/>
>       <target dev='hdc' bus='ide'/>
>       <readonly/>
>       <address type='drive' controller='0' bus='1' unit='0'/>
>     </disk>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='raw'/>
>       <source file='/var/lib/libvirt/images/test.img'/>
>       <target dev='vda' bus='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>     </disk>
>     <controller type='ide' index='0'>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>     </controller>
>     <interface type='bridge'>
>       <mac address='52:54:00:78:dd:89'/>
>       <source bridge='br0'/>
>       <target dev='vnet0'/>
>       <model type='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
>     </interface>
>     <input type='tablet' bus='usb'>
>     </input>
>     <input type='mouse' bus='ps2'/>
>     <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
>     <video>
>       <model type='vga' vram='9216' heads='1'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>     </video>
>   </devices>
>   <seclabel type='dynamic' model='selinux'/>
> </domain>
>
> Does anyone have any idea what is going on here?
>
> Regards,
>
> Gerrit van der Kolk
>
> The information contained in this communication is confidential, intended solely for the use of the individual or entity to whom it is addressed and may be legally privileged and protected by professional secrecy. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This email does not constitute any commitment from Cordys Holding BV or any of its subsidiaries except when expressly agreed in a written agreement between the intended recipient and Cordys Holding BV or its subsidiaries. Cordys is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Cordys does not guarantee that the integrity of this communication has been!
  m!
>  aintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: unable to load viostor driver in w2k3 x86

[Jes Sorensen]

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