[Qemu-devel] QEMU 0.5.2 testing

[Qemu-devel] QEMU 0.5.2 testing

[Fabrice Bellard]

Hi,

I commited all the current fixes in the CVS. I will make the 0.5.2 
release tomorrow, so it would be interesting if some people could test 
it before it is officially released...

Fabrice.

Re: [Qemu-devel] QEMU 0.5.2 testing

[Herbert Poetzl]

On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> Hi,
> 
> I commited all the current fixes in the CVS. I will make the 0.5.2 
> release tomorrow, so it would be interesting if some people could test 
> it before it is officially released...

texi2html -monolithic -number qemu-doc.texi
make: texi2html: Command not found
make: *** [qemu-doc.html] Error 127

[removed the target]

-
usual set of compiler warnings, are you interested
in that output too?

-

seems to work as expected, with the folowing options

qemu-cvs-19.01.2004/i386/qemu-fast -s -nographic -L qemu-0.5.1/pc-bios -m 128 -snapshot -hda IMGs/TEST_32M.img -hdb IMGs/TEST_256M.img -kernel <kernelpath>/arch/i386/boot/bzImage -append "rw root=/dev/hda1

tested with/out -s for 2.4.24, 2.4.25-pre6 and 2.6.0 ...
two harddisk images 32M and 256MB in size ...

-

hmm didn't notice that one until now (seems like a bug) ...

Program received signal 0, Signal 0.
default_idle () at process.c:92
92	}
(gdb) break vfs_readdir
Breakpoint 1 at 0x90152640: file readdir.c, line 17.
(gdb) c
Continuing.

# ls /proc
# ls /tmp
# <nothing happens> CTRL-C

Program received signal 0, Signal 0.
default_idle () at process.c:92
92	}
(gdb) break sys_vserver
Breakpoint 2 at 0x901261f0: file vswitch.c, line 39.
(gdb) c
Continuing.

# ls /tmp

