* [Qemu-devel] [Bug 1675458] [NEW] attach-interface - unexpected action
@ 2017-03-23 15:51 Aaron Doyle
2020-11-10 15:15 ` [Bug 1675458] " Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
0 siblings, 2 replies; 3+ messages in thread
From: Aaron Doyle @ 2017-03-23 15:51 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
Hello,
Not sure where to report this, or if it is a bug. However, I feel like
the behaviour is not what would/should be expected.
----------------------------------------------------------------------------------------------------------
Environment:
KVM Version: root@hostname:~# virsh version
Compiled against library: libvirt 1.2.9
Using library: libvirt 1.2.9
Using API: QEMU 1.2.9
Running hypervisor: QEMU 2.1.2
uname -a: Linux hostname 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
Host Debian Version: 8.7 (Jessie)
Guest Debian Version: 8.7 (Jessie)
----------------------------------------------------------------------------------------------------------
Issue:
When adding an interface to a live VM, the position of interfaces within the VM may change post reboot.
It appears a new interface takes up the first available “pci slot”. If you have removed an interface in the past, this will be the one that is taken up.
----------------------------------------------------------------------------------------------------------
Example:
If the VM Has the following interfaces layout:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 11:11:11:11:11:11
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
Now I delete the interface with MAC address 11:11:11:11:11:11, you now
have this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
And then you add a new interface with MAC address 44:44:44:44:44:44,
using virsh:
virsh attach-interface --domain guest --type bridge --source br3 --mac
44:44:44:44:44:44 --model e1000 --target vmeth3 --live --persistent
It will now look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
eth3 HWaddr 44:44:44:44:44:44
However, after a reboot, it will look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 44:44:44:44:44:44
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
This can be a problem, as /etc/network/interfaces file, etc., will be
pointing to the wrong interfaces. I.E. originally eth1 was connected to
br1 (for example), after reboot eth1 is now connected to br3.
To resolve this issue, I need to edit the .xml file in the KVM machine,
and edit the following lines:
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c'
function='0x0'/>
Changing these into the order I want them to be loaded in, i.e. eth0,
eth1, eth2…. (I know 4 are taken already and not usable by ethernet
interfaces.)
----------------------------------------------------------------------------------------------------------
Thanks in advance.
Kind regards,
Aaron Doyle
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1675458
Title:
attach-interface - unexpected action
Status in QEMU:
New
Bug description:
Hello,
Not sure where to report this, or if it is a bug. However, I feel like
the behaviour is not what would/should be expected.
----------------------------------------------------------------------------------------------------------
Environment:
KVM Version: root@hostname:~# virsh version
Compiled against library: libvirt 1.2.9
Using library: libvirt 1.2.9
Using API: QEMU 1.2.9
Running hypervisor: QEMU 2.1.2
uname -a: Linux hostname 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
Host Debian Version: 8.7 (Jessie)
Guest Debian Version: 8.7 (Jessie)
----------------------------------------------------------------------------------------------------------
Issue:
When adding an interface to a live VM, the position of interfaces within the VM may change post reboot.
It appears a new interface takes up the first available “pci slot”. If you have removed an interface in the past, this will be the one that is taken up.
----------------------------------------------------------------------------------------------------------
Example:
If the VM Has the following interfaces layout:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 11:11:11:11:11:11
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
Now I delete the interface with MAC address 11:11:11:11:11:11, you now
have this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
And then you add a new interface with MAC address 44:44:44:44:44:44,
using virsh:
virsh attach-interface --domain guest --type bridge --source br3 --mac
44:44:44:44:44:44 --model e1000 --target vmeth3 --live --persistent
It will now look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
eth3 HWaddr 44:44:44:44:44:44
However, after a reboot, it will look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 44:44:44:44:44:44
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
This can be a problem, as /etc/network/interfaces file, etc., will be
pointing to the wrong interfaces. I.E. originally eth1 was connected
to br1 (for example), after reboot eth1 is now connected to br3.
To resolve this issue, I need to edit the .xml file in the KVM
machine, and edit the following lines:
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c'
function='0x0'/>
Changing these into the order I want them to be loaded in, i.e. eth0,
eth1, eth2…. (I know 4 are taken already and not usable by ethernet
interfaces.)
----------------------------------------------------------------------------------------------------------
Thanks in advance.
Kind regards,
Aaron Doyle
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1675458/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1675458] Re: attach-interface - unexpected action
2017-03-23 15:51 [Qemu-devel] [Bug 1675458] [NEW] attach-interface - unexpected action Aaron Doyle
@ 2020-11-10 15:15 ` Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
1 sibling, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2020-11-10 15:15 UTC (permalink / raw)
To: qemu-devel
Looking through old bug tickets ... Have you tried to discuss this issue
with the libvirt people? They might need to have a look at your virsh
commands first before one could decide whether this is a libvirt or a
qemu problem...
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1675458
Title:
attach-interface - unexpected action
Status in QEMU:
Incomplete
Bug description:
Hello,
Not sure where to report this, or if it is a bug. However, I feel like
the behaviour is not what would/should be expected.
----------------------------------------------------------------------------------------------------------
Environment:
KVM Version: root@hostname:~# virsh version
Compiled against library: libvirt 1.2.9
Using library: libvirt 1.2.9
Using API: QEMU 1.2.9
Running hypervisor: QEMU 2.1.2
uname -a: Linux hostname 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
Host Debian Version: 8.7 (Jessie)
Guest Debian Version: 8.7 (Jessie)
----------------------------------------------------------------------------------------------------------
Issue:
When adding an interface to a live VM, the position of interfaces within the VM may change post reboot.
It appears a new interface takes up the first available “pci slot”. If you have removed an interface in the past, this will be the one that is taken up.
----------------------------------------------------------------------------------------------------------
Example:
If the VM Has the following interfaces layout:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 11:11:11:11:11:11
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
Now I delete the interface with MAC address 11:11:11:11:11:11, you now
have this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
And then you add a new interface with MAC address 44:44:44:44:44:44,
using virsh:
virsh attach-interface --domain guest --type bridge --source br3 --mac
44:44:44:44:44:44 --model e1000 --target vmeth3 --live --persistent
It will now look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
eth3 HWaddr 44:44:44:44:44:44
However, after a reboot, it will look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 44:44:44:44:44:44
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
This can be a problem, as /etc/network/interfaces file, etc., will be
pointing to the wrong interfaces. I.E. originally eth1 was connected
to br1 (for example), after reboot eth1 is now connected to br3.
To resolve this issue, I need to edit the .xml file in the KVM
machine, and edit the following lines:
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c'
function='0x0'/>
Changing these into the order I want them to be loaded in, i.e. eth0,
eth1, eth2…. (I know 4 are taken already and not usable by ethernet
interfaces.)
----------------------------------------------------------------------------------------------------------
Thanks in advance.
Kind regards,
Aaron Doyle
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1675458/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 1675458] Re: attach-interface - unexpected action
2017-03-23 15:51 [Qemu-devel] [Bug 1675458] [NEW] attach-interface - unexpected action Aaron Doyle
2020-11-10 15:15 ` [Bug 1675458] " Thomas Huth
@ 2021-01-10 4:17 ` Launchpad Bug Tracker
1 sibling, 0 replies; 3+ messages in thread
From: Launchpad Bug Tracker @ 2021-01-10 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1675458
Title:
attach-interface - unexpected action
Status in QEMU:
Expired
Bug description:
Hello,
Not sure where to report this, or if it is a bug. However, I feel like
the behaviour is not what would/should be expected.
----------------------------------------------------------------------------------------------------------
Environment:
KVM Version: root@hostname:~# virsh version
Compiled against library: libvirt 1.2.9
Using library: libvirt 1.2.9
Using API: QEMU 1.2.9
Running hypervisor: QEMU 2.1.2
uname -a: Linux hostname 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
Host Debian Version: 8.7 (Jessie)
Guest Debian Version: 8.7 (Jessie)
----------------------------------------------------------------------------------------------------------
Issue:
When adding an interface to a live VM, the position of interfaces within the VM may change post reboot.
It appears a new interface takes up the first available “pci slot”. If you have removed an interface in the past, this will be the one that is taken up.
----------------------------------------------------------------------------------------------------------
Example:
If the VM Has the following interfaces layout:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 11:11:11:11:11:11
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
Now I delete the interface with MAC address 11:11:11:11:11:11, you now
have this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
And then you add a new interface with MAC address 44:44:44:44:44:44,
using virsh:
virsh attach-interface --domain guest --type bridge --source br3 --mac
44:44:44:44:44:44 --model e1000 --target vmeth3 --live --persistent
It will now look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 22:22:22:22:22:22
eth2 HWaddr 33:33:33:33:33:33
eth3 HWaddr 44:44:44:44:44:44
However, after a reboot, it will look like this:
eth0 HWaddr 00:00:00:00:00:00
eth1 HWaddr 44:44:44:44:44:44
eth2 HWaddr 22:22:22:22:22:22
eth3 HWaddr 33:33:33:33:33:33
This can be a problem, as /etc/network/interfaces file, etc., will be
pointing to the wrong interfaces. I.E. originally eth1 was connected
to br1 (for example), after reboot eth1 is now connected to br3.
To resolve this issue, I need to edit the .xml file in the KVM
machine, and edit the following lines:
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c'
function='0x0'/>
Changing these into the order I want them to be loaded in, i.e. eth0,
eth1, eth2…. (I know 4 are taken already and not usable by ethernet
interfaces.)
----------------------------------------------------------------------------------------------------------
Thanks in advance.
Kind regards,
Aaron Doyle
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1675458/+subscriptions
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-01-10 4:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-23 15:51 [Qemu-devel] [Bug 1675458] [NEW] attach-interface - unexpected action Aaron Doyle
2020-11-10 15:15 ` [Bug 1675458] " Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.