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
"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 <email@example.com>
>> i think there are 2 possible sollutions here
>> OR you should mount the sysfs in the fstab of the guest config and not
>> the startup scripts of the guest /etc/vservers/<guest>/etc/fstab (or
>> OR you should add mount capabilities to the guest. Check the different
>> capabilities settings on the site:
>> hope that helps...
>> Rik Bobbaers
> Well done.
> Adding SECURE_MOUNT and BINARY_MOUNT to
> solved sysfs mount issue.
> I still have various errors, even by giving SYS_ADMIN to bcapabilities,
> 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.
> "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
Received on Fri Jan 15 15:39:05 2010