Recent content by eislon

Ok, well I just have to try and install all the same software to a identical vm and see with each software package added when this happens. Thanks for your help.

No no special application running, but will build a test vm as this one is and look if it will behave the same way! However I still think it is strange that I dont see it in the vm, this means that the proxmox host is doing stuff for the vm so it should show on the host processes then!

I upgraded my cluster from proxmox 4.2 to 4.3 and I see on one vm a difference in the usage of the cpu! In the GUI of proxmox it shows me 7,xx% usages of the cpu while in the vm I just have 0.7% cpu usage. that is a big difference. I dont see it with my other vm's! it is an LXC container, but I...

I also have seen the same issue, but I killed the process, then the load was returned to normal. Have to watch if it happens again.

The new lxcfs doesnt do the job for me either, however the converted openvz to lxc having no problems with the backup. The other is a new created LXC, so I will make some new containers and try to backup them again! With the STOP action as a backup works on that lxc container!.

I also have this problem, I normally backup to NFS but due to this problem I put a local disk on it and did backups, indeed the first backup seems ok, but also on local storage the backup is hung at suspend command. Is this solved yet?

I also see the same thing. Probably MS has build a check in on cpu code?

What is the best way to upgrade an cluster? I got three nodes, two for KVM and one just for OpenVZ (with migration posibility to the other two nodes)? Can I upgrade the "linux" only node without any problems? And then migrate the KVM vm's to the other node --> update empty node --> migrate all...

Ok, working , the full address url has to be entered in!

Re: Another unresolved bug?! Ok thanks, then I test it and will upgrade the cluster to 3.0 when the final is tested ok!

Re: Another unresolved bug?! When proxmox 3.0 final is there can it then be added to a Proxmox 2.x cluster or should the proxmox 2.x nodes be first upgrade to 3.x? What I like to do is to install proxmox 3.0RC2 on a new machine run it, test things and then add it to the cluster when 3.0 is...

first of all to test the new proxmox and secondly it is also mentioned as the way to create openvz containers ! Let me tell you that it works, but I was a bit suprised that the CT was suspended with a live migration, perhaps my previous tests (along time ago) were with kvm virtual machines...

Hi Tom, in the log is no error, but that is not the issue , what i see is that the CT is suspended, is this how online migration works? " Aug 17 18:33:52 container is running - using online migration Aug 17 18:33:52 container data is on shared storage 'qnapNFS-proxmox1' Aug 17 18:33:53 start...

No there is no cdrom attached, a migration looks like this: " Aug 17 18:33:52 starting migration of CT 154 to node 'eismox2' (192.168.1.61) Aug 17 18:33:52 container is running - using online migration Aug 17 18:33:52 container data is on shared storage 'qnapNFS-proxmox1' Aug 17 18:33:53 start...