From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Two recent patches that broke my stubdoms Date: Thu, 14 Jan 2010 09:29:09 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Weekes , "xen-devel@lists.xensource.com" Cc: Daniel Kiper List-Id: xen-devel@lists.xenproject.org On 13/01/2010 18:14, "John Weekes" wrote: > c/s 20746 : > > 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. Cc'ing the patch author. My default response on this one would be just to revert the changeset. But there's probably something stubdom-specific that could be engineered instead. -- Keir