[Bug 741706] Re: could not add physical hardware (ethernet card)

2011-05-23 Thread Launchpad Bug Tracker
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]

** Changed in: libvirt (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/741706

Title:
  could not add physical hardware (ethernet card)

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 741706] Re: could not add physical hardware (ethernet card)

2011-03-24 Thread Serge Hallyn
> I tried it with 'intel_iommu=on' kernel option but with the same result.
> It does not work.

Drat.  Thanks.

> Does physical hardware assignment for network cards really work under
> KVM?

I've never had hardware to be able to properly test this.  As soon as I
did, I was planning to test using:

http://fedoraproject.org/wiki/Features/SR-IOV#How_To_Test

Can you verify that your NIC is in fact supported, and that you followed
the steps there (in particular using 'max_vfs=7' when loading the igb
module)?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/741706

Title:
  could not add physical hardware (ethernet card)

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 741706] Re: could not add physical hardware (ethernet card)

2011-03-24 Thread Michael Zoet
Hi Serge,

I tried it with 'intel_iommu=on' kernel option but with the same result.
It does not work.

Does physical hardware assignment for network cards really work under
KVM?

Below my complete dmesg output shortly after I tried to start a VM with
a physical hardware assignment.


Bye,

Michael

** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/741706/+attachment/1936988/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/741706

Title:
  could not add physical hardware (ethernet card)

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 741706] Re: could not add physical hardware (ethernet card)

2011-03-24 Thread Serge Hallyn
Thanks for reporting this bug and helping to make Ubuntu better.

I notice the error messages include:

No IOMMU found.

Did you boot with 'intel_iommu=on' in the boot arguments?  If not,
please add that and try again, and let us know whether that worked.

** Changed in: libvirt (Ubuntu)
   Status: New => Incomplete

** Changed in: libvirt (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/741706

Title:
  could not add physical hardware (ethernet card)

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 741706] Re: could not add physical hardware (ethernet card)

2011-03-24 Thread Michael Zoet
Forgot the corresponding dmesg entries:

[ 1921.436178] igb :0b:00.1: PCI INT B disabled
[ 1921.436234] pci-stub :0b:00.1: claimed by stub
[ 1921.437855] device vnet2 entered promiscuous mode
[ 1921.439643] virbr_man: port 2(vnet2) entering forwarding state
[ 1921.441193] device vnet3 entered promiscuous mode
[ 1921.442963] virbr1: topology change detected, propagating
[ 1921.442967] virbr1: port 1(vnet3) entering forwarding state
[ 1921.467693] kvm_vm_ioctl_deassign_device: device hasn't been assigned 
before, so cannot be deassigned
[ 1921.672335] virbr_man: port 2(vnet2) entering disabled state
[ 1921.750310] device vnet2 left promiscuous mode
[ 1921.750314] virbr_man: port 2(vnet2) entering disabled state
[ 1921.991886] virbr1: port 1(vnet3) entering disabled state
[ 1922.110162] device vnet3 left promiscuous mode
[ 1922.110167] virbr1: port 1(vnet3) entering disabled state
[ 1951.656102] igb :0b:00.1: PCI INT B -> GSI 39 (level, low) -> IRQ 39
[ 1951.656135] igb :0b:00.1: setting latency timer to 64
[ 1951.657425] igb :0b:00.1: irq 128 for MSI/MSI-X
[ 1951.657428] igb :0b:00.1: irq 129 for MSI/MSI-X
[ 1951.657432] igb :0b:00.1: irq 130 for MSI/MSI-X
[ 1951.657435] igb :0b:00.1: irq 131 for MSI/MSI-X
[ 1951.657438] igb :0b:00.1: irq 132 for MSI/MSI-X
[ 1951.657441] igb :0b:00.1: irq 133 for MSI/MSI-X
[ 1951.657444] igb :0b:00.1: irq 134 for MSI/MSI-X
[ 1951.657447] igb :0b:00.1: irq 135 for MSI/MSI-X
[ 1951.657450] igb :0b:00.1: irq 136 for MSI/MSI-X
[ 1951.657507] igb :0b:00.1: 0 vfs allocated
[ 1951.888296] igb :0b:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 1951.888301] igb :0b:00.1: eth9: (PCIe:2.5Gb/s:Width x4) 00:1b:21:7b:ff:8d
[ 1951.888385] igb :0b:00.1: eth9: PBA No: e66339-003
[ 1951.888388] igb :0b:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/741706

Title:
  could not add physical hardware (ethernet card)

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs