Support for Windows failover clustering

masato said:
It worked even if I enabled S2D while keeping it as SATA and IDE, and then changed it to a SCSI HDD.
However, I don't know if it will work if I switch HDDs.
Click to expand...
That sounds good so far. I am not sure how you configured your servers to use the same disk? Can you provide an example of a working config for two servers sharing a virtio disk using S2D? Thanks.
 
thintz3112 said:
That sounds good so far. I am not sure how you configured your servers to use the same disk? Can you provide an example of a working config for two servers sharing a virtio disk using S2D? Thanks.
Click to expand...
1. Create a VM with IDE and SATA disks as shown below.

103308.conf
-----
agents: 1
bios: ovmf
boot: order=scsi0;ide1;net0
cores: 4
cpu: custom-host-fix
efidisk0: local-zfs:vm-103308-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide1: none,media=cdrom
machine: pc-q35-9.2+pve1
memory: 16384
meta: creation-qemu=9.2.0,ctime=1753485521
name: WinSrv01
net0: virtio=BC:24:11:F2:4C:05,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
ide0: local-zfs:vm-103308-disk-9,size=100G,ssd=1,serial=103308-SCSI07
ide2: local-zfs:vm-103308-disk-10,size=100G,ssd=1,serial=103308-SCSI08
sata0: local-zfs:vm-103308-disk-3,size=100G,ssd=1,serial=103308-SCSI01
sata1: local-zfs:vm-103308-disk-4,size=100G,ssd=1,serial=103308-SCSI02
sata2: local-zfs:vm-103308-disk-5,size=100G,ssd=1,serial=103308-SCSC03
sata3: local-zfs:vm-103308-disk-6,size=100G,ssd=1,serial=103308-SCSI04
sata4: local-zfs:vm-103308-disk-7,size=100G,ssd=1,serial=103308-SCSI05
sata5: local-zfs:vm-103308-disk-8,size=100G,ssd=1,serial=103308-SCSI06
scsi0: local-zfs:vm-103308-disk-4,iothread=1,size=200G,ssd=1,serial=103308-SCSI00
scsihw: virtio-scsi-single
smbios1: uuid=1df08132-c6e9-46c0-b2ed-489e57e3c643
sockets: 1
tpmstate0: local-zfs:vm-103308-disk-2, size=4M, version=v2.0
vga: std
vmgenid: 3381b5fc-5447-40c8-8fb6-ab66f1d9a921
-----

103309.conf
-----
agents: 1
bios: ovmf
boot: order=scsi0;ide1;net0
cores: 4
cpu: custom-host-fix
efidisk0: local-zfs:vm-103309-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide1: none,media=cdrom
machine: pc-q35-9.2+pve1
memory: 16384
meta: creation-qemu=9.2.0,ctime=1753485521
name: WinSrv01
net0: virtio=BC:24:11:DF:82:CC,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
ide0: local-zfs:vm-103309-disk-9,size=100G,ssd=1,serial=103309-SCSI07
ide2: local-zfs:vm-103309-disk-10,size=100G,ssd=1,serial=103309-SCSI08
sata0: local-zfs:vm-103309-disk-3,size=100G,ssd=1,serial=103309-SCSI01
sata1: local-zfs:vm-103309-disk-4,size=100G,ssd=1,serial=103309-SCSI02
sata2: local-zfs:vm-103309-disk-5,size=100G,ssd=1,serial=103309-SCSI03
sata3: local-zfs:vm-103309-disk-6,size=100G,ssd=1,serial=103309-SCSI04
sata4: local-zfs:vm-103309-disk-7,size=100G,ssd=1,serial=103309-SCSI05
sata5: local-zfs:vm-103309-disk-8,size=100G,ssd=1,serial=103309-SCSI06
scsi0: local-zfs:vm-103308-disk-1,iothread=1,size=200G,ssd=1,serial=103308-SCSI00
scsihw: virtio-scsi-single
smbios1: uuid=f56e328f-f1fe-4b46-a074-67df8448e164
sockets: 1
tpmstate0: local-zfs:vm-103309-disk-2,size=4M,version=v2.0
vga: std
vmgenid: 8c3fae22-0ad1-4081-a6e6-aa2ec2b1edef
-----

