Hi all
I have 2 additional suggestions for a smoother build with 1.0.2
* I applied this change in my specfile:
http://git.onelab.eu/?p=libvirt.git;a=commitdiff;h=184bc19ce855e1498f6775b711ea3d37808cd45c
otherwise like I reported already, I end up with a plain libvirt rpm that
requires
Hello there
I'm using libvirt-1.0.2 to spawn off linux containers
We currently have 2 very similar setups that run on fedora 16 and f18
respectively
And I'm seeing one weird difference concerning /proc/meminfo
While everything is fine on the fedora16 world, on the fedora18 side here is
what the
Just in case this is useful, I'd like to submit this change below that was not
present at least in 1.0.4
http://git.onelab.eu/?p=libvirt.git;a=blob;f=virgetlasterror.patch;h=9109d581256f35bca7b4e6b1b70cef4433413474;hb=HEAD
I'd taken this hint here in the first place
as I am concerned this workaround
is still current for 1.0.4
-- Thierry
On Apr 16, 2013, at 4:10 PM, Daniel P. Berrange wrote:
On Tue, Apr 16, 2013 at 04:01:54PM +0200, Thierry Parmentelat wrote:
Just in case this is useful, I'd like to submit this change below that was
not present at least
Hello there
I am trying to locate the namespaces in place for a given lxc container
(specifically /proc/pid/ns/*)
And to this end I was wondering what is the recommended way to probe for an lxc
container's init pid
(mostly I'm after the mnt and pid namespaces, and probably network ones, but
the trick below I essentially have what I need mind you, I’m just
concerned that it kind of works by accident :-)
Thanks for the feedback in any case — Thierry
On 20 Jan 2014, at 12:49, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Jan 20, 2014 at 11:38:08AM +0100, Thierry Parmentelat wrote
request inside the host to a simple fork that runs in the container
context, instead of relying here again on ssh to reach the container..
My $0.02 — thanks again — Thierry
On 20 Jan 2014, at 18:53, Thierry Parmentelat thierry.parmente...@inria.fr
wrote:
Hi
Well if I need to run anything
Oh, I had totally failed to spot that one..
Thanks for the tip, I’ll give this a try :-)
On 20 Jan 2014, at 18:59, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Jan 20, 2014 at 06:53:28PM +0100, Thierry Parmentelat wrote:
Hi
Well if I need to run anything in the container context
this mean we would lose any message sent on stderr ?
—
In the same conditions our own local tool would do this
# lxcsu -ro my-01 -- ls /etc/yum.repos.d/building.repo
/etc/yum.repos.d/building.repo
Hope this helps — Thierry
On 20 Jan 2014, at 19:03, Thierry Parmentelat thierry.parmente...@inria.fr
So I did give this interesting lxc-enter-namespace feature a try
Thank you.
This is great, it solves my initial problem quite nicely, and I have given up
on using my own tool :-)
So my comments are,
- first that defining some even minimal PATH would help;
PATH relative to the
Hi
This is in echo to a message originally sent on libvirt-users, but having not
received any answer yet so we figured we would try this list instead
So, we use libvirt on various flavours of fedora; with fedora18 we were using
libvirt-1.0.4, that we rebuilt using a slightly modified version
-daemon-config-network should depend on
libvirt-daemon-driver-network so that the latter gets installed first
and it seems like on our earlier setups this was working by accident
I’ll need to test this more thoroughly though — Thierry
On 11 Feb 2014, at 09:28, Thierry Parmentelat thierry.parmente
Hello Laine; please see inline — many thanks for the feedback in any case —
Thierry
On 11 Feb 2014, at 11:48, Laine Stump la...@laine.org wrote:
On 02/11/2014 10:28 AM, Thierry Parmentelat wrote:
Hi
This is in echo to a message originally sent on libvirt-users, but having
not received
for you guys
Thanks — Thierry
On 11 Feb 2014, at 12:37, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Feb 11, 2014 at 12:13:49PM +0100, Thierry Parmentelat wrote:
Hello Laine; please see inline — many thanks for the feedback in any case —
Thierry
4) Even if you are installing
Hi there
I'm trying to rebuild libvirt 1.0.2 on various targets - mostyl f16 and f18 for
now
I've started from the specfile that I found in this source rpm here
http://libvirt.org/sources/libvirt-1.0.2-1.fc17.src.rpm
in which I've mostly added without clauses :
%define _without_storage_disk
to `main'
collect2: ld returned 1 exit status
Any idea with this one ?
Thanks again for the help in any case -- Thierry
On Feb 19, 2013, at 4:55 PM, Daniel P. Berrange wrote:
On Tue, Feb 19, 2013 at 04:28:48PM +0100, Thierry Parmentelat wrote:
Hi there
I'm trying to rebuild libvirt 1.0.2
great,I can now build that stuff on f16 at least - Thanks !!
On Feb 19, 2013, at 7:51 PM, Jiri Denemark wrote:
On Tue, Feb 19, 2013 at 19:42:46 +0100, Thierry Parmentelat wrote:
Thanks ; this does help with the particular issue I had
However I'm still not quite there yet and am receiving
Hi again
Looks like I claimed victory quite a liitle bit too early ;-)
So, on f16 with the set of features turned off, I could rpmbuild but ran into
an issue when trying to yum-install libvirt, because it required
libvirt-daemon-driver-interface
looks like this interface rpm is not created in
18 matches
Mail list logo
