XCP-ng 8.3 public alpha 🚀

olivierlambert

Can you do a xe-toolstack-restart and see if it's better? (this won't interfere with the running VMs)

rRobbie

@olivierlambert said in XCP-ng 8.3 public alpha :

xe-toolstack-restart

Done and it worked now all the VMs are displayed.

[21:24 xcp-ng-1 ~]# xe-toolstack-restart
Executing xe-toolstack-restart
done.

Screenshot from 2023-04-02 21-26-50.png

FYI vm154 memory is now reported.

[21:24 xcp-ng-1 ~]# xe vm-param-list uuid=487b34dd-9437-8c4f-cc90-3c6b28c29e3b
uuid ( RO)                                  : 487b34dd-9437-8c4f-cc90-3c6b28c29e3b
                            name-label ( RW): vm154
                      name-description ( RW): Ubuntu Docker: Cloudflare Tunnel, NextCloud
                          user-version ( RW): 1
                         is-a-template ( RW): false
                   is-default-template ( RW): false
                         is-a-snapshot ( RO): false
                           snapshot-of ( RO): <not in database>
                             snapshots ( RO): d231f5cc-4cba-e51e-41ea-7e0ac7264faa; 2001da2e-4107-6863-6bfa-b188ebf12a74; 63cc7899-db54-548e-7b3a-a9d4c3a93957; 8c2c78bb-a3b5-4010-eda3-dcd3c48b3128
                         snapshot-time ( RO): 19700101T00:00:00Z
                         snapshot-info ( RO): 
                                parent ( RO): 2001da2e-4107-6863-6bfa-b188ebf12a74
                              children ( RO): 
                     is-control-domain ( RO): false
                           power-state ( RO): running
                         memory-actual ( RO): 2147483648
                         memory-target ( RO): 2147483648
                       memory-overhead ( RO): 20971520
                     memory-static-max ( RW): 2147483648
                    memory-dynamic-max ( RW): 2147483648
                    memory-dynamic-min ( RW): 2147483648
                     memory-static-min ( RW): 536870912
                      suspend-VDI-uuid ( RW): <not in database>
                       suspend-SR-uuid ( RW): <not in database>
                          VCPUs-params (MRW): 
                             VCPUs-max ( RW): 2
                      VCPUs-at-startup ( RW): 2
                actions-after-shutdown ( RW): Destroy
                  actions-after-reboot ( RW): Restart
                   actions-after-crash ( RW): Restart
                         console-uuids (SRO): 452ae8c7-c096-5f98-47b9-5da8453b94d0
                                   hvm ( RO): true
                              platform (MRW): timeoffset: 0; secureboot: false; device-model: qemu-upstream-compat; videoram: 8; hpet: true; apic: true; device_id: 0001; vga: std; nx: true; pae: true; viridian: false; acpi: 1
                    allowed-operations (SRO): changing_dynamic_range; migrate_send; pool_migrate; changing_VCPUs_live; suspend; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause; checkpoint; snapshot
                    current-operations (SRO): 
                    blocked-operations (MRW): 
                   allowed-VBD-devices (SRO): 1; 2; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19; 20; 21; 22; 23; 24; 25; 26; 27; 28; 29; 30; 31; 32; 33; 34; 35; 36; 37; 38; 39; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 60; 61; 62; 63; 64; 65; 66; 67; 68; 69; 70; 71; 72; 73; 74; 75; 76; 77; 78; 79; 80; 81; 82; 83; 84; 85; 86; 87; 88; 89; 90; 91; 92; 93; 94; 95; 96; 97; 98; 99; 100; 101; 102; 103; 104; 105; 106; 107; 108; 109; 110; 111; 112; 113; 114; 115; 116; 117; 118; 119; 120; 121; 122; 123; 124; 125; 126; 127; 128; 129; 130; 131; 132; 133; 134; 135; 136; 137; 138; 139; 140; 141; 142; 143; 144; 145; 146; 147; 148; 149; 150; 151; 152; 153; 154; 155; 156; 157; 158; 159; 160; 161; 162; 163; 164; 165; 166; 167; 168; 169; 170; 171; 172; 173; 174; 175; 176; 177; 178; 179; 180; 181; 182; 183; 184; 185; 186; 187; 188; 189; 190; 191; 192; 193; 194; 195; 196; 197; 198; 199; 200; 201; 202; 203; 204; 205; 206; 207; 208; 209; 210; 211; 212; 213; 214; 215; 216; 217; 218; 219; 220; 221; 222; 223; 224; 225; 226; 227; 228; 229; 230; 231; 232; 233; 234; 235; 236; 237; 238; 239; 240; 241; 242; 243; 244; 245; 246; 247; 248; 249; 250; 251; 252; 253; 254
                   allowed-VIF-devices (SRO): 1; 2; 3; 4; 5; 6
                        possible-hosts ( RO): 21525f67-3cf4-487d-831f-5854937b6647
                           domain-type ( RW): hvm
                   current-domain-type ( RO): hvm
                       HVM-boot-policy ( RW): BIOS order
                       HVM-boot-params (MRW): order: cdn; firmware: bios
                 HVM-shadow-multiplier ( RW): 1.000
                             PV-kernel ( RW): 
                            PV-ramdisk ( RW): 
                               PV-args ( RW): 
                        PV-legacy-args ( RW): 
                         PV-bootloader ( RW): 
                    PV-bootloader-args ( RW): 
                   last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 1fcbfbff-c7f82223-28100800-00000101-0000000f-21940283-00400104-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000
                      last-boot-record ( RO): ''
                           resident-on ( RO): 21525f67-3cf4-487d-831f-5854937b6647
                              affinity ( RW): <not in database>
                          other-config (MRW): base_template_name: Ubuntu Focal Fossa 20.04; import_task: OpaqueRef:dc23a094-507e-0ce1-a85a-b682e92ae279; mac_seed: a64f498f-a65c-48f0-aa88-293527fca70d; install-methods: cdrom,nfs,http,ftp; linux_template: true
                                dom-id ( RO): 25
                       recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="false"/><restriction field="allow-gpu-passthrough" value="1"/><restriction field="allow-vgpu" value="1"/><restriction field="allow-network-sriov" value="1"/><restriction field="supports-bios" value="yes"/><restriction field="supports-uefi" value="no"/><restriction field="supports-secure-boot" value="no"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions>
                         xenstore-data (MRW): vm-data/mmio-hole-size: 268435456; vm-data: 
            ha-always-run ( RW) [DEPRECATED]: false
                   ha-restart-priority ( RW): 
                                 blobs ( RO): 
                            start-time ( RO): 20230402T17:49:46Z
                          install-time ( RO): 20221126T20:53:47Z
                          VCPUs-number ( RO): 2
                     VCPUs-utilisation (MRO): 0: 0.031; 1: 0.030
                            os-version (MRO): name: Ubuntu 22.04.2 LTS; uname: 5.15.0-69-generic; distro: ubuntu; major: 22; minor: 04
                    PV-drivers-version (MRO): major: 7; minor: 30; micro: 0; build: 1
    PV-drivers-up-to-date ( RO) [DEPRECATED]: true
                                memory (MRO): 
                                 disks (MRO): 
                                  VBDs (SRO): 592934a3-8d90-5718-7576-014e5d5ee6b8; 90a43b06-4829-c928-245c-d5aa2ad1d414
                              networks (MRO): 0/ip: 192.168.1.54; 0/ipv4/0: 192.168.1.54; 0/ipv6/0: fe80::d46f:f4ff:fe46:10c1
                   PV-drivers-detected ( RO): true
                                 other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-vcpu-hotplug: 1; feature-suspend: 1; feature-reboot: 1; feature-poweroff: 1; feature-balloon: 1
                                  live ( RO): true
            guest-metrics-last-updated ( RO): 20230402T19:24:54Z
                   can-use-hotplug-vbd ( RO): unspecified
                   can-use-hotplug-vif ( RO): unspecified
              cooperative ( RO) [DEPRECATED]: true
                                  tags (SRW): 
                             appliance ( RW): <not in database>
                     snapshot-schedule ( RW): <not in database>
                      is-vmss-snapshot ( RO): false
                           start-delay ( RW): 0
                        shutdown-delay ( RW): 0
                                 order ( RW): 0
                               version ( RO): 0
                         generation-id ( RO): 
             hardware-platform-version ( RO): 0
                     has-vendor-device ( RW): false
                       requires-reboot ( RO): false
                       reference-label ( RO): ubuntu-20.04
                          bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; baseboard-manufacturer: ; baseboard-product-name: ; baseboard-version: ; baseboard-serial-number: ; baseboard-asset-tag: ; baseboard-location-in-chassis: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d
                     pending-guidances ( RO): 
                                 vtpms ( RO):

Thank you for your help, if it counts as bug it is a small one: so far 8.3 alpha has been super-solid.

mdavico

Is it possible to take a snapshot with usb passthrough in version 8.3?

exetico

@mdavico Are you asking if it's possible to get one processed, even though a USB passthrough are currently enabled/active on the KVM, or? I think you need to be a bit more precise.

exetico

I'm jumped on XCP-ng 8.3 on my bleeding edge ODROID H3+. Are there any plan to support the build in sensors in the host system at some point, so it's possible to get CPU package temperature readouts? Right now, I've not been able to make any readouts from the host-machine, where I've tried a few sensor terminal tools .

mdavico

@exetico I mean when you passthrough a usb, when you want to take a snapshot it gives the error VM_HAS_VUSBS(OpaqueRef:aedd32dc-6dec-4be1-aa5d-9dda799c01b2) and as in version 8.3 you can exclude certain vdi, possibly also a VUSB, that's what I mean

ashceryth

Has anyone tried installing 8.3 on a NUC12 yet? I'm about to buy a (maybe 2) NUC12 i5 (1240P) to replace my old tower servers at home. How does XCP-ng handle the hybrid architecture?

andSmv

@ashceryth XCP-ng is based on Xen 4.13, so I'm quite sure it doesn't handle Intel Hybrid architecture. I'm not even sure there's ongoing efforts on this support in Xen Project Community.

Moreover, after a very quick check, I didn't see the trace of ARM big.LITTLE support in recent XEN.

I think this kind of features needs the profound analysis how exactly is to be mapped on hypervisor based platforms. And I think the response is not obvious at all.

olivierlambert

Yes, it will simply explode if you have both cores types enabled at the same time. You will need to disable E or P cores (your choice).

The main reason is a really poor design choice from Intel, with those cores designed with similar functions doing different things. Nobody in the virt world want to deal with those.

ashceryth

Thanks, for your comments! That is basically what I was expecting.

exetico

@mdavico Saly, I also get a VM_HAS_VUSBS(OpaqueRef:***/removed/**) error message in 8.3, if I have a ongoing passthrough.

I'm not sure if it's the same thing with backups. If it is, that's problematic. One of my instances needs the USB Passthrough, but I need the rolling backup.

mdavico

@exetico tested with virtualbox and it is possible to take a snapshot with VUSB

MrJroen

@ashceryth I installed the alpha version (8.3) on a Intel RNUC12WSKI70000 a few months ago without any issue. Worked like a charm, no custom mods needed. When the official 8.3 release is available I will reinstall from scratch just to make sure its still compatible/working.
Better to use the supported hardware of course but I like the sizes of the NUC's

Edit: I need to look into the hybrid part of the question. I'm not familiar with this at the moment so not sure what the implications are from that standpoint. Anyway, seems like the experts above already provided an answer on this one.

stormi

A new batch of updates for XCP-ng 8.3 alpha arrived.

It's been a while: one specific update I wanted to push together with everything that was ready gave us more trouble than expected, but now it's solved and so I pushed all the updates at once.

Main changes

xcp-ng-release*: updated repository definitions in /etc/yum.repos.d/xcpng.repo, to add more testing repositories (disabled by default. More about this here - look for "About the new testing repositories"). Warning: If you have any local changes to this file, it won't be overwritten. In this case, look for /etc/yum.repos.d/xcpng.repo.rpmnew after applying the update, and move it over xcpng.repo. This won't change much for you as testers of XCP-ng 8.3, because we're still pushing the updates directly to xcp-ng-base when they are ready for your testing, but there might be the occasional experimental package in some other location - and the updated .repo file with make it easier to pull from there if needed.
AMD and Intel microcode updates (not the very latest yet, though)
sm (Storage Manager) ported to python 3 by XenServer, and we rebased our additional storage drivers on it
XAPI and related components
- HTTP to HTTPS redirection on the host's web page.
- lots of changes from upstream. Full changelog.
IPv6 support added to xha and xsconsole. You'll need to wait for an updated installer in order to test this and the rest of IPv6 support for the management interface.
memtest86+ updated to 6.20 to support EFI hosts and more hardware. Will be available in the installer.
xen: better hardware support (Ryzen...), security fixes, bug fixes...
Other updates synced from the preview release of XenServer 8.3.
zstd 1.5.4 (1.5.5 soon)
removed corosync and dlm from installed systems. They were unneeded dependencies for XenServer's clustering support, which is proprietary and thus unsupported on XCP-ng. Let's trim dom0 down slightly.

We also continued our work on the installer and on automating the build of installer ISO images. We'll have new builds for you shortly.

How to update

From an installed XCP-ng 8.3 alpha, just run yum update, and reboot. The usual update rules apply: master host first, etc. Check https://xcp-ng.org/docs/updates.html. I haven't tested it on this update, but XOA's Rolling Pool Update should work on this update.

What to test

Depending on the time available, it goes from "just update and check things still work as expected" to "test everything you can think of", with an intermediate step of "test specific features which are important to you".

exetico

@stormi Thank you!

Are there any planned work related to hot backups of VM's, where a USB device are attached? It's currently not possible.

In the weekend I ended up moving a single container to a alpine image, so I could continue backing up my primary docker VM. But I was hoping to have rolling backup of the alpine VM, too

https://xcp-ng.org/forum/post/61091