From: "Alessio Rocchi" <alexrocchi@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Kernel panic on Qemu-ed images runned under a live Knoppix distro.
Date: Wed, 14 Nov 2007 11:49:57 +0100 [thread overview]
Message-ID: <cf1947ad0711140249s65e429bbh368d9618e55bc024@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
Hi everybody.
I'm writing to search for help about a problem i'm experiencing.
I'm using knoppix as host system for a virtualized computing-grid testbed,
implemented as two Scientific Linux (RHEL like) guests launched by the qemu
emulator.
Two scenarios follow:
1) I boot a Knoppix "vanilla" system (which get access, when ready, to the
local disks). As the system become ready, I install qemu,
uml-utilites,bridge-utils (via apt-get), and I run qemu to virtualize two
pre-installed Scientific Linux images (laying on my main physical disc).
Everything goes ok.
2) I remaster Knoppix to include qemu/bridge-utils/uml-utilites and the two
SL images. When finished, I restart the whole system and boot from the new,
remastered, knoppix DVD. When the booting phase ends, I try to launch my
qemu-ed images. Both of the images, when trying to chroot to /, fail with a
bad kernel panic (with a different initial message).
Does someone know what is the reason for this to happen? Why this behaviour
difference within the two previous environments?
I've to precise that both images are "mirrored": they have the same OS and
Filesystem installed on.
Thank you in advance,
Alex.
N.B: Kernel Panic detailed messages are as it follows:
<FIRST RUNNED IMAGE>
Redhat nash version 4.2.1.8 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
EXT2-fs: magic mismatch, very weird!
Mount: error 22 mounting EXT2
Mount: error 2 mounting none
Switching to the new root
Switchroot: mount failed: 22
mount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
<END OF FIRST IMAGE MESSAGE>
<SECOND RUNNED IMAGE>
Redhat nash version 4.2.1.8 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
VFS: couldn't find ext2 filesystem on dev hda1
Mount: error 22 mounting EXT2
Mount: error 2 mounting none
Switching to the new root
Switchroot: mount failed: 22
mount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
<END OF SECOND IMAGE MESSAGES>
[-- Attachment #2: Type: text/html, Size: 2579 bytes --]
reply other threads:[~2007-11-14 10:57 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=cf1947ad0711140249s65e429bbh368d9618e55bc024@mail.gmail.com \
--to=alexrocchi@gmail.com \
--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).