"Stephen Borrill" <netbsd@precedence.co.uk> wrote in message 
news:Pine.NEB.4.64.0711201927210.29488@ugly.precedence.co.uk...
> On Tue, 20 Nov 2007, Zachary Kline wrote:
>>>>    This is good news.  When I've ran 4.0 with -no-acppi, I still get 
>>>> poor
>>>> networking performance.  In fact, ne2k and all other network devices 
>>>> seem
>>>> to
>>>> time out regularly.  I never noticed this in 3.1.  In fact, ne2's
>>>> performance is so poor that the DHCP request goes unacknowledged...
>>>>    I hope this won't be an issue in the real 4.0.  Any tips in the
>>>> meantime
>>>> to work around it?
>>>
>>> What networking options are you using? By default, qemu uses its own
>>> user-mode stack and so DHCP is done by qemu itself.
>>   Hi,
>>    I use either -net tap, or -net user as you suggest.  Both give 
>> extremely
>> poor performance with -no-acpi.  I don't quite understand why this is,
>> myself.
>
> Are you seeing a significant difference between -no-acpi and disable acpi 
> from bootconf? I've been using the latter very heavily recently, but I've 
> not seen much difference with -no-acpi.
>
Hi,
    I supply -no-acpi on the qemu command line, after which networking goes 
to the dogs.  It's either that, it seems, or not have network cards be 
detected at all, which I find a little strange.  I haven't yet tried 
disabling ACPI from the NetBSD side.
Thanks,
Zack.