@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.

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.

@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.

@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.

@XCP-ng-JustGreat We ended up doing the Registry bypass. After that was done it worked great! We also tried things on our ESXi cluster, but due to licensing, couldn't do the vTPM. Also made sure to mention to my IT Manager about Olivier's 20-minute response to my forum post. Very much appreciated - hopefully I can get us to switch over.

@enes-selcuk odd... Sorry I can't be of more help with this than... when you're VM is starting I think the boot key is the Delete key, maybe there is a keyboard difference?

@olivierlambert - thank you. For enterprise gear, it's working perfectly, as I'm looking into the home lab community less, but I must mention that the support here in the XCP-NG forum is great !!

@julien-f Thanks, the VM had been assigned to VIF default with VLAN ID -1, I just had to move it to my Management VLAN VIF : xe vif-move

@CodeMercenary To answer your questions about backups, they should all be fine, the remote is attached to XO rather than the host itself so XO can backup any VM from any host it has access to, to any remote configured in XO.

It's really hard to tell, I would suggest to ask directly at the Xen community. We have far more urgent things to deal with at the moment sadly

I get the following error. can you help me.@AtaxyaNetwork @DustinB xe-linux-distribution.service: Control process exited, code=exited status=203 xe-linux-distribution.service: Failed at step EXEC spawning /usr/sbin/xe-linux-distribution: No such file or directory xe-linux-distribution.service: Failed to execute command: No such file or directory $ cp xe-linux-distribution /usr/sbin/ cp: cannot create regular file '/usr/sbin/xe-linux-distribution': Read-only file system

@olivierlambert said in Export to OVA just fails immediately from CXP-ng Centre: Hi, XCP-ng Center isn't officially supported. Use Xen Orchestra for that You can export in OVA in Xen Orchestra BTW. It's just your XOA version is probably outdated from years. So update it first. Great, thanks, we will try this!

Hello, not sure I can actually help, but I'll try to bring some info. As far as I know, Xen handles the cpu scaling by default, as you checked with xenpm. Therefore I would guess it does not expose the p-states to the guest. When reading /proc/cpuinfo the kernel will call show_cpuinfo() function will call arch_freq_get_on_cpu() which ends up checking support for p-states on fallback to a simpler version that will in our case probably always report the base clock. At least that's my understanding, I went through this quickly and may have missed bits, but sound "logical" to me. I think the guest tools won't help you there, they report information from host to guest only, and as mentionned in the first point the guest frequency reporting is not live frequency. The only way I see how to confirm your VM is using turbo clocks would be to pin your VM vcpus to fixed pcpus, load the VM and check these pcpu with xenpm as you were doing. It is interesting to me you're seeing turbo clocks there at all, from my tests for some other stuff, on epyc I actually never saw the clock go above the base clock, did you do anything specific to enable it? I guess BIOS setup to enable turbo, and maybe enable it with xenpm?

haha sure you should, well deserved!

@capo I'd also add here that if you go with the Citrix tools they aren't "just" from Windows Update, you'll need to actually run the installer either way, the drivers can be kept up to date via Windows Update but still have to install the agent so you can properly control/manage the VM. I personally say go with the Citrix if you need secure boot, right now I believe you can't secure boot VMs with XCP-ng tools installed. Unless that changed and I somehow never saw news about that.