[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Re: [Xen-devel] Re: Writing a tool for Shared Persistent Windows Boot Image
- To: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
- From: "Jim Burnes" <jvburnes@xxxxxxxxx>
- Date: Fri, 29 Jun 2007 13:07:58 -0600
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, Anthony Liguori <anthony@xxxxxxxxxxxxx>
- Delivery-date: Fri, 29 Jun 2007 12:05:55 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=BVKZnq3e/k7RD1DvOmTtnN2mPyqj196nZx+D+xQB3phqN2FoqIDhdYEHMG+ijsqNP4kWRNnSKp/7XMZ0dUi1UvNF23NI24r/YSYKNw4WgkciexcvaDJRAK/cM/obT5M2UfW5nl1a1zH2kUjV+LlGxRm3FjkDrjgKTv+M9RvBZ9s=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Speaking of the XenSource 3.1.0 RPMs, I'd like to make a suggestion. When you build the xen-kernel for those 3.1.0 RPMs, can you make sure that the loop device is built as a module? By default the loop device is limited to 8 instances and when you build it into the kernel it makes it very difficult to change max_loop.
I tried adding it as a xen-kernel boot option in grub.conf, but as far as I can tell it's ignored when the loop device is compiled in the kernel.
For example, even though I added max_loop=16 to the boot options and modified the udev configuration to build 16 loop devices, every time xen does an 'losetup' on any device greater than loop7 it fails because the system doesn't think the device exists.
Just FYI. This means I'll have to raise the limit by recompiling the whole kernel.
Jim Burnes
On 6/29/07, Jim Burnes <
jvburnes@xxxxxxxxx> wrote:Just as a side note, I'm running from the RHEL 5
3.1.0 RPMs distributed by XenSource. I don't know if they include this fix.
Regards,
Jim Burnes
On 6/29/07,
Andrew Warfield <andrew.warfield@xxxxxxxxxxxx> wrote:
If you can send some more details on the crash we should be able to
sort this out -- it's certainly something that has worked in the past.
a.
On 6/29/07, Daniel P. Berrange <
berrange@xxxxxxxxxx> wrote:
> On Fri, Jun 29, 2007 at 07:38:47AM -0700, Andrew Warfield wrote:
> > This should have been fixed a few months ago:
> >
> > # HG changeset patch
> > # User
wim@xxxxxxxxxxxx
> > # Date 1170895981 28800
> > # Node ID 6524e02edbeb8aebe65aa5400af4b09dfccb8729
> > # Parent 780f097b54c5f9161f7c6cf3f86b2bb72cc43587
> > [blktap] Allow HVM booting from blktap device(s)
> >
> > What problems are you seeing?
>
> Yeah I saw that and am still trying to track down why it isn't doing what it
> ought to. Basically I see the guest start & immediately quit/crash
>
> Dan.
> --
> |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
> |=- Perl modules:
http://search.cpan.org/~danberr/
-=|
> |=- Projects: http://freshmeat.net/~danielpb/ -=|
> |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
