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
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,
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 :
ng sorting. And be extra careful that the domUs
MACs match the ones we expect on that network.
Via udev (MAC matching) or /etc/network/interfaces ?
I ask because it may help others, while this gets resolved.
--
zithro / Cyril
-b',
'mac=00:16:3e:fd:83:31,bridge=lanbr,vifname=domu-c',
...
]
Note it's just a workaround, and I've not tested it.
I only guess letters would be sorted correctly.
If you test this, can you report back please ?
--
zithro / Cyril
TART/STOP ORDER
# domains not in these lists will be started after and stopped
# before the ones here
start-order=(list of domU names)
stop-order=(list of domU names)
But then again, this only ensures "domains" start order, not "services
availability" in said domains.
--
zithro / Cyril
0.0.1:12", the
real IP address is "127.0.0.1:5912" (in your case, you'd pick 5901).
Hope it helps.
PS: as for documentation it will be in the new Debian Xen wiki page
(which I'm rewriting, for now it's still an offline draft).
--
Cyril Rébert / zithro
Hello,
I reported the bug upstream, just added there some comments to reflect
that the output is different on AMD and Intel platforms.
I also added the commit link, thanks for that.
So, "systemd-detect-virt" on non-nested dom0s reports :
- "xen" on Intel (like this bug report)
- "vm-other" on
blem can't be solved "at its roots", can't we just apply the
(harmless) workaround in the installer ?
We should really speed up the fix before the Full Freeze.
I can help for testing and reporting stuff, but I'm a noob in packaging.
Thanks all, have a nice day,
zithro / Cyril REBER
9 matches
Mail list logo
