Hi,
There's no reason why you shouldn't be able to use it
with lxc. Looking at the guide here;
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/sect-Para-virtualized_Windows_Drivers_Guide-How_SR_IOV_Libvirt_Works.html
The virtual devices show as virtual pci
wrote:
From: siraj rathore siraj_rathore2...@yahoo.com
Subject: Re: [Lxc-users] single root io virtualization
To: atp andrew.phill...@lmax.com
Date: Wednesday, February 23, 2011, 10:11 AM
Thanks, This is a good tutorial. But i wonder how
Hi,
Its not as simple as it seems. What you're asking for is to selectively
hide or modify what gets shown to container processes by the /proc file
system. In other words making /proc container aware. /proc is already
partially there - with the pid namespace, but not for ram and cpus.
We've
code?
This copy could have all neccessary patches applied (memory and cpu views).
So we could mount -t lxcproc none /proc in containers.
I think, it's a cleaner way than fuse overlay.
Regards,
Guillaume
Le 15/06/2010 11:52, atp a écrit :
Hi,
If anyone is interested, I've put
Hello,
Been looking at getting this patch working;
http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commitdiff;h=563f2f2ccd2891661836c96f92f047a735355c1b;hp=3bdf52d753ecf347b3b5cbff97675032f2de3e5e
This patch allows to shutdown the container when the system
is powered off in the
Bad idea to follow up on yourself, however I've got a bit further;
running an inotifywait -m on the file at the same time as I'm tailing
the log file gives you;
lxc-start 1275415483.290 DEBUGlxc_cgroup - using cgroup
mounted at '/cgroup'
lxc-start 1275415483.290 DEBUGlxc_utmp
Ok,
absolutely the last post tonight. I promise.
I fixed the find /var/run -exec rm -f {} command in rc.sysinit.
Now the problem is that the runlevel is written whilst things are
still shutting down;
/lxc/test01.dev.tradefair/rootfs/var/run/utmp MODIFY
Hi,
Send
ifconfig br0from the host
ifconfig eth0 from the container
and the version of lxc you're using. Do you have anything special with
the /etc/sysctl.conf?
On a completely blank container with no tuning, I get with scp;
host-container squashfs.img 100% 639MB 33.6MB/s
Toby
Just FYI in case you were unaware - it seems one of your MXs is black
holed.
I tried to email you direct, but messagelabs said;
toby.corkind...@strategicdata.com.au:
74.125.148.10 does not like recipient.
Remote host said: 554 5.7.1 Service unavailable; Client host
[74.125.149.113] blocked
Thanks to both for the replies.
This now makes sense. I've specified the rootfs.mount in the container
config, and it gets past there and boots ok.
Just in case anyone else cares, a very handy debug log can be had by
using this command.
lxc-start --logpriority=TRACE -o /tmp/trace.log --name
Daniel,
The autoconf maze has me befuddled as well. I tried briefly to see where
VERSION and PACKAGE_VERSION were defined but to no avail.
They should be defined in src/config.h (generated by autoconf).
But where does autoconf get it from :-) ?
I wanted to set the version number
Hi,
Prompted by the LXC a feature complete replacement of OpenVZ thread,
I've uploaded my interim changes to procfs to
http://www.tinola.com/lxc/
Its very much a work in progress, and the code is pretty horrible in
places. Sorry its taken so long. I've learnt a lot about fuse.
Changes from
Hi,
Apologies for the delay - I've just got to looking at the procfs
tarball.
It's for the moment very experimental, it's a prototype:
http://lxc.sourceforge.net/download/procfs/procfs.tar.gz
IMO, the code is easy to follow.
The fuse in mounted in the container but the code expect to
Hi,
I'm looking at trying to restrict a container's view of the cpus
available on the system. I'm on fedora 12, with lxc-0.6.5-1.x86_64
Does anyone know if it is possible to restrict the containers view of
the number of cpus it has access to? Would the libvirt interface to
lxc be able to do
14 matches
Mail list logo
