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. Keith _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
It works for me. Uncommented "disk" parameter in main config file ? -dulloor On Mon, May 4, 2009 at 3:56 PM, Keith Coleman <list.keith@scaltro.com>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. > > Keith > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefano Stabellini
2009-May-08 14:20 UTC
[Xen-devel] Re: Stub domains broken in 3.4.0-rc3?
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, May 8, 2009 at 10:20 AM, Stefano Stabellini <stefano.stabellini@eu.citrix.com> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefano Stabellini
2009-May-08 18:44 UTC
[Xen-devel] Re: Stub domains broken in 3.4.0-rc3?
The problem seems to be the "phy" disk that does not work correctly, but I don''t think it is caused by a bug in the new stubdomain config file generator. In fact I can reproduce the bug even using the old stubdom-dm script. Keith Coleman wrote:> > 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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, May 8, 2009 at 2:44 PM, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:> The problem seems to be the "phy" disk that does not work correctly, but > I don''t think it is caused by a bug in the new stubdomain config file > generator. > In fact I can reproduce the bug even using the old stubdom-dm script. > > Keith Coleman wrote: > >> >> 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 >> > > >I agree that this may have nothing to do with the new stubdom config generator. I have not been able to use stub domains in any of the 3.4.0-rc releases. You are probably correct about an issue with the phy disk in stubdom. Even on the stable code (3.3.1) certain types of block devices don''t seem to fully work in stub domains. DRBD is one such device. I would very much like to see stub domains working properly in time for the 3.4.0 release! Keith _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thiago Camargo Martins Cordeiro
2009-May-08 23:41 UTC
Re: [Xen-devel] Re: Stub domains broken in 3.4.0-rc3?
> I would very much like to see stub domains working properly in time forthe 3.4.0 release! +1 :-D 2009/5/8 Keith Coleman <list.keith@scaltro.com>> On Fri, May 8, 2009 at 2:44 PM, Stefano Stabellini > <stefano.stabellini@eu.citrix.com> wrote: > > The problem seems to be the "phy" disk that does not work correctly, but > > I don''t think it is caused by a bug in the new stubdomain config file > > generator. > > In fact I can reproduce the bug even using the old stubdom-dm script. > > > > Keith Coleman wrote: > > > >> > >> 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 > >> > > > > > > > > I agree that this may have nothing to do with the new stubdom config > generator. I have not been able to use stub domains in any of the > 3.4.0-rc releases. > > You are probably correct about an issue with the phy disk in stubdom. > Even on the stable code (3.3.1) certain types of block devices don''t > seem to fully work in stub domains. DRBD is one such device. > > I would very much like to see stub domains working properly in time > for the 3.4.0 release! > > Keith > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Realistically at this point you''re looking at 3.4.1 imo. Since 3.4.0 is out the door next week. -- Keir On 09/05/2009 00:41, "Thiago Camargo Martins Cordeiro" <thiagocmartinsc@gmail.com> wrote:>> I would very much like to see stub domains working properly in time for the >> 3.4.0 release! > > +1 > > :-D > > 2009/5/8 Keith Coleman <list.keith@scaltro.com> >> On Fri, May 8, 2009 at 2:44 PM, Stefano Stabellini >> <stefano.stabellini@eu.citrix.com> wrote: >>> The problem seems to be the "phy" disk that does not work correctly, but >>> I don''t think it is caused by a bug in the new stubdomain config file >>> generator. >>> In fact I can reproduce the bug even using the old stubdom-dm script. >>> >>> Keith Coleman wrote: >>> >>>> >>>> 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 >>>> >>> >>> >>> >> >> I agree that this may have nothing to do with the new stubdom config >> generator. I have not been able to use stub domains in any of the >> 3.4.0-rc releases. >> >> You are probably correct about an issue with the phy disk in stubdom. >> Even on the stable code (3.3.1) certain types of block devices don''t >> seem to fully work in stub domains. DRBD is one such device. >> >> I would very much like to see stub domains working properly in time >> for the 3.4.0 release! >> >> Keith >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel