qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu Questions
Date: Sat, 10 Nov 2007 01:57:31 +0000	[thread overview]
Message-ID: <20071110015730.GA5875@redhat.com> (raw)
In-Reply-To: <47350C9C.3090500@mmri.us>

On Fri, Nov 09, 2007 at 08:42:52PM -0500, admin@mmri.us wrote:
> I must apologize for subscribing to this list, but the Qemu users list 
> is dead, sop this is my only option.
> I understand it is a development list, but I would appreciate some help.
> 
> I will make it concise.
> 
> 1) What is the best Distro to run Qemu on with the least hassles?
> FYI, I now run it on FC7, but it is a lot of trouble. kqemu refuses to 
> work on FC7 on a v20z Sun dual cpu dual core rack server
> XEN just completely doesnt load even though  the Kernel is XEN, but at 
> least qemu works with the following Caveat;
> "Could not open '/dev/kqemu' - QEMU acceleration layer not activated"

As a general rule (with a couple of exception) Fedora only ships kernel
modules which are in upstream LKML sources. kqemu is not upstream, so it
is not included in Fedora RPMs for QEMU.

> 2)  Does an activated QEMU acceleration layer (missing above)  make a 
> huge difference?

Yes, it improves performance signficantly - although not all OS will run
under kqemu.

> 3) I have several operating systems successfully loaded in Qemu 
> sessions, but networking is just not working. I worked through loads of  
> FAQs from the net, but to no avail.

With Fedora 7 you can try  'virt-manager' which will let you setup QEMU
guests, which by default have NAT'd access to the outside world. If you
setup your host network in appropriate manner they can also be bridged
In this doc where you see 'kvm' - 'qemu' applies  just the same way

http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt

The main potential gotcha I know is that ip_forward must be enabled

eg, 

$ /sbin/sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1


> 4) Finally is there a preferred distro which is known to solve all the 
> problems mentioned above?

Networking should work correctly for NAT & bridging (assuming suitable host
config). KQEMU won't work in Fedora since the module is not upstream.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-11-10  1:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  1:42 [Qemu-devel] Qemu Questions admin
2007-11-10  1:57 ` Daniel P. Berrange [this message]
2007-11-10  2:53   ` admin
2007-11-10  3:34   ` admin
2007-11-10  3:48     ` admin
2007-11-10  2:06 ` Jonathan Kalbfeld

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=20071110015730.GA5875@redhat.com \
    --to=berrange@redhat.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).