Search results

Hello, I'm trying since hours to get a Proxmox cluster working, but every time I try to add my second node to the cluster, it fails while waiting for quorum. Because my provider does not allow multicast traffic, I needed to create a VPN to get this working - also tested it successfully with...

I just an guess. I think because the virtualization itself and because VMware ESXi itself also needs some ressources. In my opinion Proxmox is much smarter. Just be happy, that it's faster :)

My 4x 2012R2 machines are also working fine without any issues. I used VIRTIO and HOST as CPU setting.

Check your /etc/hosts file and do "apt-get install -f" again. Then it should work. http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Check_.2Fetc.2Fhosts Or post your /etc/hosts here.

Commands for Squeeze 6 are working with a high chance also on Debian Wheezy 7. Did you set in the OVH manager, that your server is using the kernel from your harddisk instead the OVH kernel?

As I know Proxmox does not have SNMP, but you could use the Proxmox API to get nearly any kind of data: http://pve.proxmox.com/wiki/Proxmox_VE_API API-docs are available at: http://pve.proxmox.com/pve2-api-doc/

Did you installed a clean Debian Wheezy and used the installation manual on http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy? I have the EX40 from Hetzner and it's always running without any issues.

I'm with the same mind as dietmar. Who is testing Proxmox on servers - like you - mostly have enough experience with Shell scripting or with using Google, to do it themself. Else there are thousands of Linux/Bash boards in the WorldWideWeb, to ask for help there. Or someone uses the board-search...

When the kernel isn't the latest one, it does not mean, that it's not maintained anymore. The OpenVZ containering does only work on 2.6.32 - there is no newer kernel version from the OpenVZ team. More to OpenVZ & the "old kernel" you can read on: http://openvz.livejournal.com/45647.html I also...

I also thought so, but my images with qcow2 just have a size about ~15 GB, but the total harddisk size of the VM is 50 GB.

Maybe this may help you: http://kashyapc.wordpress.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/

Found something interested about the qcow2 size limit on Google (in the first three results!): http://rwmj.wordpress.com/2011/10/03/maximum-qcow2-disk-size/ I guess you never would use the total possible size of 9.223.372 TB on one harddisk-file :)

qcow2 is the file system from KVM itself and vmdk from VMware. I found a nice site, describing qcow2: http://fedoraproject.org/wiki/Features/KVM_qcow2_Performance It's up to you, which one you want to use. I don't think, that there is a big performance difference. For example if you have VMware...

Sadly no. Maybe you can get some free ressources for a Windows XP machine - XP does not need so many ressources. Does the virtual machine itself use so many CPU or HDD ressources or does just the host use so much?

Hi philwild, you don't have to submit your server IDs, when you buy Proxmox. After you bought your Proxmox subscription you just get a subscription key, which you'll need to enter in the "Subscription" tab of Proxmox. You can buy one 2x sockets subscription or total two 1x CPU subscriptions -...

Which Windows Server version you have? Try R1 or R2 - maybe it's a Windows related issue? You could try other Windows versions like XP, Windows 7/8. Is the CPU usage in the VM also so high as on the host machine or just terrible slow?

I have four Windows Server 2012 R2 running on my server (with the latest virtio driver) and don't have any high load you experience. Try to change the CPU-type (e.g. host - what I currently use). Does a clean-installation of WS2012 also have such a high latency?

I don't know any tutorial about this topic, sorry. Maybe you can take a look in the Proxmox wiki. For example: Give the OpenVZ machine the internal IP address 192.168.1.2 and redirect the port 1122 from the host to port 22 on the virtual machine with iptables: iptables -t nat -A PREROUTING -d...

You can't use the same IP for two machines (for your host and for a VPS). You need an own dedicated IP address for it. The only solution I know is to give the OpenVZ VM an internal IP address and example forward the port 22 with iptables to the VM in the background.

It seems to be a wrong entry in the /etc/fstab file I guess. Boot in a recovery mode and try to fix it manually. The best and easy method would be - how dduh said - to completely reinstall your machine.