Search results

Are you running the new driver versions? i've seen a few posts about issues with these... also what versions of PVE are you running? Im not sure whether version 2.2 has the new drivers but 2.3 definatly has them.

i thnk we'd need a bit more information about the physical servers and virtual machine that you're migrating.

AFAIK - using cpu=host basically gives you're VM complete access to the CPU. All i can suggest is that you look at these two pages: https://pve.proxmox.com/wiki/Allow_Guests_Access_to_Host_CPU http://www.linux-kvm.org/page/Tuning_KVM

What version of PVE are you running? have you seen this: http://forum.proxmox.com/threads/11347-HowTo-Enable-console-login-for-OpenVZ-Debian-containers-%28V2-2-and-later%29

what about if you just use the Cpu=host option?

I've just tried this with a Windows 2003 KVM and adjusting it from 1000 - 2000 - 10000 - 100000 - 200000 made no difference to CPU performance and also the vzcpucheck showed no difference - it always showed 1000 usage. (The KVM was shutdown, and the .conf file was edited, saved and the KVM was...

So basically you are comparing a single core from a 3 year old Xeon 1.73Ghz CPU vs a single core from an i5? Which i5 are you using? In my experience with i5s and Xeon CPUs the figures look correct.

I run mostly windows KVMs on my proxmox cluster all from a SAN (MD3200i) - is it worth running regular defrags on these KVMs as they are really all loaded up from 6 disks in the SAN anyway? Surely the data pattern on the virtual disk once its been separated across a RAID array and then a virtual...

have you tried memtest on the box? could there be any faulty hardware on the 2950?

I had this same issue - had to restore from backup to get a stable machine back. An no - i'm running an older version of proxmox - that i've not had any isses with and want to keep working :D (its production so cant afford any downtime)

Surely for fencing to work correctly you will need 3 nodes or do you have a quorum disk?

you need to create a new line with size: 4096 or size: 2048 see this in the wiki: https://pve.proxmox.com/wiki/VZDump

Whats the machine's physical hardware? Does it have virtualisation enabled in BIOS?

does it still do it with only one core? My x64 has had the same issue with 1s4c and 2s2c.

it *could* be a dodgy install CD - check the MD5 - i've had it a couple of times and its given random errors during the install.

So since migrating to the NetApp box Proxmox crashes? Anything in the syslogs?

What device is providing your NFS share? if all 3 boxes are doing it, it either points to switch, cabling or NFS device.

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE Probably the best place to start. I've used clonezilla to migrate most of my servers.

Something SOOOO wrong with that expression... Dev's who wont try new things :S:S:S:S My Dev team love Proxmox!

i suspect you will still need to use multipath-tools and have a similar multipath.conf as the one on the iSCSI multipath. in the end i paid Proxmox to setup the multipathing correctly - it might be woth you doing the same if you cannot find out how to do it otherwise.