[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] QEMU virtual machine within virtual machine

From: Tony Su
Subject: Re: [Qemu-discuss] QEMU virtual machine within virtual machine
Date: Wed, 24 Dec 2014 11:50:27 -0800

 You probably need to be detailed in what you are trying to do.
What kind of app and/or development tools do you want to run?
What is your reason for even virtualizing? If you're going to run Kali
as your HostOS (not in a QEMU VM), maybe you should consider no
virtualization and try to install your development tools into your


On Tue, Dec 23, 2014 at 12:29 AM, Rachel Attias (raattias)
<address@hidden> wrote:
> Hi Tony et all,
> Thanks a lot for your response. I am new to QEMU & OpenWRT. I would really 
> appreciate if you can answer a couple of my questions to help me understand 
> what exactly I need.
> First - I am not really concerned with performance at this point. I just want 
> an off-shore system in which I can create & test apps for my TP-Link router, 
> without ruining it.
> Second - I did compile & load QEMU on my Kali linux machine, but I see that 
> QEMU is intended to work only with a pre-prepared images. I found online a 
> minimal testing Linux image, and it is working.
> But this does not feel like what I expected from OpenWRT. I expected it to be 
> a framework in which I can create apps and so. Am I mis-understanding 
> something basic here?
> Thanks,
> Rachel
> -----Original Message-----
> From: Tony Su [mailto:address@hidden
> Sent: Monday, December 22, 2014 9:08 PM
> To: Rachel Attias (raattias)
> Cc: address@hidden
> Subject: Re: [Qemu-discuss] QEMU virtual machine within virtual machine
>  Running paravirtualization within paravirtualization (or full
> virtualization) performs very poorly.
> If you want to do something like this, I'd highly recommend Linux Containers, 
> the current best implementation is probably Docker.
> Docker (and other Linux Container implementations) merely <isolates> Guests, 
> and does not use a paravirtualized kernel (ie. using hardware AMD or Intel 
> CPU extensions). Instead, the processes for each Guest are isolated from each 
> other but run as "full citizen" processes, all equal to each other. This lack 
> of kernel emulation/virtualization allows you to nest Guests within each 
> other if you want and all will run without any performance hit.
> So, as examples you can use one instance of a paravirtualized Guest, but run 
> the Guest within any number of Docker instances or run Docker instances 
> within your paravirtualized Guest.
> Tony
> On Sun, Dec 21, 2014 at 7:35 AM, Rachel Attias (raattias) <address@hidden> 
> wrote:
>> Hi All,
>> I am trying to set up a QEMU virtual machine in Linux. But I don’t
>> have root permissions, so my “make install” is failing.
>> I have a Kali Linux virtual machine on my laptop.
>> Does it make sense to install & run the QEMU virtual machine within
>> the Kali virtual machine?
>> Thanks,
>> Rachel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]