I have resolved this. I forgot that RHEL6 is based on upstart, so I
needed to set the init style to "plain". Works fine now. :)
Gordan
On 09/09/2010 03:29 PM, Gordan Bobic wrote:
> Hi,
>
> I'm trying to get a RHEL6 VM working, and I'm running into some
> problems. I got most of it where I want it, using util-vserver packages
> from F13, and tweaking the yum repo file accordingly.
>
> First problem:
> - Is there a reason why $releasever isn't available to yum? I had to
> hard-set it to 5.90Workstation (for RHEL 6b2 Worksation).
>
> I built the VM using:
> vserver testvm build -m yum --hostname testvm \
> --interface eth0:10.1.2.3/16 -- -d rhel6
>
> Note:
> - I did set up /etc/vservers/.distributions/rhel6 accordingly from
> CentOS5 and F11 examples.
> - I didn't specify the "--context 42" prameter mentioned in the
> documentation since I couldn't find any reason why it couldn't be omitted.
> - I am using the 2.6.30.10 kernel due to some 3rd party patches not
> being available for newer kernels.
>
> The VM builds, but when I try to start it, I get:
>
> # vserver internal start
> Entering non-interactive startup
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> FATAL: Could not load
> /lib/modules/2.6.30.10-vs2.3.0.36.14-pre8/modules.dep: No such file or
> directory
> Bringing up loopback interface: Device lo does not seem to be present,
> delaying initialization.
> [FAILED]
> FATAL: Could not load
> /lib/modules/2.6.30.10-vs2.3.0.36.14-pre8/modules.dep: No such file or
> directory
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> Mounting other filesystems: [ OK ]
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> Retrigger failed udev events [ OK ]
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
> initctl: Unable to connect to Upstart: Failed to connect to socket
> /com/ubuntu/upstart: Connection refused
>
> After this, the VM ends up not actually running as far as I can tell:
>
> # vserver internal enter
> 'vserver ... suexec' is supported for running vservers only; aborting...
>
> I'd like to know where the reference to /com/ubuntu is coming from on a
> RHEL/Fedora based build?
>
> I cannot see any further information in /var/log/messages. Is there a
> log elsewhere that I should be looking at?
>
> Thanks.
>
> Gordan
Received on Fri Sep 10 11:06:35 2010