XCP-ng 8.3 public alpha 🚀
-
Do you mean that the VM snapshot space is computing with all disks despite we decided to ignore one? If that's the issue, then it's a XAPI bug/something that we should add in the first place
-
@olivierlambert
Exactly, it looks like the snapshot of the entire VM is always calculated first. If there is enough space then only the selected drive is taken in the backup, if not the Backup is aborted.
In other words, only if you can take a manual snapshot of the VM, XO's backup will then only backup the selected drive.
It would be good if the backup only checked whether there was enough space for a snapshot of the selected drive. -
Okay so it's not on XO, but on XAPI then. @psafont and @BenjiReis I assume it's a basic check in VM.snapshot that's not doing the right computation since we can ignore disk
-
@olivierlambert
Seems like that to me too. Let me know if you found a solution. I leave the test VM on my Xen server so that I can test again at any time. -
@olivierlambert Snapshot is in essence a VDI clone, I don't see any checks being done before the filtering for ignored VDIs is done. And that is done pretty early on, not sure why there are operations affecting virtual block devices from ignored VDIs: https://github.com/xapi-project/xen-api/blob/master/ocaml/xapi/xapi_vm_clone.ml#L416
-
I will try to reproduce it locally with
xeand keeping you posted, thanks! -
Okay so it works with
xe. I'll see with XO doing a backup now. -
I can't reproduce the bug with XO. Here is my test setup @jhansen :
1x VM with 2 disks:
- 1x 10GiB disk on a SR with plenty of space
- 1x [NOBAK] 900GiB local LVM disk (thick) on a 1TiB SR (you can't snapshot the disk without SR disk space failure)
I did a delta backup with XO and it worked.
-
@olivierlambert
I will make a retry of the test.
Is the drive empty or filled with data
If the disk are empty it works for me to. -
@olivierlambert
by the way: which version of XO are you using, not that I am using an older one and that the cause is there.
My drives are also local LVM so should be "Thick" too. -
XOA on
latest -
@olivierlambert
Hello,
I created a new SR and installed a new VM and
installed a new XO.
The last one was definitely the answer.
It's working now, so as far as backup via XO goes.
I tested everything extensively, with different VM, SR and different drive fill levels, all ok.
A manual snapshot won't work, but that's what it is.
My old XO installation, unfortunately I didn't write down the version, was from January. Also, when I reinstalled, I switched from stable to latest as you indicated.
Unfortunately, I can't say whether the pure stable update or the change to latest was the solution.
But the main thing is a happy ending.
Greetings Joerg -
I did some testing with the 8.3 and it all went smooth except for one thing. We did a backup of a VM on 8.3 and if we try and restore it to version 8.2 I get the error
"IMPORT_INCOMPATIBLE_VERSION"which makes sense and it's just a lab system so nothing critical. Is there a way to bring it back to 8.2 or should I update the rest of my lab to 8.3?
-
What kind of backup? Delta should work (CR and warm migration too). Only basic backup with XVAs aren't able to be restored on an older version (like many things in XAPI world, it's only forward compatible)
-
This was a full backup not a delta so that makes sense. I think I need more of my lab servers to be on 8.3 so I can do some more testing. I did not find any issues and nothing broke using it so I need to try harder.
-
Great
In general: go for delta backup. It's faster (by a decent margin) because XVA generation is not really optimized on XAPI side. Even if you compare a first delta (so a "full") vs an XVA, it might be 30 to 50% faster to generate. -
@lawrencesystems said in XCP-ng 8.3 public alpha
:I did not find any issues and nothing broke using it so I need to try harder.
Maybe we should incentivize with a bounty: find bugs in XCP-ng 8.3, get a T-shirt
-
Hello, not sure the unusual behaviour it's XCP-ng or XOA related.
One vm does not show up in the RAM summary.
These are the active VMs on my Intel NUC
This is the RAM summary, vm154 is missing.
Odd but not problematic, just to let you know.
Thanks -
Hmm that's weird indeed
Do you have the exact VM missing in there? If yes, can you show the result of xe vm-param-list uuid=<UUID OF THE MISSING VM>? -
Sure! The missing vm is vm154, the result is below:
[17:25 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): 2001da2e-4107-6863-6bfa-b188ebf12a74; d231f5cc-4cba-e51e-41ea-7e0ac7264faa; 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): 0 memory-target ( RO): 0 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): 24 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): 20230401T10:12:07Z install-time ( RO): 20221126T20:53:47Z VCPUs-number ( RO): 2 VCPUs-utilisation (MRO): 0: 0.020; 1: 0.028 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): 90a43b06-4829-c928-245c-d5aa2ad1d414; 592934a3-8d90-5718-7576-014e5d5ee6b8 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): 20230401T10:12:55Z 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):I will be available for any test.
