From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Coleman Subject: Re: Stub domains broken in 3.4.0-rc3? Date: Fri, 8 May 2009 12:28:10 -0400 Message-ID: <5411dbdc0905080928m58ca21c3jab7992114dc55f85@mail.gmail.com> References: <5411dbdc0905041256w1d57cd5fvfa62d1574384851f@mail.gmail.com> <4A043FBF.6090105@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A043FBF.6090105@eu.citrix.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: Stefano Stabellini Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Fri, May 8, 2009 at 10:20 AM, Stefano Stabellini wrote: > 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 > My current config file is just a slightly modified version of the xmexample.hvm. It works for regular HVM mode if I switch the stubdom-dm for qemu-dm. I have fs-backend running in the background. # cat stub1-clean import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 512 name = "stub1" vif = [ 'type=ioemu, bridge=eth0' ] disk = [ 'phy:/dev/testvg/stub1,hda,w', 'file:/root/isos/win2003entR2.iso,hdc:cdrom,r' ] device_model = '/usr/' + arch_libdir + '/xen/bin/stubdom-dm' #device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' boot="dca" sdl=0 opengl=1 vnc=1 vnclisten="0.0.0.0" vncpasswd='' stdvga=0 serial='pty' usb=1 usbdevice='tablet' # cat /var/log/xen/qemu-dm-stub1.log Error: Device 768 (vbd) could not be connected. Device /dev/mapper/testvg-stub1 is mounted in a guest domain, and so cannot be mounted now. Using config file "/etc/xen/stubdoms/stub1-dm". Using config file "/etc/xen/stubdoms/stub1-dm". # cat /var/log/xen/qemu-dm-stub1-dm.log domid: 71 Warning: vlan 0 is not connected to host network Strip off blktap sub-type prefix to /root/isos/win2003entR2.iso (drv 'aio') Watching /local/domain/0/device-model/71/logdirty/next-active Watching /local/domain/0/device-model/71/command char device redirected to /dev/pts/3 /root/xen-3.4-rc3/xen-unstable.hg/tools/ioemu-dir/hw/xen_blktap.c:628: Init blktap pipes xs_read(): vncpasswd get error. /vm/e0dd1e52-a827-8c47-7e3d-cc26941e4419/vncpasswd. medium change watch on `hdc' (index: 1): aio:/root/isos/win2003entR2.iso -Keith