2. Start the VM and install Windows Server, create a Hyper-V cluster, and create S2D.

3. After creation, stop the cluster and shut down both VMs.

4. Change the settings as follows.

103308.conf
-----
agents: 1
bios: ovmf
boot: order=scsi0;ide1;net0
cores: 4
cpu: custom-host-fix
efidisk0: local-zfs:vm-103308-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide1: none,media=cdrom
machine: pc-q35-9.2+pve1
memory: 16384
meta: creation-qemu=9.2.0,ctime=1753485521
name: WinSrv01
net0: virtio=BC:24:11:F2:4C:05,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: local-zfs:vm-103308-disk-4,iothread=1,size=200G,ssd=1,serial=103308-SCSI00
scsi1: local-zfs:vm-103308-disk-3,size=100G,ssd=1,serial=103308-SCSI01
scsi2: local-zfs:vm-103308-disk-4,size=100G,ssd=1,serial=103308-SCSI02
scsi3: local-zfs:vm-103308-disk-5,size=100G,ssd=1,serial=103308-SCSC03
scsi4: local-zfs:vm-103308-disk-6,size=100G,ssd=1,serial=103308-SCSI04
scsi5: local-zfs:vm-103308-disk-7,size=100G,ssd=1,serial=103308-SCSI05
scsi6: local-zfs:vm-103308-disk-8,size=100G,ssd=1,serial=103308-SCSI06
scsi7: local-zfs:vm-103308-disk-9,size=100G,ssd=1,serial=103308-SCSI07
scsi8: local-zfs:vm-103308-disk-10,size=100G,ssd=1,serial=103308-SCSI08
scsihw: virtio-scsi-single
smbios1: uuid=1df08132-c6e9-46c0-b2ed-489e57e3c643
sockets: 1
tpmstate0: local-zfs:vm-103308-disk-2, size=4M, version=v2.0
vga: std
vmgenid: 3381b5fc-5447-40c8-8fb6-ab66f1d9a921
-----

103309.conf
-----
agents: 1
bios: ovmf
boot: order=scsi0;ide1;net0
cores: 4
cpu: custom-host-fix
efidisk0: local-zfs:vm-103309-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide1: none,media=cdrom
machine: pc-q35-9.2+pve1
memory: 16384
meta: creation-qemu=9.2.0,ctime=1753485521
name: WinSrv01
net0: virtio=BC:24:11:DF:82:CC,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: local-zfs:vm-103308-disk-1,iothread=1,size=200G,ssd=1,serial=103308-SCSI00
scsi1: local-zfs:vm-103309-disk-3,size=100G,ssd=1,serial=103309-SCSI01
scsi2: local-zfs:vm-103309-disk-4,size=100G,ssd=1,serial=103309-SCSI02
scsi3: local-zfs:vm-103309-disk-5,size=100G,ssd=1,serial=103309-SCSI03
scsi4: local-zfs:vm-103309-disk-6,size=100G,ssd=1,serial=103309-SCSI04
scsi5: local-zfs:vm-103309-disk-7,size=100G,ssd=1,serial=103309-SCSI05
scsi6: local-zfs:vm-103309-disk-8,size=100G,ssd=1,serial=103309-SCSI06
scsi7: local-zfs:vm-103309-disk-9,size=100G,ssd=1,serial=103309-SCSI07
scsi8: local-zfs:vm-103309-disk-10,size=100G,ssd=1,serial=103309-SCSI08
scsihw: virtio-scsi-single
smbios1: uuid=f56e328f-f1fe-4b46-a074-67df8448e164
sockets: 1
tpmstate0:local-zfs:vm-103309-disk-2,size=4M,version=v2.0
vga: std
vmgenid: 8c3fae22-0ad1-4081-a6e6-aa2ec2b1edef
-----

5. Start the VM and check the Hyper-V cluster status.
 
You must log in or register to reply here.
Top Bottom