@john-c This is just the properties window of the driver that was not installed correctly:
Driver provider: Unknown
Driver date: not available
Driver version: not available
Signature: not digitally signed
The window below says:
Driver files for this device are either not required or have been loaded.
On a Windows 2022 Server VM with uefi boot the Installation of 9.3.3 via Windows Update or directly via update file from Citrix causes a blue screen with inaccessible boot device.
Are there others who have had the same experience?
I use XenServer since 2009. In 2008 i compared Hyper-V, VMware and XenServer for about 6 months (only the free versions) and my winner was XenServer. Not only because I am a fan of Open Source I choosed XenServer. My primary focus was performance and usability (for admins). VMware was too slow on low end hardware like HP ML110 and Hyper-V needed an AD. So I stayed with XenServer.
Since XenServer 7.3 I looked for alternatives and found the XCP-ng project.
I have a small IT company with 3 employees. We serve small and medium-sized customers. Unlike other IT companies around here, we use a lot of open source to offer alternatives to our customers. About one week ago I tested Xen Orchestra (compiled from source) and I like it a lot. I miss some features, but maybe I have not discovered them yet.
If you have plans to support other languages in Xen Orchestra, I can assist you with the german version.
@olivierlambert
Hello,
there's actually not much missing for implementation.
start-delay is already present in the VM settings.
Two parameters are missing:
The vApp is created with the following command:
xe appliance-create name-label=name-label [name-description=name-description]
The VMs are added to the vApp with the following command:
xe vm-param-set uuid=VM-UUID appliance=appliance-uuid
Remove from vApp:
xe vm-param-set uuid=VM-UUID appliance=
vApp-Start:
xe appliance-start uuid=appliance-uuid [paused=true|false]
vApp-Stop:
xe appliance-shutdown uuid=appliance-uuid [force=true|false]
If multiple VMs have the same order number, the longest start delay wins before VMs with the next order number are started. The same applies in reverse order for the shutdown-delay when shutting down a vApp.
vApps are the main reason for me to use XCP-ng Center.
For all my systems I always create a vAPP, which I call Start.
The start order for all VMs and the time delay are then stored here.
When you shut down, this list is automatically processed in reverse order.
vApps is one of the features I miss most in XenOrchestra.
If necessary, from XCP-ng 8.3 onwards I have to switch to the command line to work with vApps.