> -----Original Message-----
> From: guan qin [mailto:qinguan0...@gmail.com]
> Sent: Saturday, April 23, 2011 8:46 PM
> To: e1000-de...@lists.sf.net
> Subject: [E1000-devel] VM can not get ip and with error "igbvf
> 0000:00:04.0: Unable to allocate interrupt, Error: -1 failed
> 
> Hi,
> 
> I want to use SRIOV under debian 6.0.1a ,and I had installed the drive
> igb
> 2.4.13 and igbvf 1.0.7。
> I boot the VM by virsh tool :virsh create sriov.xml ,just create a
> ubuntu10.04 VM.
> when I enter the VM ,I can't access to the network.
> If I use "sudo ifconfig eth0 192.168.1.181", I always  got the message
> "SIOCSIFFLAGS:Operation not permitted."

It looks to me like you don't have suitable account permissions to perform 
network configuration.

- Greg

> according the message "Unable to allocate interrupt, Error: -1 " from
> dmesg in VM, I see that the message coming from a function:*
> igbvf_request_irq*, failed *initialize interrupts *. But I didn't  know
> how to solve it ?
> (http://tomoyo.sourceforge.jp/cgi-
> bin/lxr/source/drivers/net/igbvf/netdev.c:
> *line 1074*)
> 
> besides, I  assigned a VF to the VM which HWaddr aa:2a:91:5a:eb:c8, but in
> the VM the HWaddr randomly change into onother mac such  as
> "b2:c1:6e:ad:67:db"
> It also puzzled me many days.
> can you help me ?
> 
> thanks,
> qinguan
> 
> *some dmesg info  in the VM:*
> JBD:barrier-based sync failed on vda1-8 - disabling barriers igbvf
> 0000:00:04.0:Unable to allocate interrupt,Error:-1
> 
> *some dmesg info in the host:*
> pci-stub 0000:02:10.1 enabling device(0000 -> 0002) assign device 0:2:10.1
> *
> /var/log/libvirt/qemu/testnew_srion.log:*
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -
> smp 1,sockets=1,cores=1,threads=1 -name testnew_sriov -uuid ea040095-01e4-
> 61cb-bb79-10b92712eb4f -nodefaults -chardev
> socket,id=monitor,path=/var/lib/libvirt/qemu/testnew_sriov.monitor,server,
> nowait
> -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive
> file=/home/qinguan/exp/ubuntu_1.img,if=none,id=drive-virtio-
> disk0,boot=on,format=raw
> -device
> virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0
> -usb -device usb-mouse,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device
> pci-assign,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x4 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
> 
> *sriov.xml:*
> 
> <domain type='kvm'>
>     <name>testnew_sriov</name>
>     <description>just test using sriov!</description>
>     <os>
>         <type>hvm</type>
>         <boot dev='hd'/>
>     </os>
>     <memory>524288</memory>
>     <currentMemory>524288</currentMemory>
>     <on_poweroff>destroy</on_poweroff>
>     <on_reboot>restart</on_reboot>
>     <on_crash>restart</on_crash>
> 
>     <features><pae/><acpi/><apic/></features>
>     <clock offset='utc'/>
>     <devices>
>         <input type='mouse' bus='usb'/>
>         <disk type='file' device='disk'>
>             <source file='/home/qinguan/exp/ubuntu_1.img'/>
>             <target dev='hda' bus='virtio'/>
>         </disk>
>         <emulator>/usr/bin/kvm</emulator>
>         <graphics type='vnc' port='-1'/>
>         <hostdev mode='subsystem' type='pci' managed='yes'>
>             <source>
>                 <address bus='0x2' slot='0x10' function='0x1'/>
>             </source>
>             <boot order='1'/>
>         </hostdev>
>     </devices>
> </domain>
> 
> 
> *more system information please look into the attachment,thanks.*

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been 
demonstrated beyond question. Learn why your peers are replacing JEE 
containers with lightweight application servers - and what you can gain 
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to