From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IsFvm-0005sE-Fj
	for qemu-devel@nongnu.org; Wed, 14 Nov 2007 05:57:14 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IsFvl-0005qR-JN
	for qemu-devel@nongnu.org; Wed, 14 Nov 2007 05:57:13 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IsFvl-0005qB-Ds
	for qemu-devel@nongnu.org; Wed, 14 Nov 2007 05:57:13 -0500
Received: from rv-out-0910.google.com ([209.85.198.189])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <alexrocchi@gmail.com>) id 1IsFvk-0006IT-W8
	for qemu-devel@nongnu.org; Wed, 14 Nov 2007 05:57:13 -0500
Received: by rv-out-0910.google.com with SMTP id g11so410327rvb
	for <qemu-devel@nongnu.org>; Wed, 14 Nov 2007 02:57:11 -0800 (PST)
Message-ID: <cf1947ad0711140249s65e429bbh368d9618e55bc024@mail.gmail.com>
Date: Wed, 14 Nov 2007 11:49:57 +0100
From: "Alessio Rocchi" <alexrocchi@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_767_874685.1195037397538"
Subject: [Qemu-devel] Kernel panic on Qemu-ed images runned under a live
	Knoppix distro.
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

------=_Part_767_874685.1195037397538
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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>

------=_Part_767_874685.1195037397538
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<span class="postbody">Hi everybody.
<br>I&#39;m writing to search for help about a problem i&#39;m experiencing. 
<br>I&#39;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.
<br>Two scenarios follow:
<br>1) I boot a Knoppix &quot;vanilla&quot; 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.
<br>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).
<br>Does someone know what is the reason for this to happen? Why this behaviour difference within the two previous environments?
<br>I&#39;ve to precise that both images are &quot;mirrored&quot;: they have the same OS and Filesystem installed on.
<br>Thank you in advance,
<br>Alex.
<br>
<br><span style="font-weight: bold;">N.B: Kernel Panic detailed messages are as it follows:
</span><br>
<br>&lt;FIRST RUNNED IMAGE&gt;
<br>
<br>Redhat nash version <a href="http://4.2.1.8">4.2.1.8</a> starting
<br>Mounted /proc filesystem
<br>Mounting sysfs
<br>Creating /dev
<br>Starting udev
<br>Creating root device 
<br>Mounting root filesystem
<br><span style="font-weight: bold;">EXT2-fs: magic mismatch, very weird!</span>
<br>Mount: error 22 mounting EXT2
<br>Mount: error 2 mounting none
<br>Switching to the new root
<br>Switchroot: mount failed: 22
<br>mount /initrd/dev failed: 2
<br>Kernel panic - not syncing: Attempted to kill init!
<br>
<br>&lt;END OF FIRST IMAGE MESSAGE&gt;
<br>
<br>&lt;SECOND RUNNED IMAGE&gt;
<br>
<br>Redhat nash version <a href="http://4.2.1.8">4.2.1.8</a> starting
<br>Mounted /proc filesystem
<br>Mounting sysfs
<br>Creating /dev
<br>Starting udev
<br>Creating root device 
<br>Mounting root filesystem
<br><span style="font-weight: bold;">VFS: couldn&#39;t find ext2 filesystem on dev hda1</span>
<br>Mount: error 22 mounting EXT2
<br>Mount: error 2 mounting none
<br>Switching to the new root
<br>Switchroot: mount failed: 22
<br>mount /initrd/dev failed: 2
<br>Kernel panic - not syncing: Attempted to kill init!
<br>
<br>&lt;END OF SECOND IMAGE MESSAGES&gt;</span>

------=_Part_767_874685.1195037397538--