-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only boot to EUFI shell #1
Comments
Thanks for the report. The VM boots to UEFI shell and then doesn't do anything, right? If it's an issue with the VM I might have to take a look at the qemu image conversion, because even if the actual setup doesn't work it should at least produce an OpenSUSE Micro-OS VM that can boot to CLI or a first setup screen... Do any of the xe commands fail/complain about something? I haven't tested this in a while, but I'll see if I can get around to it this week. |
I'm runing XCP-ng 8.3 Yes It just boots to UEFI and does nothing This is the output from the installer. Hope you can find anything usefull
|
It's definitely not happy about something, but the VHD looks like it imported fine... |
You could try deleting line 58 Xen-Orchestra-Install/createXO.bash Line 58 in 88efa3e
That stops the VM from being set to UEFI. Also note that this script is intended to run on an freshly installed system exactly once. |
Deleted line 58 and now it boots to the bios boot screen but says: |
Then it might be an issue with the image (or my method of attaching it to the VM) after all. I think there was a way to get info about a VMs configuration but I'd have to look up the commands myself. It should give you a lot of output with all the parameters set for the VM. Getting that would tell me if a virtual hard drive is installed at all. |
xe vm-list params=all uuid ( RO) : d08fc965-2176-52c1-ae47-8bb004ed437f |
A disk is connected
Also looks like it should work (c=root disk d=CD/DVD) I'll have to look into this more... There are a few other Micro-OS versions, maybe they split compatibility and we need the version explicitly using grub, or maybe the parameters for an imported disk changed, so now it's no longer bootable by default. Using https://docs.xcp-ng.org/appendix/cli_reference/ And if you're feeling like it: |
And just to be sure:
This seems wrong, but maybe it's only updated when a VM is running, or it's a legacy field, etc, etc. and therefore normal? |
SVM is enabled in BIOS Regarding VBD nad VDI |
It is documented under the Link I sent (for example the VBD stuff here: https://docs.xcp-ng.org/appendix/cli_reference/#vbd-commands) starting with something like I'm also not really familiar with all the different commands and options, so I'd have to read the documentation and google things the same way you'd have to do and since I currently don't even have a system running to test out the commands I'd come up with there isn't really a point in trying to come up with something that might work, or might have half the required CLI options missing...
Some basic definitions: Since the VM doesn't even find a boot medium it's most likely something wrong with the storage component (or a boot option). You obviously don't have to do these things it'd just be helpful in trying to come up with fixes for this and maybe speed up the whole thing since I'll have to figure out if I can test this in a VM or have to build a test system out of spare parts before I can diagnose this myself. |
The script runs true all stages but in the end I only get a server thats boot to UEFI shell
The text was updated successfully, but these errors were encountered: