[SOLVED] Cannot install windows 2012 R2 on ZFS

[Corwin]

Hello,
On a fresh proxmox VE 4.1, I can't install windows server 2012 r2.
I saw a lot of similar topics with older proxmox version that were solved but in my case the host computer itself is rebooting, not inside this single VM !!! This means all other running VM are lost !
I can see in the console the Loading files message, then the windows logo with the moving dots, then after a few seconds the dots do not move anymore and the PC restarts.

My hardware is HP Proliant ML310e
two discs are used as ZFS raid1 during install <--- this seems to be the root cause : installing from scratch to sda allows OS installation without trouble !!
Bios setting "No-Execute Memory Protection" is enabled

no entry in /var/log/syslog

Any advice to have a successful ZFS installation allowing such OS install ??

I tried :
for disks: sata, ide and virtio
for cpu: host, qemu64, haswell

/usr/bin/systemd-run --scope --slice qemu --unit 100 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=860d7a21-e7f2-4a0c-b2b3-9799fb6ba1cc' -name T-Serv2 -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -no-hpet -cpu 'qemu64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 3500 -k fr -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:afb9985e66f1' -drive 'file=/dev/cdrom,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-virtio0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=36:37:63:65:35:66,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'

Regards,

 

[wolfgang]

Hi,
generell use zfspoolplugin to run vm on zfs.
You try to run the vm on the zfs subvol data.
go to Datacenter -> Storage and add a zfs pool.

 

[Corwin]

Thanks for your reply.
I have unix VM's installed on the local storage area... Anyway, there is already a zfs pool. And I have the same issue if I use storage as 'local' (the default one) or as 'zfs' ... the host computer restarts without any visible message.
I would like to understand what is wrong here, any clue what I need to check ?

 

[wolfgang]

You understand something wrong.

You try to crate an qcow2 on a zfs pool what works id you use not no cache.
But you should use the zfs poolplugin to you zvols and not using raw or qcow2 images on the zfs pool.

 

[mmenaz]

He means something like:

zfs create rpool/zfsdisks
pvesm add zfspool zfsvols -pool rpool/zfsdisks -content images,rootdir -sparse

then when you create a VM, choose "zfsvols" as storage. This way the disks of the vm will not be files on the file system, but volumes, so removing one layer of "cow" stuff.

 

[wolfgang]

Yes and now use the zfsvols as storage

 

[Corwin]

Indeed I checked the zfs pool and selected zfsvols as storage before installing, but still I got a complete reboot of the host while installing. I don't have this issue while installing three different linux OS (eg. debian)
Anyway thanks for your input, but as this is not stable enough, I cannot continue with zfs, I will try to change our requirements.