libvirt users - Nov 2014 - Re: Unable to start container after OS upgrade

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good
after upgrade until reboot. When rebooted to container I'm getting the
following errors.. Any help would be greatly appreciated
/bin/mknod: `/dev/lp2': Operation not permitted
/bin/chown: cannot access `/dev/lp2': No such file or directory
/bin/mknod: `/dev/lp3': Operation not permitted
/bin/chown: cannot access `/dev/lp3': No such file or directory
/bin/mknod: `/dev/net/tun': Operation not permitted
/bin/mknod: `/dev/ppp': Operation not permitted
/bin/mknod: `/dev/fuse': Operation not permitted
/sbin/start_udev: line 269: /proc/sys/kernel/hotplug: Read-only file system
udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0
udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0

udevd[71]: matchpathcon(/dev/.udev/rules.d) failed
udevd[71]: matchpathcon(/dev/.udev/rules.d) failed

                                                           [  OK  ]
Setting hostname vm1292ussac1-goagent1.cust.aops-eds.com:  [  OK  ]
Checking filesystems
                                                           [  OK  ]
mount: can't find / in /etc/fstab or /etc/mtab
Mounting local filesystems:                                [  OK  ]
/etc/rc.d/rc.sysinit: line 606: plymouth: command not found
Enabling /etc/fstab swaps:                                 [  OK  ]
init: kexec-disable main process (139) terminated with status 1

On Fri, Nov 14, 2014 at 07:32:46PM +0000, mallu mallu
wrote:
> I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks
good after upgrade until reboot. When rebooted to container I'm getting the
following errors.. Any help would be greatly appreciated
> /bin/mknod: `/dev/lp2': Operation not permitted
> /bin/chown: cannot access `/dev/lp2': No such file or directory
> /bin/mknod: `/dev/lp3': Operation not permitted
> /bin/chown: cannot access `/dev/lp3': No such file or directory
> /bin/mknod: `/dev/net/tun': Operation not permitted
> /bin/mknod: `/dev/ppp': Operation not permitted
> /bin/mknod: `/dev/fuse': Operation not permitted
> /sbin/start_udev: line 269: /proc/sys/kernel/hotplug: Read-only file system
> udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0
> udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0
> 
> udevd[71]: matchpathcon(/dev/.udev/rules.d) failed
> udevd[71]: matchpathcon(/dev/.udev/rules.d) failed
You don't want to have  udevd running in any container. The /dev filesystem
for a container is pre-populated by libvirt and udev will not have permission
to create any further device nodes. So just disable udev init script.



Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

You don't want to have  udevd running in any container. The /dev filesystem
for a container is pre-populated by libvirt and udev will not have permission
to create any further device nodes. So just disable udev init script.



I have uninstalled udev prior to reboot. Still lxc container is not coming up
after reboot. Any help would be greatly appreciated.

init: kexec-disable main process (79) terminated with status 1