[Qemu-devel] OSZOO: current status

[Qemu-devel] OSZOO: current status

[Stefano Marinelli]

Hi. I'm trying to install the several OSes, and I'm trying to do it 
using the latest CVS and the VNC interface. There are some issues with 
the mouse, but it's almost usable.
I had to get up installing:
-OpenBSD (it detects 3 disks (wrong), then use one of those but as soon 
as tries to write an error message comes out sayng "cannot access, disk 
may be full)
-FreeBSD (doesn't even boot)
-NetBSD (it detects correctly the disk, but when trying to write gives a 
"panic: npxdna vector not initialized" and gives me something like a 
shell)

I successfully installed ReactOS 0.2.2, even if it doesn't show (on VNC) 
the whole screen (but I suspect it's a problem of my vnc client)

Anybody had same issues with those OSes? Any work-around?

Bye,
Stefano

[Qemu-devel] Re: OSZOO: current status

[Gabriel Ebner]

Hello,

Stefano Marinelli wrote:
> -NetBSD (it detects correctly the disk, but when trying to write gives a
> "panic: npxdna vector not initialized" and gives me something like a
> shell)

That's a kernel debugger and I get that too (beginning with NetBSD 1.6.2).

        Gabriel.

-- 
Gabriel Ebner - reverse "ta.renbeleirbag@eg"

Re: [Qemu-devel] OSZOO: current status

[Fabrice Bellard]

If you can give an URL to small *BSD images or CDROM to do testing, it 
should be easy to fix.

Fabrice.

Stefano Marinelli wrote:
> Hi. I'm trying to install the several OSes, and I'm trying to do it 
> using the latest CVS and the VNC interface. There are some issues with 
> the mouse, but it's almost usable.
> I had to get up installing:
> -OpenBSD (it detects 3 disks (wrong), then use one of those but as soon 
> as tries to write an error message comes out sayng "cannot access, disk 
> may be full)
> -FreeBSD (doesn't even boot)
> -NetBSD (it detects correctly the disk, but when trying to write gives a 
> "panic: npxdna vector not initialized" and gives me something like a 
> shell)
> 
> I successfully installed ReactOS 0.2.2, even if it doesn't show (on VNC) 
> the whole screen (but I suspect it's a problem of my vnc client)
> 
> Anybody had same issues with those OSes? Any work-around?
> 
> Bye,
> Stefano
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
> 

Re: [Qemu-devel] Re: OSZOO: current status

[J. Mayer]

On Sat, 2004-05-08 at 16:36, Gabriel Ebner wrote:
> Hello,
> 
> Stefano Marinelli wrote:
> > -NetBSD (it detects correctly the disk, but when trying to write gives a
> > "panic: npxdna vector not initialized" and gives me something like a
> > shell)
> 
> That's a kernel debugger and I get that too (beginning with NetBSD 1.6.2).
> 

I did install NetBSD 1.6.1 successfully from floppy & CDROM some times
ago...

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

Re: [Qemu-devel] OSZOO: current status

[Johannes Schindelin]

Hi,

On Sat, 8 May 2004, Stefano Marinelli wrote:
> I successfully installed ReactOS 0.2.2, even if it doesn't show (on VNC)
> the whole screen (but I suspect it's a problem of my vnc client)

Probably you see the warning (from qemu) that your VNC client does not
support the NewFB coding. Just close your viewer and reconnect. If you
happen upon a segmentation fault right after the warning, I suggest
upgrading the LibVNCServer to 0.7pre (probably all prior versions have
that problem).

I trid to install Windowses 95, 98 (don't know if SE or not), ME and 2003
(If you buy a lot of machines, you have to buy a lot of Windows :-( ).
Windows 95 did not even boot from CD image, but quit right away with a
"BIOS panic at rombios.c, line 1558". The others did install fine
(changing the screen dimensions a few times, so I had to reconnect a few
times). The younger the OS, the slower the install. I suspect the
component registrations to be responsible for that. But the boot times are
comparable.

The only problem I still have is that network is "notwork" at the moment.
Windows 2003 (as mentioned before on the mailing list) does not recognize
the card automatically (and I did not yet install the driver manually).
With 98 I tried both the enhanced ifup-qemu and the new user-net. I use
shorewall on my machine, so I had to fiddle around with those settings to
get dhcpd to work, but it only receives a "DHCPDISCOVER" and returns a
"DHCPOFFER" which is not answered by the guest OS. I'll try a little
harder with user-net in the next days.

Ciao,
Dscho

[Qemu-devel] Re: Re: OSZOO: current status

[Gabriel Ebner]

Hello,

J. Mayer wrote:
> I did install NetBSD 1.6.1 successfully from floppy & CDROM some times
> ago...

That worked here too but as I said NetBSD 1.6.2 fails with that npxdna
error.

        Gabriel.

-- 
Gabriel Ebner - reverse "ta.renbeleirbag@eg"

Re: [Qemu-devel] OSZOO: current status

[Hetz Ben Hamo]

Fabrice Bellard wrote:
> If you can give an URL to small *BSD images or CDROM to do testing, it 
> should be easy to fix.
> 
> Fabrice.

Solaris 10 also suffers the same problem...

Download Solaris 10 ISO's (the 1st one should be enough - the error 
happends right at the beginning) from:

http://jsecom15c.sun.com/ECom/EComActionServlet?StoreId=8&PartDetailId=Sol-Express_4-04-x86-G-F&TransactionId=try&LMLoadBalanced=

(you'll need to register)

Problem seems to be also on Solaris 9 and 8 (same problem, as much as I 
heard from a friend)..

Coming soon: Windows Longhorn install test (screenshots will be sent)..

Thanks,
Hetz

Re: [Qemu-devel] OSZOO: current status

[Taras]

Hi
Freebsd floppies are here(cdrom just freezes at boot)
ftp://ftp3.freebsd.org/pub/FreeBSD/releases/i386/5.2.1-RELEASE/floppies

For netbsd get boot1 & boot2 from
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6.2/i386/installation/floppy

Recent keyboard changes also broke keyboard support in the netbsd 
installer. For example the return key seems to get ignored now even 
though arrow keys work.
Taras

Fabrice Bellard wrote:

> If you can give an URL to small *BSD images or CDROM to do testing, it 
> should be easy to fix.
>
> Fabrice.
>
> Stefano Marinelli wrote:
>
>> Hi. I'm trying to install the several OSes, and I'm trying to do it 
>> using the latest CVS and the VNC interface. There are some issues 
>> with the mouse, but it's almost usable.
>> I had to get up installing:
>> -OpenBSD (it detects 3 disks (wrong), then use one of those but as 
>> soon as tries to write an error message comes out sayng "cannot 
>> access, disk may be full)
>> -FreeBSD (doesn't even boot)
>> -NetBSD (it detects correctly the disk, but when trying to write 
>> gives a "panic: npxdna vector not initialized" and gives me something 
>> like a shell)
>>
>> I successfully installed ReactOS 0.2.2, even if it doesn't show (on 
>> VNC) the whole screen (but I suspect it's a problem of my vnc client)
>>
>> Anybody had same issues with those OSes? Any work-around?
>>
>> Bye,
>> Stefano
>>
>>
>> _______________________________________________
>> Qemu-devel mailing list
>> Qemu-devel@nongnu.org
>> http://mail.nongnu.org/mailman/listinfo/qemu-devel
>>
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] OSZOO: current status

[Fabrice Bellard]

Taras wrote:
> Hi
> Freebsd floppies are here(cdrom just freezes at boot)
> ftp://ftp3.freebsd.org/pub/FreeBSD/releases/i386/5.2.1-RELEASE/floppies
> 
> For netbsd get boot1 & boot2 from
> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6.2/i386/installation/floppy

The boot disks are working for me with QEMU 0.5.5 (althought the IDE 
probe is slow in NetBSD 1.6.2). QEMU CVS fixes the FPU probe of NetBSD 
(the FPU was not recognized).

Fabrice.

Re: [Qemu-devel] OSZOO: current status

[Taras]

Fabrice Bellard wrote:

> Taras wrote:
>
>> Hi
>> Freebsd floppies are here(cdrom just freezes at boot)
>> ftp://ftp3.freebsd.org/pub/FreeBSD/releases/i386/5.2.1-RELEASE/floppies
>>
>> For netbsd get boot1 & boot2 from
>> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.6.2/i386/installation/floppy
>
>
> The boot disks are working for me with QEMU 0.5.5 (althought the IDE 
> probe is slow in NetBSD 1.6.2). QEMU CVS fixes the FPU probe of NetBSD 
> (the FPU was not recognized).

Thanks,
I just updated cvs & I can partition the hd now. However the slirp(?) 
network doesn't seem to work.
http://glek.net/~taras/netbsd.png
I used qemu -hda netbsd_hda -boot a -fda boot1.fs to boot
I also tried with qemu -user-net -hda netbsd_hda -boot a -fda boot1.fs 
and ne1 ethernet still doesn't work.

Thanks,
Taras