Search results

No, not actually, nothing I can see in the apt-get and aptitude logs previous to updating to -11 or in the one where I did update to it, by explicitly using aptitude to tell it to install kernel -11. I don't mean to complain too loudly since I chose to try running our production servers on a...

OK, changing to kernel 2.6.24-11-pve with aptitude install pve-kernel-2.6.24-11-pve fixed things. Makes me very wary about doing updates.

Apparently it is safe enough ... but I'm feeling kind of dumb. I routinely do updates/upgrades thinking that is the safest way to keep things working, but I find out that 1) aptitude and apt-get never upgraded/updated my kernel 2.6.24-8-pve to 2.6.24-11-pve and 2) if it had upgraded it...

OK, this is making me strongly reconsider how we do our production servers. Both our primary and backup PVE machines mysteriously stopped running VMs and could not restart them until, after hours of reading and experimenting, I did an "aptitude install pve-kernel-2.6.24-11-pve" to change my...

How safe is that to do? I have the same issue with a KVM hanging at the "hit F12" point, and I'm running 2.6.24-8-pve ... If one "downgrades" as you suggest, won't that break other things? And where does that leave you for the longer term ... you can't update/upgrade without hurting your...

OK, got the very same problem here, when trying to use our backup host box to fire up VMs I brought over from our primary host (both are updated/upgraded to latest everything). pvevervsion -v gives me: pve-manager: 1.5-10 (pve-manager/1.5/4822) running kernel: 2.6.24-7-pve...

....aaaaaand it gets worse. Using a qmrestore to bring up my VM101 Win2k8 on my backup hardware PVE machine, it looks just fine in the web interface, every part of every configuration area looks identical to the VM on the main hardware. Looks like the qmrestore has indeed duplicated the VM on...

I do have an earlier snapshot, thankfully, but here's another question: what would have precipitated this? Last night's snapshot, which is done to an NFS share on our backup host, did fail on VM 101, but this morning, BOTH VMs were stopped. 101 would not even try to start until I did the qm...

Yeah, I have a Linux VM (102) and a Windows 2008 VM (101), and they both SAY they have started. The system log as shown in the PVM web interface shows "VM 102 started", (likewise VM 101), and no errors that I can see. But both VMs are using almost no RAM and no CPU time at all, and they...

I had this exact problem. But after unlocking the VMs, they still won't start, and there don't seem to be any errors ... they just don't boot. The memory bar shows them only using about 10 Mb of RAM. Rebooting the whole PVE host doesn't seem to help. I know the drill: look through error...

That sounds reassuring. Thanks! I assume that .... aptitude full-upgrade ... would accomplish the same thing, since the only thing running "aptitude safe-upgrade" leaves out is the distribution update.

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

Hmm, that poses a problem. Because my 1.3 box is a production server, I want to be sure I've got my VMs saved and able to run on the new box before I go upgrading (and potentially breaking) my production box to 1.4. (Which, actually, I see on the forums some concerns that may make me wait a...

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

Wow, that was fast. I guess I'll trust the dist-upgrader. However, since I *will* have my new failover server running in about a week or two and will be doping out how to copy/move VMs over to it, I would kick myself if I got impatient about running that upgrade before I have my KVM (which...

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

Yes, I agree, the ipv6 stuff seems to be keeping me from using shorewall/iptables in the Ubuntu 8.04 pre-configured OpenVZ container supplied by proxmox.