Hi
On Mon, Jul 09, 2007 at 12:03:26AM +0200, Daniel Hokka Zakrisson wrote:
> Ola Lundqvist wrote:
> > Hi
> >
> > Now I have checked again and it do not seem to work. I'll try with a later
> > kernel as well. Is it because I use xfs maybe?
>
> How does it not work? What do you have in the fstab? What is happening
> that you weren't expecting?
If I have mounted the root filesystem for the vserver before starting
the vserver everything works fine. That is that I have it in
the /etc/fstab in the normal host (not the virtual server).
However if I add the line to /etc/vservers/xxxx/fstab instead the
vserver do not start.
For example I have a vserver named leuzit on a vserver enabled host.
In /etc/fstab on the host I have
/dev/vg0/leuzit-root /srv/vservers/leuzit xfs defaults 0 0
I also have
/dev/vg0/leuzit-root / xfs defaults 0 0
in /etc/vservers/leuzit/fstab
I only enable one of the two lines at the same time.
1) Working
If I have the line enabled in /etc/fstab and mount it before I start
the vserver it works just fine.
2) Not working
If I unmount the filesystem and rely on the fstab inside vserver
configuration to handle it, then it do not work that well anymore.
This is the information I get back!
zircone:~# vserver leuzit start
vcontext: open("/dev/null"): Permission denied
An error occured while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(/sbin/init) failed.
Common causes are:
* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
method knows how to deal with this, but on existing installations,
appending 'true' to this file will help.
Failed to start vserver 'leuzit'
I expect it to work just as well as alternative 1. It did so
for the versions in sarge.
Regards,
// Ola
> --
> Daniel Hokka Zakrisson
>
--
--- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ----
/ [EMAIL PROTECTED] Annebergsslingan 37 \
| [EMAIL PROTECTED] 654 65 KARLSTAD |
| http://opalsys.net/ Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
