Displaying 20 results from an estimated 300 matches similar to: "Question about setns recognising in libvirt autoconf"
2013 Dec 09
2
Re: Question about setns recognising in libvirt autoconf
On 2013-12-09 13:18 , Gao feng wrote:
On 12/09/2013 01:06 PM, hzguanqiang@corp.netease.com wrote:
> Hi experts,
>
> When I test lxc container with lxc-enter-namespace command, It reported an error as
> following:
> root@debian:~/github/libvirt# vir lxc-enter-namespace lxc --noseclabel /bin/df -hl
> error: Cannot get namespaces for 3145: Function not implemented
>
> It
2013 Dec 09
0
Re: Question about setns recognising in libvirt autoconf
Hi Gaofeng,
It seems that I've got the answer.
In manual page about setns, it said that library support was added to glibc
in version 2.14 while my libc version is 2.13.
Thanks for help anyway.
On 2013-12-09 13:22 , hzguanqiang@corp.netease.com wrote:
On 2013-12-09 13:18 , Gao feng wrote:
On 12/09/2013 01:06 PM, hzguanqiang@corp.netease.com wrote:
> Hi experts,
>
> When I test lxc
2013 Dec 09
0
Re: Question about setns recognising in libvirt autoconf
On 12/09/2013 01:06 PM, hzguanqiang@corp.netease.com wrote:
> Hi experts,
>
> When I test lxc container with lxc-enter-namespace command, It reported an error as
> following:
> root@debian:~/github/libvirt# vir lxc-enter-namespace lxc --noseclabel /bin/df -hl
> error: Cannot get namespaces for 3145: Function not implemented
>
> It seems that setns is not supported by my
2013 Nov 14
2
Re: Problem about lxc-enter-namespace interface
On 11/14/2013 02:57 PM, hzguanqiang@corp.netease.com wrote:
> On 2013-11-14 14:17 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
>
> On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote:
> > On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
> >
> > On 11/14/2013 01:24 PM, Gao feng wrote:
> > >
2013 Nov 14
2
Re: Problem about lxc-enter-namespace interface
On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote:
> On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
>
> On 11/14/2013 01:24 PM, Gao feng wrote:
> > On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote:
> >> Hi experts,
> >>
> >> When I test lxc-enter-namespace interface, it turned out such
2013 Nov 14
2
Re: Problem about lxc-enter-namespace interface
On 11/14/2013 03:09 PM, hzguanqiang@corp.netease.com wrote:
> On 2013-11-14 15:03 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
>
> On 11/14/2013 02:57 PM, hzguanqiang@corp.netease.com wrote:
> > On 2013-11-14 14:17 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
> >
> > On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote:
2013 Nov 14
2
Re: Problem about lxc-enter-namespace interface
On 11/14/2013 01:24 PM, Gao feng wrote:
> On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote:
>> Hi experts,
>>
>> When I test lxc-enter-namespace interface, it turned out such an error:
>>
>> hzguanqiang@debian:~$ <mailto:hzguanqiang@debian:~$> vir version
>> Compiled against library: libvirt 1.1.4
>> Using library: libvirt 1.1.4
2018 May 08
1
mount failing client to gluster cluster.
Hi,
On a debian 9 client,
========
root at kvm01:/var/lib/libvirt# dpkg -l glusterfs-client
8><---
ii glusterfs-client 3.8.8-1 amd64
clustered file-system (client package)
root at kvm01:/var/lib/libvirt#
=======
I am trying to to do a mount to a Centos 7 gluster setup,
=======
[root at glustep1 libvirt]# rpm -q glusterfs
glusterfs-4.0.2-1.el7.x86_64
2013 Nov 14
2
Problem about lxc-enter-namespace interface
Hi experts,
When I test lxc-enter-namespace interface, it turned out such an error:
hzguanqiang@debian:~$ vir version
Compiled against library: libvirt 1.1.4
Using library: libvirt 1.1.4
Using API: LXC 1.1.4
Running hypervisor: LXC 3.9.6
hzguanqiang@debian:~$ vir list
Id Name State
----------------------------------------------------
1544 instance-00000015
2013 Nov 14
0
Re: Problem about lxc-enter-namespace interface
On 2013-11-14 15:03 , Gao feng wrote:
On 11/14/2013 02:57 PM, hzguanqiang@corp.netease.com wrote:
> On 2013-11-14 14:17 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
>
> On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote:
> > On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
> >
> > On 11/14/2013 01:24 PM,
2013 Nov 14
0
Re: Problem about lxc-enter-namespace interface
On 2013-11-14 14:17 , Gao feng wrote:
On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote:
> On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
>
> On 11/14/2013 01:24 PM, Gao feng wrote:
> > On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote:
> >> Hi experts,
> >>
> >> When I test
2013 Nov 14
0
Re: Problem about lxc-enter-namespace interface
On 2013-11-14 13:41 , Gao feng wrote:
On 11/14/2013 01:24 PM, Gao feng wrote:
> On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote:
>> Hi experts,
>>
>> When I test lxc-enter-namespace interface, it turned out such an error:
>>
>> hzguanqiang@debian:~$ <mailto:hzguanqiang@debian:~$> vir version
>> Compiled against library: libvirt 1.1.4
2013 Nov 14
0
Re: Problem about lxc-enter-namespace interface
On 2013-11-14 16:40 , Gao feng wrote:
On 11/14/2013 03:09 PM, hzguanqiang@corp.netease.com wrote:
> On 2013-11-14 15:03 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
>
> On 11/14/2013 02:57 PM, hzguanqiang@corp.netease.com wrote:
> > On 2013-11-14 14:17 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote:
> >
> > On 11/14/2013 01:52 PM,
2015 Apr 21
2
QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
List,
I was under the impression that I could restart libvirtd without it
destroying my VMs, but am not finding that to be true. When I killall
libvirtd then my VM's keep running, but then when I start libvirtd it
calls qemuDomainObjEndJob:1542 : Stopping job: modify (async=none
vm=0x7fb8cc0d8510 name=test) and my domain gets whacked.
Any way to disable this behavior?
Also, while I'm
2012 Jul 24
2
virsh iface-list error
Hello
Facing below error while trying to access the iface-list.
# virsh iface-list
*error: Failed to list active interfaces
error: this function is not supported by the connection driver:
virConnectNumOfInterfaces*
root at kvm-1:/usr/local/src/libvirt# virsh list
Id Name State
----------------------------------------------------
1 vm1
2015 Apr 21
0
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
On 04/20/2015 08:45 PM, Matthew Schumacher wrote:
> List,
>
> I was under the impression that I could restart libvirtd without it
> destroying my VMs, but am not finding that to be true.
If not, then something is wrong.
> When I killall
> libvirtd then my VM's keep running, but then when I start libvirtd it
> calls qemuDomainObjEndJob:1542 : Stopping job: modify
2014 Jun 10
4
[LLVMdev] use of undeclared identifier '__NR_*' error while building clang
Hi guys,
I am following this[1] tutorial to install clang. However, I have made a
small change in the configure command, and I am running it with
'--enable-optimized' option to avoid the debug build.
I am getting the errors (given at the end) related to *undeclared
identifiers '__NR_*'*. Can someone please provide some input about how to
tackle this issue?
On my other machine, I
2014 Feb 20
2
libvirt_lxc namespace and umount in global namespace
Hi,
I am currently having an issue with the libvirt_lxc binary that is launched
when starting a lxc instance using libvirt. This process seems to have its
own namespace for mounts.
What happens is that if I umount something in the global namespace, it
stays mounted in the libvirt_lxc namespace.
I'm working with drbd, and after unmounting the mount point, I want to
change the state of the drbd
2013 Nov 14
0
Re: Problem about lxc-enter-namespace interface
On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote:
> Hi experts,
>
> When I test lxc-enter-namespace interface, it turned out such an error:
>
> hzguanqiang@debian:~$ <mailto:hzguanqiang@debian:~$> vir version
> Compiled against library: libvirt 1.1.4
> Using library: libvirt 1.1.4
> Using API: LXC 1.1.4
> Running hypervisor: LXC 3.9.6
>
>
2013 Feb 02
2
Relaxing strict chroot checks on recent Linux kernels?
At the risk of beating a dead horse, I'd like to see the chroot
security checks relaxed a bit. On newer Linux kernels, there's a
prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0) that prevents privilege
elevation (via setuid binaries, etc) for the caller and all of its
descendants. That means that chroot(untrusted directory),
prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0), setreuid(uid, uid), execve(a