Program received signal SIGTRAP, Trace/breakpoint trap.
vfs_readdir (file=0xc183c189, filler=0x2e9c103, buf=0xde89a5f3) at readdir.c:17
17	{

(gdb) disable 1
(gdb) c
Continuing.

# sys_vserver (call)

Program received signal SIGTRAP, Trace/breakpoint trap.
sys_vserver (cmd=0, id=0, data=0x0) at vswitch.c:39
39	{


> Fabrice.
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.5.2 testing

[Fabrice Bellard]

Herbert Poetzl wrote:
> On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> 
>>Hi,
>>
>>I commited all the current fixes in the CVS. I will make the 0.5.2 
>>release tomorrow, so it would be interesting if some people could test 
>>it before it is officially released...
> 
> 
> texi2html -monolithic -number qemu-doc.texi
> make: texi2html: Command not found
> make: *** [qemu-doc.html] Error 127

In the distribution I add the html et man files, so it should not be a 
problem to most users (I am relunctant to add texi2html in the 
distribution).

> usual set of compiler warnings, are you interested
> in that output too?

I know they are warnings in translate.c about a function prototype. If 
you have others I am interested.

> seems to work as expected, with the folowing options
> 
> qemu-cvs-19.01.2004/i386/qemu-fast -s -nographic -L qemu-0.5.1/pc-bios -m 128 -snapshot -hda IMGs/TEST_32M.img -hdb IMGs/TEST_256M.img -kernel <kernelpath>/arch/i386/boot/bzImage -append "rw root=/dev/hda1
> 
> tested with/out -s for 2.4.24, 2.4.25-pre6 and 2.6.0 ...
> two harddisk images 32M and 256MB in size ...

So you don't use the '-kernel' option ? I am thinking about modifying 
this option so that the PC bios is used in all cases (it would allow to 
have the VGA output even with '-kernel'). A possible way would be to 
integrate a custom linux loader ROM, as it is done now in plex86.


> hmm didn't notice that one until now (seems like a bug) ...
> 
> Program received signal 0, Signal 0.
> default_idle () at process.c:92
> 92	}
> (gdb) break vfs_readdir
> Breakpoint 1 at 0x90152640: file readdir.c, line 17.
> (gdb) c
> Continuing.
> 
> # ls /proc
> # ls /tmp
> # <nothing happens> CTRL-C
> 
> Program received signal 0, Signal 0.
> default_idle () at process.c:92
> 92	}
> (gdb) break sys_vserver
> Breakpoint 2 at 0x901261f0: file vswitch.c, line 39.
> (gdb) c
> Continuing.
> 
> # ls /tmp
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> vfs_readdir (file=0xc183c189, filler=0x2e9c103, buf=0xde89a5f3) at readdir.c:17
> 17	{
> 
> (gdb) disable 1
> (gdb) c
> Continuing.
> 
> # sys_vserver (call)
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> sys_vserver (cmd=0, id=0, data=0x0) at vswitch.c:39
> 39	{

Do you have the problem if you don't use gdb ? Maybe my last TLB 
optimisations broke the gdb stub logic. I will check...

Fabrice.

Re: [Qemu-devel] QEMU 0.5.2 testing

[Jens Axboe]

On Mon, Jan 19 2004, Fabrice Bellard wrote:
> Hi,
> 
> I commited all the current fixes in the CVS. I will make the 0.5.2 
> release tomorrow, so it would be interesting if some people could test 
> it before it is officially released...

Works on ppc out-of-the-box. Trying to see if the w98 install will work
now.

There's still an odd issue with win98se (the version I can test here).
fdisk will report a read failure first time you invoke it, succeed the
next. After a reboot, if you try and format c: it will fail with "memory
allocation failure". If I run fdisk prior to format (twice, until it
succeeds), format c: will run fine afterwards.

-- 
Jens Axboe

Re: [Qemu-devel] QEMU 0.5.2 testing

[J. Mayer]

On Mon, 2004-01-19 at 00:09, Fabrice Bellard wrote:
> Hi,
> 
> I commited all the current fixes in the CVS. I will make the 0.5.2 
> release tomorrow, so it would be interesting if some people could test 
> it before it is officially released...

Hi.

I made random tests with several OSes I got:
- SkyOS v4.0a seems to boot but fails to  
  recognize IDE drives. It complains that 
  ATA_CMD_PID fails (status 0x41 error 0x4) 
  Then it seems to hang...
- ReactOS is unable to see IDE disk drives.
- QNX v6.21 starts booting but cannot detect 
  hard drives if I ask it to install. It seems to  
  hang after a few seconds when running 
  from CDROM. When I run it in debug mode,
  I got: "Crash[0,0] at nano_allox line 260".
  Who's got the sources :-) ?
  I got another version which crashes while 
  selecting boot options.
- Plan9 asks me where to boot from, and I 
  didn't found the right answer, so I loose...
- OS2 Warp3 install disks seems to wait for 
  another day to run. I can see the OS/2 
  prompt, then nothing...
- Oberon cannot find disks. With old driver, it 
  complains. With the standard ATAPI driver, 
  it crashes (qemu segfault) and I lose my 
  mouse (seems to be a sdl conflict). 
  Fortunately, I get it back if I re-run qemu.
- minix 2.0.4 starts but seems to have 
  problems with the floppy. I'll investigate...
- MenuetOS starts but complains that the 
  CPU isn't what it expects:
  "Fatal - CPU 386+ required."
- memtest86 reports some errors
  in test 5 (bloc move, cached). The 
  addresses seem like random, but it quite 
  always the bit 31 which fails. I can 
  reproduce it.
- ELKS runs but the keyboard is buggy:
  I need to keep playing with <CTRL> to
  have a correct mapping. And it seems
  to detect only 640kb of memory (but it may
  be normal ?).
- DrDOS 7.0.2 runs
- DrDOS 7.0.3 seems to hang when 
  launching HIMEM.SYS (doesnt't refresh the
  screen anymore).
- Atari GEMDOS doesn't run, don't ask
  me why :-)
- All MSDOS variants I got boot
- FreeBSD now boots. In facts, it mounts its
  root partition, then I get no messages. Still 
  some fdc problems...
- OpenDarwin 6.1 complains that it don't 
  recognize the CPU type. Seems to run, but I
  don't have any output after the very first 
  messages.
- NetBSD 1.6.1 still runs.
- OpenBSD 3.4 likes 1.5 GHz PPro !
  but stops while trying to open the console...
  (qemu then don't consume any host CPU).
- Beos:
  qemu: fatal: invalid tss type
  EAX=00000000 EBX=00000000 ECX=00000001 EDX=00000000
  ESI=00000000 EDI=00000004 EBP=ffffffff ESP=1ed08c50
  EIP=fc800000 EFL=00321302 [-------]    CPL=3 II=0
  ES =9fe5 0009fe50 0000ffff 00000000
  CS =75b1 00075b10 0000ffff 00000000
  SS =d88e 000d88e0 0000ffff 00000000
  DS =5d0a 0005d0a0 0000ffff 00000000
  FS =88cf 00088cf0 0000ffff 00000000
  GS =1eb1 0001eb10 0000ffff 00000000
  LDT=0000 00000000 0000ffff 00008000
  TR =0000 00000000 0000ffff 00008000
  GDT=     000080e2 00000057
  IDT=     0007f000 000007ff
  CR0=60000011 CR2=00000000 CR3=00000000 CR4=00000000
  CCS=00000055 CCD=000ffe6c CCO=EFLAGS  
  ST0=0.000000 ST1=0.000000 ST2=0.000000 ST3=0.000000
  ST4=0.000000 ST5=0.000000 ST6=1428.276747 ST7=0.500000
  I can reproduce this with all the boot
  floppies I got.
  I got another CD which doesn't crash, but
  seems completely hanged...
- AROS seems to have video problems

I must try to run all those OSes under bochs to see how they run. Or I
may be courageous and install a test PC... I know that my BeOS, QNX,
os2, DrDOS and xxxBSD images run on a real PC.

Regards.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

Re: [Qemu-devel] QEMU 0.5.2 testing

[Lennert Buytenhek]

On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:

> I commited all the current fixes in the CVS. I will make the 0.5.2 
> release tomorrow, so it would be interesting if some people could test 
> it before it is officially released...

NetBSD 1.6.1 install CD: says "npx0 at isa0 port 0xf0-0xff: error reporting
broken; not using" during kernel boot, but continues.  When commencing the
install to disk, it complains "wdc_atapi_intr: warning: reading only 1 of 2
bytes" and seem to hang -- it makes no progress at least for a minute.

FreeBSD 5.1 install CD: hangs while it's starting the boot loader.  Even
the SDL window stops redrawing itself.

Win98 second edition install CD.  Spews a bunch of "FLOPPY ERROR: fd_seek:
try to read 0 00 02 (max=1 00 01)" messages while starting up the setup.
When copying files is complete, it says "Detection Manager failed to allocate
memory for internal use." followed by "Error loading Explorer.exe.  You must
reinstall Windows." and the termination of the setup.  If I then boot from
hard disk (-boot c), Windows finishes the installation, but after reboot,
I just get "While initializing device IOS: Windows protection error.  You
need to restart your computer."

Red Hat Enterprise Linux 3: after selecting Disk Druid to partition my
disks, it goes nonresponsive (stops reacting to the keyboard), but it does
keep repainting its window.


--L

Re: [Qemu-devel] QEMU 0.5.2 testing

[Herbert Poetzl]

On Mon, Jan 19, 2004 at 11:49:09AM +0100, Fabrice Bellard wrote:
> Herbert Poetzl wrote:
> >On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> >
> >>Hi,
> >>
> >>I commited all the current fixes in the CVS. I will make the 0.5.2 
> >>release tomorrow, so it would be interesting if some people could test 
> >>it before it is officially released...
> >
> >texi2html -monolithic -number qemu-doc.texi
> >make: texi2html: Command not found
> >make: *** [qemu-doc.html] Error 127
> 
> In the distribution I add the html et man files, so it should not be a 
> problem to most users (I am relunctant to add texi2html in the 
> distribution).

good

> >usual set of compiler warnings, are you interested
> >in that output too?
> 
> I know they are warnings in translate.c about a function prototype. If 
> you have others I am interested.

will check ...

> >seems to work as expected, with the folowing options
> >
> >qemu-cvs-19.01.2004/i386/qemu-fast -s -nographic -L qemu-0.5.1/pc-bios -m 
> >128 -snapshot -hda IMGs/TEST_32M.img -hdb IMGs/TEST_256M.img -kernel 
> ><kernelpath>/arch/i386/boot/bzImage -append "rw root=/dev/hda1
> >
> >tested with/out -s for 2.4.24, 2.4.25-pre6 and 2.6.0 ...
> >two harddisk images 32M and 256MB in size ...
> 
> So you don't use the '-kernel' option ? I am thinking about modifying 
> this option so that the PC bios is used in all cases (it would allow to 
> have the VGA output even with '-kernel'). A possible way would be to 
> integrate a custom linux loader ROM, as it is done now in plex86.

huh?  -kernel <kernelpath>...

please, I'm _verry_ happy that I do not need the vga 
and interface stuff, and that it works on the console
I'm planning to use it for automated kernel testing,
so _please_ don't do that ...

  -nographic -L qemu-0.5.1/pc-bios -kernel ... -append ...

by the way, I tried to pass commands to qemu in the
following way:

 echo "abcdefghij" | qemu ....

and it seems to work 'somewhat' but there are some 
'weird' deficiencies ...

 - the first two characters are always swallowed
 - depending on the kernel a number of 'padding'
   chars is required, they are displayed but do
   not reach the init process (or might be discarded
   by the busybox I use)

for example:
echo -e "  aaaaaaaaaaaaaaaaaaaaaa\n/tmp/testme.sh\n" | qemu ...

will work for 2.4.25-pre6 ;) and execute /tmp/testme.sh

