[pve-devel] PVE 4 and CPU errors

Alexandre DERUMIER aderumier at odiso.com
Fri Oct 2 11:39:38 CEST 2015


>>1) If a server has Intel, and other has AMD, and i want to do live
>>migration, what will be the best practice of PVE configuration?

cpumodel = kvm64

2) This new patch, will be it available in PVE 3.x?

I don't think . (this need kernel 3.10 and it's not the default on PVE 3.x)



----- Mail original -----
De: "Cesar Peschiera" <brain at click.com.py>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 2 Octobre 2015 11:34:38
Objet: Re: [pve-devel] PVE 4 and CPU errors

So i only need testing it before putting it in a production enviroment. 
Oh thats good, it is wonderful !!!.... congratulations for the great work 
!!!! :-) 

And please, let me to do two questions more: 
1) If a server has Intel, and other has AMD, and i want to do live 
migration, what will be the best practice of PVE configuration? 
2) This new patch, will be it available in PVE 3.x? 

----- Original Message ----- 
From: "Alexandre DERUMIER" <aderumier at odiso.com> 
To: "pve-devel" <pve-devel at pve.proxmox.com> 
Sent: Friday, October 02, 2015 5:03 AM 
Subject: Re: [pve-devel] PVE 4 and CPU errors 


>>>I think that such information will be very util for choose the better 
>>>processor when we create a VM and we want enable live migration with old 
>>>and 
>>>differents processors and not die in the intent. 
> 
> The good news is the now, 
> it'll not die, because the target server will refuse to launch qemu if 
> some 
> vcpus features are not supported :) 
> 
> 
> ----- Mail original ----- 
> De: "Cesar Peschiera" <brain at click.com.py> 
> À: "pve-devel" <pve-devel at pve.proxmox.com> 
> Envoyé: Vendredi 2 Octobre 2015 06:45:45 
> Objet: Re: [pve-devel] PVE 4 and CPU errors 
> 
> Hi Alexandre 
> 
> Since much time ago, i did want to have a list of processor names (as 
> Nehalem, Sandy bridge, Haswell etc.) and his respective models (X7560, 
> etc.). 
> 
> Is there a web link internet with this information?, or 
> Can you or anyone add this information in the wiki of PVE? 
> 
> I think that such information will be very util for choose the better 
> processor when we create a VM and we want enable live migration with old 
> and 
> differents processors and not die in the intent. 
> 
> Best regards 
> Cesar 
> 
> ----- Original Message ----- 
> From: "Alexandre DERUMIER" <aderumier at odiso.com> 
> To: "pve-devel" <pve-devel at pve.proxmox.com> 
> Sent: Thursday, October 01, 2015 9:46 PM 
> Subject: Re: [pve-devel] PVE 4 and CPU errors 
> 
> 
>>>>64 x Intel(R) Xeon(R) CPU X7560 @ 2.27GHz 
>> 
>> It's a Nehalem processor. 
>> 
>> You can't emulate a sandybridge or haswell with this. 
>> 
>> 
>> Note that with proxmox 3.4 it was possible, but bad thing can happen 
>> (crashs,slowdown,...). 
>> In proxmox 4, we have added the qemu enforce option, which check if the 
>> vcpu model is compatible 
>> with physical cpu. 
>> 
>> 
>> ----- Mail original ----- 
>> De: "Gilberto Nunes" <gilberto.nunes32 at gmail.com> 
>> À: "pve-devel" <pve-devel at pve.proxmox.com> 
>> Envoyé: Jeudi 1 Octobre 2015 20:48:24 
>> Objet: Re: [pve-devel] PVE 4 and CPU errors 
>> 
>> 64 x Intel(R) Xeon(R) CPU X7560 @ 2.27GHz 
>> 
>> 
>> 2015-10-01 15:29 GMT-03:00 Alexandre DERUMIER < aderumier at odiso.com > : 
>> 
>> 
>> What is your physical cpu model ? 
>> 
>> 
>> ----- Mail original ----- 
>> De: "Gilberto Nunes" < gilberto.nunes32 at gmail.com > 
>> À: "pve-devel" < pve-devel at pve.proxmox.com > 
>> Envoyé: Jeudi 1 Octobre 2015 19:34:08 
>> Objet: [pve-devel] PVE 4 and CPU errors 
>> 
>> Hi guys 
>> 
>> Sometimes, when I create a VM, and depend on what CPU I choose, ( p. ex. 
>> SandyBirgdge os HosWell), I get the error below: 
>> 
>> Running as unit 112.scope. 
>> warning: host doesn't support requested feature: 
>> CPUID.01H:ECX.pclmulqdq|pclmuldq [bit 1] 
>> warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 
>> 25] 
>> warning: host doesn't support requested feature: CPUID.01H:ECX.xsave [bit 
>> 26] 
>> warning: host doesn't support requested feature: CPUID.01H:ECX.avx [bit 
>> 28] 
>> warning: host doesn't support requested feature: CPUID.0DH:EAX.xsaveopt 
>> [bit 0] 
>> kvm: Host doesn't support requested features 
>> TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice 
>> qemu --unit 112 -p 'CPUShares=1000' /usr/bin/kvm -id 112 -chardev 
>> 'socket,id=qmp,path=/var/run/qemu-server/112.qmp,server,nowait' -mon 
>> 'chardev=qmp,mode=control' -vnc 
>> unix:/var/run/qemu-server/112.vnc,x509,password -pidfile 
>> /var/run/qemu-server/112.pid -daemonize -smbios 
>> 'type=1,uuid=07fd45ca-f300-4338-93a9-0c89b4750fab' -name 
>> Win7-Pro-32bits -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 
>> 'menu=on,strict=on,reboot-timeout=1000' -vga qxl -no-hpet -cpu 
>> 'SandyBridge,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+kvm_pv_unhalt,+kvm_pv_eoi,-kvm_steal_time,enforce' 
>> -m 2048 -k pt-br -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' -spice 
>> 'tls-port=61002,addr=localhost,tls-ciphers=DES-CBC3-SHA,seamless-migration=on' 
>> -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 
>> 'spicevmc,id=vdagent,name=vdagent' -device 
>> 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -device 
>> 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 
>> 'initiator-name=iqn.1993-08.org.debian:01:ab655a2a85b4' -drive 
>> 'file=/mnt/pve/STG-NFS/images/112/vm-112-disk-1.raw,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on' 
>> -device 
>> 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' 
>> -drive 
>> 'file=/var/lib/vz/template/iso/Windows7-All.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' 
>> -device 
>> 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 
>> 'type=tap,id=net0,ifname=tap112i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' 
>> -device 
>> 'virtio-net-pci,mac=02:0B:AE:90:F0:2C,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 
>> 
>> 
>> What is that means???? 
>> 
>> Thanks 
>> 
>> -- 
>> 
>> Gilberto Ferreira 
>> +55 (47) 9676-7530 
>> Skype: gilberto.nunes36 
>> 
>> 
>> _______________________________________________ 
>> pve-devel mailing list 
>> pve-devel at pve.proxmox.com 
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
>> 
>> _______________________________________________ 
>> pve-devel mailing list 
>> pve-devel at pve.proxmox.com 
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> 
>> Gilberto Ferreira 
>> +55 (47) 9676-7530 
>> Skype: gilberto.nunes36 
>> 
>> 
>> _______________________________________________ 
>> pve-devel mailing list 
>> pve-devel at pve.proxmox.com 
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
>> _______________________________________________ 
>> pve-devel mailing list 
>> pve-devel at pve.proxmox.com 
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
>> 
> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
> 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 


More information about the pve-devel mailing list