@XCP-ng-JustGreat

I only use the passthrough part of disks, not controllers. VUSB part in xo i don't use. I think that's a completely different approach. Maybe you could check your drivers and manager. There is a cleaner somewhere, don't know the link, to remove the old drivers in windows with powershell and after that install the xen drivers XenServer VM Tools for Windows 9.4.1. I got it from here: https://www.xenserver.com/downloads

https://github.com/xcp-ng/win-pv-drivers/releases/download/v9.0.9065/XenClean.zip
docs:
https://docs.xcp-ng.org/vms/#fully-removing-xen-pv-drivers-with-xenclean

@XCP-ng-JustGreat
I add my passthrough disks this way so I can attach them to my vm in xo ce. And also USB 3.1 an 3.2.

on the host:
find your disk. .. fdisk ok lsblk

sudo mkdir -p /srv/pass_drives
xe sr-create name-label=Pass_Drives type=udev content-type=disk device-config:location=/srv/pass_drives
sudo ln -sf /dev/disk/by-id/usb-Seagate_Desktop_NA7HMMDC-0:0 /srv/pass_drives/sdg

scan ...
after that you can attach it in you (down) vm and startup.

I have 4 disks in passthrough configuration this way (2 x 8TB sata for truenas vm in a mirror conf, 1 TB sata and 1 x USB 8TB for external backup) and as long as you don't change the /dev/sdX order it works fine.

xcp-ng 8.3

If I set the vm auto power on in Xen Orchestra web interface community version it works. But the Start delay (seconds) in the web interface does not change anything in the config and the variable auto_poweron_delay is not set or changed when I look with xe vm-param-list uuid=....
Only when I type in at the cli: xe vm-param-set other-config:auto_poweron_delay=30 uuid=.... does the variable auto_poweron_delay appear or change.
Xen Orchestra, commit fd2c7
xo-server 5.113.0
xo-web 5.116.1

Ok. Great I wait for the release. Thanks

@olivierlambert Hello Olivier, Another year since the question. Time flies By now, do you know the eta of version 8.3? And is it still an option in that version to be able to backup only the boot disk.

Kind regards,
Jan

@olivierlambert ok.

For info: xo-server 5.113.0 / xo-web 5.116.1 Installed this version XO yesterday and tried a smart reboot with 14 vm's running. Windows and linux vm's. Of which some linux vm's have NFS shares which I use for ISO files and making backups with XO. These I normally have to disconnect before I can do a reboot of the host otherwise it will not reboot and had expected that this would not be necessary now. It took a very long time for all vm's to enter suspend mode (>2 hours) and the server did not reboot. Probably ran into not shutting down the NFS shares. I finish much faster if I manually shut down all vm's (and disconnect the NFS shares) reboot the host and restart the vm's. But maybe I am overlooking something then I would like to hear about it.

@olivierlambert

Ok thanks for your response. I understand your "making money" but, as a simple home user, am very happy with the open source and philosophy behind it. Of course, whenever possible, I advise companies to look at xcp-ng and xen-orchestra and get a subscription. Great what you guys are doing.

Greetings,
Jan

Is xo going to support smart host reboot in the community version?
Will smart reboot then also work with nfs shares that are still open? Now if I want to reboot the host I have to first disconnect all the nfs share, then shut down the vm's and then reboot the host.

@olivierlambert Is there a date known when 8.3 will be released?

@olivierlambert

Ok that sounds good. Do I understand correctly that this is then possible not only for snapshots but also for backups?

Hello,
I have truenas running on a virtual machine.
As data disks I have linked two 8TB disks via passthrough in a mirror configuration.

I would like to take occasional snapshot and backup just the boot disk. Not those 8TB disks.

The question is actually is it possible to exclude this passthrough disk from the snapshot and backup?

@ronivay Ok. In between jobs I did a new VM install of debian 11 and on it the XO community version.
Version numbers now:
xo-server 5.100.1
xo-web 5.101.1
I seem to have everything working again. Thanks for the help and tip. Now it seems really solved.
If I come across anything else, which I don't think I will, I will report back.
Greetings and thanks,
Jan

@ronivay I understand that there is no point in troubleshooting error because apparently I am using an old config. Node is version v16.17.0. Maybe it is better to create a total new vm with latest version debian. And then install a clean version of xo community edition there. Is it then possible to import in that new installation of xoce the config of the current version?
Thanks for your patience.

Turns out that unfortunately it doesn't quite work yet. Updated the xoa but the version still say xo-server 5.70.0 and xo-web 5.74.0. As far as I understand it, this is the community version where the backup also works. But when I take a snapshot of a vm I immediately get an Orphaned VMs snapshot line at health. Also rebooted the host once just to be sure.

@ronivay Problem seems to have been solved by an update. Thanks for the tip.

@ronivay ok going to have a go at that soon. Thank you

@ronivay

xo-server 5.70.0
xo-web 5.74.0

Hello,
I searched for the error but couldn't find it anywhere here.
When I made a snapshot and want to revert it I get an error message in xen orchestra no such object undefined.
I have already reconnected the server once but that didn't help.
What I also see at helth is that there are also a number of Orphaned VMs snapshots.
This scares me a little bit because it probably means that I have a lot of snapshots that are not usable.
But for now it is important to get the snapshots working again because I use them a lot and the backups use them too.

Recognizable for someone and maybe someone knows a solution?

Thanks in advance
Regards,
Jan