similar to: lxc--sshd

Hello, I am having difficulty getting any sort of LXC container running. I am trying to use the following tutorial to run the hello world example: https://www.berrange.com/posts/2011/09/27/getting-started-with-lxc-using-libvirt/ Here are the results of my running the tutorial: [root@terraria ~]# virsh list Id Name State

Hello! I'm testing user namespaces and I have quite some problem getting them to work. First of all, I have user namespaces support enabled in kernel: offlinehacker:~/ $ uname -r 3.10.10 offlinehacker:~/ $ ls /proc/self/ns/ ipc@ mnt@ net@ pid@ user@ uts@ I created simple ubuntu rootfs and when I start container without idmap, so without user namespace mappings, it works just fine:

Hello! Okay i tried again with only staticly linked busybox: offlinehacker:~/ $ /home/offlinehacker/busybox/busybox BusyBox v1.17.1 (Debian 1:1.17.1-8) multi-call binary. Copyright (C) 1998-2009 Erik Andersen, Rob Landley, Denys Vlasenko and others. Licensed under GPLv2. See source distribution for full notice. .... Again my id: uid=499(offlinehacker) gid=100(users)

Hello list, we're trying to use NTLMv2 authentication from Liferay Portal 6.0.5 as specified in http://www.liferay.com/community/wiki/-/wiki/Main/NTLMv2+SSO+Configuration. We've created a machine account for it that looks like that: dn: uid=liferay$,ou=Maquinas,o=global,dc=map,dc=es sambaNTPassword: 76DBDF27BB32912AD61BC369DB8FEBD8 sambaPwdLastSet: 1298373376 sambaAcctFlags: [W]

I applied your patch, but no success. What bothers me is that connection gets reseted. By the way, i'm using systemd, with process started in forking mode and as daemon. Could this cause any problems? This is my libvirtd.conf, if it helps anything: unix_sock_group = "libvirtd" unix_sock_rw_perms = "0770" auth_unix_ro = "none" auth_unix_rw = "none" Can

Some more details on my system. I am running CentOS 6.5. To install libvirt and LXC, I performed the following command: yum install libvirt libvirt-client python-virtinst I have turned selinux to DISABLED. On Wed, Jan 22, 2014 at 10:34 AM, Jacob Everist <jacob.everist@gmail.com>wrote: > Hello, > > I am having difficulty getting any sort of LXC container running. I am >

Hi, Has anyone used libvirt to start/stop/manage LXC (linux containers) ? Is it supported at all? Last I tried, had few issues and the reply was : /// Note that libvirt lxc driver is a different implementation from lxc tools and doesn't use lxc tools internally. You may not be able to do what you are doing with lxc tools. Especially, the driver doesn't take aware of files and settings

I hope this question isn't considered too off topic for this list, I am trying to reach the libvirt-sandbox developers, but I could not find a libvirt-sandbox specific mailing list, and it seemed to me that libvirt-sandbox was a part of libvirt itself. I am trying to port libvirt-sandbox to run on a CentOS 6.5 system. This wasn't too hard but, I had to do the following: I have used the

Currently I have a RH6.1 host with selinux enabled On this I am running a LXC container with ubuntu (without selinux) with OpenSSH_5.3p1 Debian-3ubuntu4, OpenSSL 0.9.8k 25 Mar 2009 when I try to do a ssh connection to the lxc container I get : ... debug1: Next authentication method: password root at 192.168.2.11's password: debug1: Authentication succeeded (password). debug1: channel 0: new

I'm trying to narrow down the source of a bug where a docker container sshd closes the connection after a successful authentication (https://bugzilla.redhat.com/show_bug.cgi?id=1085081) - filed with libvirt as there's no docker-io component for RHEL 6.5 in bugzilla. One of the steps I'm taking is to reproduce a similar setup using LXC but while it seemed to have worked I'm not

I'm testing 0.9.7 now with lxc, and get the following error when trying to start a container: 2011-12-07 22:49:26.293: 1997: error : lxcControllerRun:1158 : unsupported configuration: Expected exactly one TTY fd My configuration is very simply: <domain type='lxc'> <name>hw</name> <uuid>38320e75-1ba0-d85a-6138-532a3a66f13d</uuid>

Hi everyone again, I did discover the following works (see below). However, does anyone know of the "proper" way with LLVM? llvm-gcc -g -c -emit-llvm helloworld.c opt -load=mypass.dylib -mypass < helloworld.o > helloworld-mypass.o llc -fast -f -o helloworld.s helloworld-mypass.o as -o helloworld-prime.o gcc -o helloworld helloworld-prime.o gdb helloworld On May 5, 2008, at

I think you probably need to pass -O0 to llvm-ld. The link-time optimizations are probably killing your debug info. --Owen On May 5, 2008, at 8:21 PM, Mark Oskin wrote: > Hi everyone again, > > I did discover the following works (see below). However, does anyone > know of the "proper" way with LLVM? > > llvm-gcc -g -c -emit-llvm helloworld.c > opt

Hi, I try to make my first package? The HelloWorld.R file is: #### HelloWorld.R #### #' showHello est une fonction R permettant d'afficher le message #' "Hello World!" sur la console. #' @title la fonction showHello() showHello <-function(){ cat("Hello World!\n") } I use the following procedure to get the tar: # set the working directory where the file is

> I think you probably need to pass -O0 to llvm-ld. The link-time > optimizations are probably killing your debug info. > No dice. Doing it this way makes gdb spew out this: warning: Could not find object file "/var/folders/cQ/cQ+L3+RP2RWOpE +8ZNQdPU+++TI/-Tmp-//ccVljWhn.o" - no debug information available for "defs.h" And then no debug symbols are available.

Just re-sending this. Anyone have any suggestions on how to proceed with debugging LLVM produced executables? The problem appears to be register-allocated variables. Global variables and syntax lines do get symbols using the llc / as method I described below. -Mark On May 6, 2008, at 7:36 AM, Mark Oskin wrote: > >> I think you probably need to pass -O0 to llvm-ld. The

On Wed, 7 May 2008, Mark Oskin wrote: > Just re-sending this. Anyone have any suggestions on how to proceed > with debugging LLVM produced executables? The problem appears to be > register-allocated variables. Global variables and syntax lines do > get symbols using the llc / as method I described below. -Mark Have you considered adding your pass to llvm-backend.cpp in llvmgcc?

Hi everyone, I have a question that seems simple, but has been confounding me for several hours. I'd like to debug a binary produced with LLVM. For the life of me, I can't get any symbols into gdb and llvm-db won't even start the program nor load any useful information about it. Here's my current strategy (which isn't working): llvm-gcc -g -O0 -c -emit-llvm

I could do that, but before I venture there, if I did that, could I have llvm-gcc produce native object files (not LLVM bytecode) that way (using my pass)? thanks, -Mark On May 7, 2008, at 11:40 AM, Chris Lattner wrote: > On Wed, 7 May 2008, Mark Oskin wrote: >> Just re-sending this. Anyone have any suggestions on how to proceed >> with debugging LLVM produced executables?

Hi everyone, I have been attempting to build a very simple R package interfacing with some very simple C++ code. Everything I try though results in the function working but on return it produces a memory error. Here is the output: ***********OUTPUT*************************** > library(MyPackage) > hello(); *** caught segfault *** address 0x3, cause 'memory not mapped'