Hello,
I'm currently in the process of cleaning up and i noticed this bug i
reported is still open.
Based on what we know now i think the bug can be closed.
To summarize:
* the ordering of network interfaces (and therefore the ethn names) was
never meant to be stable and changed with Xen 4.1
On 08 Aug 2023 16:59, Hans van Kranenburg wrote:
I didn't read the other mailthread on the xen list fully yet.
You gave me the idea to post the IRC digest, so the report here is more
complete, and people not tracking the xen-devel ML can read it nicely.
For those who do, the mail is dated "02
Hi,
On 8/8/23 15:22, Valentin Kleibel wrote:
>> On [0], you can read "In both cases the device naming is subject to the
>> usual guest or backend domain facilities for renaming network devices".
>> It says "naming/renaming", but you can assume "detecting".
>>
>>> I also checked which net_ids udev
On [0], you can read "In both cases the device naming is subject to the
usual guest or backend domain facilities for renaming network devices".
It says "naming/renaming", but you can assume "detecting".
I also checked which net_ids udev knows about and the only things that
pop up are:
ID_NET_N
On 08 Aug 2023 12:08, Valentin Kleibel wrote:
I posted on xen-devel, you can follow from :
https://lists.xenproject.org/archives/html/xen-devel/2023-08/msg00244.html
(Unfortunately, the formatting is weird via html, split the IRC part
on "- ").
Thank you for posting upstream.
No prob, althou
I posted on xen-devel, you can follow from :
https://lists.xenproject.org/archives/html/xen-devel/2023-08/msg00244.html
(Unfortunately, the formatting is weird via html, split the IRC part on
"- ").
Thank you for posting upstream.
Note that, at first sight, I was told this seems "not-a-Xen" bu
On 02 Aug 2023 18:09, Valentin Kleibel wrote:
#xen-devel is the IRC Xen channel. I just pinged them, I'll wait.
Depending on their answers, I'll post on the xen-devel mailing list.
thanks for the clarification, looking forward to an answer.
I posted on xen-devel, you can follow from :
https:/
#xen-devel is the IRC Xen channel. I just pinged them, I'll wait.
Depending on their answers, I'll post on the xen-devel mailing list.
thanks for the clarification, looking forward to an answer.
Our current workaround is to edit the interface names in the domUs
config to match the wrong sortin
Hello,
the bug has been mentionned on #xen-devel, will keep you posted.
Meanwhile, you may try to force the domU vif names with a letter, like :
vif = [
'mac=00:16:3e:fd:83:2f,bridge=lanbr,vifname=domu-a',
'mac=00:16:3e:fd:83:30,bridge=lanbr,vifname=domu-
Package: xen-utils-4.17
Version: 4.17.1+2-gb773c48e36-1
Severity: important
Dear Maintainers,
On one of our domUs we discovered that the network interface names were
wrongly assigned since recreating the domU after an upgrade to bookworm.
If over 10 network interfaces are configured the mappi
10 matches
Mail list logo
