Displaying 3 results from an estimated 3 matches for "qemudomaindefassignaddress".
Did you mean:
qemudomaindefassignaddresses
2019 Apr 18
2
Re: [libvirt] Why virsh domxml-to-native qemu-argv changes PCI slot number
...rsion is 4.5.0
I can reproduce this, and also confirm that it shouldn't happen :)
qemuDomainAssignAddresses() is supposed to make sure that any address
configured explicitly by the user (or previously by libvirt) is
preserved, and it's doing that correctly when it's called from inside
qemuDomainDefAssignAddresses(); 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.
> here is the full domain XML -
>
> <doma...
2019 Apr 18
1
Re: [libvirt] Why virsh domxml-to-native qemu-argv changes PCI slot number
...19 at 04:23:05PM +0200, Andrea Bolognani wrote:
> > qemuDomainAssignAddresses() is supposed to make sure that any address
> > configured explicitly by the user (or previously by libvirt) is
> > preserved, and it's doing that correctly when it's called from inside
> > qemuDomainDefAssignAddresses(); 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.
>...
2019 Apr 18
0
Re: [libvirt] Why virsh domxml-to-native qemu-argv changes PCI slot number
...roduce this, and also confirm that it shouldn't happen :)
>
> qemuDomainAssignAddresses() is supposed to make sure that any address
> configured explicitly by the user (or previously by libvirt) is
> preserved, and it's doing that correctly when it's called from inside
> qemuDomainDefAssignAddresses(); 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 qemuConnectDoma...