Search results

I can add to this post that the problem was also in previous versions (2.1, 1.9, 1.8) too. If the NFS storage is down the whole cluster becomes unresponsive. During this the VM's in the cluster (part of them at least) don't respond as well.

Hmm. As for me I think this looks rather like a kernel defect than a hardware defect. (The server worked well alone and in the cluster with version 1.8, 1.9, 2.0, and 2.1)

No, all of them are different. These are different models of HP server blades in one bay with shared SAS storage HP MSA 2012 SA Problem server is HP ProLiant BL460c G6 Other (working) servers in the cluster are: 1) HP ProLiant BL620c G7 2) HP ProLiant BL460c G7

I have a problem with the latest update 2.2.31. I created a separate topic about this but no one answered. May be someone can answer here... I updated all my proxmox ve hosts in a cluster two days ago from 2.1 to 2.2. After the update one of my nodes begun to fall into general protection fault...

I updated all my proxmox ve hosts in a cluster that night from 2.1 to 2.2. After the update one of my nodes begun to fall into general protection fault right or after few minutes after boot. Here is a screen http://s18.postimage.org/ew7hvrrg9/image.jpg The two other nodes of the cluster seem to...

The same two messages: "Status: plain authentication" and after that "Error: authentication failed"

No ideas? Is more information needed?

Thanks for all advices! I will first try to update the proxmox. I now have: pverversion -v: pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a) running kernel: 2.6.32-12-pve proxmox-ve-2.6.32: 2.1-68 pve-kernel-2.6.32-11-pve: 2.6.32-66 pve-kernel-2.6.32-12-pve: 2.6.32-68 lvm2: 2.02.95-1pve2 clvm...

I have a three node cluster. The cluster seems to work correct. The problem is: I can't launch the kvm console window from the other node (not the one on which the kvm guest is running). When I open the console window ot the different node it shows me a white window with some diagnostic messages...

The situation is: I have about 15 kvm guests on a proxmox ve host. It has 60GB RAM 15 kvm guests altogether are assigned 75 GB RAM. Most of the time they altogether consume about 50GB RAM. But there were several times when the RAM consumption of the KVM guests grew till the host's all available...

I managed to fix it manually by using the dmsetup command. So the question is closed.

No ideas yet? Strange... :(

Yes, it works! ivan901, you are the best! :-) So that means, windows xp guest should shutdown out of the box because this option is off by default for windows xp. Seems like a collision (bug?) which was never noticed by MS company.

I have a 3-node cluster with a shared LVM SAS-storage. I created a VM 129 (the id is essential in this case), played with it for a while and deleted it from the web gui. I think something went wrong while deleting the lvm disk of that VM. And now I have a problem. When sitting on the same node I...

Yes. It was right. After I installed the acpid packet on a debian guest it shuts down correctly even from the main window without having to open the VM console window. But the question with the windows guests still remains. I already set up the security policy in windows guests that they may be...

Hmm... I think if it were up to the missing acpid packet debian guests wouldn't shut down at all regardless of where we press the "shutdown" button...Or am I wrong?

I must wait till it happens :-)

# cat /etc/pve/.members { "nodename": "srv-bld-a07", "version": 11, "cluster": { "name": "****************", "version": 3, "nodes": 3, "quorate": 1 }, "nodelist": { "srv-bld-a06": { "id": 1, "online": 1, "ip": "172.16.10.236"}, "srv-bld-a05": { "id": 2, "online": 1, "ip": "172.16.10.235"}...

Using the VM Console I can shutdown any machine (I have win2003 win7 win2008 win2008r2 and some debian guests). In some windows guests i had to set up in the security policy that the machine may be shutdown without being logged on. By the way the message "TASK ERROR: VM quit/powerdown failed -...

I stress on the fact, that the VM shuts down correct (these are mainly Windows guests) when I press the button on top of the VM console window (where the buttons Start Shutdown SendKey Reset Suspend are placed). So the ACPI signal sent to the VM works fine. I don't try to shutdown the windows...