From: Yannick Patois <patois@calvix.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] SLC linux in qemu-system-x86_64 kernel panic at boot
Date: Fri, 27 Jan 2006 17:14:30 +0100 [thread overview]
Message-ID: <43DA46E6.9040101@calvix.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm testing qemu for amd64 and couldnt get very far. Any help appreciated.
I'm using a cdrom image for the SLC3 linux distribution:
http://linuxsoft.cern.ch/cern/slc30X/x86_64/images/boot.iso
I ran:
$ qemu-system-x86_64 -cdrom boot.iso
Seems to start nicely (I get the install menu). Type "enter" to start
the boot, and get:
Decompressing Linux...
[...]
Code: Bad RIP value.
Kernel panic: Fatal exception
Couldnt go further.
Surprisingly, it seems to work better with SLC4:
http://linuxsoft.cern.ch/cern/slc4X/x86_64/images/SL/boot.iso
But as I'm interested by slc3 for now, I would be glad to get any feedback.
Versions note for the host system:
> uname -a
Linux 2.4.21-37.EL.cernsmp #1 SMP i686 i686 i386 GNU/Linux
It's an SLC3 on a PIV computer.
qemu is compiled from a CVS checkout of today (27/01): after trying the
regular 0.8.0 version -same error failure-, I went to the CVS, hoping
for a fix.
Thanks for any help.
Yannick
- --
_/ Yannick Patois _________________ Address (home) __________________
| irc(undernet): Garp on #france25+ | 1, rue de Bale |
| http://garp.feelingsurfer.net/ | 67100 Strasbourg |
| Tel-home: +(33)(0)3 88 84 88 16 | FRANCE |
| Le Portail des Copains : http://rezo.net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org
iD8DBQFD2kbmZY3s/IVpRFIRAkoOAKCATVUwQ53B66V/0w7M4Il7TluSvgCfQ2jA
BqC8sVctE+n3pW8N8HRiWY8=
=4VHl
-----END PGP SIGNATURE-----
reply other threads:[~2006-01-27 16:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43DA46E6.9040101@calvix.org \
--to=patois@calvix.org \
--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).