@ronan-a I think it would be a really useful option, hopefully we'll see it in the future. Thanks again for taking the time to answer my questions.
Posts made by David
-
RE: Multiple Volumes Alternate Primary
-
RE: Multiple Volumes Alternate Primary
@ronan-a Thanks for taking the time to explain, it is appreciated. I will have a further read to help my understanding more.
Do you know if it is possible to add multiple XOSTOR SRs so that I have the option of separating disk types e.g. one XOSTOR for NVMe SSD and one for SATA SSD?
-
RE: Multiple Volumes Alternate Primary
Set up a two node cluster, hv-01 & hv-02, created a VM.
With the VM on hv-01
hv-01 shows:
xcp-volume-a5fd7961-af4c-47ed-a24b-99d432330107 role:Primary disk:UpToDate hv-02 role:Secondary peer-disk:UpToDate
hv-02 shows:
xcp-volume-a5fd7961-af4c-47ed-a24b-99d432330107 role:Secondary disk:UpToDate hv-01 role:Primary peer-disk:UpToDate
Migrated VM to hv-02
hv-01 shows:
xcp-volume-a5fd7961-af4c-47ed-a24b-99d432330107 role:Secondary disk:UpToDate hv-02 role:Primary peer-disk:UpToDate
hv-02 shows:
xcp-volume-a5fd7961-af4c-47ed-a24b-99d432330107 role:Primary disk:UpToDate hv-01 role:Secondary peer-disk:UpToDate
It looks like the VMs disk is automagically assigned primary to it's local node, mind blown! Am I reading this right?
-
Multiple Volumes Alternate Primary
This looks really cool, I'm looking forward to testing it. A quick question...
I was wondering in a two node system if there is performance benefit to VMs hosted on a node where the DRBD volume is master and if so can I have multiple XOSTOR volumes using separate disks on each nodes e.g. linstor_group1 / linstor_group 2 where node1 is primary for linstor_group1 and node2 is primary for linstor_group2?
In this case I could organise VM home servers according to where their DRDB master is.
So I guess the questions are:
- Can I have multiple XOSTOR volumes
- Can I have alternate primaries
Thanks
-
RE: Google Auth Fail after after XOA update (From Sources)
@olivierlambert Thanks for the clarification, it is definitely from sources. Apologies I will try to remember!
I'll patch my system a little later today.
Edit: Patched to
Xen Orchestra, commit 6953e
- All good.Thanks, really appreciate the prompt fix!
-
RE: Google Auth Fail after after XOA update (From Sources)
@pdonias Thanks, I'm happy to patch my XOA when you're ready and let you know how I get on.
-
Google Auth Fail after after XOA update (From Sources)
Hi,
We are experiencing problems logging into XOA (from sources) via Google Auth after a recent update:
From Xen Orchestra, commit 996ab to Xen Orchestra, commit 60434
We can see that the Google Auth plug-in has gone from
v0.2.2
tov0.3.0
, the issue was noticed only after a reboot. The browser error is a simple Internal Server Error, and the log shows onlyxo-server[1053]: Cannot read properties of undefined (reading 'id')
.I can log in with a local (non Google Auth) user.
Has anyone else experience this and/or have any troubleshooting suggestions?
Thanks
-
RE: Windows 2016 HVM or PVHVM
Thanks @olivierlambert
I changed the release channel to 'latest' and updated to xo-server 5.64.1
/ xo-web 5.67.0Both now report as being PVHVM with the additional "Management agent 7.2 detected" / "Management agent not detected"
Thanks
-
RE: Windows 2016 HVM or PVHVM
Sorry, I have messed that up a bit!
Hardware virtualization (HVM)
# xe vm-param-list uuid=094095a8-cb25-ff8f-b5bf-818dc6d87448 |grep PV PV-kernel ( RW): PV-ramdisk ( RW): PV-args ( RW): PV-legacy-args ( RW): PV-bootloader ( RW): PV-bootloader-args ( RW): PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: true PV-drivers-detected ( RO): true
Hardware virtualization with paravirtualization drivers enabled (PVHVM)
# xe vm-param-list uuid=b783132d-b76b-ab4d-4a39-a3f23e2cb07c |grep PV PV-kernel ( RW): PV-ramdisk ( RW): PV-args ( RW): PV-legacy-args ( RW): PV-bootloader ( RW): PV-bootloader-args ( RW): PV-drivers-version (MRO): major: 7; minor: 2; micro: 0; build: 1555 PV-drivers-up-to-date ( RO) [DEPRECATED]: true PV-drivers-detected ( RO): true
I am running xo-server 5.59.0, but the appliance itself is pretty old, I probably need to rebuild it from a later version.
-
RE: Windows 2016 HVM or PVHVM
Yes, just really wanting to know why PVHVM is only present in XO after the manual agent install and a confirmation if possible that they're basically the same mode wise just presented differently. There is a discrepancy on the PV driver from that output:
Hardware virtualization (HVM)
PV-drivers-version (MRO): major: 7; minor: 2; micro: 0; build: 1555
Hardware virtualization with paravirtualization drivers enabled (PVHVM)
PV-drivers-version (MRO):
-
RE: Windows 2016 HVM or PVHVM
@olivierlambert said in Windows 2016 HVM or PVHVM:
xe vm-param-list uuid=<VM UUID>
Hardware virtualization (HVM)uuid ( RO) : 094095a8-cb25-ff8f-b5bf-818dc6d87448 name-label ( RW): Windows 2016 (HVM) name-description ( RW): Windows 2016 (HVM) user-version ( RW): 2 is-a-template ( RW): false is-default-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): 2fa90525-468f-b023-f2f7-2c6470e8a853; 2ac06157-9c4e-ed70-3619-80e60f3a7019 snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): 2ac06157-9c4e-ed70-3619-80e60f3a7019 children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 8589934592 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): weight: 256 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): 1ec97d94-47d2-9124-a077-e17f8de52db6 hvm ( RO): true platform (MRW): timeoffset: 3598; videoram: 8; hpet: true; device-model: qemu-upstream-compat; apic: true; device_id: 0002; cores-per-socket: 2; pae: true; vga: std; nx: true; viridian_time_ref_count: true; viridian: true; acpi: 1; viridian_reference_tsc: true allowed-operations (SRO): changing_dynamic_range; migrate_send; pool_migrate; suspend; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause; checkpoint; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO): 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): 8d38c36c-eb67-4823-ba4b-05f60bae9dc9; 65ab2fdc-cc96-4e93-ac00-71dd409b6101 domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): order: c 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: 17cbfbff-f7fa3223-2d93fbff-00000123-00000001-001c0fbb-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): 65ab2fdc-cc96-4e93-ac00-71dd409b6101 affinity ( RW): <not in database> other-config (MRW): import_task: OpaqueRef:5ecfcf41-8da9-4d52-bbe2-e58785ba50ae; xo:resource_set: "ztUeP5XFTVk"; instant: true; base_template_name: Windows Server 2016 (64-bit); mac_seed: 1321ad65-a344-f3e3-7d8a-c35df8d37694; install-methods: cdrom dom-id ( RO): 5 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="true"/><restriction field="allow-network-sriov" value="1"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions> xenstore-data (MRW): vm-data: ; vm-data/mmio-hole-size: 268435456 ha-always-run ( RW) [DEPRECATED]: false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 20200727T00:08:39Z install-time ( RO): 19700101T00:00:00Z VCPUs-number ( RO): 4 VCPUs-utilisation (MRO): 0: 0.022; 1: 0.016; 2: 0.019; 3: 0.021 os-version (MRO): PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): dd170d9e-0e4f-702f-9557-bfec48035265; deeaf63b-e024-a157-51a9-892e4fbb2dcb; 933d8efb-4446-fac0-69fd-bd6063a83d9c networks (MRO): 0/ip: 192.168.52.115; 0/ipv4/0: 192.168.52.115; 0/ipv6/0: fe80:0000:0000:0000:cc6c:b18a:e77c:5847 PV-drivers-detected ( RO): true other (MRO): platform-feature-multiprocessor-suspend: 1; has-vendor-device: 1; feature-suspend: 1; feature-balloon: 1; feature-poweroff: 1; feature-reboot: 1; feature-s3: 1; feature-s4: 1; feature-shutdown: 1 live ( RO): true guest-metrics-last-updated ( RO): 20200727T00:11:46Z 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): aa628084-49b0-c9e5-5230-2bef501300c6 is-vmss-snapshot ( RO): false start-delay ( RW): 0 shutdown-delay ( RW): 0 order ( RW): 0 version ( RO): 2 generation-id ( RO): 2695189925407817237:1100109927073744675 hardware-platform-version ( RO): 2 has-vendor-device ( RW): true requires-reboot ( RO): false reference-label ( RO): windows-server-2016-64bit bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d
Hardware virtualization with paravirtualization drivers enabled (PVHVM)
uuid ( RO) : b783132d-b76b-ab4d-4a39-a3f23e2cb07c name-label ( RW): Windows 2016 (PVHVM) name-description ( RW): Windows 2016 (PVHVM) user-version ( RW): 2 is-a-template ( RW): false is-default-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): 10503218-40dd-5095-c1ec-b434ccfca7f9; ee3328d3-ec85-0efc-f65a-e580b4628681 snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): ee3328d3-ec85-0efc-f65a-e580b4628681 children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 8589934592 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): weight: 256 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): 876eb207-46d5-791a-3ed1-28b0bac3fd50 hvm ( RO): true platform (MRW): timeoffset: 3600; videoram: 8; hpet: true; device-model: qemu-upstream-compat; apic: true; device_id: 0002; cores-per-socket: 2; pae: true; vga: std; nx: true; viridian_time_ref_count: 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; 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): 0; 2; 3; 4; 5; 6 possible-hosts ( RO): 8d38c36c-eb67-4823-ba4b-05f60bae9dc9; 65ab2fdc-cc96-4e93-ac00-71dd409b6101 domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): order: c 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-2d93fbff-00000523-0000000f-019c4fbb-00000008-00000000-00001000-9c000400-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): 65ab2fdc-cc96-4e93-ac00-71dd409b6101 affinity ( RW): <not in database> other-config (MRW): import_task: OpaqueRef:19995e32-87b6-41da-bd55-c3483038c373; base_template_name: Windows Server 2016 (64-bit); mac_seed: 0c225579-5b4a-0983-36dc-c331d27caf31; install-methods: cdrom; auto_poweron: false dom-id ( RO): 36 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="true"/><restriction field="allow-network-sriov" value="1"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions> xenstore-data (MRW): vm-data: ; vm-data/mmio-hole-size: 268435456 ha-always-run ( RW) [DEPRECATED]: false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 20200814T08:38:09Z install-time ( RO): 19700101T00:00:00Z VCPUs-number ( RO): 4 VCPUs-utilisation (MRO): 0: 0.038; 1: 0.026; 2: 0.022; 3: 0.036 os-version (MRO): name: Microsoft Windows Server 2016 Standard|C:\Windows|\Device\Harddisk0\Partition2; distro: windows; major: 6; minor: 2; spmajor: 0; spminor: 0 PV-drivers-version (MRO): major: 7; minor: 2; micro: 0; build: 1555 PV-drivers-up-to-date ( RO) [DEPRECATED]: true memory (MRO): disks (MRO): VBDs (SRO): dfee0252-6edb-a58c-e30f-48ec6d52fcc7 networks (MRO): 1/ip: 192.168.52.10; 1/ipv4/0: 192.168.52.10; 1/ipv6/0: fe80:0000:0000:0000:dccd:43c6:c210:1f9d PV-drivers-detected ( RO): true other (MRO): platform-feature-multiprocessor-suspend: 1; has-vendor-device: 1; feature-suspend: 1; feature-balloon: 1; feature-poweroff: 1; feature-reboot: 1; feature-s3: 1; feature-s4: 1; error: WTSQueryUserToken : 1008 failed.; feature-setcomputername: 1; feature-xs-batcmd: 1; feature-ts2: 1; feature-ts: 1; feature-static-ip-setting: 1; feature-wuRebootRequired: 1; data-ts: 1 live ( RO): true guest-metrics-last-updated ( RO): 20200814T08:43:51Z 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): aa628084-49b0-c9e5-5230-2bef501300c6 is-vmss-snapshot ( RO): false start-delay ( RW): 0 shutdown-delay ( RW): 0 order ( RW): 0 version ( RO): 3 generation-id ( RO): 4915069278103354312:7221504440612414521 hardware-platform-version ( RO): 2 has-vendor-device ( RW): true requires-reboot ( RO): false reference-label ( RO): windows-server-2016-64bit bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d
-
Windows 2016 HVM or PVHVM
Hello,
Any clarification on this would be appreciated.
I have some Windows 2016 VMs that have 'Windows Update tools' enabled, PV drivers are installed onto the system, however in XO the mode is Hardware virtualization (HVM), however if I install the Citrix Management agent, the mode changes to Hardware virtualization with paravirtualization drivers enabled (PVHVM). I have checked the drivers and they are identical, I'm not quite sure why the modes have changed, has the mode changed or has the reporting in XO changed because of the agent install?
Thanks