The server had high memory usage so I expect lots of paging, which could explain the block writes. I've increased the mem and want to see what difference that makes.
M
Offline
Best posts made by McHenry
-
RE: Large incremental backups
-
RE: Disaster Recovery hardware compatibility
Results are in...
Four VMs migrated. Three using warm migration and all worked. 4th used straight migration and BSOD but worked after a reboot.
-
RE: ZFS for a backup server
Thanks Oliver. We have used GFS with Veeam previously and will be a great addition.
-
RE: Windows11 VMs failing to boot
Thank you so much. If you want me I'll be at the pub.
-
RE: Zabbix on xcp-ng
We have successfully installed using:
rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-latest.el7.noarch.rpm yum install zabbix-agent2 zabbix-agent2-plugin-* --enablerepo=base,updates -
RE: Migrating a single host to an existing pool
Worked perfectly. Thanks guys.
-
RE: from Hyper-V
Our Hyper-V servers have no GUI and the process I use is:
- RDP to the Hyper-V host
- Open PowerShell
- Get a list of the VMs on the host
Get-VM- Stop the VM
STOP-VM -Name <name of VM>- Identify the VM's disk(s) for conversion
Get-VMHardDiskDrive -VMName <name of VM>- Convert the VHDX to VHD (destination file extension sets the type so use ".vhd")
Convert-VHD -Path <source path> -DestinationPath <destination path> -VHDType DynamicTo transfer the newly created .vhd files to xcp-ng we use Putty via the cli
-
RE: from Hyper-V
Either way.
-
If you can have the server offline then shutdown and create the VHD from the VHDX. The process creates another disk file so the original remains unchanged and if it all goes wrong you can simply restart the VM in Hyper-V and try again another day. You will need enough disk space for the original VM & the new VHD file.
-
If the server cannot be offline then export the VM and then convert the VHDX to VHD. The issue being the original will VM still be updated whilst the migration to xcp-ng takes place. You will need enough disk space for the original VM, the exported VM and the new VHD file.
-
-
RE: from Hyper-V
We have a simplified process now.
- Shutdown VM in Hyper-V
- Convert VHDX to VHD using PowerShell
- Move VHD to xcp-ng using SSH
- Generate new name using uuidgen
- Rename VHD
- Create VM in XO and attach VHD
After much trial and error this works every time.
Latest posts made by McHenry
-
Backup schedule
I have configured the following backup schedule:
When looking to restore the oldest backup I have is 1st April which appears to be the quarterly.
The backup logs list backups going back much further in time:
Is there a problem with my schedule as my intent is to keep 1 year of backups, i.e. 4 quarters?
-
RE: Confirming health checks work
Good to know the management agent is not required on FreeBSD (pfSense)
-
RE: Confirming health checks work
@olivierlambert said in Confirming health checks work:
xe vm-param-list uuid=
[07:16 hst100 ~]# xe vm-param-list uuid=57ca2b95-2516-41ea-c2a3-1df02dc9ed4e uuid ( RO) : 57ca2b95-2516-41ea-c2a3-1df02dc9ed4e name-label ( RW): server.cloud - rtr000 name-description ( RW): pfSense 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): 6ac4aa42-5d12-ca8e-aa70-bc5a70e12012; e491e534-8a09-b1c6-e124-9ee18c8d7c48 snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): e491e534-8a09-b1c6-e124-9ee18c8d7c48 children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 1073729536 memory-target ( RO): 1073741824 memory-overhead ( RO): 11534336 memory-static-max ( RW): 1073741824 memory-dynamic-max ( RW): 1073741824 memory-dynamic-min ( RW): 1073741824 memory-static-min ( RW): 134217728 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): <not in database> VCPUs-params (MRW): VCPUs-max ( RW): 1 VCPUs-at-startup ( RW): 1 actions-after-shutdown ( RW): Destroy actions-after-softreboot ( RW): Soft reboot actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): b324db63-c892-09a2-6b34-332732eeebdc hvm ( RO): true platform (MRW): timeoffset: 0; device-model: qemu-upstream-compat; secureboot: false; viridian: true; nx: true; acpi: 1; apic: true; pae: true; hpet: true allowed-operations (SRO): metadata_export; changing_dynamic_range; migrate_send; pool_migrate; checkpoint; snapshot current-operations (SRO): blocked-operations (MRW): pause: true; clean_shutdown: true; suspend: true; hard_shutdown: true; shutdown: true; hard_reboot: true; clean_reboot: true; destroy: true 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): 2; 3; 4; 5; 6 possible-hosts ( RO): cb2ae4d4-6ed4-4790-8739-3cf0c2940c99 domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): firmware: bios; 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: AuthenticAMD; features: 178bfbff-f6f83203-2e500800-040001f3-0000000f-f1bf07a9-00405f4e-00000000-711ed005-10000010-00000020-18000144-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): cb2ae4d4-6ed4-4790-8739-3cf0c2940c99 affinity ( RW): <not in database> other-config (MRW): auto_poweron: true; import_task: OpaqueRef:2d9c20fa-8f3f-ab13-da2e-523397d0311b; mac_seed: aead2513-60f2-c322-af2a-2e2a5b13a0f0; xo:6eb22368: {"creation":{"date":"2025-03-09T05:14:39.610Z","template":"552bce37-51b2-445d-84f2-5f33fa112d7e","user":"a2e57b71-9b1b-4044-b7c6-4199ab307f28"}}; base_template_name: Other install media; install-methods: cdrom dom-id ( RO): 8 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="137438953472"/><restriction field="vcpus-max" max="64"/><restriction field="has-vendor-device" value="false"/><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): 20250710T21:50:55Z install-time ( RO): 19700101T00:00:00Z VCPUs-number ( RO): 1 VCPUs-utilisation (MRO): 0: 0.026 os-version (MRO): netbios-name (MRO): PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): f219ecc9-6986-11ef-901c-e9843e595f19 networks (MRO): PV-drivers-detected ( RO): true other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-suspend: 1; feature-reboot: 1; feature-poweroff: 1 live ( RO): true guest-metrics-last-updated ( RO): 20250710T21:51:20Z can-use-hotplug-vbd ( RO): unspecified can-use-hotplug-vif ( RO): unspecified cooperative ( RO) [DEPRECATED]: true tags (SRW): Backup appliance ( RW): <not in database> groups ( RW): 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): other-install-media 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): pending-guidances-recommended ( RO): pending-guidances-full ( RO) -
Confirming health checks work
I understand Health Checks wait for the management tools to load however I have a device being backed up that does not have these management tools loaded yet still passes.
How is this possible?
-
RE: Windows11 VMs failing to boot
Thank you so much. If you want me I'll be at the pub.
-
RE: Windows11 VMs failing to boot
I deleted a few ISOs and the VM now boots.
So the issue was I was storing ISOs in the root partition and it was full?