> >hmm didn't notice that one until now (seems like a bug) ...
> >
> >Program received signal 0, Signal 0.
> >default_idle () at process.c:92
> >92	}
> >(gdb) break vfs_readdir
> >Breakpoint 1 at 0x90152640: file readdir.c, line 17.
> >(gdb) c
> >Continuing.
> >
> ># ls /proc
> ># ls /tmp
> ># <nothing happens> CTRL-C
> >
> >Program received signal 0, Signal 0.
> >default_idle () at process.c:92
> >92	}
> >(gdb) break sys_vserver
> >Breakpoint 2 at 0x901261f0: file vswitch.c, line 39.
> >(gdb) c
> >Continuing.
> >
> ># ls /tmp
> >
> >Program received signal SIGTRAP, Trace/breakpoint trap.
> >vfs_readdir (file=0xc183c189, filler=0x2e9c103, buf=0xde89a5f3) at 
> >readdir.c:17
> >17	{
> >
> >(gdb) disable 1
> >(gdb) c
> >Continuing.
> >
> ># sys_vserver (call)
> >
> >Program received signal SIGTRAP, Trace/breakpoint trap.
> >sys_vserver (cmd=0, id=0, data=0x0) at vswitch.c:39
> >39	{
> 
> Do you have the problem if you don't use gdb ? Maybe my last TLB 
> optimisations broke the gdb stub logic. I will check...

hum, how would I test without gdb? color me confused.

TIA,
Herbert

> Fabrice.
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] QEMU 0.5.2 testing

[J. Mayer]

On Tue, 2004-01-20 at 05:07, Lennert Buytenhek wrote:
> On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> 
> > I commited all the current fixes in the CVS. I will make the 0.5.2 
> > release tomorrow, so it would be interesting if some people could test 
> > it before it is officially released...
> 
> NetBSD 1.6.1 install CD: says "npx0 at isa0 port 0xf0-0xff: error reporting
> broken; not using" during kernel boot, but continues.  When commencing the
> install to disk, it complains "wdc_atapi_intr: warning: reading only 1 of 2
> bytes" and seem to hang -- it makes no progress at least for a minute.

In fact, it runs, but the install is very slow, because of those errors.
You should also get:
"wdc1:0:0 lost interrupt
    type: atapi tc_bcount: 0 tc_skip: 65536"
It may take a few day to deal with the install but should be OK.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

Re: [Qemu-devel] QEMU 0.5.2 testing

[Renzo Davoli]

On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> I commited all the current fixes in the CVS. I will make the 0.5.2 
> release tomorrow, so it would be interesting if some people could test 
> it before it is officially released...
I have tested the latest cvs version but I still have the same problems:
- win does not see cd-rom and network interface
(I can boot from a CD, but when Win(98) boots from hd there are not
CD-ROMS.)
- animated menus are quite slow to appear
- is the soundcard working?

ciao
	renzo

Re: [Qemu-devel] QEMU 0.5.2 testing

[Jens Axboe]

On Tue, Jan 20 2004, Renzo Davoli wrote:
> On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> > I commited all the current fixes in the CVS. I will make the 0.5.2 
> > release tomorrow, so it would be interesting if some people could test 
> > it before it is officially released...
> I have tested the latest cvs version but I still have the same problems:
> - win does not see cd-rom and network interface
> (I can boot from a CD, but when Win(98) boots from hd there are not
> CD-ROMS.)

You can get around that with loading an msdos atapi driver (and mscdex).
Not sure it's supposed to work othersie.

> - animated menus are quite slow to appear

Indeed. Overall the speed is _very_ impressive, though.

-- 
Jens Axboe

Re: [Qemu-devel] QEMU 0.5.2 testing

[Renzo Davoli]

> Indeed. Overall the speed is _very_ impressive, though.
Please don't let me be misunderstood.

Mine are not "criticisms", Qemu is one step to "perfection".
I wanna give "constructive" hints and debugging advises.

I agree: the overall speed *is* impressive.

renzo

Re: [Qemu-devel] QEMU 0.5.2 testing

[Chris Emerson]

On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
> I commited all the current fixes in the CVS. I will make the 0.5.2 
> release tomorrow, so it would be interesting if some people could test 
> it before it is officially released...

On my Debian PPC box, I had to make two changes to get it to compile
install:
 * Change the uc_context regs to gregs in cpu-exec.c.
 * Comment out the rule for install in i386/Makefile, since $(PROGS) was
   empty.

I booted the Debian/i386 install floppies, which seems to work except
that the keymap is wrong.  I got part-way through the installation once
I worked out that "/" gave me Enter.

Good work!

Chris

Re: [Qemu-devel] QEMU 0.5.2 testing

[Lennert Buytenhek]

On Tue, Jan 20, 2004 at 11:45:01AM +0100, J. Mayer wrote:

> > NetBSD 1.6.1 install CD: says "npx0 at isa0 port 0xf0-0xff: error reporting
> > broken; not using" during kernel boot, but continues.  When commencing the
> > install to disk, it complains "wdc_atapi_intr: warning: reading only 1 of 2
> > bytes" and seem to hang -- it makes no progress at least for a minute.
> 
> In fact, it runs, but the install is very slow, because of those errors.
> You should also get:
> "wdc1:0:0 lost interrupt
>     type: atapi tc_bcount: 0 tc_skip: 65536"
> It may take a few day to deal with the install but should be OK.

Yes, that's exactly what I get.

It's been running for 12 hours now, how long did you say it would take
to complete the install? :)


