From: Miguel Filipe <miguel.filipe@gmail.com>
To: qemu-devel@nongnu.org, users@crater.dragonflybsd.org
Subject: [Qemu-devel] Re: Running DragonFlyBSD on qemu, network device problems.
Date: Fri, 1 Apr 2005 13:04:18 +0100 [thread overview]
Message-ID: <f058a9c305040104046c267738@mail.gmail.com> (raw)
In-Reply-To: <f058a9c305040103573dd843db@mail.gmail.com>
Hi again,
On Apr 1, 2005 12:57 PM, Miguel Filipe <miguel.filipe@gmail.com> wrote:
> Sorry about that...
>
> On Apr 1, 2005 12:53 PM, Miguel Filipe <miguel.filipe@gmail.com> wrote:
> > Hi there,
> >
> > I'm running dragonflyBSD on a qemu virtual PC on top of linux.
> > Instalation went fine.
> >
> > Configuring the ethernet is the problem:
> > 1 - dhclient ed0 gives no valid address
> > 1.a - when using tun0 for the ethernet interface to qemu
> > dhclient results in the following kernel error/warning message:
> date kernel: ed0: device timeout
> - acording to qemu docs, the network interface is a ne2000 pci
>
> 1.b - when using qemu with -user-net the error doesn't occurr..
>
> 2 - how should one set-up a lan between the host OS (linux) and the
> guest OS in qemu (dragonflyBSD) ?
I've tried putting a dhcp server on the host OS running in the tun0
device and trying dhclient on dragonfly, but cannot tell if its ed0
device problems or me being stupid...
tcpdump tells me this:
tun0 is on host machine 10.0.0.254, and dhcpd.conf is configured for
10.0.0.5-10.
miguel@garfield:~/qemu/qemu$ sudo tcpdump -i tun0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun0, link-type EN10MB (Ethernet), capture size 96 bytes
13:02:29.479081 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 52:54:00:12:34:56, length: 300
13:02:29.480481 arp who-has 10.0.0.10 tell 10.0.0.254
13:02:30.002689 IP 10.0.0.254.bootps > 10.0.0.10.bootpc: BOOTP/DHCP,
Reply, length: 300
13:02:30.480340 arp who-has 10.0.0.10 tell 10.0.0.254
13:02:31.480200 arp who-has 10.0.0.10 tell 10.0.0.254
13:02:35.478582 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 52:54:00:12:34:56, length: 300
13:02:35.479423 IP 10.0.0.254.bootps > 10.0.0.10.bootpc: BOOTP/DHCP,
Reply, length: 300
those dhcp requests are from dragonflybsd...
Still dragonfly gets NO IP.
>
> I cannot send the dmesg or any other dragonfly info since I can't
> access it besides the console, and I cannot copy&paste it.
>
> TIA.
>
> >
> >
> > --
> > Miguel Sousa Filipe
> >
>
> Best regards to all,
>
> --
> Miguel Sousa Filipe
>
--
Miguel Sousa Filipe
prev parent reply other threads:[~2005-04-01 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 11:53 [Qemu-devel] Running DragonFlyBSD on qemu, network device problems Miguel Filipe
2005-04-01 11:57 ` [Qemu-devel] " Miguel Filipe
2005-04-01 12:04 ` Miguel Filipe [this message]
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=f058a9c305040104046c267738@mail.gmail.com \
--to=miguel.filipe@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=users@crater.dragonflybsd.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).