[PVE-User] Windows 10/2016 type doesn't allow more than 2GB RAM

[Eneko Lacunza]

Hi Emmanuel,

El 02/02/17 a las 17:09, Emmanuel Kasper escribió:
>> It seem's Proxmox will fail to start a VM of Windows 10/2016 type and
>> more than 2 GB RAM?
>> I recall something about this in the mailing list, and have changed the
>> type to Windows 8 and it works, but I was surprised this is not yet
>> fixed in non-subscription repo :)
>>
> Which failure do you exactly get ? QEMU refuses to start or Windows BSOD ?
>
> For ostype win7,win8,win10 we pass the same parameters to the qemu
> process, so I am surprised changing the ostype to win8 solves a boot
> problem.
>
Mmmm, seems I was mistaken, as it works now. I had the following issue:

kvm: cannot set up guest memory 'pc.ram': Cannot allocate memory
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 
'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 
'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid 
-daemonize -smbios 'type=1,uuid=4a193ad5-df77-41c7-ba59-468233367cf9' 
-name intranet2 -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 
'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' 
-vga std -vnc unix:/var/run/qemu-server/100.vnc,x509,password -no-hpet 
-cpu 
'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce' 
-m 3072 -k en-us -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:a312cc109af' -drive 
'file=/var/lib/vz/template/iso/virtio-win-0.1.126.iso,if=none,id=drive-ide0,media=cdrom,aio=threads' 
-device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200' 
-drive 
'file=/var/lib/vz/template/iso/SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_Spanish_-2_MLF_X21-22828.ISO,if=none,id=drive-ide2,media=cdrom,aio=threads' 
-device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201' 
-device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 
'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-scsi0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' 
-device 
'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,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=BE:9A:FA:E3:6A:9B,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' 
-rtc 'driftfix=slew,base=localtime' -global 
'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

But this was with only 4GB of RAM (3GB requested for VM). I fixed this 
changing to 2GB RAM. I would expect this to work, but that's another 
issue :)

I have now 20GB of RAM in that server, and increased VM to 8GB, but the 
first time I wrongly typed 80GB, so I mistakenly thought this was 
because of win10/win8 setting.

Thanks a lot and sorry for the noise!

Cheers
Eneko

-- 
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943493611
       943324914
Astigarraga bidea 2, planta 6 dcha., ofi. 3-2; 20180 Oiartzun (Gipuzkoa)
www.binovo.es