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

No problem 🙂 FYI the update is now available: https://xcp-ng.org/forum/post/70029

You should ask on XenDevel Matrix channel: https://xenproject.org/help/matrix/

Hi !
@m4x116 I have same issue from last two days, its your problem is solved then please explain why this issue occurred and solution of this problem.

@apattyn Hmmmm I wonder if some of this comes down to ARC's immaturity, I have a 2060 passed through to a Ubuntu VM that is in UEFI mode and it works flawlessly for GPU rendering in the VM. So don't think using BIOS should be a requirement, but I am also not as familiar with Fedora so I could be missing something.

@tuxen
I did send the MEMORY.DMP-files to a microsoft specialist and did post the result on Juli 25 in that thread.
daemon.log is quite hard for me to read. I did not find something, I can see as an error. It looks, like a "shutdown" - not a reboot.

@chrisfonte
Yes, fully licensed. It is not a "shutdown because of missing licenses after 24h".

@Hightmar Excellent to see, yeah this worked well for me on the 2060 and have been using it on Jellyfin for a while now without any crashes or other odd behavior.

@olivierlambert

This is great news.
Looking forward to testing this functionality on a xcp-ng server in the future:)