(sorry for the duplicate mark)
Excellent :) In fact, latest OpenBIOS SVN has a fix for the scsi-options part (it adds an extra property which gets picked up by the Solaris ESP driver) and so you shouldn't have to do this any more. Any testing gratefully received though!
Yes - there is currently an issue with the Sun shell which causes OpenBIOS to select the wrong build settings. See Nathan's second thread here: http://lists.openbios.org/pipermail/openbios/2011-April/006389.html. If you could test the fix suggested at the end of the thread and report back to the mailing list, that would be greatly appreciated :)
As soon as I can test this I'll report back. Unfortunately, I won't be able to copy logs & the like as it's on an air-gapped network, but I'll do what I can to give pertinent details.
That's interesting, since the guest should have no knowledge of the
underlying storage mechanism being using in the host. Can you point to any more specific error messages (again, back on the list) to help people work out what is happening?
Not a problem.
In return, thank you for testing. It really is exciting to be close to the
point where QEMU can run SPARC Solaris out of the box - I have already used it to great effect here and I know other people are excited to be able to move applications of legacy hardware onto something a lot more modern.
Out of curiosity, how likely is it that qemu-sparc32 could be used to run a solaris-based statically-linked user-mode application?
-Brian
For some reason, the boot prompt's help system doesn't work correctly
with openbios, but it does with ss5.bin.
Lastly, it looks like qcow2 doesn't work (at least with solaris 8). I tried with both bios'.
That's interesting, since the guest should have no knowledge of the underlying storage mechanism being using in the host. Can you point to any more specific error messages (again, back on the list) to help people work out what is happening?
I re-tested a bit ago and I'm not running into issues with qcow2 now. Must've been a fluke on my part.
I /am/ having trouble getting solaris to install on a custom partition scheme, or getting it to boot from the mini-root it copies to the swap partition ... but hopefully I'll be able to work my way through those issues.
-Brian
On Fri, May 13, 2011 at 9:56 PM, Brian Vandenberg phantall@gmail.com wrote:
(sorry for the duplicate mark)
Excellent :) In fact, latest OpenBIOS SVN has a fix for the scsi-options part (it adds an extra property which gets picked up by the Solaris ESP driver) and so you shouldn't have to do this any more. Any testing gratefully received though!
Yes - there is currently an issue with the Sun shell which causes OpenBIOS to select the wrong build settings. See Nathan's second thread here: http://lists.openbios.org/pipermail/openbios/2011-April/006389.html. If you could test the fix suggested at the end of the thread and report back to the mailing list, that would be greatly appreciated :)
As soon as I can test this I'll report back. Unfortunately, I won't be able to copy logs & the like as it's on an air-gapped network, but I'll do what I can to give pertinent details.
That's interesting, since the guest should have no knowledge of the underlying storage mechanism being using in the host. Can you point to any more specific error messages (again, back on the list) to help people work out what is happening?
Not a problem.
In return, thank you for testing. It really is exciting to be close to the point where QEMU can run SPARC Solaris out of the box - I have already used it to great effect here and I know other people are excited to be able to move applications of legacy hardware onto something a lot more modern.
Out of curiosity, how likely is it that qemu-sparc32 could be used to run a solaris-based statically-linked user-mode application?
This would be implemented within QEMU only, so this does not concern OpenBIOS much, but I gave a shot at it once: http://article.gmane.org/gmane.comp.emulators.qemu/41437
It may be possible to make a Solaris user emulator which would allow running Solaris/Sparc binaries on Solaris/x86 or vice versa, but there are license compatibility issues and some technical issues to be solved.
On 2011-May-13 16:43 , Blue Swirl wrote:
Out of curiosity, how likely is it that qemu-sparc32 could be used to run a solaris-based statically-linked user-mode application?
This would be implemented within QEMU only, so this does not concern OpenBIOS much, but I gave a shot at it once: http://article.gmane.org/gmane.comp.emulators.qemu/41437
It may be possible to make a Solaris user emulator which would allow running Solaris/Sparc binaries on Solaris/x86 or vice versa, but there are license compatibility issues and some technical issues to be solved.
Wouldn't it be easier to simply boot the Solaris 9 under qemu, copy the user-mode application into the environment and run it under that Solaris 9?
On Fri, May 13, 2011 at 11:46 PM, Tarl Neustaedter tarl-b2@tarl.net wrote:
On 2011-May-13 16:43 , Blue Swirl wrote:
Out of curiosity, how likely is it that qemu-sparc32 could be used to run a solaris-based statically-linked user-mode application?
This would be implemented within QEMU only, so this does not concern OpenBIOS much, but I gave a shot at it once: http://article.gmane.org/gmane.comp.emulators.qemu/41437
It may be possible to make a Solaris user emulator which would allow running Solaris/Sparc binaries on Solaris/x86 or vice versa, but there are license compatibility issues and some technical issues to be solved.
Wouldn't it be easier to simply boot the Solaris 9 under qemu, copy the user-mode application into the environment and run it under that Solaris 9?
Maybe, but it would be nice to be able to run applications seamlessly in the host environment. With user emulator, for example host file system would be available to the emulated executable just like to a native one.
Wouldn't it be easier to simply boot the Solaris 9 under qemu, copy the user-mode application into the environment and run it under that Solaris
9?
Maybe, but it would be nice to be able to run applications seamlessly in the host environment. With user emulator, for example host file system would be available to the emulated executable just like to a native one.
Exactly. In our case, the user-mode app we're working with makes use of the host's shared memory to simulate shared memory between multiple embedded devices. I'm not averse to re-writing that to use ethernet instead of the host's shared memory, but it'd be one less thing to re-write for this phase of our conversion.
Sorry about the cross-post. It honestly didn't occur to me that I was posting the question to the wrong list.
-Brian