@dingo xcp-ng templates and cs templates are something irrelevant.
What are you trying to do?

I am using cs with xcp-ng around 4 years.

I could help you

@andSmv
Damn - i was quick and have a coral m2 A+E coming in a few days 😆

It's just for fun/learning so as long as it doesn't break my homelab too much i will be willing to test so we might get it included 👍
Already using the 4.17 test version without a hitch since it came out.

It's a bit hard to tell with so little details 😕

Could you provide more context, the network bandwidth between XO, XCP-ng, your PC where you import the drives etc.

@mchadley002 @BobTB12 Thanks for the info! I concur, it boots now! (XCP 8.2 and 8.3)

Two important hints: First ENABLE Viridian for the VM. It does not want to boot without it. Second BOOT with UEFI, BIOS does work but disk IO sucks.

I used the ISO boot image: OI-hipster-minimal-20240426.iso

@splastunov why do you extract the vgpu RPM rather than just installing the RPM directly?

@Danp

yes your correct .. however my source issues started again..

there is some issue using kubernetes, longhorn with mariadb operator in xcpng

having a hard time tracking down the root cause

That's interesting though 🙂

@alpenliebeanj

I know you resolved this a different way but what I did when migrating P2V from a bare metal debian system to xcpng is using clonezilla I transferred the image via the network to the VM which was booted to clonezilla as well. Then I changed the boot option to UEFI in advanced, pressed escape on startup and then proceeded to add a boot menu entry for grub of the Debian system. I would assume the process would have been similar in your case as well to resolve.

Thanks! We didn't test on threadrippers yet, so it's useful info 🙂

Okay then try CPU cap at 400 🙂

@Danp
I do not have a power outage or did you recently install XCP updates.
I shutdown the host at the console.
Next day,I power on the host,and that was it.

@kait said in how to disable vm console or make it secondary display device:

@DustinB im using passthrough not vgpu but i could try that anyways

I assumed you were attempting to use passthrough.

@alexredston Hey, sorry I'm a little bit late here. So, with regard of VCPUs - there's a hardcoded limit of 128 actually in XEN hypervisor. Moreover XEN toolstack (when creating a guest) will check that guest VCPU limit is below physical CPUs available on the platform.
Bypassing the VCPU 128 limit will require some rather important adjustements in XEN Hypervisor (basically the restrictions go with IOREQ server from QEMU and how LAPIC id are affected in XEN). So with the next XEN version this limit could potentially be increased (there's an ongoing work on this).

The things you also probably would like to know about this VCPUs limit

not all of the guests can handle this VCPUs number (e.g. Windows will certainely crash) when you gives a VM such a big VCPU number (basically more than 32) the VM can potentially provoke the DoS on the whole platform (this is related how some routines are "serialized" in XEN Hypervisor). So, when you do this - be aware that if your guest is broken, pawned, whatever... your whole platform can potentially become unresponsive.

Finally, I follow an existing topic and configure nut-server on the hypervisor to access the ups via usb.
I know that Olivier is not fully aligned with the fact that the host is modified but IMO it is an acceptable change on my XCP-NG host.

@olivierlambert Do you think it's possible for that support to be added, or are there proprietary code limitations that prevent it?
What would it take to solve that limitation?

We have currently delivered a project which which uses vmware, and the current temporary licenses end in September (could probably be extended a little).
In our cluster we have a total of 10x Nvidia A2, and 3x Nvidia L40 cards.
I would love to move to xcp-ng, as it really seems perfect for us, but the lack of Nvidia vgpu support stops us.

@enes-selcuk The error is telling you that you're host doesn't have enough Memory to actually start the VM.

Is this VM from an OVA and being imported (or has been imported?)

If you have XO or XOLite installed, you can try to reduce the amount of Memory assigned to the VM and start it then.

In case someone ends up here with a similar issue, you also end up at the UEFI shell when UEFI is selected for a BIOS-based image.

Try with Advanced -> Boot firmware changed to bios.

As long as you configure things right like @DustinB said you should be good to go, I don't believe anything will override that and sync to the host.

@ambad4u For sure! Yeah, 1.29 does not work for me either. Going to keep an eye out for any new versions and report back.

For the record, I only have this one unit to test; so there's always the chance mine could be bunk. Luckily these units make it easy to change out the firmware in either direction, so anyone willing to (carefully) test and confirm, would be appreciated.

Been running some benches and it's a fine little machine otherwise.

@high-voltages you also can try xenpm start 10 to gather info for 10s and it will print a sumarry at the end, in my case it had each core average frequency, not sure you'll get it too, but you can give it a shot.