test enviorement and windows 2012 R2 hyperv

[tsis]

hello

its posible a test enviorement with proxmox host hipervisor 4.2 v and one virtual machines windows 2012 r2 with hyperv ?


regards

 

[tsis]

hello

its posible a test enviorement with proxmox host hipervisor 4.2 v and one virtual machines windows 2012 r2 with hyperv ?


regards

 

[t.lamprecht]

its posible a test enviorement with proxmox host hipervisor 4.2 v and one virtual machines windows 2012 r2 with hyperv ?

You may have luck with setting the VM CPU as hist and hidden (in the config it woud be "cpu: host,hidden") else hyperV refuses to start at all, but if it then works it's not certain, try it with those options.

 

[tsis]

hello

where the changed? this type off CPU?

 

[t.lamprecht]

I think we do not have that option in the GUI, its a "special" one.

Execute the following command from the shell as root:

qm set 500 --cpu "cputype=host,hidden=1"

Replace 500 with your VM ID.

 

[tsis]

same error

 

[fabian]

Are you running an uptodate version of Proxmox? This feature was introduced in qemu-server 4.0-50 .
Please post the output of "pveversion -v".

 

[tsis]

proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie

 

[t.lamprecht]

Did you restarted the vm (not restart from inside the vm, rather shutdown, then new start)? As else this change does not get applied.

 

[tsis]

shutdown and apply

 

[tsis]

now its ok.

thanks

 

[tsis]

Did you restarted the vm (not restart from inside the vm, rather shutdown, then new start)? As else this change does not get applied.

its ok now

thanks for your help