qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Carrera <dcarrera@gmail.com>
To: Cliff Wright <cliff@snipe444.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Networking problems
Date: Thu, 12 Aug 2010 22:15:26 +0200	[thread overview]
Message-ID: <AANLkTi=b0XnFKXMH609FVj23XW5HAXMvgPaqik7zNB5N@mail.gmail.com> (raw)
In-Reply-To: <20100812123548.67ae33ce.cliff@snipe444.org>

On Thu, Aug 12, 2010 at 9:35 PM, Cliff Wright <cliff@snipe444.org> wrote:
> Its been a while since updating qemu, so on old version I had
> -net nic,model=ne2k_pci -net user -redir tcp:2023::22 -soundhw es1370
> is the missing "-net user" causing you trouble?

Actually, yes, the "-net user" flag makes a difference. The QEMU
documentation *says* that it is not necessary, so I omitted it. But if
you add "-net user" then at least NetBSD can get an IP and gateway
from QEMU's DHCP server.

Unfortunately, that's as far as it goes. It still cannot go online.
When NetBSD tries to "ping 10.0.2.3" (gateway I think) it just gets
100% packet loss. Let me show you qemu's output on the command line:

--------%<--------
$ qemu -cdrom foo.iso -hda bar.img -net nic,model=ne2k_pci -net user -no-acpi
open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
--------%<--------

Judging from wikipedia, KVM is a reference to kernel-based native
virtualization using Intel VT-x or AMD-V. Unfortunately, my CPU is
just a bit to old to support VT-x so naturally I don't get KVM. But
QEMU should not require KVM to work, since that's a very recent
feature on Linux.

Daniel.
-- 
Intolerant people should be shot.

  reply	other threads:[~2010-08-12 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 17:12 [Qemu-devel] Networking problems Daniel Carrera
2010-08-12 19:35 ` Cliff Wright
2010-08-12 20:15   ` Daniel Carrera [this message]
2010-08-14 18:10     ` Mulyadi Santosa
2010-09-02  4:39 ` [Qemu-devel] " chandra shekar

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='AANLkTi=b0XnFKXMH609FVj23XW5HAXMvgPaqik7zNB5N@mail.gmail.com' \
    --to=dcarrera@gmail.com \
    --cc=cliff@snipe444.org \
    --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).