[libvirt] Multpile network interfaces have same MAC address
I remember seeing this problem before, but I can't remember what the resolution was, nor can I find a discussion of the issue in the list archives or Bugzilla. I've had my setup working for a while now, on both Fedora 8 and Fedora 10. Now I'm trying to get it to work with CentOS 5 and running into an old bug. My guest VM has multiple virtual network interfaces, with the MAC address defined in the XML file used to define the VM. However, I'm seeing each network interface getting the same MAC addrss (the last one defined in the XML file) on all if the interfaces when I run ifconfig in the guest. Was there a workaround for this, or do I need to upgrade libvirt? CentOS 5.2 is what I'm working with; they haven't released 5.3 yet so I don't know if that will have a newer version. # rpm -qa libvirt libvirt-0.3.3-7.el5 # virsh version Compiled against library: libvir 0.3.3 Using library: libvir 0.3.3 Using API: QEMU 0.3.3 Running hypervisor: QEMU 0.9.1 - David
On Tue, Feb 24, 2009 at 01:29:41PM -0800, David Mueller wrote:
I remember seeing this problem before, but I can't remember what the resolution was, nor can I find a discussion of the issue in the list archives or Bugzilla.
I've had my setup working for a while now, on both Fedora 8 and Fedora 10. Now I'm trying to get it to work with CentOS 5 and running into an old bug. My guest VM has multiple virtual network interfaces, with the MAC address defined in the XML file used to define the VM. However, I'm seeing each network interface getting the same MAC addrss (the last one defined in the XML file) on all if the interfaces when I run ifconfig in the guest.
Was there a workaround for this, or do I need to upgrade libvirt? CentOS 5.2 is what I'm working with; they haven't released 5.3 yet so I don't know if that will have a newer version.
Last time I saw this was with QEMU and the rtl8139 nic, where there was a bug setting up the MMIO space, so all NICs were reading their mac from the first NIC's region instead of their own. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Wed, Feb 25, 2009 at 3:21 AM, Daniel P. Berrange <berrange@redhat.com> wrote:
Last time I saw this was with QEMU and the rtl8139 nic, where there was a bug setting up the MMIO space, so all NICs were reading their mac from the first NIC's region instead of their own.
I think I understand this, but I'm not sure it helps me fix the problem. Is this something that will require an updated libvirt or qemu or is there a simple change to make somewhere? CentOS 5.3 is running a bit behind and I'm not sure where to check to see what the versions of these packages are in RHEL 5.3 to know if I can just wait for the updated CentOS or should roll my own updated package. - David
On Feb 25, 2009, at 7:29 AM, David Mueller wrote:
On Wed, Feb 25, 2009 at 3:21 AM, Daniel P. Berrange <berrange@redhat.com
wrote: Last time I saw this was with QEMU and the rtl8139 nic, where there was a bug setting up the MMIO space, so all NICs were reading their mac from the first NIC's region instead of their own.
I think I understand this, but I'm not sure it helps me fix the problem. Is this something that will require an updated libvirt or qemu or is there a simple change to make somewhere? CentOS 5.3 is running a bit behind and I'm not sure where to check to see what the versions of these packages are in RHEL 5.3 to know if I can just wait for the updated CentOS or should roll my own updated package.
To follow up, I just found the bug that dealt with the problem: https://bugzilla.redhat.com/show_bug.cgi?id=247641 So it looks like the fix is an updated version of qemu? - David
On Wed, 25 Feb 2009, Daniel P. Berrange wrote:
On Tue, Feb 24, 2009 at 01:29:41PM -0800, David Mueller wrote:
I remember seeing this problem before, but I can't remember what the resolution was, nor can I find a discussion of the issue in the list archives or Bugzilla.
I've had my setup working for a while now, on both Fedora 8 and Fedora 10. Now I'm trying to get it to work with CentOS 5 and running into an old bug. My guest VM has multiple virtual network interfaces, with the MAC address defined in the XML file used to define the VM. However, I'm seeing each network interface getting the same MAC addrss (the last one defined in the XML file) on all if the interfaces when I run ifconfig in the guest.
Was there a workaround for this, or do I need to upgrade libvirt? CentOS 5.2 is what I'm working with; they haven't released 5.3 yet so I don't know if that will have a newer version.
Last time I saw this was with QEMU and the rtl8139 nic, where there was a bug setting up the MMIO space, so all NICs were reading their mac from the first NIC's region instead of their own.
Does anyone know if the patch for this is going to be rolled into RHEL5 at some point? I'm still having this problem with CentOS 5.3. For reference, I found the original Fedora 7 bug as well as filed one for CentOS: https://bugzilla.redhat.com/show_bug.cgi?id=247641 http://bugs.centos.org/bug_view_page.php?bug_id=3466 Thanks, David
On Wed, Apr 15, 2009 at 10:39:42AM -0700, David Mueller wrote:
On Wed, 25 Feb 2009, Daniel P. Berrange wrote:
On Tue, Feb 24, 2009 at 01:29:41PM -0800, David Mueller wrote:
I remember seeing this problem before, but I can't remember what the resolution was, nor can I find a discussion of the issue in the list archives or Bugzilla.
I've had my setup working for a while now, on both Fedora 8 and Fedora 10. Now I'm trying to get it to work with CentOS 5 and running into an old bug. My guest VM has multiple virtual network interfaces, with the MAC address defined in the XML file used to define the VM. However, I'm seeing each network interface getting the same MAC addrss (the last one defined in the XML file) on all if the interfaces when I run ifconfig in the guest.
Was there a workaround for this, or do I need to upgrade libvirt? CentOS 5.2 is what I'm working with; they haven't released 5.3 yet so I don't know if that will have a newer version.
Last time I saw this was with QEMU and the rtl8139 nic, where there was a bug setting up the MMIO space, so all NICs were reading their mac from the first NIC's region instead of their own.
Does anyone know if the patch for this is going to be rolled into RHEL5 at some point? I'm still having this problem with CentOS 5.3. For reference, I found the original Fedora 7 bug as well as filed one for CentOS:
We don't ship QEMU or KVM in RHEL yet, so there's nothing to fix in RHEL for QEMU/KVM, and I don't believe Xen suffers from it, since it uses a different way of handling MMIO memory registration. Whereever that CentOS user got their qemu & kvm RPMs from, they weren't a standard part of RHEL & those versions are absolutely ancient too. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Thu, 16 Apr 2009, Daniel P. Berrange wrote:
We don't ship QEMU or KVM in RHEL yet, so there's nothing to fix in RHEL for QEMU/KVM, and I don't believe Xen suffers from it, since it uses a different way of handling MMIO memory registration.
Whereever that CentOS user got their qemu & kvm RPMs from, they weren't a standard part of RHEL & those versions are absolutely ancient too.
You're right, I missed that they're in the CentOS Extras repositories and not the base repository that is dervied from RHEL. They do have a newer version of kvm in their testing repository; I might give that a try. I use a customized Fedora kernel in the guest VMs, so in order to use Xen I'd have to get it built as a domU kernel. Thanks, David
participants (2)
-
Daniel P. Berrange -
David Mueller