[libvirt-users] Definition /dev/shm prevent LXC container from start: "Failed to access '(null)': Bad address"

[Daniel P. Berrange]

On Thu, Aug 11, 2016 at 03:38:06PM +0300, mxs kolo wrote:
>  Hi all
> 
> We use libvirt 1.2.x and 1.3.x with next filesystem definition in config:
> <filesystem type='ram' accessmode='passthrough'>
>   <source usage='524288' units='KiB'/>
>   <target dir='/dev/shm'/>
> </filesystem>
> 
> But libvirt 2.1.0 with same config report error:
> Failed to access '(null)': Bad address
> 
> Debug level 1 show:
> 2016-08-11 10:14:56.661+0000: 1: debug : lxcContainerMountAllFS:1618 :
> Mounting all non-root filesystems
> 2016-08-11 10:14:56.661+0000: 1: debug : lxcContainerMountAllFS:1625 :
> Mounting '(null)' -> '/dev/shm'
> 2016-08-11 10:14:56.661+0000: 1: error :
> lxcContainerResolveSymlinks:629 : Failed to access '(null)': Bad
> address
> 2016-08-11 10:14:56.661+0000: 1: debug : virFileClose:102 : Closed fd 15
> 2016-08-11 10:14:56.661+0000: 1: debug : virFileClose:102 : Closed fd 10
> 2016-08-11 10:14:56.661+0000: 1: debug : virFileClose:102 : Closed fd 12
> 2016-08-11 10:14:56.661+0000: 1: debug : lxcContainerChild:2271 :
> Tearing down container
> Failure in libvirt_lxc startup: Failed to access '(null)': Bad address
> 
> Someone use libvirt 2.x with /dev/shm device ?
> Probably need change config and add some definitions to /dev/shm ?

it is a bug introduced in 2.1.0 - i've just copied you on a patch
that should fix it. If possible, it'd be good if you can build with
that patch and report whether it works for you

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 :|