Re: [Vserver] gentoo util-vserver-0.30.212/baselayout-1.13 issues
Christian Affolter wrote:
> Hi!
>
> I finally found some time to play with the new util-vserver (0.30.212)
> on a gentoo host.
>
> First, thanks to all the involved people for their hard work!
>
> After installing
> * sys-kernel/vserver-sources-2.0.2.1
> * sys-cluster/util-vserver-0.30.212-r2
please update ro -r3, see below
>
> and the latest available stage4 (stage4-i686-20070321) from hollow's
> stage repository, I ran into some small problems:
>
> On a newly (template) created vserver (with gentoo init style) the
> following errors appearing while starting the vserver:
> # vserver basesystem-ng start
> ...
> klogctl: Operation not permitted
just a cosmetic bug, will be fixed soon
> * Using existing device nodes in /dev ...[ ok ]
> ...
> * Starting syslog-ng ...
> Error opening file /proc/kmsg for reading (Operation not permitted)
> Error initializing configuration, exiting.
fixed in -r3
> * Failed to start syslog-ng [ !! ]
> ...
>
> The second error can easily be solved by removing the /proc/kmsg source
> entry out of the syslog-ng.conf file (as there is no kmsg within the
> vserver's proc directory).
> It would be nice if the pre-built vserver stages would reflect this change.
>
>
> The vserver stop process drops the following error messages:
> # vserver basesystem-ng stop
> ...
> * Deactivating swap ...
> Not superuser. [ !! ]
> * Unmounting loopback devices ... [ ok ]
> * Unmounting filesystems ...
> * Unmounting /usr/portage/distfiles ...
> umount2: Operation not permitted
> umount: /usr/portage/distfiles: must be superuser to umount
> umount2: Operation not permitted
> umount: /usr/portage/distfiles: must be superuser to umount [ !! ]
> * Unmounting /usr/portage ...
> umount2: Operation not permitted
> umount: /usr/portage: must be superuser to umount
> umount2: Operation not permitted
> umount: /usr/portage: must be superuser to umount [ !! ]
> * Unmounting /tmp ...
> umount2: Operation not permitted
> umount: none: not found
> umount: /tmp: must be superuser to umount
> umount2: Operation not permitted
> umount: none: not found
> umount: /tmp: must be superuser to umount [ ok ]
> WARNING: could not determine runlevel - doing soft halt
> (it's better to use shutdown instead of halt from the command line)
> shutdown: /dev/initctl: No such file or directory
> init: /dev/initctl: No such file or directory
> /usr/lib/util-vserver/vserver.stop: line 85: 3682 Killed
> "[EMAIL PROTECTED]" ${USE_VNAMESPACE:+$_VNAMESPACE --enter "$S_CONTEXT" --
> } $_VCONTEXT $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" --
> "[EMAIL PROTECTED]"
>
more or less cosmetic too, will be fixed soon too, together with updated
stages.. feel free to poke me if there aren't new stages within the next
week
>
> The /usr/portage and /tmp mounts are from the vserver's config fstab
> (/etc/vservers/basesystem-ng/fstab).
> The 'umount none:' messages are possibly related to /proc and /dev/pts
>
> The internal vserver init process probably shouldn't try to swap-off and
> unmount those mounts ;)
>
>
> Are these some known issues or did I something completely wrong?
> Many thanks for your help!
>
>
> Kind regards
> Christian
HTH,
Bene
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] gentoo util-vserver-0.30.212/baselayout-1.13 issues
Hi!
I finally found some time to play with the new util-vserver (0.30.212)
on a gentoo host.
First, thanks to all the involved people for their hard work!
After installing
* sys-kernel/vserver-sources-2.0.2.1
* sys-cluster/util-vserver-0.30.212-r2
and the latest available stage4 (stage4-i686-20070321) from hollow's
stage repository, I ran into some small problems:
On a newly (template) created vserver (with gentoo init style) the
following errors appearing while starting the vserver:
# vserver basesystem-ng start
...
klogctl: Operation not permitted
* Using existing device nodes in /dev ...[ ok ]
...
* Starting syslog-ng ...
Error opening file /proc/kmsg for reading (Operation not permitted)
Error initializing configuration, exiting.
* Failed to start syslog-ng [ !! ]
...
The second error can easily be solved by removing the /proc/kmsg source
entry out of the syslog-ng.conf file (as there is no kmsg within the
vserver's proc directory).
It would be nice if the pre-built vserver stages would reflect this change.
The vserver stop process drops the following error messages:
# vserver basesystem-ng stop
...
* Deactivating swap ...
Not superuser. [ !! ]
* Unmounting loopback devices ... [ ok ]
* Unmounting filesystems ...
* Unmounting /usr/portage/distfiles ...
umount2: Operation not permitted
umount: /usr/portage/distfiles: must be superuser to umount
umount2: Operation not permitted
umount: /usr/portage/distfiles: must be superuser to umount [ !! ]
* Unmounting /usr/portage ...
umount2: Operation not permitted
umount: /usr/portage: must be superuser to umount
umount2: Operation not permitted
umount: /usr/portage: must be superuser to umount [ !! ]
* Unmounting /tmp ...
umount2: Operation not permitted
umount: none: not found
umount: /tmp: must be superuser to umount
umount2: Operation not permitted
umount: none: not found
umount: /tmp: must be superuser to umount [ ok ]
WARNING: could not determine runlevel - doing soft halt
(it's better to use shutdown instead of halt from the command line)
shutdown: /dev/initctl: No such file or directory
init: /dev/initctl: No such file or directory
/usr/lib/util-vserver/vserver.stop: line 85: 3682 Killed
"[EMAIL PROTECTED]" ${USE_VNAMESPACE:+$_VNAMESPACE --enter "$S_CONTEXT"
-- } $_VCONTEXT $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" --
"[EMAIL PROTECTED]"
The /usr/portage and /tmp mounts are from the vserver's config fstab
(/etc/vservers/basesystem-ng/fstab).
The 'umount none:' messages are possibly related to /proc and /dev/pts
The internal vserver init process probably shouldn't try to swap-off and
unmount those mounts ;)
Are these some known issues or did I something completely wrong?
Many thanks for your help!
Kind regards
Christian
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] xdmcp on host and vserver
On Tue, Mar 27, 2007 at 11:45:42AM +0200, Lars Brandi Jensen wrote: > Hi > > I am having a little problem getting xdmcp working from my gentoo > guest. It is installed with kdm and when i try to connect i get the > greeter from my host. > I guess it is similar to #30 in the FAQ. yep, looks like your host's X/xdmcp has already bound to all IPs and thus the guest cannot bind his IP > Is there any references to setting up xdmcp and kdm in a guest around. no, but it should be quite simple, here with an older gdm, I just go to the configuration/security setup and change the listen ip to something more appropriate HTH, Herbert > Lars Brandi Jensen > > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] xdmcp on host and vserver
Hi I am having a little problem getting xdmcp working from my gentoo guest. It is installed with kdm and when i try to connect i get the greeter from my host. I guess it is similar to #30 in the FAQ. Is there any references to setting up xdmcp and kdm in a guest around. Lars Brandi Jensen ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
