Recent content by bhennigar

I have a KVM with Windows Server 2008R2. Everything runs normally however file copies will occasionally hang for multiple minutes. It happens for both local and LAN copies. The VM itself isn't frozen. RDP is still responsive and I can open applications and files. The Proxmox host is under light...

There is no problem with adding more nodes to a cluster. The new nodes being added should not have any VMs on them prior to adding them.

I would love to see this implemented!

Java 7 u51 has caused many problems for me. I do know that you need to add your servers to the exception list (Java control panel -> security tab). This worked for about a day for me and then hasn't worked since. I've switched everything to use SPICE. Edit: Keep an eye on this thread

This looks fantastic! I will try it out on my test box in the next few days So once I have this set up, I'd continue to use the backup scheduler in the proxmox web console?

I know this may be a little out of date but may I get more information about how your encrypting the backups to removable hard drives?

You could look at CPU units. This thread has some good information http://forum.proxmox.com/threads/889-CPU-questions

This is normal. Are you sure you have the subnet mask the same as the rest of the network? From the proxmox server, can it ping other devices on the network?

I'd first check the boot order. Make sure it's actually booting to the primary hard drive and not a second HD or usb drive.

You're right, the Virtio network is detected as a PCI device, not USB. Did you use the same ISO for the Virti hard drive and Ballooning? It could be that the driver is corrupt. Delete the ISO from proxmox and download the ISO again

Is this a new install? You could try stopping the VM, remove the Virtio network device and then add a new one. I did not have any issues upgrading my virtio drivers 0.1-74 on multiple Windows server 2008R2 servers. This guide may help...

I had that error often in 2.3 and occasionally in 3.0. Since upgrading to 3.1, this error has gone away. Twice I got this error and found that my backup drive was full. I never did find a cause for all of the other failures.

I agree with udo. I've tried changing the hostname and IP addresses post install and found that you can get it working by modifying a few config files but I would occasionally encounter issues where it was looking for the original hostname or IP. When possible, a clean install is the best option.

Migrating VMs can be easy. If the servers are not part of the same cluster, the easiest way to do this is to shutdown the Windows VMs and perform a backup in Proxmox, move the backup files to the 3.1 server and the restore the VMs. You can move the backup files using something like SCP or...