ThasianXi

ThasianXi

@MrNaz I recommend reading the XO blog; updates are published monthly.

NBD was introduced in the 5.76 release and the ability to enable in the Xen Orchestra UI was introduced in 5.79
https://xen-orchestra.com/blog/xen-orchestra-5-76/
https://xen-orchestra.com/blog/xen-orchestra-5-79/

Also enhancements were released in 5.81
https://xen-orchestra.com/blog/xen-orchestra-5-81/

ThasianXi

@sb2014 In the 5.85 release of XO there were updates to the Netbox plugin that now requires three objects in the UUID field.
https://xen-orchestra.com/blog/xen-orchestra-5-85/

Here are the ones you need:

Virtualization > cluster
Virtualization > virtual machine 
Virtualization > interface

ThasianXi

@cichy This can be accomplished using vApps via the CLI.
Check out this forum post in which a member shared the process: XCP-ng Pool Boot Order

ThasianXi

@Denson You can mount from the CD in Xen Orchestra on the Console tab or install from the EPEL repo. (I always install from EPEL)

EPEL install:
dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -y

Tool install:
dnf install xe-guest-utilities-latest -y
Be sure to enable and start after installing: systemctl enable --now xe-linux-distribution

Doc ref: https://xcp-ng.org/docs/guests.html#linux

ThasianXi

This is now solved. I rebuilt the XO VM and can create multiple VMs as expected.

ThasianXi

I am using the current build of XO [commit: 1c01f] and there appears to be an issue when using the Multiple VMs creation feature.

I noticed the following TypeError in the browser console when either recalculating the VM number or refreshing the VM name. The goal is to create three VMs however only two are created and the name does not update.
I use this feature when rebuilding my lab and previously have not had any issue.

I can work around this however wanted to report here. Same behaviour in two browsers Firefox and Brave. I have not seen any other reports of this on the forum. Let me know if this can be replicated or if I can capture more information; thanks.

index.js:780 Uncaught TypeError: Cannot read properties of undefined (reading 'forEach')
    at a._buildTemplate (index.js:780:28)
    at index.js:771:25
    at index.js:65:1
    at index.js:27:1
    at a.u [as _buildVmsNameTemplate] (index.js:76:1)
    at index.js:821:29
    at Object.o (ReactErrorUtils.js:24:1)
    at s (EventPluginUtils.js:83:1)
    at Object.executeDispatchesInOrder (EventPluginUtils.js:106:1)
    at d (EventPluginHub.js:41:1)
(anonymous)	@	index.js:780
(anonymous)	@	index.js:771
(anonymous)	@	index.js:65
(anonymous)	@	index.js:27
u	@	index.js:76
(anonymous)	@	index.js:821
o	@	ReactErrorUtils.js:24
s	@	EventPluginUtils.js:83
executeDispatchesInOrder	@	EventPluginUtils.js:106
d	@	EventPluginHub.js:41
f	@	EventPluginHub.js:52
t.exports	@	forEachAccumulated.js:22
processEventQueue	@	EventPluginHub.js:250
(anonymous)	@	ReactEventEmitterMixin.js:15
handleTopLevel	@	ReactEventEmitterMixin.js:25
f	@	ReactEventListener.js:70
perform	@	Transaction.js:141
batchedUpdates	@	ReactDefaultBatchingStrategy.js:60
batchedUpdates	@	ReactUpdates.js:95
dispatchEvent	@	ReactEventListener.js:145

ThasianXi

@cichy This can be accomplished using vApps via the CLI.
Check out this forum post in which a member shared the process: XCP-ng Pool Boot Order

ThasianXi

@kagbasi-ngc You are welcome.

ThasianXi

@kagbasi-ngc Yes. I have XO configured to send system logs to Graylog via UDP.
It is mentioned in the last section of this blog for Xen Orchestra 5.76
Also see this forum post XO logs to external syslog

However to setup a remote syslog for an XCP-ng host, that can be configured on the Advanced tab of a host in Xen Orchestra.

ThasianXi

@rtjdamen Yes. See this forum post: CPU Stats bottoming out to Zero every five minutes

ThasianXi

@gecant Yes. That hotfix was released with the XCP-ng March 2023 Security Update

ThasianXi

@Denson You're welcome; glad to help.

ThasianXi