Re: [Qemu-devel] sparc guest

[Andreas Färber]

Am 27.06.2007 um 22:43 schrieb Blue Swirl:

> On 6/27/07, Nigel Horne <address@hidden> wrote:
> > Thiemo Seufer wrote:
> > > Blue Swirl wrote:
> > >> On 6/25/07, Thiemo Seufer <address@hidden> wrote:
> > >>> Nigel Horne wrote:
> > >>>> Good news, sparc emulation with -nographic no longer core dumps.
> > >>>>
> > >>>> The bad news, networking still fails:
> > >>> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe  
> > that's
> > >>> related.
> > >> On my test cases the network is still fine. What was the setup  
> > again?
> > >
> > > What I see is apparently not triggered by a change in Qemu. An  
> > older
> > > 2.6.16 kernel works with current Qemu, but 2.6.21 breaks  
> > networking.
> >
> > 2.6.16 and 2.6.21 are not involved here. My host is running 2.6.20,
> > the guest is running 2.6.8.
>
> I just updated guest from Debian 3.1r1 to 4.0. After reboot net still
> works fine (4Mbytes/s), though the kernel is still 2.4.29. I tried
> installing a 2.6 series kernel but something went wrong with the ram
> disk creation. Host is 2.6.18.

My guest is using 4.0's 2.6.18 and it does not work for me (host OS X  
v10.4.10).

I also sometimes get this:
...
Starting Hardware abstraction layer: hald
floppy driver state
-------------------
now=4294959146 last interrupt=4294937998 diff=21148 last called  
handler=f0120824
timeout_message=lock fdc
last output bytes:
13 80 4294937998
 0 80 4294937998
1a 80 4294937998
 0 80 4294937998
12 80 4294937998
 0 80 4294937998
14 80 4294937998
18 80 4294937998
 8 80 4294937998
12 80 4294958847
 0 80 4294958847
13 80 4294958847
 0 80 4294958847
1a 80 4294958847
 0 80 4294958847
 3 80 4294958847
c1 80 4294958847
11 80 4294958847
 7 80 4294958847
 0 80 4294958847
last result at 4294937998
last redo_fd_request at 4294958843

status=80
fdc_busy=1
do_floppy=f01205ac
cont=f01dd0f8
current_req=00000000
command_status=-1

floppy0: floppy timeout called
.
Starting DHCP D-Bus daemon: dhcdbd.
...

So maybe it's a more general problem with interrupt handling?
Lance complains about timeouts, too, and so did DHCP during  
installation.

Andreas