Recent content by baboo

thanks Tom for the reply.

Good Day, I am running 2.3. Recently the last two weeks I am seeing behavior in my new virtual servers that I have never seen before. I created two new VS that have the heartbleed patch. I have not pateched the proxmox server its self. I use these servers to test applications. The behavior I am...

Tom: thanks! Misunderstood Dietmar's response.

Hi Dietmar, thanks - As I suspected, a restart.

I setup a VM with 2G Ram. I came to realize that I needed 3G Ram. So, I clicked on VM and changed memory to 3G and saved. However, the VM is still using only 2G. Do I need to reboot VM to have change take effect? thanks

Tom: thanks

Tom: hi - its been awhile since we spoke. I don't want to upgrade to 2.0 on that box yet. So, if I change sources.list to support going to 1.9 and then do a dist-upgrade, would that work? BTW: do you have any hourly support contracts. I'm just a one man show with one server. thanks

bump: so if I do 'aptitude update && aptitude full-upgrade' will that screw up the system? Please let me know if that is how I should proceed, as I need to get this server backup. thanks

Dietmar: good to hear from you. Just do a simple aptitude update? Will that fix problem and allow starting of kvm? thanks

I have a site running on: pveversion -v pve-manager: 1.7-10 (pve-manager/1.7/5323) running kernel: 2.6.35-1-pve proxmox-ve-2.6.35: 1.6-7 pve-kernel-2.6.32-4-pve: 2.6.32-28 pve-kernel-2.6.35-1-pve: 2.6.35-7 qemu-server: 1.1-25 pve-firmware: 1.0-9 libpve-storage-perl: 1.0-16 vncterm: 0.9-2...

spirit: thanks for the reply. I think that is a pretty good suggestion. However, I was having other issues as well so I rolled back to 1.9. Now everything is working. thanks for your help

I read on the forum that one individual deleted the VM and re-created and the vnc worked. So, I deleted the VM and sure enought the vnc is working. I am installing the os currently (KVM) and after its done will exit and see if vnc continues to work.