check the startup scripts... you should not let it do any "hardware related" stuff at bootup since that's allready done by the host. (clock, disks, hardware monitoring, kernel logging, networking/firewalling stuff, ...) you should only start what you need in the guest Greetings, Rik Bobbaers -- http://harry.enzoverder.be linux/unix/system/network/security/hardware/DR admin "If a man speaks his mind in a forest, and there's no woman to hear it ... is he still wrong?" > 2010/1/15 Rik Bobbaers <rik@enzoverder.be> > >> i think there are 2 possible sollutions here >> >> OR you should mount the sysfs in the fstab of the guest config and not >> in >> the startup scripts of the guest /etc/vservers/<guest>/etc/fstab (or >> something) >> OR you should add mount capabilities to the guest. Check the different >> capabilities settings on the site: >> http://linux-vserver.org/Capabilities_and_Flags >> >> hope that helps... >> >> Rik Bobbaers >> > > > Well done. > Adding SECURE_MOUNT and BINARY_MOUNT to > /etc/vservers/myserver/ccapabilities > solved sysfs mount issue. > > I still have various errors, even by giving SYS_ADMIN to bcapabilities, > and > my VServer won't start. > I'm making the most basic thing I can, I don't understand why it wouldn't > work :-( > > Anyway, many thanks for your help. > > -- > Pierre. > "Sometimes when I'm talking, my words can't keep up with my thoughts. I > wonder why we think faster than we speak. Probably so we can think twice." > - > Bill Watterson >