Search results

Minor problem: I may have mismanaged renaming a new PV server. To upgrade an existing PV host to PV 5.2 I had our network folks assign a new physical computer a temporary name in our campus DNS, then ran a clean PVE 5 install on it. I copied over my VM snapshot files, unpacked and ran one...

Briefly: needing to upgrade our two ProxMox 3.4 hosts to a newer release, I followed the recommendation to back up VMs and save the /etc directory someplace, then pop the install disk in to do a clean install of 4.4. I did this on our backup host and after a couple hiccups and tweaks it is now...

Well, I did it again . . . I didn't pay attention to the major distribution upgrades, and I've got a pair of hosts still on Proxmox 3.4. My recollection from the last time I was similarly neglectful, was I was able to upgrade from 1.9 to 3.2 in one go and just reload my VMs, I'm *assuming* I...

I'll try to be brief - after lots of forum reading I realized that though I was able to use the Proxmox web management client to increase the size of the drive on a Linux KVM, I probably wasn't going to have a quick way to let my Linux OS expand the partition to include the space. It'd be...

From checking the forums it appears that yes, I should be able to migrate KVM virtual machines I am currently running on a Proxmox 1.9 system to one running version 3.1 and simply reload them. (Thankfully I have a backup physical host so I can install 3.1, migrate the VMs, then upgrade the main...

We have been running our main Windows 2008 SP1 production file and license server as a ProxMox VM for some time. Mostly I've been impressed with the performance and the ability to move the VM to another Proxmox host when we needed to. The problem is unreliable booting/restarting of the Windows...

We've been happily running Windows Server 2008 R2 in a KVM with ProxMox as a production file server for quite some time with few problems. Today we found the Win2008 KVM was no longer serving and when rebooted, it would go to a black screen after initially showing the Windows splash screen...

Minor question: Just this morning I finally spotted that I made a typo when naming one of my production VMs running under PVE, i.e. it got named "ee-dept.un.ledu" instead of "ee-dept.unl.edu". I can see that the PVE web client will *let* me simply rename it, and I believe the title is just...

In brief: need informed speculation as to whether a "simple" upgrade of a non-clustered Proxmox server from 1.3 to 1.5 is a straightforward, painless thing or a fiddly operation that will result in big downtime. We originally installed v1.3 to test if it would suit our need for a VM server, and...

I finally got The Man to let me buy a second computer so that I have a "fail-over" Proxmox system where I can run our KVM VMs if something needs work on the main computer. However, our current production server is running ProxMox 1.3, and I just installed V1.4 on the new failover server. Will...

Proxmox 1.3 has been successfully hosting a KVM Linux machine for our website. In running updates on the Proxmox system I see updates "held back" ( proxmox-ve pve-kernel pve-manager qemu-server) and following online suggestions, I tried "apt-get dist-upgrade". Among other things it tells me...

So what I gather from an entire day of searching forums here and elsewhere is that iptables cannot be happy running in the Ubuntu 8.04 template for OpenVZ, because it can't access the modules it wants to have. Since not having a firewall is no way to run a production server, I guess I'm going...