From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Stub domains broken in 3.4.0-rc3? Date: Fri, 8 May 2009 15:20:47 +0100 Message-ID: <4A043FBF.6090105@eu.citrix.com> References: <5411dbdc0905041256w1d57cd5fvfa62d1574384851f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5411dbdc0905041256w1d57cd5fvfa62d1574384851f@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keith Coleman Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Keith Coleman wrote: > Is there a known issue that prevents stub domains from working in 3.4.0-rc3? > > I attempted to use a stub domain configuration files that worked in > xen 3.3.1 but they don't work due to the recent addition of > automatically generated -dm files. Moving some config lines from the > old -dm file to the -stub file allows the creation process to go a > little further but I get the following error: > > # cat /var/log/xen/qemu-dm-win4.log > Error: Device 768 (vbd) could not be connected. > Device /dev/mapper/testvg-win4s is mounted in a guest domain, > and so cannot be mounted now. > Using config file "/etc/xen/stubdoms/win4-dm". > Using config file "/etc/xen/stubdoms/win4-dm". > > The stub domain dies immediately. Could you please post your config file? After the recent stubdom config file changes you only have one configuration file, as for normal non-stubdom domains. As a consequence you need to specify in that config file all the informations, including vif and disk and graphic frontend type. Sorry for the late reply, Stefano