I don't know about others, but what i did to resolve this problem was CPU downgrade from Xeon E5-2620 v2 to Xeon E5 2620.
Since then, we don't had this error anymore. I would like to know, if this problems exists with latest Intel Xeon v3 CPUs ?
Production server with 4x 2TB RAID10 by LSI 2208
CPU BOGOMIPS: 100795.20
REGEX/SECOND: 1039030
HD SIZE: 29.53 GB (/dev/mapper/pve-root)
BUFFERED READS: 235.59 MB/sec
AVERAGE SEEK TIME: 7.34 ms
FSYNCS/SECOND: 4287.30
DNS EXT: 17.44 ms
DNS INT: 1.35 ms
m.ardito,
Each VM in proxmox has unique ID number. Usually it starts with number 100.
If you have already created few VM, those VMID can be found in the VM list.
For example, in new proxmox installation, if you create a new VM, it will be auto assign with VMID: 100
Next VM will be 101, 102...
Spirit,
I just tried your mentioned method, but it is not working quite well.
I setup allowed IP in <vmid>.conf file , restarted machine and then, i changed IP address in VM (centos 6.5) and i wasn't able to ping "the internet" but this VM was pingable from outside world.
Basically, outgoing...
Thank you for the new update, it rocks.
Is it possible to "assign IP address" to the KVM VM with new firewall feature ?
For example, VM network interface tap101 is allowed to use only 8.8.8.8 address or maybe there is already other options to prevent IP spoofing/stealing ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.