xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Wang, Shane" <shane.wang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: [Xen-users] Re: How does pvops create loop device for initrd to support Xen live image?
Date: Thu, 17 Jun 2010 17:59:23 -0300	[thread overview]
Message-ID: <AANLkTilZ0S6OsYeVxW9UK3XVW3ETKHIXb8okXPbGqUtO@mail.gmail.com> (raw)
In-Reply-To: <4C19F2C6.5080909@goop.org>


[-- Attachment #1.1: Type: text/plain, Size: 2792 bytes --]

For sure, that's your problem, you must correct the kernel modules
version...

On 17 June 2010 07:02, Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> 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
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

[-- Attachment #1.2: Type: text/html, Size: 3659 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-06-17 20:59 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 ` [Xen-devel] " Jeremy Fitzhardinge
2010-06-17 20:59   ` Martinx - ジェームズ [this message]

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=AANLkTilZ0S6OsYeVxW9UK3XVW3ETKHIXb8okXPbGqUtO@mail.gmail.com \
    --to=thiagocmartinsc@gmail.com \
    --cc=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 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).