All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Wang, Shane" <shane.wang@intel.com>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
	"'xen-users@lists.xensource.com'" <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] How does pvops create loop device for initrd to support Xen live image?
Date: Thu, 17 Jun 2010 11:02:46 +0100	[thread overview]
Message-ID: <4C19F2C6.5080909@goop.org> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A1F372B96@shsmsx501.ccr.corp.intel.com>

On 06/17/2010 02:07 AM, Wang, Shane wrote:
> Hi,
>
> I want to create a Xen live image based on fedora project (http://fedoraproject.org/wiki/FedoraLiveCD/USBHowTo).
> Since the root fs is packed as a squashfs image, initrd will have script to mount it and switch root into it.
> But now I get the errors after booting up xen and pvops. (see log attached)
> It complains pvops is not aware of any loop device. I compile pvops with BLK_DEV_LOOP=y.
>
> ...
> losetup: Could not find any loop device. Maybe this kernel does not know
>        about the loop device? (If so, recompile or `modprobe loop'.)
> loop: can't get info on device /osmin.img: Inappropriate ioctl for device
> Usage: mount -V                 : print version
>        mount -h                 : print this help
>        mount                    : list mounted filesystems
>        mount -l                 : idem, including volume labels
> So far the informational part. Next the mounting.
> The command is `mount [-t fstype] something somewhere'.
> ...
>   

I think your problems are earlier:

[    4.866595] ehci_hcd: version magic '2.6.31.12 SMP mod_unload ' should be '2.
6.30-rc3-tip SMP mod_unload '
[    4.870773] ohci_hcd: version magic '2.6.31.12 SMP mod_unload ' should be '2.
6.30-rc3-tip SMP mod_unload '
[    4.875282] uhci_hcd: version magic '2.6.31.12 SMP mod_unload ' should be '2.
6.30-rc3-tip SMP mod_unload '
[    4.892417] scsi_mod: version magic '2.6.31.12 SMP mod_unload ' should be '2.
6.30-rc3-tip SMP mod_unload '
[    4.896594] sd_mod: version magic '2.6.31.12 SMP mod_unload ' should be '2.6.
30-rc3-tip SMP mod_unload '
[    4.902025] libata: version magic '2.6.31.12 SMP mod_unload ' should be '2.6.
30-rc3-tip SMP mod_unload '
[    4.907591] pata_acpi: version magic '2.6.31.12 SMP mod_unload ' should be '2
.6.30-rc3-tip SMP mod_unload '
[    7.413066] ata_piix: version magic '2.6.31.12 SMP mod_unload ' should be '2.
6.30-rc3-tip SMP mod_unload '
[    9.919044] ata_generic: version magic '2.6.31.12 SMP mod_unload ' should be
'2.6.30-rc3-tip SMP mod_unload '
[    9.924079] ahci: version magic '2.6.31.12 SMP mod_unload ' should be '2.6.30
-rc3-tip SMP mod_unload '
[   12.430218] scsi_wait_scan: version magic '2.6.31.12 SMP mod_unload ' should
be '2.6.30-rc3-tip SMP mod_unload '

It looks like you're trying to mix modules from a different kernel build.

	J

  reply	other threads:[~2010-06-17 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  1:07 How does pvops create loop device for initrd to support Xen live image? Wang, Shane
2010-06-17 10:02 ` Jeremy Fitzhardinge [this message]
2010-06-17 20:59   ` [Xen-users] " Martinx - ジェームズ

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=4C19F2C6.5080909@goop.org \
    --to=jeremy@goop.org \
    --cc=shane.wang@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.