XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XCP-ng 8.3 betas and RCs feedback 🚀

    Scheduled Pinned Locked Moved
    News
    89
    791
    79.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      TheFrisianClause
      last edited by TheFrisianClause

      Well the problem is dat it sometimes goes over IPv4 and most of the time it does not.. It did the samen on 8.2 LTS as well.

      1 Reply Last reply Reply Quote 0
      • T
        TheFrisianClause @moussa854
        last edited by

        @moussa854 This did not help, I have not even enabled IPv6. As I upgraded the 8.2 LTS system to 8.3 Beta 2.

        1 Reply Last reply Reply Quote 0
        • Tristis OrisT
          Tristis Oris @TheFrisianClause
          last edited by

          @TheFrisianClause try with another dns. I have similar problem at some networks.

          T 1 Reply Last reply Reply Quote 0
          • T
            TheFrisianClause @Tristis Oris
            last edited by

            @Tristis-Oris Did it, same problem still. I don't understand why it tries to connect to a IPv6 address while it is not configured on the system.

            1 Reply Last reply Reply Quote 0
            • A
              Ajmind 0 @Ajmind 0
              last edited by

              @Ajmind-0 said in XCP-ng 8.3 beta 🚀:

              I have today upgraded an very old Intel Server (S5520UR) running XCP-NG 8.1 to XCP-NG 8.3 beta with the latest beta ISO:

              Server:

              • Intel S5520UR
              • Dual Xeon E5645
              • 48GB RAM
              • Intel RAID Cotnroller
              • RAID1 73GB SSD for DOM0
              • RAID5 1100GB SAS HDD for Localstorage 2

              As the Server was initially a XenServer 6.5 I had to change the partition layout with

              touch /var/preserve/save2upgrade

              The installation was running smooth, no error message.
              I could manage local via CLI and via SSH but not via XO (commit a2c36) from sources or via Xolite.

              server.enable
{
  "id": "a1886440-588f-4630-86b9-b1e888553a12"
}
{
  "errno": -111,
  "code": "ECONNREFUSED",
  "syscall": "connect",
  "address": "192.168.1.116",
  "port": 443,
  "originalUrl": "https://192.168.1.116/jsonrpc",
  "url": "https://192.168.1.116/jsonrpc",
  "call": {
    "method": "session.login_with_password",
    "params": "* obfuscated *"
  },
  "message": "connect ECONNREFUSED 192.168.1.116:443",
  "name": "Error",
  "stack": "Error: connect ECONNREFUSED 192.168.1.116:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
}

              I could start VMs and they seem to run as expected.

              I have not yet stated to use yum update.

              Today I have updated the host via yum update. Everyting runs smooth, however still no luck in getting a https connection to that host.

              Any advise where I could look into? Wbserver configuration or firewall settings?

              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.

              A 1 Reply Last reply Reply Quote 0
              • olivierlambertO
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Have you enabled IPv6 out of curiosity?

                A 1 Reply Last reply Reply Quote 0
                • A
                  Ajmind 0 @olivierlambert
                  last edited by

                  @olivierlambert

                  No, I have not enabled IPv6.

                  Had the 8.3 beta it enabled by default?

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by olivierlambert

                    No, you had a choice during 8.3 install (IPv4 only, or v4+v6 or v6 only)

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      Ajmind 0 @olivierlambert
                      last edited by

                      @olivierlambert said in XCP-ng 8.3 beta 🚀:

                      No, you had a choice during 8.3 install (IPv4 only, or v4+v6 or v6 only)

                      The was no choice option or dialogue!
                      (I had selected to upgrade the exisiting 8.1 installation.)

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by olivierlambert

                        Ah because of the upgrade then, so your issue can't be related to that.

                        1 Reply Last reply Reply Quote 0
                        • jivanpalJ
                          jivanpal
                          last edited by jivanpal

                          Feedback/comments relating to IPv6 after some usage of beta1 and beta2:

                          • There is no way to configure IPv6 on the management interface via xsconsole, such as if one wants to switch between static configuration, autoconf via RAs, or DHCPv6.

                          • There is apparently no support for IPv6 DNS servers, only IPv4. For example, if I try to add an IPv6 address like fd00::1 or [fd00::1] as a DNS server via xsconsole, there is apparently no change to the configuration. Editing /etc/resolv.conf works to achieve this (e.g. adding the line nameserver fd00::1), but this is known not to persist across reboots.

                          • There is apparently no support for RDNSS (advertisement of DNS servers in RAs rather than via DHCPv6).

                          • The "autoconf" option (available during installation, after choosing IPv6-only or dual-stack, and then being asked which mode to use to configure IPv6 addresses) appears to only be used at installation time to determine values such as the gateway's link-local address, the available address prefixes, and perform SLAAC and DAD, but then the resulting values are hard-coded and don't change according to changes in the environment, such as an upstream change in network prefix. (I will need to do some more testing to really confirm this, but this seems to be the case in my experience.) Compare this to when IPv4 is configured to use DHCP(v4), in which the management interface may have a different IPv4 address at different times, namely if it's assigned a different address by the DHCP server when it attempts to get or renew a lease.

                          • Some repos are unreachable in IPv6-only environments, which I'm aware is already known, and I can get around this by using NAT64 (either with CLAT to perform 464XLAT; or with DNS64), but this fact is currently a blocker for me to move to being IPv6-only.

                          • Speaking of NAT64, this is just a question, I haven't tested or looked into this myself: Does XCP-ng include a CLAT daemon and support for auto-configuring 464XLAT using either the "PREF64" RA option (RFC8781) or resolution of ipv4only.arpa via a DNS64 server (RFC7050)?

                          T BenjiReisB 2 Replies Last reply Reply Quote 1
                          • T
                            TheFrisianClause @jivanpal
                            last edited by

                            @jivanpal I think I have the second option you mention. The yum update command tries to resolve via an IPv6 which is timing out unfortunately.

                            jivanpalJ 1 Reply Last reply Reply Quote 0
                            • jivanpalJ
                              jivanpal @TheFrisianClause
                              last edited by jivanpal

                              @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 a and ip -6 route? If you share the output here, you may want to redact any geographically identifying info in it.

                              T 1 Reply Last reply Reply Quote 0
                              • BenjiReisB
                                BenjiReis Vates 🪐 XCP-ng Team @jivanpal
                                last edited by

                                @jivanpal Thx for your report, I'll reply to you in the dedicated IPv6 thread. 🙂

                                Regards

                                1 Reply Last reply Reply Quote 1
                                • stormiS
                                  stormi Vates 🪐 XCP-ng Team
                                  last edited by

                                  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 🙂

                                  jivanpalJ 1 Reply Last reply Reply Quote 1
                                  • stormiS
                                    stormi Vates 🪐 XCP-ng Team
                                    last edited by

                                    This post is deleted!
                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      Ajmind 0 @Ajmind 0
                                      last edited by

                                      @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.

                                      stormiS 1 Reply Last reply Reply Quote 0
                                      • stormiS
                                        stormi Vates 🪐 XCP-ng Team @Ajmind 0
                                        last edited by

                                        @Ajmind-0 could you open a separate thread so we can discuss your issues in detail there?

                                        A 1 Reply Last reply Reply Quote 0
                                        • R
                                          rmaclachlan
                                          last edited by rmaclachlan

                                          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): unknown

                                          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/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
                                          psafontP 1 Reply Last reply Reply Quote 0
                                          • A
                                            Ajmind 0 @stormi
                                            last edited by

                                            @stormi
                                            https://xcp-ng.org/forum/post/72099

                                            F 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post