[Top][All Lists]

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

Re: [Qemu-discuss] Coldfire 5208 Network

From: William Mahoney
Subject: Re: [Qemu-discuss] Coldfire 5208 Network
Date: Thu, 28 Sep 2017 22:04:12 +0000

Then this:


is kind of misleading: "For example, if you are emulating a particular embedded 
board, then you should use the virtual network device that matches that 
embedded board's configuration."

So you’re saying that as long as “I don’t touch anything” I should be able to 
netcat between the 5208 and a bash on the same host? Assuming the host and the 
guest are on the same subnet? (So I should just force the host IP to be on the 
same 10…. sublet that QEMU?)

Then would I also be able to redirect with the old-style -redirect option as 
well so that I can get to port 80?



On Sep 28, 2017, at 4:50 PM, Peter Maydell 
<address@hidden<mailto:address@hidden>> wrote:

On 28 September 2017 at 14:40, William Mahoney 
<address@hidden<mailto:address@hidden>> wrote:

Still stuck on this most of the afternoon. Here’s what I am trying to do:

./bin/qemu-system-m68k -trace events=/tmp/events \
                          -cpu m5208 \
                          -M mcf5208evb \
                          -kernel ./coldfire-test-0.1/vmlinux-2.6.21-uc0 \
user,id=net0,net=,host=,restrict=off \
filter-dump,id=f1,netdev=net0,file=temp_net.pcap \

But I need the device set up on the guest side, so I go add:

         -device mcf-fec,netdev=net0

This won't work. -device is for pluggable devices (ie ones which
the end-user can plug in, like PCI or ISA devices). It doesn't
work for devices that are built in to the SoC or board and always
exist (and the mcf5208 ethernet is one of those).

You can only use "new style" -netdev/-device networking command
line options with pluggable devices. For builtin ethernet devices
you have to use the "old style" networking command line options
which are all "-net".

The default (ie don't specify any -net or -netdev options at all)
should I think give you user mode networking (it is equivalent to
-net user -net nic), which ought to be fine for your purposes;
just don't try to test it using "ping", because usermode networking
doesn't support ping.

-- PMM

reply via email to

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