This was all referenced in a previous post, and I did my best to follow all the suggestions and the problem seemed to go away. But it came back last night with a vengeance.
Latest stable proxmox 1.6 kernel
64 bit Debian Lenny guest.
Virtio Disk on a LVM partition from a shared pool (exactly as recommended)
3 processor cores
Twice in a row I had to issue a qm stop command against it. No shut down possible. Twice in a row the guest had to check the damaged file system and reboot a second time.
qm monitor 'info cpus' command showed 2 of 3 CPU's in an ?inactive? state (sorry I should have documented exactly what it said -- I was in a hurry to get it back up, at any rate 3 CPU's were listed and two had an extra flag something to do with inactive) Anyways I reconfigured the guest for only one core and it seems to be stable now. Any Idea what causes this behaviour?
Latest stable proxmox 1.6 kernel
64 bit Debian Lenny guest.
Virtio Disk on a LVM partition from a shared pool (exactly as recommended)
3 processor cores
Twice in a row I had to issue a qm stop command against it. No shut down possible. Twice in a row the guest had to check the damaged file system and reboot a second time.
qm monitor 'info cpus' command showed 2 of 3 CPU's in an ?inactive? state (sorry I should have documented exactly what it said -- I was in a hurry to get it back up, at any rate 3 CPU's were listed and two had an extra flag something to do with inactive) Anyways I reconfigured the guest for only one core and it seems to be stable now. Any Idea what causes this behaviour?
2:30:41:CA:CD