--L

Re: [Qemu-devel] QEMU 0.5.2 testing

[Gabriel Ebner]

Hello,

Fabrice Bellard wrote:
> I know they are warnings in translate.c about a function prototype. If 
> you have others I am interested.

Well, that's what I get with current CVS:

gcc -Wall -O2 -g -fomit-frame-pointer -mpreferred-stack-boundary=2
-falign-functions=0 -fno-reorder-blocks -fno-optimize-sibling-calls -I.
-I$WORKDIR/qemu/target-sparc -I$WORKDIR/qemu -D_GNU_SOURCE -c -o op.o
$WORKDIR/qemu/target-sparc/op.c
$WORKDIR/qemu/target-sparc/op.c: In function `op_eval_ble':
$WORKDIR/qemu/target-sparc/op.c:541: warning:  unused variable `C'
$WORKDIR/qemu/target-sparc/op.c: In function `op_eval_bl':
$WORKDIR/qemu/target-sparc/op.c:547: warning: unused variable `Z'
$WORKDIR/qemu/target-sparc/op.c:547: warning: unused variable `C'
$WORKDIR/qemu/target-sparc/op.c: In function `op_eval_bleu':
$WORKDIR/qemu/target-sparc/op.c:553: warning: unused variable `N'
$WORKDIR/qemu/target-sparc/op.c:553: warning: unused variable `V'
$WORKDIR/qemu/target-sparc/op.c: In function `op_eval_bg':
$WORKDIR/qemu/target-sparc/op.c:579: warning: unused variable `C'
$WORKDIR/qemu/target-sparc/op.c: In function `op_eval_bge':
$WORKDIR/qemu/target-sparc/op.c:585: warning: unused variable `Z'
$WORKDIR/qemu/target-sparc/op.c:585: warning: unused variable `C'
$WORKDIR/qemu/target-sparc/op.c: In function `op_eval_bgu':
$WORKDIR/qemu/target-sparc/op.c:591: warning: unused variable `N'
$WORKDIR/qemu/target-sparc/op.c:591: warning: unused variable `V'

	Gabriel.

