@ronan-a I am very interested in implementing XOSTOR on XCP-NG 8.3 in my production environment. Currently running two nodes but I can expand to 3. How can I help to create a stable release of XOSTOR? I am not a developer but maybe I can provide feedback.
Posts
-
RE: XOSTOR on 8.3?posted in XOSTOR
-
RE: XOSTOR and mdadm software RAIDposted in XOSTOR
Going by the documentation didn’t indicate clear to me that it would create an LVM extend (so like a RAID0 or JBOD) and then now I understand redundancy is achieved using the replication.
Thanks!
With two diskfull nodes, would it be recommended to use a factor of 3 replication? Meaning data is on 3 places. And does this guarantee me that data is on both servers, so if one server is struck by lightning the other can HA recover the virtual machines without losing any other data than RAM? And what if in this scenario als one drive of the only running server dies?
-
XOSTOR and mdadm software RAIDposted in XOSTOR
I am using a dual server cluster with both 10x 4TB SSD storage and using mdadm to create a RAID10 volume on top of this where my virtual machines are running of.
Now I am interested in using XOSTOR, by adding one more host. Is it possible to still use mdadm software raid with this solution?
-
RE: VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
@olivierlambert Yes! Live migration is now available and working. Which is great!
-
RE: VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
@olivierlambert The problem with fully installing the tools is our antivirus solution SentinelOne. Simply pausing the agent + reboot gave the XenTools the possibility to install succesfully. After a succesfull installation, enabling the SentinelOne agent again is possible without any other issues regarding the tools or drivers.
-
RE: VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
@olivierlambert I am not using any kind of PCI passthrough, but it seems like the storage device for xcp-ng is not using the correct driver.
This is the result of the migrated CTX servers (now using a different server as example, but the result is the same):
With the test server:
however, just changing the storage driver doesn't seem to work. Any experience or tips with this?
-
RE: VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
Also just tried a warm migration with CTX035001 (also imported from ESXi, like CTX035002) but this doesn't change the ability to live migrate
Output of this VM now is:
[12:05 hxctx05 ~]# xe vm-param-list uuid=60fcb435-4436-5fab-a0f4-00011f534d7a uuid ( RO) : 60fcb435-4436-5fab-a0f4-00011f534d7a name-label ( RW): CTX035001 - Warm migration - (20240418T100016Z) name-description ( RW): 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): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 30066860032 memory-target ( RO): 30064771072 memory-overhead ( RO): 243269632 memory-static-max ( RW): 30064771072 memory-dynamic-max ( RW): 30064771072 memory-dynamic-min ( RW): 30064771072 memory-static-min ( RW): 1073741824 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): <not in database> VCPUs-params (MRW): VCPUs-max ( RW): 6 VCPUs-at-startup ( RW): 6 actions-after-shutdown ( RW): Destroy actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): 7384aa3f-fd71-db2e-2cee-2db7d64068e3 hvm ( RO): true platform (MRW): timeoffset: 7200; device-model: qemu-upstream-uefi; secureboot: false; videoram: 8; hpet: true; viridian_apic_assist: true; apic: true; device_id: 0002; cores-per-socket: 2; viridian_crash_ctl: true; pae: true; vga: std; nx: true; viridian_time_ref_count: true; viridian_stimer: true; viridian: true; acpi: 1; viridian_reference_tsc: true allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO): 1; 2; 3; 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): 230365b3-4916-43bc-8a25-65c000b6937e; a235982c-c51a-4578-82bb-51e8c6d37bed domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): order: cnd; firmware: uefi 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-f7fa3223-2c100800-00000121-0000000f-009c0fab-00000008-00000000-00001000-bc000400-00000000-00000000-00000000-00000000-00000000-00000000-0c000004-00000000-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): 230365b3-4916-43bc-8a25-65c000b6937e affinity ( RW): <not in database> other-config (MRW): xo:base_delta: 8a757bfb-e932-0284-e955-c3dddd5d1d4d; xo:backup:schedule: one-time; xo:backup:job: 68009e5a-fd8f-481f-94e7-ec11b197a2e3; xo:backup:sr: d47ab4ba-7e64-3ad3-e729-6d15719ca26a; xo:backup:datetime: 20240418T10:00:16Z; xo:backup:vm: 8a757bfb-e932-0284-e955-c3dddd5d1d4d; xo:8a757bfb: {"creation":{"date":"2024-04-18T09:20:43.171Z","template":"1c33af1c-e919-418c-ad45-85d7d6fb604a","user":"00b23cda-6f3e-42a0-ac32-8074336f5363"}}; base_template_name: Windows Server 2022 (64-bit); import_task: OpaqueRef:a775fe45-36e8-435f-8919-21dced27a55a; mac_seed: 154ecbda-6194-7f18-15ed-209815894afa; install-methods: cdrom; xo:copy_of: dc82eb93-fae9-4356-bda2-b71d37dd1440 dom-id ( RO): 21 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-min" min="2"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="true"/><restriction field="allow-network-sriov" value="1"/><restriction field="supports-bios" value="yes"/><restriction field="supports-uefi" value="yes"/><restriction field="supports-secure-boot" value="yes"/><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): 20240418T10:01:09Z install-time ( RO): 19700101T00:00:00Z VCPUs-number ( RO): 6 VCPUs-utilisation (MRO): 0: 0.014; 1: 0.019; 2: 0.012; 3: 0.014; 4: 0.012; 5: 0.010 os-version (MRO): name: Microsoft Windows Server 2022 Standard|C:\WINDOWS|\Device\Harddisk0\Partition3; distro: windows; major: 10; minor: 0; spmajor: 0; spminor: 0 PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): 3ff10668-2513-0308-61dc-6cb16eaccd7f networks (MRO): 0/ip: 10.1.3.192; 0/ipv4/0: 10.1.3.192; 0/ipv6/0: fe80:0000:0000:0000:3244:e07f:54d8:e112 PV-drivers-detected ( RO): true other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-xs-batcmd: 1; feature-wuRebootRequired: 1; feature-updatetime: 1; feature-ts2: 1; feature-ts: 1; data-cant-suspend-reason: {"error":{"class":"GenericError","desc":"State blocked by non-migratable device '0000:00:07.0/nvme'","data":{}},"id":"qmp-000245-21"}; feature-static-ip-setting: 1; feature-shutdown: 1; feature-setcomputername: 1; feature-s4: 1; feature-s3: 1; feature-reboot: 1; feature-poweroff: 1; feature-laptop-slate-mode: 1; feature-balloon: 1; data-ts: 1 live ( RO): true guest-metrics-last-updated ( RO): 20240418T10:01:32Z can-use-hotplug-vbd ( RO): unspecified can-use-hotplug-vif ( RO): true 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): 378209165448628250:411053949495876535 hardware-platform-version ( RO): 0 has-vendor-device ( RW): false requires-reboot ( RO): false reference-label ( RO): windows-server-2022-64bit 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 -
RE: VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
@olivierlambert
SRS2022_Test:[12:02 hxctx05 ~]# xe vm-param-list uuid=351b9e5b-c5b8-3893-6942-1bcd58d7c9e1 uuid ( RO) : 351b9e5b-c5b8-3893-6942-1bcd58d7c9e1 name-label ( RW): SRV2022_Test name-description ( RW): 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): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 8592023552 memory-target ( RO): 0 memory-overhead ( RO): 73400320 memory-static-max ( RW): 8589934592 memory-dynamic-max ( RW): 8589934592 memory-dynamic-min ( RW): 8589934592 memory-static-min ( RW): 1073741824 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): <not in database> VCPUs-params (MRW): VCPUs-max ( RW): 4 VCPUs-at-startup ( RW): 4 actions-after-shutdown ( RW): Destroy actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): 7bb85a23-6c56-61f2-45b1-645f913b0419 hvm ( RO): true platform (MRW): timeoffset: -25200; device-model: qemu-upstream-uefi; secureboot: false; videoram: 8; hpet: true; viridian_apic_assist: true; apic: true; device_id: 0002; cores-per-socket: 2; viridian_crash_ctl: true; pae: true; vga: std; nx: true; viridian_time_ref_count: true; viridian_stimer: true; viridian: true; acpi: 1; viridian_reference_tsc: true 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): a235982c-c51a-4578-82bb-51e8c6d37bed domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): firmware: uefi; order: cd 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-f7fa3223-2c100800-00000121-0000000f-009c0fab-00000008-00000000-00001000-bc000400-00000000-00000000-00000000-00000000-00000000-00000000-0c000004-00000000-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): a235982c-c51a-4578-82bb-51e8c6d37bed affinity ( RW): <not in database> other-config (MRW): xo:351b9e5b: {"creation":{"date":"2024-04-17T19:51:42.647Z","template":"1c33af1c-e919-418c-ad45-85d7d6fb604a","user":"00b23cda-6f3e-42a0-ac32-8074336f5363"}}; base_template_name: Windows Server 2022 (64-bit); import_task: OpaqueRef:a775fe45-36e8-435f-8919-21dced27a55a; mac_seed: 8ca53f9c-82eb-d664-4346-74e8e3db8045; install-methods: cdrom dom-id ( RO): 10 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-min" min="2"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="true"/><restriction field="allow-network-sriov" value="1"/><restriction field="supports-bios" value="yes"/><restriction field="supports-uefi" value="yes"/><restriction field="supports-secure-boot" value="yes"/><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): 20240417T20:00:37Z install-time ( RO): 20240417T19:51:44Z VCPUs-number ( RO): 4 VCPUs-utilisation (MRO): 0: 0.008; 1: 0.004; 2: 0.003; 3: 0.003 os-version (MRO): name: Microsoft Windows Server 2022 Standard|C:\Windows|\Device\Harddisk0\Partition3; distro: windows; major: 10; minor: 0; spmajor: 0; spminor: 0 PV-drivers-version (MRO): major: 9; minor: 3; micro: 2; build: 110 PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): f32a601a-840e-98a3-08e3-95fb63acc547; 09eb4ebf-874c-4543-dc17-b57680628684 networks (MRO): 0/ip: 10.1.3.196; 0/ipv4/0: 10.1.3.196; 0/ipv6/0: fe80:0000:0000:0000:8cf2:5497:8793:ed3a PV-drivers-detected ( RO): true other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-xs-batcmd: 1; feature-wuRebootRequired: 1; feature-updatetime: 1; feature-ts2: 1; feature-ts: 1; feature-suspend: 1; feature-static-ip-setting: 1; feature-shutdown: 1; feature-setcomputername: 1; feature-s4: 1; feature-s3: 1; feature-reboot: 1; feature-poweroff: 1; feature-laptop-slate-mode: 1; feature-balloon: 1; data-ts: 0 live ( RO): true guest-metrics-last-updated ( RO): 20240417T20:00:56Z can-use-hotplug-vbd ( RO): true can-use-hotplug-vif ( RO): true 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): 5943050155679112586:446876449901291824 hardware-platform-version ( RO): 0 has-vendor-device ( RW): false requires-reboot ( RO): false reference-label ( RO): windows-server-2022-64bit 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/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3dCTX035002:
[12:03 hxctx05 ~]# xe vm-param-list uuid=e729854b-3956-97ca-c7f0-f2155099bfb2 uuid ( RO) : e729854b-3956-97ca-c7f0-f2155099bfb2 name-label ( RW): CTX035002 name-description ( RW): from esxi 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): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 30066860032 memory-target ( RO): 30064771072 memory-overhead ( RO): 243269632 memory-static-max ( RW): 30064771072 memory-dynamic-max ( RW): 30064771072 memory-dynamic-min ( RW): 30064771072 memory-static-min ( RW): 30064771072 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): <not in database> VCPUs-params (MRW): VCPUs-max ( RW): 6 VCPUs-at-startup ( RW): 6 actions-after-shutdown ( RW): Destroy actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): 13b8a928-e790-e724-2a80-919fd1fe8848 hvm ( RO): true platform (MRW): timeoffset: 7200; device-model: qemu-upstream-uefi; nx: true; acpi: 1; apic: true; pae: true; hpet: true; viridian: true allowed-operations (SRO): changing_dynamic_range; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause; 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): 230365b3-4916-43bc-8a25-65c000b6937e; a235982c-c51a-4578-82bb-51e8c6d37bed domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): firmware: uefi; order: cdn 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-f7fa3223-2c100800-00000121-0000000f-009c0fab-00000008-00000000-00001000-bc000400-00000000-00000000-00000000-00000000-00000000-00000000-0c000004-00000000-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): 230365b3-4916-43bc-8a25-65c000b6937e affinity ( RW): <not in database> other-config (MRW): mac_seed: b5a38321-902b-94c2-9df0-7a62fa53fca0; vgpu_pci: ; base_template_name: Other install media; install-methods: cdrom dom-id ( RO): 22 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="137438953472" /><restriction field="vcpus-max" max="32" /><restriction property="number-of-vbds" max="255" /><restriction property="number-of-vifs" max="7" /><restriction field="has-vendor-device" value="false" /></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): 20240418T10:03:55Z install-time ( RO): 19700101T00:00:00Z VCPUs-number ( RO): 6 VCPUs-utilisation (MRO): 0: 0.712; 1: 0.751; 2: 0.760; 3: 0.730; 4: 0.670; 5: 0.696 os-version (MRO): name: Microsoft Windows Server 2022 Standard|C:\WINDOWS|\Device\Harddisk0\Partition3; distro: windows; major: 10; minor: 0; spmajor: 0; spminor: 0 PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): a61b6a43-9010-4d16-f6f2-dbd115ab63ba; 51ab5bd8-f039-e3cd-2592-99481b2c34ac networks (MRO): 0/ip: 10.1.3.228; 0/ipv4/0: 10.1.3.228; 0/ipv6/0: fe80:0000:0000:0000:4324:f2d3:7183:52db PV-drivers-detected ( RO): true other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-xs-batcmd: 1; feature-wuRebootRequired: 1; feature-updatetime: 1; feature-ts2: 1; feature-ts: 1; data-cant-suspend-reason: {"error":{"class":"GenericError","desc":"State blocked by non-migratable device '0000:00:07.0/nvme'","data":{}},"id":"qmp-000253-22"}; feature-static-ip-setting: 1; feature-shutdown: 1; feature-setcomputername: 1; feature-s4: 1; feature-s3: 1; feature-reboot: 1; feature-poweroff: 1; feature-laptop-slate-mode: 1; feature-balloon: 1; data-ts: 1 live ( RO): true guest-metrics-last-updated ( RO): 20240418T10:04:19Z can-use-hotplug-vbd ( RO): unspecified can-use-hotplug-vif ( RO): true cooperative ( RO) [DEPRECATED]: true tags (SRW): 0350 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): 3441820287309222538:4765684607619708731 hardware-platform-version ( RO): 0 has-vendor-device ( RW): false requires-reboot ( RO): false reference-label ( RO): 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 -
RE: VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
Also after disconnecting the VHD, creating a new similar virtual machine and attaching the VHD, there is no difference in live migration capability or tools version showing up
-
VM's from ESXi, live migration not possibleposted in Migrate to XCP-ng
I am running an proof of concept for the company I work for to migrate 16 of our ESXi hosts to XCP-NG, which I am running at home for years now with great succes.
Importing a couple of virtual machines to the newly created XCP-NG pool went great using the builtin tool of Xen Orchestra.
However, after installing the XenServer tools it still is not possible for me to do a live migration of the migrated virtual machines.The error I am getting is VM_LACKS_FEATURE.
It does however work for newly created virtual machines (Windows Server 2022 and Debian 12)
I did test with the latest XCP-NG tools and with the latest XenServer tools, no difference there.The Windows Server 2022 that does work and has the XenServer tools installed.
The following hints me to a working and not working situation, the machine that does not want to live migrate (imported from ESXi) show up with "Management agent detected" and the newly created server 2022 shows up as "Management agent 9.3.2-110 detected"
Working VM:
Not working VM:
Also in XCP-NG center (I know, not supported):
The option shows
And here the option doesn't show:
Any hints what this can be?
-
RE: Full backup instead of delta after storage migrationposted in Backup
Just came here to ask for a solution as well.
I just moved all machines in my pool with 2 hosts and local storage from host 1 to host 2 and all VM's are creating a full backup instead of a delta backup. Maybe I am doing the migration wrong? (XO --> migrate VM --> select other host) It is in the same pool after all... -
RE: VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
@Danp Exporting to XVA (no compression) does work!
After importing the exported machine, the export of the VHD works on that machine!
I am now doing the same for the 4 other machines to get a 5/5 score.
By the looks of it, this seems to be the solution!
BTW, uploading de XVA in XO didn't work for some reason, it prompts about prepairing and then just stops. Importing via XCP-NG center does work fine however.
-
RE: VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
Full clone/copy via XCP-NG center indeed stuck at 100% (not 99%):
But in XCP-NG center there comes a warning up, result out of range, can this be a clue?
@Danp let me try an XVA export next
-
RE: VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
@olivierlambert I tried a full clone, which also remains stuck at 99%, I can try a clone in XCP-NG Center maybe? I currently have nothing else to migrate to from this machine.
-
RE: VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
Trying in latest commit, no change in result.
This is what the task view looks like couple seconds before it thinks it is ready:
.vhd backup file in SMB target (test target)
Then, couple minutes later, it just seems to give up:
the exported .vhd is also gone:
result of job:
log attached
-
RE: VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
@Danp Has never worked for these VM's, I will look into the logs. Is daemon.log expected to have information about this?
-
RE: VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
@olivierlambert Errors on 79671e6d6, I am now trying commit 5c0b29c51
-
VHD export and (delta) backup stuck at 99%posted in Xen Orchestra
Hi,
I am having a bit of a strange issue;
XCP-NG, current release, XO build from source, latest build.
The problem:
When making a backup or exporting the disk to a VHD, the export in XCP-NG will get stuck at 99%. The backup target will receive the VHD and data is transmitted. After a period of time the created VHD will be removed and XO will give up. The task will stay at 99% in XCP-NG, only be removed after restarting the toolstack.This is how the job looks in XO:
The HTTP connection has timed out seems to be the connection between XCP-NG and XO (XO is a VM on this XCP-NG machine), there is no sign of actually being a network related issue.
What does, and what does not work:
5 VM's which were physical machines and made virtual by using microsoft disk2vhd (Windows 2019 machins). All of these will get stuck at 99%, tools are installed and running, and the vm's perform like expected otherwise.2 VM's which were migrated from Hyper-V (Windows 2022 and Debian 11) do succesfully backup.
1 VM made from scratch on XCP-NG also work (debian 11).
What I tried:
Other backup target (local, fast), no difference.
Converting the original .vhd file in hyper-v to dynamic vhd (was already a dynamic vhd but I figuered I can at least try), also no difference.Any suggestions?
-
RE: Error after Xen Orchestra update | SyntaxError: The requested module 'node:crypto' does not provide an export named 'X509Certificate'posted in Xen Orchestra
@Danp Yes, that was it!
Last update I thougt to find a solution to a different problem bij installing nodejs 17.
Removing version 17, and manually updating to the correct version did fix the issue.Thank you!