After installing updates: 0 bytes free, Control domain memory = 0B
-
-
You might want to check out the Essential or Essential+ options at https://vates.tech/pricing-and-support/. This would allow you get obtain support for up to 3 hosts.
-
You can export the VMs running on 8.3 and then import them to a host running 8.2
-
Maybe @stormi will have some ideas on how to recover your 8.3 hosts
-
-
@Danp Thank you for your advice.
If I only purchase support for 3 servers; How will XO behave with all 8? You do not have to reply; I will try contacting sales on monday.
I will look closer at @stormi's articles
Now I remember why I landed on 8,3 instead of 8.2 : Black screen during initial installation routine after "xcp-ng xen is relinquishing vga console" :
This post describes the problem precisely:
https://forum.qubes-os.org/t/blank-screen-after-xen-xen-is-relinquishing-vga-console/10243Seems the super simple and cheap fanless gforce 710 GPU is not supported in 8.2 (but it works fine with 8.3).
I've failed finding 8.2 ISO with drivers for PCs included. Promising links have turned up dead. Efforts to make own build failed and cost me a lot of time.
Is there a guide - that actually works - on how one can include a standard gforce driver for linux on the USB installation drive for XCP-ng?
Or: Is it possible to use serial interface, SSH or something to complete installation?
Or is it easiest to just install 8.3 and not install any updates until the problem has been fixed?
I see this issue has been discussed - and fixed - previously: https://github.com/xcp-ng/xcp/issues/436
-
@Dataslak Are you booting the newest 8.2.1 IOS?
-
@Dataslak XO won't treat them any differently. You will simply have a support contract that covers three of your hosts. They would need to be segmented into their own pool (simply for support reasons), but your other servers will still be manageable from XOA.
Have you tried the new 8.2 ISO that was released back in December? I thought that it now included the i915 driver.
https://updates.xcp-ng.org/isos/8.2/xcp-ng-8.2.1-20231130.iso -
@Andrew I started looking at https://xcp-ng.org/docs/releases.html, which led me to standard release 8.2.1.
@Danp I have now downloaded and tried installing with your link. And this installation image worked
Thank you so much!I guess there are good reasons for not listing this on the download page (https://xcp-ng.org/#easy-to-install) ?
Had it been available then perhaps I and others would have tried it earlier, avoided 8.3, and perhaps also avoided the big mess I'm in right now?
I will now try to migrate VMs.
-
@Dataslak said in After installing updates: 0 bytes free, Control domain memory = 0B:
I guess there are good reasons for not listing this on the download page (https://xcp-ng.org/#easy-to-install) ?
I had the same question. Perhaps it is because 8.2 is a LTS release and they didn't want to switch to the newer ISO by default. It's also possible that someone simply forgot to update the link.
@olivierlambert will know for sure.
Had it been available then perhaps I and others would have tried it earlier, avoided 8.3, and perhaps also avoided the big mess I'm in right now?
Not sure that is true in your case since it sounds like you've been on 8.3 for > 6 months and the new ISO has been out for less time than that.
I will now try to migrate VMs.
I don't think that you can live migrate from 8.3 to 8.2, so you will need to export to XVA format and then import to the 8.2 host.
-
I'm not sure to understand. The link on XCP-ng.org is pointing to https://mirrors.xcp-ng.org/isos/8.2/xcp-ng-8.2.1-20231130.iso?https=1 (which is the latest ISO). What am I missing?
-
@olivierlambert The link at the top of https://xcp-ng.org/docs/release-8-2.html leads to https://mirrors.xcp-ng.org/isos/8.2/xcp-ng-8.2.1.iso?https=1
-
Ah so in the doc itself, understood, fixing it now!
edit: that's the old doc, cf https://docs.xcp-ng.org/releases/release-8-2/
I will be sure to redirect the old one to the new one.
-
@Danp where did you find the https://xcp-ng.org/docs/release-8-2.html link originally?
-
-
Just out of curiosity, if you ssh to the host and execute "xentop" what does it tell you?
I mean it makes no sense that its actually using all the memory, so the question is if XAPI thinks so, OS or XEN. -
@Danp I mean, originally, the link where you found it, outside the doc itself? I have redirect almost all old docs link to the new one.
-
@olivierlambert You would need to ask @Andrew as I only went off of his post where he stated the following
I started looking at https://xcp-ng.org/docs/releases.html,
-
@Dataslak Have you moved all your servers to 8.2.1 yet, or do you still have stuck 8.3 servers that we could have a look at to understand if this may be an issue in the 8.3 beta itself?
-
The grey circle next to the host name in XO means the host is disabled (you can hover with the mouse cursor and this will tell it). Why it is disabled is the true question here. It could be XO not having re-enabled it after the update, but you did try to leave maintenance mode, so it looks like the problem may be elsewhere.
/var/log/xensource.logcontains the answer (or/var/log/xensource.log.*) , but what to look for exactly I can't say off memory. -
@Danp said in After installing updates: 0 bytes free, Control domain memory = 0B:
You can export the VMs running on 8.3 and then import them to a host running 8.2
IIRC you can't (moving towards a newer release is always supported, but towards a lower release isn't), but you can use XO's warm migration to do so. However, to export the VMs you need an enabled host.
Also, be aware that UEFI VMs started on 8.3 will not start on 8.2 unless we wipe their EFI variables completely from the host's command line. Which in most cases is okay but we have seen at least one version of debian fail to start after that and require a bootloader reinstallation.
-
@stormi said in After installing updates: 0 bytes free, Control domain memory = 0B:
IIRC you can't (moving towards a newer release is always supported, but towards a lower release isn't), but you can use XO's warm migration to do so. However, to export the VMs you need an enabled host.
I thought that applied to live migration, but that export/import would still function when moving VMs to an earlier release.
-
@stormi Thank you for your input. It is much appreciated
I have not dared to move all hosts from 8.3 to 8.2.1 out of fear of losing VMs. If you wish to look at them to discover things that may be of value in your beta development then I wish you more than welcome. Please instruct me on how to assist you in this.
I have re-created all VMs on the one host that I restarted and could not get the VMs to boot on. Thus you can go berserk on this server in your bughunt :-D. If you can somehow get the VMs to start up then I only ask that I be allowed to run a quick powershell command on each of them to release their Windows licenses. Thereafter the host is yours for destructive testing.
-
@stormi and @Danp Thank you for all your helpful input.
I look forward to purchasing a contract that opens up tools to more easily handle VMs and pools.
I have tried to enable the host. But can still not get VMs to start, getting "no hosts available".
When I restart the host it is again disabled / put in mainenance (I am actually not sure what it is).I can easily SSH into the command line. I am familiar with DOS and somewhat PowerShell. But not with Linux/Unix. How risky and difficult do you think it will be for me to wipe EFI variables from VMs?
If Debian failed to start; Do you have any experience with Windows VMs?
