* [Qemu-devel] SunOS Testing on latest SVN snapshot
@ 2007-04-19 0:34 Jason Height
2007-04-19 14:24 ` Blue Swirl
0 siblings, 1 reply; 7+ messages in thread
From: Jason Height @ 2007-04-19 0:34 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
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)
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.
I get the following output from the console (Sorry i dont have the *exact*
console output here, but this is the general gist of it)
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Not a bootable ELF image
Not a Linux kernel image
(And then dumps back to the openbios prompt)
Is there some tests/changes that i can make to assist in getting this to
work.
Jason
[-- Attachment #2: Type: text/html, Size: 1062 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] SunOS Testing on latest SVN snapshot
2007-04-19 0:34 [Qemu-devel] SunOS Testing on latest SVN snapshot Jason Height
@ 2007-04-19 14:24 ` Blue Swirl
2007-04-23 1:27 ` JmH
0 siblings, 1 reply; 7+ messages in thread
From: Blue Swirl @ 2007-04-19 14:24 UTC (permalink / raw)
To: qemu-devel, jason.height
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On 4/19/07, Jason Height <jason.height@gmail.com> 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?
[-- Attachment #2: enable-interpose.diff --]
[-- Type: text/x-patch, Size: 529 bytes --]
Index: openbios-quilt/drivers/esp.c
===================================================================
--- openbios-quilt.orig/drivers/esp.c 2007-04-19 14:16:45.000000000 +0000
+++ openbios-quilt/drivers/esp.c 2007-04-19 14:17:18.000000000 +0000
@@ -285,7 +285,7 @@
selfword("open-deblocker");
-#if WHEN_INTERPOSE_IS_FIXED
+#if 1
// Buggy implementation of "interpose" breaks SunOS 4.
// inst2pkg of the device returned by open() should return
// the same phandle regardless of whether any interposition
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] SunOS Testing on latest SVN snapshot
2007-04-19 14:24 ` Blue Swirl
@ 2007-04-23 1:27 ` JmH
2007-04-23 17:51 ` Blue Swirl
0 siblings, 1 reply; 7+ messages in thread
From: JmH @ 2007-04-23 1:27 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 4488 bytes --]
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\Qemu>qemu-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: 00000000 %g1: 00000004 %g2: 04000fe4 %g3: f026ff9c
%g4: 00000001 %g5: f0243b88 %g6: 00000001 %g7: f0244020
Current Register Window:
%o0: 00000000 %o1: 00000000 %o2: 00000000 %o3: 044000c4
%o4: 00000000 %o5: ffe87000 %o6: f015f828 %o7: f0041c70
%l0: 00000004 %l1: f0041c68 %l2: f0041c6c %l3: f02690c8
%l4: 0000000f %l5: f02630d0 %l6: 000015bb %l7: f015f828
%i0: ffff8000 %i1: 80000000 %i2: 00000f00 %i3: 044000c5
%i4: 00000000 %i5: ffe87000 %i6: f015f8d0 %i7: f0041bd4
Floating Point Registers:
%f00: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f04: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f08: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f12: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f16: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f20: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f24: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
%f28: 000000000.000000 000000000.000000 000000000.000000 000000000.000000
psr: 0x04000004 -> ---- --- wim: 0x00000008
fsr: 0x00080000
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 <blauwirbel@gmail.com> wrote:
>
> On 4/19/07, Jason Height <jason.height@gmail.com> 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?
>
>
[-- Attachment #2: Type: text/html, Size: 5460 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] SunOS Testing on latest SVN snapshot
2007-04-23 1:27 ` JmH
@ 2007-04-23 17:51 ` Blue Swirl
2007-04-23 18:34 ` Jonathan Kalbfeld
2007-04-24 0:53 ` JmH
0 siblings, 2 replies; 7+ messages in thread
From: Blue Swirl @ 2007-04-23 17:51 UTC (permalink / raw)
To: qemu-devel
On 4/23/07, JmH <jason.height@gmail.com> 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?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] SunOS Testing on latest SVN snapshot
2007-04-23 17:51 ` Blue Swirl
@ 2007-04-23 18:34 ` Jonathan Kalbfeld
2007-04-23 18:42 ` Blue Swirl
2007-04-24 0:53 ` JmH
1 sibling, 1 reply; 7+ messages in thread
From: Jonathan Kalbfeld @ 2007-04-23 18:34 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
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 <blauwirbel@gmail.com> wrote:
>
> On 4/23/07, JmH <jason.height@gmail.com> 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
[-- Attachment #2: Type: text/html, Size: 1181 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] SunOS Testing on latest SVN snapshot
2007-04-23 18:34 ` Jonathan Kalbfeld
@ 2007-04-23 18:42 ` Blue Swirl
0 siblings, 0 replies; 7+ messages in thread
From: Blue Swirl @ 2007-04-23 18:42 UTC (permalink / raw)
To: qemu-devel
On 4/23/07, Jonathan Kalbfeld <jonathan.kalbfeld@gmail.com> 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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] SunOS Testing on latest SVN snapshot
2007-04-23 17:51 ` Blue Swirl
2007-04-23 18:34 ` Jonathan Kalbfeld
@ 2007-04-24 0:53 ` JmH
1 sibling, 0 replies; 7+ messages in thread
From: JmH @ 2007-04-24 0:53 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
No different with SS-10.
Jason
On 24/04/07, Blue Swirl <blauwirbel@gmail.com> wrote:
>
> On 4/23/07, JmH <jason.height@gmail.com> 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?
>
>
>
[-- Attachment #2: Type: text/html, Size: 858 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-04-24 0:59 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-04-19 0:34 [Qemu-devel] SunOS Testing on latest SVN snapshot Jason Height
2007-04-19 14:24 ` Blue Swirl
2007-04-23 1:27 ` JmH
2007-04-23 17:51 ` Blue Swirl
2007-04-23 18:34 ` Jonathan Kalbfeld
2007-04-23 18:42 ` Blue Swirl
2007-04-24 0:53 ` JmH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).