On Wed, Jun 23, 2021 at 06:49:12PM +0200, Riccardo Ravaioli wrote: > Hi everyone, > > We have an issue with how network interfaces are presented in the VM with > the latest libvirt 7.4.0 and qemu 6.0.0. > > Previously, we were on libvirt 7.0.0 and qemu 5.2.0, and we used increasing > virtual PCI addresses for any type of network interface (virtio, PCI > passthrough, SRIOV) in order to decide the interface order inside the VM. > For instance the following snippet yields ens1, ens2 and ens3 in a Debian > Buster VM: > > <interface type="ethernet"> > <target dev="0.vSrv"/> > <mac address="52:54:00:aa:cc:05"/> > <address bus="0x01" domain="0x0000" function="0x0" slot="0x01" > type="pci"/> > <model type="virtio"/> > <driver> > <host csum="off"/> > </driver> > </interface> > <interface type="ethernet"> > <target dev="1.vSrv"/> > <mac address="52:54:00:aa:bb:81"/> > <address bus="0x01" domain="0x0000" function="0x0" slot="0x02" > type="pci"/> > <model type="virtio"/> > <driver> > <host csum="off"/> > </driver> > </interface> > <hostdev managed="yes" mode="subsystem" type="pci"> > <source> > <address bus="0x0d" domain="0x0000" function="0x0" slot="0x00"/> > </source> > <address bus="0x01" domain="0x0000" function="0x0" slot="0x03" > type="pci"/> > </hostdev> So your config here does NOT list any ACPI indexes > After upgrading to libvirt 7.4.0 and qemu 6.0.0, the XML snippet above > yielded: > - ens1 for the first virtio interface => OK > - rename4 for the second virtio interface => **KO** > - ens3 for the PCI passthrough interface => OK So from libvirt's POV, nothing should have changed upon upgrade, as we wouldn't be setting any ACPI indexes by default. Can you show the QEMU command line from /var/log/libvirt/qemu/$GUEST.log both before and after the libvirt upgrade. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
