qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ajallooiean Hossein <hossein.ajallooiean@epfl.ch>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
Date: Tue, 25 Apr 2017 17:28:31 +0000	[thread overview]
Message-ID: <1493141311023.87468@epfl.ch> (raw)
In-Reply-To: <1492904528362.73566@epfl.ch>

Hi Mark

Sorry for pinging so early.

Im just wondering if youve had time to go over my email below.

Any help would be greatly appreciated.

Thanks
Hoss
________________________________________
From: Qemu-devel <qemu-devel-bounces+hossein.ajallooiean=epfl.ch@nongnu.org> on behalf of Ajallooiean Hossein <hossein.ajallooiean@epfl.ch>
Sent: Sunday, April 23, 2017 1:42:08 AM
To: qemu-devel@nongnu.org
Cc: Mark Cave-Ayland
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic

Hi Mark,

Thanks a lot for this. - it did work!

So, now im wondering how did you install the iso on disk?

would you mind sharing your command line for the install please? and hacks if any

i am now able to install and boot, but my boot hang after this line "[   22.559491] [TTM] Initializing pool allocator" - inside user space. - I did blacklist bochs_drm for installing as such "-append 'modprobe.blacklist=bochs_drm'".

also, i have a couple of questions if you dont mind responding to them. - ill appreciate this a lot:
1- did you use virtio for your install? i.e. not using the "-cdrom" command and blacklisting the pata_cmd64x and also providing your own virtio device (/dev/vdb)?
    - i used this link for hints on how to install with virtio http://tyom.blogspot.ch/2013/03/debiansparc64-wheezy-under-qemu-how-to.html

2- i see that you used ext3 for your OS install, isnt that slower than ext4? -again im referencing this: http://tyom.blogspot.ch/2013/03/virtio-performance-and-filesystems.html

3- also, im noticing that you didnt define root=/dev/sda or root=/dev/vda1 for when your running qemu. and when im running your image i have to do that, otherwise ill get to the initramfs only. is there a trick behind this?

4- i dont see you defining a kernel and initrd? is there a reason for this? if i just use your cmd line, ill get this: also, are you extracting the kernel and initrd from the image or the iso?

OpenBIOS for Sparc64
Configuration device id QEMU version 1 machine id 0
kernel cmdline
CPUs: 1 x SUNW,UltraSPARC-IIi
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.1 built on Mar 15 2017 19:37
  Type 'help' for detailed information
Trying disk:a...
Not a bootable ELF image
Loading a.out image...
Loaded 7680 bytes
entry point is 0x4000
SILO Version 1.4.14
boot:

Thanks a lot in advance for your help.

Cheers
Hoss
________________________________________
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Sent: Saturday, April 22, 2017 11:12 AM
To: Ajallooiean Hossein; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic

On 21/04/17 16:12, Ajallooiean Hossein wrote:

> Thanks for the files and the notes.
>
> I am attaching my config-host file for you. I'm on x86_64, running Linux 64, Ubuntu 16.04.2 LTS
>
> so, i can also boot like you do - this worked before as well. btw, if you try to install that to a disk, itll not be able to as youll need to define memory for it.
>
> The problem is after i install the iso on the qcow2 disk and then try to boot qemu-system-sparc64.
>
> so here is the steps to reproduce the issue:
> 1- create a qcow2 image : debian-9.0-sparc64-NETINST-1.qcow2
> 2- download debian image: debian-9.0-sparc64-NETINST-1.iso
> 3- install the OS on dIsk
> i use the below command line to do it:
>
> ./qemu-system-sparc64 -cdrom /home/nihosa/Downloads/debian-9.0-sparc64-NETINST-1.iso -hda /home/nihosa/Downloads/debian-sparc.qcow2 -nographic -boot d -L pc-bios -m 200
>
> i guess i dont have to define a kernel in the above code???
>
> 4- installation goes all well.
> 5- i try to run the new disk image: - here i add kernel as if i dont add it ill get the below:
>
> https://pastebin.com/cFwrX9E9

I've just done a test install with
https://people.debian.org/~glaubitz/debian-cd/2017-03-24/debian-9.0-sparc64-NETINST-1.iso
and I didn't see any errors similar to the ones you mention (although I
did have to blacklist the bochs_drm module upon boot).

The resulting qcow2 image can be found temporarily at
https://www.ilande.co.uk/tmp/qemu/sparc64-kernel/deb90.qcow2.xz and you
can launch it with:

./qemu-system-sparc64 -hda deb90.qcow2 -m 256 -nographic

Username and password are both root.


ATB,

Mark.

  reply	other threads:[~2017-04-25 17:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  5:25 [Qemu-devel] Help needed: Sparc 64, kernel panic Ajallooiean Hossein
2017-04-20  7:26 ` Mark Cave-Ayland
2017-04-20  9:29   ` Ajallooiean Hossein
2017-04-20  9:47     ` Mark Cave-Ayland
2017-04-20 10:26     ` Philippe Mathieu-Daudé
2017-04-20 12:40     ` Peter Maydell
2017-04-20 13:08       ` Ajallooiean Hossein
2017-04-20 14:07         ` Ajallooiean Hossein
2017-04-21 12:03     ` Mark Cave-Ayland
2017-04-21 15:12       ` Ajallooiean Hossein
2017-04-22  9:12         ` Mark Cave-Ayland
2017-04-22 23:42           ` Ajallooiean Hossein
2017-04-25 17:28             ` Ajallooiean Hossein [this message]
2017-05-01 19:06             ` Mark Cave-Ayland
2017-05-04  9:44               ` Ajallooiean Hossein
  -- strict thread matches above, loose matches on Subject: below --
2017-04-21 11:37 Siavash Katebzadeh
2017-04-21 11:55 ` Mark Cave-Ayland
     [not found] <AA896828-A1B7-4060-9537-F738C1E2012C@gmail.com>
2017-04-21 15:06 ` Mark Cave-Ayland
2017-04-21 15:28   ` Siavash Katebzadeh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1493141311023.87468@epfl.ch \
    --to=hossein.ajallooiean@epfl.ch \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).