search for: qemuconnectdomainxmltonative

...ome reason, by the time > > we call it again in qemuProcessPrepareDomain() the PCI address for > > the network interface is no longer set, and so a fresh one gets > > assigned instead. > > > > I'll investigate further and get back to you. > > It is a bug in qemuConnectDomainXMLToNative. You'll see we replace > the original type=bridge NIC with a type=ethernet, except we fail > to copy the address info & probably other properties too. Yeah, I figured that out after digging a bit more :) I'm not quite sure how to fix it properly, though. Adding yet more properti...

Moving to libvirt-users where it belongs. On Thu, 2019-04-18 at 06:47 +0000, Tal Attaly wrote: > Hi, > I have bridge type interface defined with slot 3 - > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > but after running virsh domxml-to-native qemu-argv I get slot 2- > -netdev tap,fd=21,id=hostnet0 -device

...efAssignAddresses(); however, for some reason, by the time > we call it again in qemuProcessPrepareDomain() the PCI address for > the network interface is no longer set, and so a fresh one gets > assigned instead. > > I'll investigate further and get back to you. It is a bug in qemuConnectDomainXMLToNative. You'll see we replace the original type=bridge NIC with a type=ethernet, except we fail to copy the address info & probably other properties too. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-...