XCP-ng 8.3 betas and RCs feedback 🚀
-
@jivanpal I think I have the second option you mention. The
yum updatecommand tries to resolve via an IPv6 which is timing out unfortunately. -
@TheFrisianClause No, my remark is about wanting to resolve any and all DNS queries using a DNS server that is accessible over IPv6 (such as wanting to use Google's 2001:4860:4860::8888 rather than Google's 8.8.8.8, or in my case wanting to use my LAN's DNS server at fd00::1 rather than 10.0.0.1), whereas yours is about your host attempting to connect to IPv6 addresses that it obtained by resolving AAAA queries, despite the host only having IPv4 connectivity.
The behaviour you're observing is definitely odd. Are you sure that no IPv6 addresses are configured? What is the output of
ip aandip -6 route? If you share the output here, you may want to redact any geographically identifying info in it. -
@jivanpal Thx for your report, I'll reply to you in the dedicated IPv6 thread.
Regards
-
I just pushed a new update which fixes an issue with IPv6 and live migration, and also fixes an issue in the format of the stats files XO relies on. This is necessary, but not enough, to fix the stats issue, as Xen Orchestra also needs to be updated so that it can handle the new format.
Note: if you are currently testing Xen 4.17, check the dedicated thread for update instructions: https://xcp-ng.org/forum/topic/8370/xen-4-17-on-xcp-ng-8-3
And if you are not, please come test it
-
This post is deleted! -
@Ajmind-0 said in XCP-ng 8.3 beta
:
...Update 22.02.2023:
Without feedback I have returned this host to XCP-NG 8.1 and from this version I updated via recent ISO to 8.2.1 without any problem.
Access from XO from sources or https no problem.
It seems to be that this old host does not work with 8.3 beta for whatever reason.
Update 23.02.2023:
Just a quick note for a quick test:
Upgraded from the smooth running 8.2.1 towards 8.3 beta, no XO / http /https connection possible. Still only local or via ssh possible.
-
@Ajmind-0 could you open a separate thread so we can discuss your issues in detail there?
-
Updated to latest XCP 8.3 build, however I'm on XOA Premium and that hasn't updated yet so I can't confirm stats restored.
However my issue with NFS speed remains (currently only getting 50MB/s write speed inside VMs or migrating a VM but when I ssh onto the host I can write to the mounted NFS share at 480MB/s)My Bond0 speed is still not registering. Xe pif-param-list shows speed 0, I'm still seeing errors in my xensource.log
[09:44 xcpng-core-3 ~]# xe pif-param-list uuid=13924cb4-288a-b340-e9ac-0034870c2bb5 uuid ( RO) : 13924cb4-288a-b340-e9ac-0034870c2bb5 device ( RO): bond0 MAC ( RO): fe:ff:ff:ff:ff:ff physical ( RO): false managed ( RO): true currently-attached ( RO): true MTU ( RO): 9000 VLAN ( RO): 500 vlan-master-of ( RO): 0f0b3661-03aa-79a3-9592-21c6512e2aff vlan-slave-of ( RO): bond-master-of ( RO): bond-slave-of ( RO): <not in database> sriov-physical-PIF-of ( RO): sriov-logical-PIF-of ( RO): tunnel-access-PIF-of ( RO): tunnel-transport-PIF-of ( RO): management ( RO): false network-uuid ( RO): 2f450b68-035d-77d6-3478-69779015cc4e network-name-label ( RO): Storage host-uuid ( RO): 17cde123-69de-4e13-9306-35ac7d1e25bd host-name-label ( RO): xcpng-core-1 IP-configuration-mode ( RO): Static IP ( RO): 10.10.30.30 netmask ( RO): 255.255.255.0 gateway ( RO): IPv6-configuration-mode ( RO): Static IPv6 ( RO): IPv6-gateway ( RO): primary-address-type ( RO): IPv4 DNS ( RO): properties (MRO): capabilities (SRO): io_read_kbs ( RO): 51259.102 io_write_kbs ( RO): 52415.578 carrier ( RO): false vendor-id ( RO): vendor-name ( RO): device-id ( RO): device-name ( RO): speed ( RO): 0 Mbit/s duplex ( RO): unknown disallow-unplug ( RW): false pci-bus-path ( RO): N/A other-config (MRW): igmp-snooping-status ( RO): unknownFeb 23 09:47:00 xcpng-core-3 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/carrier, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/carrier")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 09:47:00 xcpng-core-3 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/device, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/device")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 09:47:00 xcpng-core-3 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/vendor, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/vendor")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 09:47:05 xcpng-core-3 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/carrier, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/carrier")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 09:47:05 xcpng-core-3 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/device, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/device")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 09:47:05 xcpng-core-3 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/vendor, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/vendor")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A--Edit--
It appears as though that sys/class/net folder doesn't exist for the Bond0 which is why it can't read it, my physical NIC speeds are correct but those folders do exists[09:51 xcpng-core-1 2d00931d-0af4-1ec8-4bca-08d822c6c335]# ls /sys/class/net/ eth0 eth1 eth2 eth3 lo ovs-system vif1.0 vif10.0 vif11.0 vif12.0 vif13.0 vif14.0 vif15.0 vif16.0 vif17.0 vif18.0 vif19.0 vif2.0 vif20.0 vif3.0 vif4.0 vif5.0 vif6.0 vif7.0 vif8.0 vif9.0 xapi0 xapi1 xapi2 xapi4 xapi5 xapi6--Edit2--
I migrated some more VMs onto NFS and the migrations themselves seem to be hard capped at 50MB/s however I am able to get around 250MB/s when testing INSIDE the VM. So I'm not sure if migrations are CPU capped or what's happening there.I also noticed on ifconfig the bond0 doesn't exist either but they appear to be the xapi networks, each numbered xapi network is a VLAN on my Bond0 interface. Looks like xcp-networkd is just looking in the wrong location
xapi4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000 inet 10.10.30.30 netmask 255.255.255.0 broadcast 10.10.30.255 ether 00:62:0b:bf:8f:44 txqueuelen 1000 (Ethernet) RX packets 22114210 bytes 138926062482 (129.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 15131116 bytes 94882708122 (88.3 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -
-
I am also seeing lots of xcp-networkd errors in xensource.log
Feb 23 11:41:17 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/vendor, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/vendor")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 11:41:22 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/carrier, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/carrier")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 11:41:22 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/device, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/device")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0A Feb 23 11:41:22 xcpng-test-01 xcp-networkd: [error||3 ||network_utils] Error in read one line of file: /sys/class/net/bond0/device/vendor, exception Unix.Unix_error(Unix.ENOENT, "open", "/sys/class/net/bond0/device/vendor")\x0ARaised by primitive operation at Xapi_stdext_unix__Unixext.with_file in file "lib/xapi-stdext-unix/unixext.ml", line 90, characters 11-40\x0ACalled from Xapi_stdext_unix__Unixext.buffer_of_file in file "lib/xapi-stdext-unix/unixext.ml" (inlined), line 177, characters 31-83\x0ACalled from Xapi_stdext_unix__Unixext.string_of_file in file "lib/xapi-stdext-unix/unixext.ml", line 179, characters 47-73\x0ACalled from Network_utils.Sysfs.read_one_line in file "ocaml/networkd/lib/network_utils.ml", line 156, characters 6-33\x0AMy bond interfaces in XO report as running at 0 b/s as well.
-
@stormi
Stats seems to work now -
Stats are back after the latest batch of patches.
-
Stats are back in XO after latest XCP-ng 8.3 updates and compiling XO from latest source. That was fast!
-
Great work from both XCP-ng and XO teams
-
@jivanpal No IPv6 addresses are configured on the host, still getting this error when doing
yum updatefailure: repodata/repomd.xml from xcp-ng-base: [Errno 256] No more mirrors to try. http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address" -
@ravenet I did not have any problems with my Mellanox Connect-4 Lx card during upgrades from 8.2.1 (5.0 driver), to 8.3 (5.4 driver), then update to current 8.3 (5.9 driver), and then update to Xen 4.17.3. My card has the 14.32.1010 firmware. It is not used for the management interface. It is used by VMs and continued to keep the same ethernet name and function for the VMs.
-
@TheFrisianClause Please open a separate thread for this, where we'll follow-up (was it you who already had one about this very problem?)
-
By the way, it is OK, and even good, to mention any issues you have with 8.3 here. It's what's this thread is for. However, if you don't see any answers because there are too many different discussions happening at the same time, I advise to open a separate thread and mention it here, so that people can jump there and help there.
-
@rmaclachlan This looks awfully similar to https://github.com/xapi-project/xen-api/pull/5451
-
A new version of xo-lite for XCP-ng 8.3 has been released:
Version:
xo-lite-0.2.0-1.xcpng8.3You can update it like this:
yum update xo-liteFor more information about the changes between version 0.1.3 and 0.2.0, you can consult this link: https://github.com/vatesfr/xen-orchestra/blob/master/%40xen-orchestra/lite/CHANGELOG.md
