On Thu, 8 Feb 2007 00:47:26 +0100 (CET), Daniel Hokka Zakrisson wrote: >Lyn St George wrote: >> In the end, it seems that it was LVM. I eventually found this > >No, this was an actual bug. It should be fixed in 2.2.0-rc12.
Ah ... though applying the specified config did fix it. >> page: http://oldwiki.linux-vserver.org/Step-by-Step+Guide+2.6 >> which specifically mentions that LVM needs a different >> configuration. So I did that - and with the new-style config >> so the LVM fix would work - and now the vservers start and >> can be entered properly. They still don't stop properly, and >> 'ps -ax' does not show all processes, so I guess things need >> to be tweaked. But at least they run. > >What? ps ax is not supposed to show _all_ processes, just the ones >belonging to the current context. If you want to show all of them, use vps >on the host. I meant all processes in the guest, not also those on the host. Some were known to be running, eg Apache could be connected to, but were not showing in the process list. And my current configuration is to explicitly mount both proc and dev/pts on the host's fstab. Doing this allows things to work as expected, and as they used to do before being hit with LVM on the host. >-- >Daniel Hokka Zakrisson - Lyn _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
