Re: [Qemu-devel] SunOS Testing on latest SVN snapshot

2007-04-23 Thread Blue Swirl

On 4/23/07, JmH [EMAIL PROTECTED] wrote:

With the enable-interpose patch to open bios (Thanks Blue Swirl), Qemu can
at least find the bootable potion of the installation media.

Unfortunately though, the boot doesnt progress very far. I have summarised
the results below:


Thanks for the report. Is there any difference if you use a
Sparcstation 10 machine?




Re: [Qemu-devel] SunOS Testing on latest SVN snapshot

2007-04-23 Thread Jonathan Kalbfeld

Now, if I remember correclty about suns, you have to boot the correct slice
according to the architecture.

It used to be something like one slice for sun4c, one for sun4d, one for
sun4m, one for sun4u, etc.

Does the openboot32 properly grab the slice for sun4m?

jonathan

On 4/23/07, Blue Swirl [EMAIL PROTECTED] wrote:


On 4/23/07, JmH [EMAIL PROTECTED] wrote:
 With the enable-interpose patch to open bios (Thanks Blue Swirl), Qemu
can
 at least find the bootable potion of the installation media.

 Unfortunately though, the boot doesnt progress very far. I have
summarised
 the results below:

Thanks for the report. Is there any difference if you use a
Sparcstation 10 machine?






--
--
Jonathan Kalbfeld
+1 323 620 6682


Re: [Qemu-devel] SunOS Testing on latest SVN snapshot

2007-04-23 Thread Blue Swirl

On 4/23/07, Jonathan Kalbfeld [EMAIL PROTECTED] wrote:

Now, if I remember correclty about suns, you have to boot the correct slice
according to the architecture.

It used to be something like one slice for sun4c, one for sun4d, one for
sun4m, one for sun4u, etc.

Does the openboot32 properly grab the slice for sun4m?


OpenBIOS tries :d slice.




Re: [Qemu-devel] SunOS Testing on latest SVN snapshot

2007-04-23 Thread JmH

No different with SS-10.

Jason

On 24/04/07, Blue Swirl [EMAIL PROTECTED] wrote:


On 4/23/07, JmH [EMAIL PROTECTED] wrote:
 With the enable-interpose patch to open bios (Thanks Blue Swirl), Qemu
can
 at least find the bootable potion of the installation media.

 Unfortunately though, the boot doesnt progress very far. I have
summarised
 the results below:

Thanks for the report. Is there any difference if you use a
Sparcstation 10 machine?





Re: [Qemu-devel] SunOS Testing on latest SVN snapshot

2007-04-22 Thread JmH

With the enable-interpose patch to open bios (Thanks Blue Swirl), Qemu can
at least find the bootable potion of the installation media.

Unfortunately though, the boot doesnt progress very far. I have summarised
the results below:

Solaris 1.0.1 (Note: SunOS 4.1.2, not 4.1.4 as below)
Boot hangs (well i left it for  10 minutes with no further output, local
CPU @ 100% on qemu-system-sparc process) after the following console output:
Loading a.out image...
Loaded 7680 bytes
entry point is 0x4000
Jumping to entry point...
Bootblock: libprom.a: Romvec version 3
checksum a73ed1ff6 != 3078aade, trying to boot anyway

Solaris 1.1.1
Boot hangs as per 1.0.1, but with a slightly different checksum

Solaris 2.3
Boot hangs after the following console output
Loading a.out image...
Loaded 7483136 bytes
entry point is 0x4000
Jumping to entry point...

Solaris 2.5.1
Boot hangs after the following console output, curiously this is the first
version that prints a '/' at the end of the output (which i recall is an
ASCII art representation indicating that the kernel is booting)
Loading a.out image...
Loaded 7483136 bytes
entry point is 0x4000
Jumping to entry point...
/

Solaris 7
Console boots (note the spinning ASCII art correctly spins and completes)
then fails. After which Qemu crashes with the following console output:
C:\Program Files\Qemuqemu-system-sparc.exe -m 256 -L . -cdrom
d:\solaris_7.iso -boot d
qemu: fatal: Trying to execute code outside RAM or ROM at 0xf00415e0

pc: f00415e0  npc: f00415e4
General Registers:
%g0:    %g1: 0004   %g2: 04000fe4   %g3: f026ff9c
%g4: 0001   %g5: f0243b88   %g6: 0001   %g7: f0244020
Current Register Window:
%o0:    %o1:    %o2:    %o3: 044000c4
%o4:    %o5: ffe87000   %o6: f015f828   %o7: f0041c70
%l0: 0004   %l1: f0041c68   %l2: f0041c6c   %l3: f02690c8
%l4: 000f   %l5: f02630d0   %l6: 15bb   %l7: f015f828
%i0: 8000   %i1: 8000   %i2: 0f00   %i3: 044000c5
%i4:    %i5: ffe87000   %i6: f015f8d0   %i7: f0041bd4

Floating Point Registers:
%f00: 0.00 0.00 0.00 0.00
%f04: 0.00 0.00 0.00 0.00
%f08: 0.00 0.00 0.00 0.00
%f12: 0.00 0.00 0.00 0.00
%f16: 0.00 0.00 0.00 0.00
%f20: 0.00 0.00 0.00 0.00
%f24: 0.00 0.00 0.00 0.00
%f28: 0.00 0.00 0.00 0.00
psr: 0x0404 -  --- wim: 0x0008
fsr: 0x0008

This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.

C:\Program Files\Qemu

Please let me know if i can run anything that would be of assistance to
hopefully chase the issues down.

As an aside does anyone know how to get the -nographic to work in windows,
it current fails with
Unable to open driver: stdio
qemu: could not open serial driver 'mon:stdio'

I think that there is some additional info in the Solaris 7 boot, which is
placed onto the virtual machine console, that does not appear when qemu
dumps the machine state after the crash.

Jason

On 19/04/07, Blue Swirl [EMAIL PROTECTED] wrote:


On 4/19/07, Jason Height [EMAIL PROTECTED] wrote:
 Inspired by Blue Swirl's statement in an earlier email that SunOS
testing
 can now commence against the latest SVN snapshot, i thought that i may
 finally be able to contribute.

 I have available:

 Solaris 1.0.1 (SunOS 4.1.4)
 Solaris 2.4
 Solaris 2.5
 Solaris 6.5 (SPARC)
 Solaris 7.0 (SPARC)
 Solaris 8.0 (SPARC)

Nice selection, thanks for testing!

 I think that all should run on a Sparstation 10, certainly up to Solaris
 7.0.

 However when i try to boot from the installation media to install, it
would
 appear that Qemu/openbios cannot find the bootable portion of the media.

This may be related to the change that disabled the buggy interpose
operation to improve SunOS support. Unfortunately fixing the interpose
bugs is beyond my Forth skills.

 Is there some tests/changes that i can make to assist in getting this to
 work.

Can you try if the attached patch to OpenBIOS changes anything?