Displaying 3 results from an estimated 3 matches for "lxc_name".
Did you mean:
lc_name
2019 Jan 22
0
Re: libvirt 5.0.0 - LXC container still in "virsh list" output after shutdown
...rk-5.0.0-1.el7.x86_64
> libvirt-libs-5.0.0-1.el7.x86_64
> +
> systemd-219-62.el7_6.2.x86_64
>
> Now lxc containers with type='direct' can be started, but can't be stopped
Additional info.
When shutdown LZXC container with --mode signal, nothing happened on
virsh console LXC_NAME
If use --mode initctl, container powering off:
...
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Remote File Systems.
[ OK ] Stopped Load/Save Random Seed.
[ OK ] Stopped Update UTMP about System Boot/Shutdown.
[ OK ] Stopped Create Volatile Files and Directories.
[...
2014 Apr 16
0
LXC vCPU controlling problem
...39;ve been using libvirt-1.1.1 with LXC1.0.0 to do my CS
homework.But I met a problem when I tried to set vcpu for a LXC.The
/sys/fs/cgroup/cpuset/machine/cpuset.cpus always show 0-3 no matter how
many vcpu I defined in the XML setting file.
But I found the command "virsh -c lxc:/// domaininfo lxc_name" got the
right number as it is defined.
What's the problem there? Is it a bug in libvirt-1.1.1?
Thank you!
2019 Jan 21
2
libvirt 5.0.0 - LXC container still in "virsh list" output after shutdown
Hello.
Centos 7.6 with libvirt build from base "virt" repository:
libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64
libvirt-client-5.0.0-1.el7.x86_64
libvirt-daemon-5.0.0-1.el7.x86_64
libvirt-daemon-driver-network-5.0.0-1.el7.x86_64
libvirt-libs-5.0.0-1.el7.x86_64
+
systemd-219-62.el7_6.2.x86_64
Now lxc containers with type='direct' can be started, but can't be stopped :)