@olivierlambert I tried but getting this error when turning on the VM

INTERNAL_ERROR(xenopsd internal error: (Failure
"Error from xenguesthelper: Populate on Demand and PCI Passthrough are mutually exclusive"))

Not sure what it means

EDIT: after googleing it seems that static and dynamic memory has to be the same:

Just updated to lastest commit https://github.com/vatesfr/xen-orchestra/commit/4bd5b38aeb9d063e9666e3a174944cbbfcb92721

It's fixed now. Working wonderfully. Thanks!

0 fbeauchamp committed to vatesfr/xen-orchestra

fix(backups): fix health check task during CR (#6830)

Fixes https://xcp-ng.org/forum/post/62073

`healthCheck` is launched after `cleanVm`, therefore it should be closing the parent task, not `cleanVm`.

@olivierlambert

I got it working!

Pic while transcoding with plex

Plex info:

Detected:

For future reference if anyone finds this with google:

I had to " sudo chmod -R 777 /dev/dri" inside the Ubuntu VM, otherwise it didnt work.

I'm using binhex plex docker image, I have to add the device to the container. It's really easy with portainer:

The "/dev/dri/" part is the important

PS: @olivierlambert there is a typo in the xcp docs, a space is missing in Step 5:
https://docs.xcp-ng.org/compute/#5-put-this-pci-device-into-your-vm

This copy/pastes as:
xe vm-param-set other-config:pci=0/0000:04:01.0uuid=<vm uuid>

It should be:
xe vm-param-set other-config:pci=0/0000:04:01.0 uuid=<vm uuid>

@florent said in Continuous Replication health check fails:

@bullerwins nice catch, the fix is trivial with such a detailled error : https://github.com/vatesfr/xen-orchestra/pull/6830

nice! as soon as it's merges I'll update it and check. I'm so happy if this report helped you guys in any way!

@julien-f said in XOA Proxy Error when updating:

@bullerwins XO Proxy Appliance deployment is not supported in XO built from sources.

my bad, it used to work a few months back I believe

@olivierlambert said in XOA Proxy Error when updating:

I missed that in the original message, indeed

FYI @bullerwins there's no such thing as XOA built from sources, you have either:

• XOA is Xen Orchestra virtual Appliance, that's the VM we distribute with pro support and QA/stable channel, updater and such
• XO from the sources is from Github, without pro support but community support, no QA no stable version, no udpater and such

Thanks, I got confused with the naming, I'm using the second option.

As a workaround I used a VPN to manage the remote XCP-ng host, thanks!

@julien-f Thank you so much, I restarted the XOA built from source ubuntu VM and now it works! (how could I not thought of this before #1 rule in IT, turn off and on again).
Thanks a lot for the support.

@Soarin Hi! Would you mind sharing what config did you use for openvpn?
Did you install openvpn in the xcp-ng host? in a vm?