Recent content by unleeshop

Thanks, good to know I'm on right track. What was throwing me was that I would try to COPY the vmid.conf file to the new node, but the command would not work. No error message, just wouldn't "go". But when I did a "move" it moved happily enough. Don't care why, it's all working now. Thanks...

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...

OK, I *was* off on the wrong track. It had everything to do with the thin LVM model, not that I understand why having a thin lvm meant that this data area was basically invisible to me. In any case, by following this procedure exactly, I got my original storage space back the way I need it...

I may be on the wrong track. The web GUI on the server I just upgraded to 4.4 shows, under "storage", that the drive I'm seeing from the command line is a 95Gb "local" drive, but the GUI also shows me an active, enabled, "local-lvm" drive of 812 Gb of type "LVM-Thin" - that's the storage that I...

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...

VERY nice documentation. Excellent! I have the added advantage that besides our main VM host, I am running a backup VM host and can test upgrades on that box first without threatening our production VMs. Thanks!

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...

Thanks for input - I did reboot the Linux OS and also stop/start the KVM, but the Proxmox GUI setting still said the larger number. But because I didn't every succeed in actually expanding Linux into the additional space before shrinking it back down, as far as Linux is concerned nothing has...

Windows update issues caused us to eventually give up on using a ProxMox-based KVM for the department's Win 2008 server and return to dedicated hardware. I just could not be sure that I'd get my server "back" after running a Windows update.

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...