Recent content by joolsr

Re: update to 1.9 problem : sh: xrealloc: ../bash/general.c:888: cannot reallocate 26 The details are sketchy as it happened a few weeks back now. But after upgrading to 1.9 and the 2.6.32-6 kernel, I too got mysterious lock ups on one of my VM's, with a fairly basic Ubuntu 10.04 server (not...

You can work with these ova files in virtualbox. Then see what hard disks are within the ova file export and use these within proxmox.

Hi I'm running Debian 5 2.6.26.2-686 as a guest on a proxmox 1.8 box. I have this setup # pveversion -v pve-manager: 1.8-15 (pve-manager/1.8/5754) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-32 pve-kernel-2.6.32-4-pve: 2.6.32-32 pve-kernel-2.6.18-2-pve: 2.6.18-5 qemu-server: 1.1-30...

Well uptime is now nearly 4 days far longer than the usual one day or so when the vm would normally hang. Looks like chnaging back to normal vga driver has fixed this - thanks UDO ;-)

After removing vmware from the display, so far its been ok. A bit too early to be certain as yet. Interestingly, the vmware 100% cpu lock up issue is covered here :- https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/553081 Confusingly, people get the 100% cpu...

just a word of warning :- to anyone wanting to use vmware display driver, for at least two of us, using with vm guest of ubuntu lucid, caused 100% cpu lockup isues after about a day of use. So be warned !

Udo, you may have it ! I AM using vga=vmware I changed to this when I upgraded to 2.6.32, as the default graphics arent very good for me. I will try this and keep my fingers crossed ! Many thanks for your help. Whether I keep running KVM 0.13 and pvetest repo I dont know.

sorry i misread your post, did you mean upgrade to 2.6.32 with kvm 0.13, or did you mean 2.6.35 ??? (which i ended up doing ..)

ok i've have upgraded with pvetest repo and am now running with:- vm:/etc/apt# pveversion -v perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = "en_GB.utf8" are supported and installed on...

without upgrading to kvm 0.13, i get vm:~# pveperf perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = "en_GB.utf8" are supported and installed on your system. perl: warning: Falling back to...

I will try kvm 0.13 later; the box is more a dev box at the moment. Any idea why you believe kvm 0.13 might help? After all its a fairly plain ubuntu server on it that has the problem ... pveversion is currently vm:/var/log# pveversion -v perl: warning: Setting locale failed. perl...

Hi I have proxmox running with 1.6 and 2.6.35 kernel. I have 5 VM's that run fine, but one which is proving really problematic. Almost every day it will hang, ie is not reachable from the network or with ssh. The only wait to deal with it is to kill the KVM process. This process will using end...

Yes, I think I understand now. VG and LVM is setup bry default even for a normal directory. I thought I had to set up LVM via the Add LVM in the gui. Perhpas this could be made a little clearer in the docs ? Still a great system though !!;-)

Do i take it then that 2.6.32-2 is still problematic ? I dont have 2.6.32-1 to go to.

If a normal 'Directory' as you call it is really a LVM then it might be better to mention this in the docs/wiki, as it confused me.