[Lxc-users] LXC + VirtualBox = Frozen Host

Okky mawcikurl at gmail.com
Thu Nov 22 16:09:25 UTC 2012


Hi Derek, 

Currently VirtualBox is the only virtualization technology running on the host OS as I found myself quite comfortable with it.

I did once try to run KVM after VirtualBox was running on my other host and the KVM refused, saying that the specific virtualization technology on the CPU was already being used by other hypervisor, and vice versa but no freeze-up happening.

Where should I be looking at to see what is going on under the hood when the froze happen next time?

Thank you! 

-- 
Okky
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Monday, November 19, 2012 at 7:00, Derek Simkowiak wrote:

>     Be sure you are not also running KVM, VMware, or any other VM software.  At this writing, only one virtualization platform can run at a time.
> 
>     LXC is not a virtualization platform (because it doesn't run multiple kernels on one CPU).  So your VirtualBox freeze-ups are probably not related to the use of LXC (but I haven't tried it myself).
> 
> 
> --Derek
> 
> On 11/18/2012 10:03 AM, John Drescher wrote:
> > > I have been seeing reproducible freezes each time I start a VirtualBox VM when at least one of my LXC containers are already running. Even my mouse cursor is frozen, and all I could do is a hard reset each time. 
> > > 
> > > Here are some of the cases that I have tried:
> > > 1.) Starting a VirtualBox VM when an LXC container is already running effectively freezes the host.
> > > 2.) Starting an LXC container when a VirtualBox VM is already booted is fine. 
> > > 3.) Starting another LXC container after point (2) is also fine.
> > > 4.) Starting antother VirtualBox VM after point (3) is also fine.
> > > 
> > > Could somebody kindly share some light here? It seems that the initial startup of the VirtualBox module is the trigger here. Does LXC and VirtualBox really could co-exists together at the same time? 
> > 
> > Yes. They have no problem working together for me.
> >  
> > > 
> > > I intend to utilize the VirtualBox VMs for other-than-Linux-workload, whereas the LXC containers for all Linux workload. For the info, the host is a Linux Mint 13 (3.2.0-33-generic 64-bit) using VirtualBox 4.2.4. Both VirtualBox VM's files and LXC container's rootfs are on top of ZFS filesystem.
> > 
> > I start with a newer kernel. 
> > 
> > John
> > 
> > 
> > ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov 
> > 
> > _______________________________________________ Lxc-users mailing list Lxc-users at lists.sourceforge.net (mailto:Lxc-users at lists.sourceforge.net) https://lists.sourceforge.net/lists/listinfo/lxc-users 
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20121122/9e95176d/attachment.html>


More information about the lxc-users mailing list