WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Two recent patches that broke my stubdoms

To: John Weekes <lists.xen@xxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Two recent patches that broke my stubdoms
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 14 Jan 2010 10:16:28 +0000
Cc:
Delivery-date: Thu, 14 Jan 2010 02:16:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <B138B2C115654718BF085220A293DC17@JohnPC>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqUfFCJxZni5feIQVKq5mFPfZ05RAAhlHVT
Thread-topic: [Xen-devel] Two recent patches that broke my stubdoms
User-agent: Microsoft-Entourage/12.23.0.091001
On 13/01/2010 18:14, "John Weekes" <lists.xen@xxxxxxxxxxxxxxxxxx> wrote:

> Error: Device 768 (vbd) could not be connected. losetup /dev/loop0
> /path/to/file.img failed
>  
> Reverting c/s 20631 made it work again. I run Gentoo, and losetup -f works
> fine, but the new method apparently doesn't (I suspect it has something to do
> with having to start up the two domains so close together).

Should be fixed by c/s 20804.

>                 if count > 100:
>                     break

Should be fixed by c/s 20805.

> I tried to start my domain again, and it still wouldn't go. With the original
> image.py, it would just hang and show the main domain as --p--- and the
> stubdom as -b----. This told me that something was probably wrong with the
> stubdom or its configuration, so I took a look at the autogenerated stubdom
> file and found "monitor=null" in the vfb line, which was different than what
> previous versions put in. I simply edited image.py to revert c/s 20746, and
> this got rid of "monitor=null", allowing the domain to start.

We'll see if patch author comes up with a solution. Else I will revert the
changeset before doing an -rc2 next week.

 Thanks,
 Keir



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

<Prev in Thread] Current Thread [Next in Thread>