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

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

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