XCP-ng 8.3 betas and RCs feedback 🚀
-
@BenjiReis It's a clean install never had an old version on it. Also it is very able to be reproduced.
-
@john-c Okay thanks, and are confident in your IPv6 DHCP server etc?
I can't reproduce the issue on my infra and the logs doesn't help much.
-
@BenjiReis I'm confident of the DHCP server as it's the same as the one, used by the laptop which the posts are being made on is connected to. Additionally I can use the IPv6 address for another device with a web interface (iLO) and still access it successfully, also the other device is running Cockpit to enable over web browser administration and that system is configured for IPv6 only. Additionally that other device is able to obtain an IPv6 address successfully as well as configure its DNS via DHCP. It's running CentOS 7 but planning transition to possibly Rocky Linux 8 or Ubuntu Linux 20.04 Server.
-
@john-c Are you certain that the IPv6 address+DNS configuration obtained on your laptop + CentOS-machine is actually from DHCP and not from SLAAC?
Can you send the the IPv6-address you got on your laptop? (Possibly only the last 64 bits if not comfortable sending the entire IP)
-
@Dennis-0 Yes I can be certain. As the laptop OS (Windows 10) though later to go Linux. It allows you to configure the automatic IP assignment protocol used. In this case it was set to "Automatic (DHCP)", the option can be set to that or manual. The manual option is another way of saying Static IP address.
39b5:5b18:bfa2
-
@john-c
I'm not entirely sure I understand your writing correctly, but be aware that "Automatic (DHCP)" can mean both SLAAC and DHCP. DHCP can't stand alone on the network - SLAAC is also needed for route announcement, so you either get defaultroute/address/DNS from SLAAC only or SLAAC+DHCP. Never DHCP alone.Although it is by no means a bulletproof "method", the address part of the last bits of your IP seems a bit too "random" compared to a DHCP-based address - at least from my experience. In the networks I've seen it looks more like DHCP tends to give out more sequential addresses like ::1000:1044.
You've posted a screenshot further up which has two IPv6-addresses assigned. Both a ULA and a GUA. They are almost definitely SLAAC-based as they both have the last 64-bits in common and looks like EUI64-based. Do you get addresses from both subnets on your laptop too?
What kind of router do you have on your network? Is it some Busiess-grade Cisco, Juniper etc. or i.e OpenWRT which defaults to announcing a ULA-network (not that others can't, but not that typical AFAIK).
-
Please tell me, is it true that machines from 8.3 are not copied to 8.2 ?
Copied some machines from 8.2 to 8.3, but does not copy back. -
@alex821982 Yes, migration to a lower release is not possible. However you can replicate them using Xen Orchestra's replication feature, which is a way to workaround this constraint.
-
@stormi Thanks, it works that way)
-
Replication or warm migration will work, indeed
-
Copied, I get the following error when starting up
FAILED_TO_START_EMULATOR(OpaqueRef:1286de32-6c5a-4e51-b85c-794e66b4d3f7, varstored, Daemon exited unexpectedly)
-
@alex821982 Interesting. There have been changes in UEFI handling in 8.3, but the daemon failing to start when copied back to 8.2 is unexpected. We'll try to replicate this in our lab. If we can't, we'll ask you for more logs.
-
@alex821982 Is Secure Boot enabled for this VM in Xen Orchestra? If so, can you try disabling it?
-
@stormi
No is not enabled. I don 't use this option on any machines at all ) -
@alex821982 What's the operating system on the VM?
-
@stormi
This is a XOA machine on Ubuntu 22.04 -
Went to restart my Server to test my vApp loading, and it didn't actually reboot. The Splash screen cam up as if it was shutting down, and then just stood there.
I was able to access XO Lite, and saw this task just stuck there, obviously for 13 minutes.
Had to hard reboot, and will check to see if any updates available (probably been a couple days since I checked). If so, I'll try again and report back.
UPDATE: No Updates Found. Attempted another reboot. This time it worked. Not sure what locked it up the previous time.
-
@seanmcg182 I know I am a bit late but have you tried to press ESC on the spalsh screen, usually you should then see kernel/systemd messages and see which task may have hung there. Just for the next time when it occurs.
-
Yes, that's the usual thing, especially if you have a VM on the same host that is hosting your ISO SR for example (in NFS). The VM will be shutdown, and the NFS will stop answering, and the reboot will be stuck until the timeout is reach (10 minutes?). That might explain why it takes so long to reboot
-
@bufanda I appreciate the response. I did not know/try that, but I will keep it in mind if it happens again.
