** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solaris 9 Sparc Segmentation Fault
Status in QEMU:
Fix Rele
Great news! AFAICT it's just convention that the first disk slice is
used, and I've also proposed a patch for OpenBIOS to include this in the
boot search path in future, hopefully in time for 2.7.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
Hi Mark,
We are finally in:)
By the way, how do you figure out which slice its in?
>From solaris 8 dvd onwards, i seems to see 2 disk label options: SMI and
EFI. Not sure why you didnt see those.
0 > boot disk:a Not a bootable ELF image
Loading a.out image...
Loaded 7680 bytes
entry point is 0x
Hmmm I've just tried a second installation of Solaris 9 with a
completely blank disk image and now it appears that "boot disk:a" is
correct, i.e. boot from slice a. Not sure yet if this is the correct
convention for HDs.
--
You received this bug notification because you are a member of qemu-
deve
It works here as per my post above, so I think the problem is still with
the disk label. With the above ISO image, I don't get asked for the type
of label which makes me think you are using a newer version of Solaris
for labelling than you are for installation.
Can you re-label the disk using the
Hi Mark,
I have tried boot diisk:d. After this
Not a bootable ELF image
Not a bootable a.out image
No valid state has been set by load or init-program
0 > boot disk:d No valid state has been set by load or init-program
ok
0 >
Somehow I am getting invalid boot
--
You received this bug notif
If you use OpenBIOS then you don't explicitly have to set scsi-options
since the value can be overridden via the device tree which is exactly
what OpenBIOS does.
Interestingly enough it seems that the default bootloader for Solaris 9
is installed in the slice rather than the root of the disk as pe
Hi Mark,
Thanks for the update. I would definitely be nice to have other than the
black screen. Still got a problem though. I managed to install sparc9
but after i removed the cdrom, it fails to boot.
qemu-system-sparc -nographic -monitor null -serial
mon:telnet:0.0.0.0:3000,server -hda ./Sparc9.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solaris 9 Sparc Segmentation Fault
Status in QEMU:
Fix Committed
Bu
** Changed in: qemu
Status: Fix Committed => Fix Released
** Changed in: qemu
Status: Fix Released => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solari
Great news! FWIW with newer versions of QEMU, including 2.6.0, the
framebuffer emulation is good enough to install and run Solaris
(including X) without the -nographic/-serial options if you need it.
I've also CCd the relevant patch to qemu-stable so it should appear in
2.6.1 also.
Many thanks for
Hi Mark,
Thanks a lot. Got it working now. When formatting the label, there are 2
options, SMI and EFI. Once I format it with SMI, it seems to be able to
find the disk.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
I've just tried v2.6.0 with the recent ldstub patch applied and it looks
from the output above that you're using an incorrect format to put down
the disk label. I see the following:
$ ./qemu-system-sparc -cdrom sol-9-905hw-ga-sparc-dvd.iso -hda
/home/build/src/qemu/image/sparc32/sol9.qcow2 -boot
May 11 2016. qemu-2.6.0 from http://wiki.qemu.org/Download
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solaris 9 Sparc Segmentation Fault
Status in QEMU:
New
Bug descr
Okay. Can you confirm which version (or git revision) you've used to
apply the patch so I can try and reproduce locally?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solari
Hmm.. strange. I did make a new disk went into the setup, then format
the disk. After that, i rebooted and start that installation. But, it
seems still there is no disk detected.
Media [1]: 1
Reading disc for Solaris Operating Environment...
The system is being initialized, please wait... |
No D
I ran all the way through the installer in order to test the patch, so
it should be working for you. Is your Spark9.disk labelled? See
http://virtuallyfun.superglobalmegacorp.com/2010/10/03/formatting-disks-
for-solaris/ for more information on how to do this.
--
You received this bug notificatio
Hi all,
Thanks for the patch. I just tried, it seems to be not able to find the
disk when it try to start the installation. :(
...
Please specify the media from which you will install the Solaris Operating
Environment.
Media:
1. CD/DVD
2. Network File System
3. HTTP (Flash archive only)
4. FTP
Artyom has located the regression and posted a patch here:
https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg07226.html.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6
On 17/06/16 12:42, Artyom Tarasenko wrote:
> Can you guys check if the problem persists when qemu is launched with
> the -singlestep option?
> I think it's in general a good idea always check TCG-related problems
> with -singlestep , because it helps to find out whether a bug is in
> the optimizer
Can you guys check if the problem persists when qemu is launched with
the -singlestep option?
I think it's in general a good idea always check TCG-related problems
with -singlestep , because it helps to find out whether a bug is in
the optimizer or generator module of TCG.
Artyom
On Tue, Jun 14,
Thanks for the test case. It appears that this is a regression that
occurred somewhere between 2.5 and 2.6 - bisecting now.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Sol
Hi Mark,
Attached is the new link:
https://mega.nz/#!94ZVXBra!8QMsQ2d9eKKkMuawg_0YelfyWTy47CyyD1f6tvSv1bQ
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solaris 9 Sparc Segm
Hi Mark,
I have uploaded a copy of it to mega.nz
https://mega.nz/#!94ZVXBra
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1588328
Title:
Qemu 2.6 Solaris 9 Sparc Segmentation Fault
Status in QEM
If you can verify that the media is correct and you still see problems,
I'd be interested to take a look if you are able to provide me a copy of
the media for debugging.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Hi Mark,
I compared the cksum provided and the dvd cksum that i did, seems to
match. I did try out Solaris 8 too. It seems to work fine with sun
formatted hda disk. I did try removing the -hda for solaris 9, the
problem still persist. I shall find if i can get another solaris 9 image
source to try
That basically looks like it should work. The only time I've seen random
segfaults similar to this is with a corrupted disk, so the first
question to ask is whether you've verified the ISO image you are using?
Unfortunately this isn't an image I currently have access to, but I can
report my Solaris
27 matches
Mail list logo