Re: [Qemu-devel] QEMU 0.5.2 testing

[J. Mayer]

On Wed, 2004-01-21 at 12:43, Lennert Buytenhek wrote:
> On Tue, Jan 20, 2004 at 11:45:01AM +0100, J. Mayer wrote:
> 
> > > NetBSD 1.6.1 install CD: says "npx0 at isa0 port 0xf0-0xff: error reporting
> > > broken; not using" during kernel boot, but continues.  When commencing the
> > > install to disk, it complains "wdc_atapi_intr: warning: reading only 1 of 2
> > > bytes" and seem to hang -- it makes no progress at least for a minute.
> > 
> > In fact, it runs, but the install is very slow, because of those errors.
> > You should also get:
> > "wdc1:0:0 lost interrupt
> >     type: atapi tc_bcount: 0 tc_skip: 65536"
> > It may take a few day to deal with the install but should be OK.
> 
> Yes, that's exactly what I get.
> 
> It's been running for 12 hours now, how long did you say it would take
> to complete the install? :)

I don't know. I let it turn run 36 hours, but qemu get frozen while I
was at work...
It reboots, but complains that some file are missing.
And the keymap is completely broken, making it unusable...

-- 
J. Mayer <l_indien@magic.fr>
Never organized

Re: [Qemu-devel] QEMU 0.5.2 testing

[Sylvain OBEGI]

Le mar 20/01/2004 à 05:07, Lennert Buytenhek a écrit :
> Win98 second edition install CD.  Spews a bunch of "FLOPPY ERROR: fd_seek:
> try to read 0 00 02 (max=1 00 01)" messages while starting up the setup.
> When copying files is complete, it says "Detection Manager failed to allocate
> memory for internal use." followed by "Error loading Explorer.exe.  You must
> reinstall Windows." and the termination of the setup.  If I then boot from
> hard disk (-boot c), Windows finishes the installation, but after reboot,
> I just get "While initializing device IOS: Windows protection error.  You
> need to restart your computer."

I get the same things here with 0.5.2 final, except that it seems random
freezes during install causes some vxd errors, so I can't boot windows
at all.

-- 

Sylvain OBEGI
Email : katios@nolabel.net
ICQ : 661913

Re: [Qemu-devel] QEMU 0.5.2 testing

[Renzo Davoli]

I am testing 0.5.2 (or the latest cvs).

Win98:

- install quite okay: it complains about a shortage of memory when 
testing plug&pray devices.
- after install CD-ROM, Network interface are not automatically recognized.
- with in CONFIG.SYS: 
    device=c:\windows\oakcdrom.sys /d:mscd001 
  and in AUTOEXEC.BAT
    mscdex /d:mscd001
  (standard msdos methods)
  the cdrom works (oakcdrom has been copied from the rescue disk).
- no way now to let the network interface work.
- I am going to reinstall it. Now at boot time ot complaints about the
  display adapter ("your  display adapter is not configured properly).
- floppy are okay at boot (I can boot from the rescue floopy) but
  when win98 has boot all the floppies appear as unformatted, and
  fails whem trying to format a new image.

Debian Linux:
- I have started a net installation and it worked quite well.
- I had to configure the ne.o (ne2000) module by hand (irq=9
  iobase=0x300) but then the installation continued okay.
- CDROM is recognized at boot.
- I have not finished the installation just because it was too late
  yesterday night. 
- more info follows, I am planning to complete the installation 
  as soon as possible.

In both tests I am using the vdeq tool that interfaces qemu with my
"virtual distributed ethernet" vde network (see vde.sf.net).

ciao
	renzo