From: "Alexey Eremenko" <al4321@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Merging improvements from VirtualBox OSE into qemu?
Date: Wed, 24 Dec 2008 13:31:58 +0000 [thread overview]
Message-ID: <7fac565a0812240531s202b3dafm5ccd8516f21292d4@mail.gmail.com> (raw)
In-Reply-To: <49522F8D.4000203@turnkeylinux.org>
On Wed, Dec 24, 2008 at 12:48 PM, Liraz Siri <liraz@turnkeylinux.org> wrote:
> Hi,
>
> I'm new to the list so let me introduce myself. I am one of the
> developers for TurnKey Linux, a new opensource project that develops a
> family of lightweight installable live CDs optimized for various
> server-type tasks including LAMP, Ruby on Rails, Django, Joomla, Drupal,
> MediaWiki, and others: http://www.turnkeylinux.org/
>
> This type of pre-integrated, ready-to-use system is typically called a
> software appliance: http://en.wikipedia.org/wiki/Software_appliance
>
> We use qemu heavily in our development/testing. We find it's better
> suited as a scriptable primitive than other opensource alternative such
> as VirtualBox. Thankfully the KVM fork has gotten rid of the performance
> disadvantage qemu used to suffer from.
>
> Anyhow, I've recently explored the latest release of VirtualBox (which I
> understand is based on qemu).
>
> Two major changes in version 2.1 caught my attention:
>
> 1) complex setup is no longer required for "bridged" networking:
>
> This is a big win for us as the former networking setup complexity
> indirectly made TurnKey appliances much more difficult for regular
> users to set up.
>
> VirtualBox came to its senses and realized the tap configuration mess
> was way too complex for most users and cumbersome even for advanced
> users. Also, I don't think it worked with wireless NICs.
>
> In the latest release, "host interface networking" just works. The
> user simply selects which NIC to connect the guest to (e.g., eth0)
> and they're done.
>
> Behinds the scenes VirtualBox is putting your NIC into promisc mode to
> sniff packets to guests and injecting packets directly to the NIC.
> Essentially it creates a virtual NIC in software.
>
> This works without root privileges somehow, probably by taking
> advantage of new infrastructure in the VirtualBox device driver.
Yes, the new networking option makes life easier - and it works
without root if you are part of "vboxusers" group on your PC.
This feature is unlikely to be copied, because it is part of the
"vboxdrv" driver + part of the GUI.
However, other features, such as improved ICMP support via NAT, may
eventually make it into Qemu/KVM.
--
-Alexey Eromenko "Technologov"
next prev parent reply other threads:[~2008-12-24 13:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 12:48 [Qemu-devel] Merging improvements from VirtualBox OSE into qemu? Liraz Siri
2008-12-24 13:17 ` Samuel Thibault
2008-12-24 13:26 ` Alexey Eremenko
2008-12-24 13:31 ` Alexey Eremenko [this message]
2008-12-24 13:36 ` Paul Brook
2008-12-24 14:33 ` Liraz Siri
2008-12-24 14:51 ` Jernej Simončič
2008-12-24 15:02 ` Paul Brook
2008-12-24 15:29 ` Liraz Siri
2008-12-24 15:40 ` Anthony Liguori
2008-12-24 20:52 ` Liraz Siri
[not found] ` <E71DFB2B-0B73-46AE-B423-0BF605A9D679@hotmail.com>
2008-12-25 4:37 ` C.W. Betts
2008-12-25 7:06 ` Avi Kivity
2008-12-25 7:07 ` Avi Kivity
2008-12-25 7:08 ` Avi Kivity
2008-12-25 14:51 ` Liraz Siri
2008-12-25 16:14 ` Avi Kivity
2008-12-24 23:18 ` Jamie Lokier
2008-12-25 7:11 ` Avi Kivity
2008-12-24 15:23 ` Anthony Liguori
2008-12-24 20:21 ` Liraz Siri
2008-12-24 20:55 ` Liraz Siri
2009-01-05 21:12 ` Frank Mehnert
2009-01-05 22:03 ` Stefan Weil
2009-01-05 23:58 ` Anthony Liguori
2009-01-06 7:41 ` Frank Mehnert
2009-01-06 15:46 ` Blue Swirl
2009-01-06 17:33 ` Anthony Liguori
2009-01-06 20:40 ` Frank Mehnert
2009-01-06 22:17 ` Jamie Lokier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fac565a0812240531s202b3dafm5ccd8516f21292d4@mail.gmail.com \
--to=al4321@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).