Unfortunately they are not related. I've been following a mailing list for qemu that dietmar has been discussing this issue in. This isn't a Proxmox related issue. There is no fix yet, just a workaround, but the work around unfortunately involves disabling vhost which triggers the issue.
Updates for Proxmox VE 2.2
- Thread starter martin
- Start date
Unfortunately they are not related. I've been following a mailing list for qemu that dietmar has been discussing this issue in. This isn't a Proxmox related issue. There is no fix yet, just a workaround, but the work around unfortunately involves disabling vhost which triggers the issue.
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 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 be OK.
I tried to reinstall the proxmox ve 2.2 from the CD. Right after the install it seemed to be OK. I ran "apt-get update" and "apt-get dist-upgrade".
Then I rebooted and tried to ssh to the host. And again the host got into general protection fault.
What to do?
Should I install proxmox ve from the CD and leave it without update? May be I should wait for another (more stable update)?
Then another question: will I be able to add that node ( 2.2 from CD without the latest update) to my cluster where two other nodes were already updated to the latest version?
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 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 be OK.
I tried to reinstall the proxmox ve 2.2 from the CD. Right after the install it seemed to be OK. I ran "apt-get update" and "apt-get dist-upgrade".
Then I rebooted and tried to ssh to the host. And again the host got into general protection fault.
What to do?
Should I install proxmox ve from the CD and leave it without update? May be I should wait for another (more stable update)?
Then another question: will I be able to add that node ( 2.2 from CD without the latest update) to my cluster where two other nodes were already updated to the latest version?
Last edited:
we once had a similar issue - when Proxmox moved to the RHEL kernel, we had a node which locked up randomly (afair with a panic). Using a stress test tool, we were able to reproduce this - and also that kernel versions before that new one did not have the problem.
At the end it turned out that it was indeed hardware related. We got a new (same type) mainboard, new (same types) cpus, and the problem was 100% gone.
So yes, a kernel *could* make the difference, and "trigger" an hardware defect...
At the end it turned out that it was indeed hardware related. We got a new (same type) mainboard, new (same types) cpus, and the problem was 100% gone.
So yes, a kernel *could* make the difference, and "trigger" an hardware defect...
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)