Re: [Lxc-users] Issues in using lxc in Fedora 14
Hi, Thanks everyone for the time to reply back. My only reason for using FEDORA14 is I am really uncomfortable with systemd which got added into FEDORA15 and above. I initially started up with FEDORA17 and ended up with issues in systemd which needed some manual changes to make it work on FEDORA17. As pointed eventhough FEDORA14 is EOL I just wanted to try it out without systemd jargon as I am trying for embedded environment. If there is any better alternative without systemd I could try the same. As michael pointed out I could try 0.9 version of lxc library. On Wed, Jul 31, 2013 at 9:53 AM, Michael H. Warfield m...@wittsend.comwrote: On Tue, 2013-07-30 at 16:02 +0530, Ajith Adapa wrote: Hi, I am stuck with a issue in Fedora 14 using lxc. Stuck? Stuck with what? Stuck with an issue or stuck with Fedora 14. Using Fedora 14 as a host at this point in time is insane. It's way over a year and a half past EOL - end of life (F16 is already EOL) - and I've already shotgunned all my Fedora 14 hosts and guests. You won't even get high risk security fixes and updates for F14 at this point. You're just engaging in an unsupportable exercise in masochism. You won't have recent kernels and you won't have recent versions of lxc which will never become available for that version of Fedora from the repositories. I have create a container using the template available at - https://launchpadlibrarian.net/83751818/lxc-fedora container is created successfuly and when I try lxc-start command I am getting stuck as shown below. There seems to be some issues with /etc/fstab. Any pointers or proper template to create a container would be of great help. No clue. I've been working on the Fedora template and patching it. That template you pointed to is seriously very out of date. It looks like the old template I started patching some time ago. I wouldn't trust it. I've added a lot of patches (someone pointed to an up-to-date cut on github) for a lot of fedora versions. Still... I would not guarantee THAT will work on lxc 0.7.2. You got bigger problems on both fronts (Fedora version and LXC version) that you need to fix first. # lxc-start -n test Welcome to Fedora Setting hostname localhost:[ OK ] Checking filesystems WARNING: couldn't open /etc/fstab: No such file or directory [ OK ] warning: can't open /etc/fstab: No such file or directory mount: can't find / in /etc/fstab or /etc/mtab Mounting local filesystems: warning: can't open /etc/fstab: No such file or directory [ OK ] No such file or directory Enabling /etc/fstab swaps: swapon: /etc/fstab: open failed: No such file or directory [FAILED] Entering non-interactive startup Bringing up loopback interface:[ OK ] Bringing up interface eth0: Determining IP information for eth0... done. [ OK ] Starting system logger:[ OK ] awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) Mounting other filesystems: warning: can't open /etc/fstab: No such file or directory [ OK ] ^[[17~^C^Z^F[root@localhost ~]# lxc-version lxc version: 0.7.2 That version has to end. I can't support it and won't even bother to debug it. We're at 0.9 and closing in on 1.0. I have patches for templates and even base lxc binaries at all those levels. We can't even support 0.7.5 while even 0.8 has problems that can only be resolved by upgrading. There are rpms available (which will install on Fedora 14 - I have built and installed similar in parallel). Upgrade to lxc 0.9.0 FIRST and then try it. Upgrade to the latest Fedora and then ask... I refuse to even test on a Fedora 14 host (which I don't even have any longer and haven't had for almost a year). It makes no bloody sense. If it doesn't work, well, there's your first problem. I wouldn't even look at it at this point. That's got to be fundamental, to your ground work, to get up-to-date first. Fedora is nice and rock solid stable and I absolutely love it but it is intended for those of us who (yes - are batshit crazy and) want and demand the latest toys and features and have no fear of venturing onto the bleeding edge of technology. You accept that burden and responsibility
[Lxc-users] Issues in using lxc in Fedora 14
Hi, I am stuck with a issue in Fedora 14 using lxc. I have create a container using the template available at - https://launchpadlibrarian.net/83751818/lxc-fedora container is created successfuly and when I try lxc-start command I am getting stuck as shown below. There seems to be some issues with /etc/fstab. Any pointers or proper template to create a container would be of great help. # lxc-start -n test Welcome to Fedora Setting hostname localhost:[ OK ] Checking filesystems WARNING: couldn't open /etc/fstab: No such file or directory [ OK ] warning: can't open /etc/fstab: No such file or directory mount: can't find / in /etc/fstab or /etc/mtab Mounting local filesystems: warning: can't open /etc/fstab: No such file or directory [ OK ] No such file or directory Enabling /etc/fstab swaps: swapon: /etc/fstab: open failed: No such file or directory [FAILED] Entering non-interactive startup Bringing up loopback interface:[ OK ] Bringing up interface eth0: Determining IP information for eth0... done. [ OK ] Starting system logger:[ OK ] awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) awk: cmd. line:1: fatal: cannot open file `/etc/fstab' for reading (No such file or directory) Mounting other filesystems: warning: can't open /etc/fstab: No such file or directory [ OK ] ^[[17~^C^Z^F[root@localhost ~]# lxc-version lxc version: 0.7.2 -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] Using common rootfs for multiple containers
Hi, I would like it know is it possible to create a single rootfs (might be in read-only mode) and share it among multiple containers ? Currently for every container we create its own unique rootfs. What would be the best place to look in code for using single rootfs across multiple containers. Regards, Ajith -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Regarding creating a LXC container in fedora 17
[1281973.370052] [c044007b] ? console_start+0xb/0x20
[1281973.370052] [c0979bbf] ? _raw_spin_unlock_irqrestore+0xf/0x20
[1281973.370052] [c07918d6] ? ata_scsi_queuecmd+0x96/0x250
[1281973.370052] [c076ad18] ? scsi_dispatch_cmd+0xb8/0x260
[1281973.370052] [c066007b] ? queue_store_random+0x4b/0x70
[1281973.370052] [c07711b3] ? scsi_request_fn+0x2c3/0x4b0
[1281973.370052] [c042f2b7] ? kvm_clock_read+0x17/0x20
[1281973.370052] [c0409448] ? sched_clock+0x8/0x10
[1281973.370052] [c065cace] ? __blk_run_queue+0x2e/0x40
[1281973.370052] [c066214a] ? blk_execute_rq_nowait+0x6a/0xd0
[1281973.370052] [c066221d] ? blk_execute_rq+0x6d/0xe0
[1281973.370052] [c06620b0] ? __raw_spin_unlock_irq+0x10/0x10
[1281973.370052] [c0446ba7] ? irq_exit+0x67/0xb0
[1281973.370052] [c04258ee] ? smp_apic_timer_interrupt+0x5e/0x90
[1281973.370052] [c097a440] ? apic_timer_interrupt+0x34/0x3c
[1281973.370052] [c076ffa0] ? scsi_execute+0xb0/0x140
[1281973.370052] [c0771429] ? scsi_execute_req+0x89/0x100
[1281973.370052] [c077f3d5] ? sr_check_events+0xb5/0x2e0
[1281973.370052] [c07a64cd] ? cdrom_check_events+0x1d/0x40
[1281973.370052] [c077f856] ? sr_block_check_events+0x16/0x20
[1281973.370052] [c06663c5] ? disk_check_events+0x45/0xf0
[1281973.370052] [c0666485] ? disk_events_workfn+0x15/0x20
[1281973.370052] [c045788e] ? process_one_work+0x12e/0x3d0
[1281973.370052] [c097a440] ? apic_timer_interrupt+0x34/0x3c
[1281973.370052] [c0459939] ? worker_thread+0x119/0x3b0
[1281973.370052] [c0459820] ? flush_delayed_work+0x50/0x50
[1281973.370052] [c045e2a4] ? kthread+0x94/0xa0
[1281973.370052] [c0980ef7] ? ret_from_kernel_thread+0x1b/0x28
[1281973.370052] [c045e210] ? kthread_create_on_node+0xc0/0xc0
[1281973.370052] Code: 5d c3 8d b4 26 00 00 00 00 89 02 c3 90 8d 74 26 00
81 fa ff ff 03 00 89 d1 77 2e 81 fa 00 00 01 00 76 0e 81 e2 ff ff 00 00 66
ef c3 90 8d 74 26 00 55 ba 2c 5a b2 c0 89 e5 89 c8 e8 01 ff ff ff
[1281991.139165] ata2: lost interrupt (Status 0x58)
[1281991.148055] ata2: drained 12 bytes to clear DRQ
[1281991.165039] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[1281991.172924] sr 1:0:0:0: CDB:
[1281991.172932] Get event status notification: 4a 01 00 00 10 00 00 00 08
00
[1281991.497342] ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio
16392 in
[1281991.497342] res 40/00:02:00:04:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[1281991.523767] ata2.00: status: { DRDY }
[1281991.616161] ata2: soft resetting link
[1281998.232648] ata2.01: qc timeout (cmd 0xec)
[1281998.238559] ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
[1281998.247432] ata2: soft resetting link
[1281998.575468] ata2.01: NODEV after polling detection
[1281998.698009] ata2.00: configured for MWDMA2
[1281998.714460] ata2: EH complete
3. Last but not least after sometime my host kernel crashed as a result
need to restart the VPC.
Regards,
Ajith
On Thu, May 16, 2013 at 8:09 PM, Ajith Adapa ajith.ad...@gmail.com wrote:
Thanks @thomas and @michael.
I will try the RPMs and steps provided to start a container.
Regards,
Ajith
On Wed, May 15, 2013 at 2:01 PM, Thomas Moschny
thomas.mosc...@gmail.comwrote:
2013/5/14 Michael H. Warfield m...@wittsend.com:
What I would recommend as steps on Fedora 17...
Download lxc-0.9.0 here:
http://lxc.sourceforge.net/download/lxc/lxc-0.9.0.tar.gz
You should have rpm-build and friends installed via yum on your system.
Build the lxc rpms by running rpmbuild (as any user) as follows:
You could also try using the pre-built packages I put here:
http://thm.fedorapeople.org/lxc/ .
Regards,
Thomas
--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Regarding creating a LXC container in fedora 17
Sorry for the confusion.
In case of issue 3, I felt host kernel crashed because of the soft lock
issue mentioned in Issue 2.That's the reason I was saying as a result of
... Ideally speaking I haven't done anything other than creating the
lxc-container at the time. Once I restarted the host machine after crash I
havent observed any issues.
Then I have started the container using below command and tried to connect
to its shell using lxc-console command but I ended up with below message.
Ideally I should see a prompt but its just hangs down there. Ctl+a q
works and nothing else.
[root@ipiblr ~]# lxc-start -n TEST -d
[root@ipiblr ~]# lxc-console -n TEST
Type Ctrl+a q to exit the console, Ctrl+a Ctrl+a to enter Ctrl+a itself
Regards,
Ajith
On Sat, May 18, 2013 at 5:55 PM, Michael H. Warfield m...@wittsend.comwrote:
Hello,
On Sat, 2013-05-18 at 12:35 +0530, Ajith Adapa wrote:
Hi,
I have installed all the rpms created by @thomas and followed @michael
steps to start a lxc container.
I have a doubt.
1. When I give lxc-create command I came across huge download of various
files.
As per my understanding rootfs is created for new container (where can i
get the steps for it ? ).
Steps for what? It's in /var/lib/lxc/{Container}/rootfs/
But I see below log. Is there any issue ?
Copy /var/cache/lxc/fedora/i686/17/rootfs to
/var/lib/lxc/TEST/TEST/rootfs
...
Copying rootfs to /var/lib/lxc/TEST/TEST/rootfs ...setting root passwd to
root
installing fedora-release package
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
The warnings are perfectly normal and harmless. I ran into this with
recent versions of yum and researched it. It's because /proc is not
mounted in the container itself when the container is being created.
You can ignore them.
Package fedora-release-17-2.noarch already installed and latest version
Nothing to do
Again, normal.
container rootfs and config created
'fedora' template installed
'TEST' created
Looks like your container was created. I don't see a problem.
2.I see a SOFT LOCK issue with latest version kernel shown below.
# uname -a
Linux blr 3.8.8-100.fc17.i686 #1 SMP Wed Apr 17 17:26:59 UTC 2013 i686
i686
i386 GNU/Linux
[1098069.351017] SELinux: initialized (dev binfmt_misc, type
binfmt_misc),
uses genfs_contexts
[1281973.370052] BUG: soft lockup - CPU#0 stuck for 23s!
[kworker/0:1:2201]
I've seen that on my Dell 610's but they haven't caused any real
failures. Not quite sure what that is.
[1281973.370052] Modules linked in: binfmt_misc lockd sunrpc snd_intel8x0
snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm i2c_piix4 i2c_core
microcode virtio_balloon snd_page_alloc snd_timer snd soundcore
virtio_net
uinput virtio_blk
[1281973.370052] Pid: 2201, comm: kworker/0:1 Not tainted
3.8.8-100.fc17.i686 #1 Bochs Bochs
[1281973.370052] EIP: 0060:[c068b17a] EFLAGS: 0206 CPU: 0
[1281973.370052] EIP is at iowrite16+0x1a/0x40
[1281973.370052] EAX: 0001 EBX: f69b3000 ECX: 0001c050 EDX: c050
[1281973.370052] ESI: e9d9b600 EDI: EBP: f5009b90 ESP: f5009b8c
[1281973.370052] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[1281973.370052] CR0: 8005003b CR2: 09cae530 CR3: 345e CR4: 06d0
[1281973.370052] DR0: DR1: DR2: DR3:
[1281973.370052] DR6: 0ff0 DR7: 0400
[1281973.370052] Process kworker/0:1 (pid: 2201, ti=f5008000
task=f6830cb0
task.ti=f4bb2000)
[1281973.370052] Stack:
[1281973.370052] c07107cd f5009b9c c070ffb9 f4a17a00 f5009bcc f7c36f2b
e9d9b600
[1281973.370052] 0020 e9d9b600 f69b2000
f4b5a740 0036
[1281973.370052] f5009c00 c088ea5e e9d9b600 f7c384c0 f6822600
f69b2000
[1281973.370052] Call Trace:
[1281973.370052] [c07107cd] ? vp_notify+0x1d/0x20
[1281973.370052] [c070ffb9] virtqueue_kick+0x19/0x20
[1281973.370052] [f7c36f2b] start_xmit+0x14b/0x370 [virtio_net]
[1281973.370052] [c088ea5e] dev_hard_start_xmit+0x24e/0x4c0
[1281973.370052] [c08a793f] sch_direct_xmit+0xaf/0x180
[1281973.370052] [c088f01e] dev_queue_xmit+0x12e/0x370
[1281973.370052] [c08bf670] ? ip_fragment+0x870/0x870
[1281973.370052] [c08bf88e] ip_finish_output+0x21e/0x3b0
[1281973.370052] [c08bf670] ? ip_fragment+0x870/0x870
[1281973.370052] [c08c0354] ip_output+0x84/0xd0
[1281973.370052] [c08bf670] ? ip_fragment+0x870/0x870
[1281973.370052] [c08bfb00] ip_local_out+0x20/0x30
Re: [Lxc-users] Regarding creating a LXC container in fedora 17
Hmm sounds one more road block for using lxc in fedora 17 because of
systemd.
Currently there is no place where there is a guide for starting up with LXC
for latest fedora versions. I think a page in fedoraproject would be of
great help with the known issues and steps using lxc under various fedora
versions.
I am really thinking to start using LXC containers in fedora 14. Build and
Boot it up with latest stable kernel version (Might be 3.4) and LXC version
(0.9) and try out using LXC- containers :)
On Sat, May 18, 2013 at 7:28 PM, Michael H. Warfield m...@wittsend.comwrote:
On Sat, 2013-05-18 at 19:02 +0530, Ajith Adapa wrote:
Sorry for the confusion.
In case of issue 3, I felt host kernel crashed because of the soft
lock issue mentioned in Issue 2.That's the reason I was saying as a
result of ... Ideally speaking I haven't done anything other than
creating the lxc-container at the time. Once I restarted the host
machine after crash I havent observed any issues.
Then I have started the container using below command and tried to
connect to its shell using lxc-console command but I ended up with
below message. Ideally I should see a prompt but its just hangs down
there. Ctl+a q works and nothing else.
[root@ipiblr ~]# lxc-start -n TEST -d
[root@ipiblr ~]# lxc-console -n TEST
Type Ctrl+a q to exit the console, Ctrl+a Ctrl+a to enter Ctrl+a
itself
Oh, crap... I keep forgetting about that (because I don't use it).
That needs to be noted somewhere in the documentation.
That's yet another BAD decision on the part of the systemd crowd,
lxc-console is probably not going to work, at least for the time being.
They (systemd) intentionally, with documented malice a forethought,
disable gettys on the vtys in the container if systemd detects that it's
in a container. However, /dev/console in the container is still active
and is connected to lxc-start and I'm able to log in there but I have
never gotten lxc-console to work with a systemd container and I don't
know of anything I can do about it. You would need some way to force
the container to start gettys on the vtys.
Maybe, if I (or someone else) can figure out a way to do that (force the
gettys to start on the vtys), it could be integrated into the Fedora
template. My patches for the autodev stuff (plus other stuff) have now
been accepted and applied by Serge, so that's done. Maybe I can look
deeper into this morass now.
Regards,
Mike
Regards,
Ajith
On Sat, May 18, 2013 at 5:55 PM, Michael H. Warfield
m...@wittsend.com wrote:
Hello,
On Sat, 2013-05-18 at 12:35 +0530, Ajith Adapa wrote:
Hi,
I have installed all the rpms created by @thomas and
followed @michael
steps to start a lxc container.
I have a doubt.
1. When I give lxc-create command I came across huge
download of various
files.
As per my understanding rootfs is created for new container
(where can i
get the steps for it ? ).
Steps for what? It's in /var/lib/lxc/{Container}/rootfs/
But I see below log. Is there any issue ?
Copy /var/cache/lxc/fedora/i686/17/rootfs
to /var/lib/lxc/TEST/TEST/rootfs
...
Copying rootfs to /var/lib/lxc/TEST/TEST/rootfs ...setting
root passwd to
root
installing fedora-release package
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
warning: Failed to read auxiliary vector, /proc not mounted?
The warnings are perfectly normal and harmless. I ran into
this with
recent versions of yum and researched it. It's because /proc
is not
mounted in the container itself when the container is being
created.
You can ignore them.
Package fedora-release-17-2.noarch already installed and
latest version
Nothing to do
Again, normal.
container rootfs and config created
'fedora' template installed
'TEST' created
Looks like your container was created. I don't see a problem.
2.I see a SOFT LOCK issue with latest version kernel shown
below.
# uname -a
Linux blr 3.8.8-100.fc17.i686 #1 SMP Wed Apr 17 17:26:59 UTC
2013 i686 i686
i386 GNU/Linux
Re: [Lxc-users] Regarding creating a LXC container in fedora 17
Thanks @thomas and @michael. I will try the RPMs and steps provided to start a container. Regards, Ajith On Wed, May 15, 2013 at 2:01 PM, Thomas Moschny thomas.mosc...@gmail.comwrote: 2013/5/14 Michael H. Warfield m...@wittsend.com: What I would recommend as steps on Fedora 17... Download lxc-0.9.0 here: http://lxc.sourceforge.net/download/lxc/lxc-0.9.0.tar.gz You should have rpm-build and friends installed via yum on your system. Build the lxc rpms by running rpmbuild (as any user) as follows: You could also try using the pre-built packages I put here: http://thm.fedorapeople.org/lxc/ . Regards, Thomas -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] Regarding creating a LXC container in fedora 17
Hi, Sorry for my basic question as I am new to LXC. I would like to know the steps to create a LXC container using lxc in fedora 17. I have searched for the same in google but I am not able to find any useful posts to do the same. It would be more helpful if anyone can share the steps if they got any. Regards, Ajith -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
