Installed in my Homelab. Install went smoothly.
Small bugs I have noticed :
1.
This ONLY happens when using KVM and 'scaling' the display to fit window.
This happens ONLY on the first boot after applying patch ( 6 programs ) once release iso is installed.
This goes away from the second boot.
Everything seems to be working smoothly for now. Kudos to the Vates Team !
@stormi said in XCP-ng 8.3 betas and RCs feedback 
:
http-nbd-transfer-1.4.0-1.xcpng8.3: XOSTOR-related fixes
Does this mean XOSTOR is ready to be tested in 8.3 ?
Thanks for the tip ! Anyway to delete the crontab created for root ? Or it is not required (since it is blank anyways) ? (I should have just used crontab -ir)
I also noticed that I get an option to "Upgrade" to RC1 from beta 2. This should technically not happen since I installed beta 2 in Legacy BIOS mode and am now installing RC1 in UEFI mode since the former would be deprecated.
Is that an error in installer or upgrade is possible ?
I have also successfully run a test install of RC1 on my lab. Everything seems to be working fine. The TLS issue also seems to go away (will also put a separate post on the topic concerned).
Good Job guys !
One thing I noticed :
I seem to get an error message
no crontab for root
while running crontab -e the first time.
Is that normal? Is it ok to run a cron job for root ?
Thank you soooo much for your valuable answers !
Thanks for letting me know about the deprecation. I missed seeing it in XCP-Ng 8.3 Beta 2 while I was testing it using the ISO install method.
I believe there is no 'upgrade' path from BIOS to UEFI? ( I would need to completely re-install the host again... right ?)
Does XCP-ng have the option of secure boot when installing from iso? (I am not talking about the Guest VMs here)
Hello @stormi @olivierlambert
Is there any real performance difference between installing XCP-NG host on BIOS mode vs installing it on UEFI mode? (Not the VMs, I mean the host itself)
Is there any benefit of installing xcp-ng using uefi, considering we can still have uefi VMs even if we install the host in BIOS mode... correct ?
I have a suggestion w.r.t interface-rename.
Can we have a screen at the installation (using iso method) which lists all the NICs and we can rename the interfaces at install time itself ?
@planedrop said in Get Properties of VxLAN:
@gb-123 Yeah I do think it'd be really nice to have all the info exposed in the GUI, not sure if there are any plans for that, but I like the idea.
+1 for this but I think the Devs are busy with other important features.
@BenjiReis said in SDN Controller Errors:
@gb-123 The tunnel are numbered by order of creation by XAPI, you can't change them.
Bug Report: At the time of adding a host to existing GRE/VxLANs in the network, the XAPI takes into account the Alphabetical name while creating the tunnel numbers. Specific Eg.:
Error : New Host will have GRE as tunnel0 and VxLAN as tunnel1
I don't know if the above happened to me as a one-time case scenario or there is a bug, but worth a check.
You should take a look a look at XO's logs to see if you can find something that might trigger the SDN controller.
Does the host added frequently has another weird behavior?
Can you let me know the file I should see the log or should I look for journalctl ?
The weird behavior is that after several restarts, the VM gets connected and then after restart looses connection again. But I noticed whenever a VM is started on a host, the Host gets added to the SDN as per the logs above.
Just a last question which I need to further diagnose this-
Does the Host ever call on XO or is it always XO that calls on the Host (Server-Client)?
Or do they use WebSockets connection (so that the host does not need to call XO) ?
What would happen if I turn off XO after creating a SDN network ?
Update 4 :
The GRE connection works, but us spotty at times. Sometimes, the VM doesn't connect, but if I restart the VM several times, it starts to connect. This is when I have not changed any setting between starts.
(From what I remember, it was working perfectly in 8.2.1. Do you think this is a problem with 8.3 beta ? )
Yup. I was looking at seeing other properties also (specifically encryption)
Update 3:
I managed to sync the tunnels by deleting the network and then recreating all networks one by one. However, I think the code allots tunnel numbers as per alphabetical name sorting rather than taking it from the pool.
(VxLan - not working
GRE - working)
Update 2:
I added another host, in which the tunnel for GRE is showing as tunnel0 and for VxLAN is showing as tunnel1. However, in the pool, tunnel0 is VxLAN and tunnel1 is GRE.
So now GRE has also stopped working on the new Host.
Any way I can change the tunnel numbers manually ?
I think the code allots tunnel0 and tunnel1 as per name of the connection in the first time.
GRE Encrypted Network Seems to work fine.
VxLAN still not connecting
Thank you so much!
PS: Btw, there is a slight typo in your post. Its other-config instead of other_config
is there another SDN controller connected to your pools? (not necessarily an XO SDN controller) that would override the certificates of XO?
None. I have just done a clean install of Xcp-NG 8.3 beta 2
Are there any XAPI error (in /var/log/xensource.log) when you restart your VM?
I just ran cat /var/log/xensource.log | grep error and got the following :
xapi: [error||376 |xapi events D:exxcfeaxxbxx|xenops] events_from_xapi: missing from the cache: [ 1xx05x9-x65x-xxxxxxx]
Are the certs copied to the xcp-ng hosts in a pool ?
Is there way to delete all SDN certificates from hosts so that new ones are copied automatically ?
Update :
I don't think certificates are at fault. Checked /etc/stunnel/certs and the certificates are same in all hosts
New Error while re-creating VxLAN (this time non encrypted)
xo:xo-server:sdn-controller:ovsdb-client ERROR No result for select {
columns: [ 'name', 'options' ],
table: 'Interface',
where: [ [ '_uuid', '==', [Array] ] ],
host: 'xxxxx-2'
}
I'll try the GRE networks now
I have also noticed that the same host gets 'added' after a while (restarts of VMs on that Host)
2024-04-16T04:23:54.252Z xo:xo-server:sdn-controller:private-network INFO Host added {
privateNetwork: '',
network: 'VxLAN',
host: 'xxxx-2',
pool: 'XXXX'
}
2024-04-16T04:24:33.462Z xo:xo-server:sdn-controller:private-network INFO duplicates of the previous log were hidden { nDuplicates: 2 }
2024-04-16T04:24:39.152Z xo:xo-server:sdn-controller:private-network INFO Host added {
privateNetwork: 'xxx-xxx-xxx-xxx-xxx',
network: 'VxLAN',
host: 'xxxx-2',
pool: 'XXXX'
}
I am unable to connect to VMs using VxLAN.
I am unable to reproduce the exact problem, but sometimes this works:
However, even if the VM is able to connect at start, re-starting the VM without touching/changing any config leads to VM not being able to connect.
I get following errors:
2024-04-15T19:39:59.933Z xo:xo-server:sdn-controller:ovsdb-client ERROR No result for select {
columns: [ '_uuid', 'name' ],
table: 'Bridge',
where: [ [ 'external_ids', 'includes', [Array] ] ],
host: 'xxxxx-1'
2024-04-15T19:41:51.55XX xo:xo-server:sdn-controller ERROR Error in _objectsUpdated {
error: TypeError: Cannot read properties of undefined (reading 'network')
at find (/home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:241:38)
at Array.find (<anonymous>)
at getHostTunnelForNetwork (/home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:241:26)
at SDNController._addHostToPrivateNetwork (/home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:1134:20)
at SDNController._addHostToPrivateNetworks (/home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:1198:18)
at SDNController._hostMetricsUpdated (/home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:994:19)
at /home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:846:22
at /home/node/xen-orchestra/node_modules/lodash/lodash.js:4967:15
at baseForOwn (/home/node/xen-orchestra/node_modules/lodash/lodash.js:3032:24)
at forOwn (/home/node/xen-orchestra/node_modules/lodash/lodash.js:13082:24)
at SDNController._objectsUpdated (/home/node/xen-orchestra/packages/xo-server-sdn-controller/src/index.js:838:11)
at Collection.emit (node:events:529:35)
at Collection.emit (/home/node/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
at /home/node/xen-orchestra/packages/xo-collection/src/collection.js:291:16
at /home/node/xen-orchestra/node_modules/lodash/_createBaseFor.js:17:11
at baseForOwn (/home/node/xen-orchestra/node_modules/lodash/_baseForOwn.js:13:20)
at forOwn (/home/node/xen-orchestra/node_modules/lodash/forOwn.js:33:20)
at /home/node/xen-orchestra/packages/xo-collection/src/collection.js:289:13
at Xapi._processEvents (file:///home/node/xen-orchestra/packages/xen-api/index.mjs:1066:5)
at Xapi._watchEvents (file:///home/node/xen-orchestra/packages/xen-api/index.mjs:1226:14),
object: host_metrics {
uuid: '9xxx',
memory_total: 1xxxx83072,
memory_free: 1xxxx41824,
live: true,
last_updated: '20240413T08:39:XX',
other_config: {}
}
}
When I create a new Private Network, I can choose Encapsulation, Encrypted (or not), MTU etc.
Once the Network is created, it does not show if the Network is Encrypted or not.
Is there any way to know this from CLI ? Or any other way ?