[Qemu-devel] Re: NE2000 problem found

[Qemu-devel] Re: NE2000 problem found

[Mike Nordell]

I have now seen some pretty convincing evidence that ASIC byte-writes
*shall* be honoured, and disregard the 8/16-bit mode as specified by (dcfg &
1).

Guest: Windows 2000 sp4.

While in 16-bit mode (dcfg & 1):
- It sets EN0_RCNTLO to an odd value.
- Writes everything as 16-bit values (outw) except for the last byte.
- Writes the last byte using outb, which triggers the interrupt.

So there should be a separate ne2000_asic_ioport_writeb.

I also have good reasons to believe there should not be a matching readb
function. As a test I did implement such a function, but then I got a MAC of
52-52-54-54-00-00 :-)

/Mike

[Qemu-devel] IDE issues?? (Was re: NE2000 problem found)

[Tim]

> Guest: Windows 2000 sp4.

Sorry to change the subject, but how did you go about getting sp4 to
install?  I have tried numerous changes and installation methods within
the guest OS, but SP4 just refuses to install.  It stops while "checking
for disk space" right before the final step, and then stops, saying "an
error occurred".

I am currently booting with:
  qemu -pci -cirrusvga -m 256 -cdrom win2k-install-cd.img\
	-hda win2k-cow.img -boot c -n "$TUN_SCRIPT"

I created the win2k-cow.img with:
  qemu-mkcow win2k-cow.img 6144


It has been this way for quite a while, and under slightly different
boot options.  I read in another thread that the IDE driver shows up in
a weird place in win2k's device manager.

Is it possible there are still issues that need to be worked out with
the IDE emulation?  Sorry, I don't know enough about this low-level
stuff to debug it myself.  Are there some logs in the guest or in qemu
that I can turn on that would help someone squash this one?

I appreciate any guidance.
thanks,
tim


PS- the cirrus emulation under win2k has been great so far (only tested
this evening).  Some broken-ness when switching modes in guest, but
after a restart of qemu, it all went back to normal.