@Andrew No, it's not safer, as it's not tested, and there are far more changes than just Xen.
Posts made by stormi
-
RE: XCP-ng 8.3 beta 🚀
-
RE: XCP-ng 8.3 beta 🚀
@Andrew said in XCP-ng 8.3 beta :
@olivierlambert Will XCP-ng 8.3 be using Xen 4.17 for the release (like XenServer)? If so, when will Xen 4.17 be part of the base install?
I'm the one who can answer the second part of this question, actually. It's all built in the
xcp-ng-ci
repository. We are now testing them in CI, will fix issues if there's any, and then this will reach thexcp-ng-base
repository and make the packages inxcp-ng-lab
deprecated (and should update them smoothly). -
RE: XCP-ng 8.3 beta 🚀
@Andrew I now pushed a rebased build of XAPI in the
xcp-ng-lab
repo. -
RE: XCP-ng 8.3 beta 🚀
A new update is available. It's a small one (though, as it touches XAPI, it causes many packages to be updated): the webserver will now report the correct mimetype for SVG files, which is needed by XO Lite.
-
RE: ISO modification with additional RPM for NIC
Yes, without any network connectivity available, that's the main option.
Regarding modifying the installation ISO, you'd need two things:
- modify install.img to put the driver in it. That's the easiest part and you can use https://github.com/xcp-ng/xcp/tree/master/scripts/iso-remaster (see the example script in
samples/
). We still need to update the online docs to mention this option (ping @yann). This will give you network connectivity during the installation, but won't install the driver on the system. - install the driver on the target system. If I had done things right, you could just add the RPM in a directory and modify an XML file. However I have not done this right so it's not possible at the moment. There are several options, but I think the simplest is:
- add the RPM in Packages/ and regenerate the repodata + modify the installer code in install.img so that it installs it (look up 'xcp-ng-deps' and add the package name next to it)
- modify install.img to put the driver in it. That's the easiest part and you can use https://github.com/xcp-ng/xcp/tree/master/scripts/iso-remaster (see the example script in
-
RE: ISO modification with additional RPM for NIC
Do you absolutely need all in one ISO? Otherwise there's a rather simple solution with an unmodified ISO + a driver ISO. We even already provide one: https://updates.xcp-ng.org/isos/drivers/8.x/
-
RE: ISO modification with additional RPM for NIC
I haven't forgotten you, but have been busy. Still need help?
-
RE: Updates announcements and testing
Now live. Thanks everyone!
https://xcp-ng.org/blog/2024/04/13/april-2024-security-update/
-
RE: 8.3 beta, crashed Windows11 VM when trying to snapshot with memory
@manilx I agree about snapshots. I don't know how we can checkpoint a VM without suspending it (I think it shortly suspends it and them resumes it), so I have trouble understanding XenServer's statement.
-
RE: 8.3 beta, crashed Windows11 VM when trying to snapshot with memory
Actually, I'm not sure checkpoints are supported, or snapshots of a suspended VM which as a vTPM: https://docs.xenserver.com/en-us/xenserver/8/vms/windows.html#constraints
I had already noted we need to investigate what this actually means, but this might explain why it crashes sometimes.
-
RE: 8.3 beta, crashed Windows11 VM when trying to snapshot with memory
With
scp
(or a windows equivalent such as WinSCP maybe? I seldom use Windows) -
RE: 8.3 beta, crashed Windows11 VM when trying to snapshot with memory
We'll try to reproduce. If you can upload the tarball created by
xen-bugtool -y
somewhere private, we can try to have a look at it. -
RE: 8.3 beta, crashed Windows11 VM when trying to snapshot with memory
Does it always crash, or just sometimes?
-
RE: Wyse 5070 VM won't booting after update bios 1.27
However, logs from a debug Xen might give more clues.
If you can, please follow the instructions given by @andyhhp - a Xen developer - at https://xcp-ng.org/forum/post/74855.
-
RE: Wyse 5070 VM won't booting after update bios 1.27
@t-chamberlain No need to, unless you have some doubts. For now the conclusion will be
xl dmesg
doesn't output anything particular when the VM hangs. -
RE: Wyse 5070 VM won't booting after update bios 1.27
@t-chamberlain Was the xl dmesg output produced before, or after the VM hanged?
-
RE: Wyse 5070 VM won't booting after update bios 1.27
@t-chamberlain Yes, please. One host, with one failed VM start, would be enough