thr3ads.net - libvirt users - [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre [Mar 2010]

If this information is useful, please help other people find it:
Share via:

Mike Viau

2010-Mar-10 14:45 UTC

[Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Hi there,

Last night I was trying to start a HVM domU via stubdom-dm device model.
Initially I did not receive any error to stdout when I did so with Xen-3.4.2.

My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The
stubdom-dm guest I was trying to create did not really operate as I was unable
to connect to the VNC console. The output of xm list showed the DomU was there,
but it did not show it was actively running, almost like it was pause at
0:00:00.

This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM stubdom
configuration and got this message.

localhost:~/XENSTORE/router#xm create router

Using config file "./router".
Error: Device 768 (vbd) could not be connected.
File /root/XENSTORE/router/hd.img is loopback-mounted through /dev/loop1,
which is mounted in a guest domain,
and so cannot be mounted now.

AND

localhost:/var/log/xen# cat qemu-dm-router-dm.log

domid: 2
Warning: vlan 0 is not connected to host network
Watching /local/domain/0/device-model/2/logdirty/next-active
Watching /local/domain/0/device-model/2/command
char device redirected to /dev/pts/2
/usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628: Init
blktap pipes
bind() failed    <<-- This was also the last line in the log when using
Xen-3.4.2


AND


localhost:~/XENSTORE/router# xm info
host                   : localhost.site
release                : 2.6.33-xen
version                : #2 SMP Sat Mar 6 15:26:37 EST 2010
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2800
hw_caps                :
bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 8182
free_memory            : 7061
node_to_cpu            : node0:0-7
node_to_memory         : node0:7061
xen_major              : 3
xen_minor              : 4
xen_extra              : .3-rc4-pre
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Tue Mar 09 18:15:52 2010 +0000 19924:6e72f8c3c017
cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by          : root
cc_compile_domain      : site
cc_compile_date        : Wed Mar 10 08:46:50 EST 2010
xend_config_format     : 4


AND the configuration file


kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "router"
vcpus=1
pae=1
acpi=1
apic=1
vif = [ ''type=ioemu, mac=00:16:3e:11:11:01, bridge=br100'',
        ''type=ioemu, mac=00:16:3e:11:11:02, bridge=br101'',
        ''type=ioemu, mac=00:16:3e:11:11:03, bridge=br200'',
        ''type=ioemu, mac=00:16:3e:11:11:04, bridge=br300'',
        ''type=ioemu, mac=00:16:3e:11:11:05, bridge=br400'' ]
disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',
        
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
hdc:cdrom,r'' ]
device_model = ''/usr/lib/xen/bin/stubdom-dm''
boot="cda"
sdl=0
opengl=1
vnc=1
vnclisten="10.254.2.81"
vncdisplay=0
vncunused=0
vncpasswd=''router''
stdvga=0


LASTLY the router-dm file

#This file is autogenerated, edit router instead!
kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''
vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
vncdisplay=0, vnclisten=10.254.2.81, vncunused=0, vncpasswd=router'']
disk = [
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
]
vif = [
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
]



Can someone suggest what I might have done wrong, thanks!


-M

 		 	   		  
_________________________________________________________________
Check your Hotmail from your phone. 
http://go.microsoft.com/?linkid=9712957

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thomas Halinka

2010-Mar-10 15:29 UTC

head link

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Hi Mike,

Am Mittwoch, den 10.03.2010, 09:45 -0500 schrieb Mike
Viau:> Hi there,
> 
> Last night I was trying to start a HVM domU via stubdom-dm device
> model. Initially I did not receive any error to stdout when I did so
> with Xen-3.4.2.
> 
> My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
> guests). The stubdom-dm guest I was trying to create did not really
> operate as I was unable to connect to the VNC console. The output of
> xm list showed the DomU was there, but it did not show it was actively
> running, almost like it was pause at 0:00:00.
> 
> This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
> stubdom configuration and got this message.
> 
> localhost:~/XENSTORE/router#xm create router
> 
> Using config file "./router".
> Error: Device 768 (vbd) could not be connected.
> File /root/XENSTORE/router/hd.img is loopback-mounted
> through /dev/loop1,
> which is mounted in a guest domain,
> and so cannot be mounted now.
So, your domU has this disk mounted or used as loop-device, which 

losetup -a

should show. The Disk can be detached through 

losetup -d

This should help getting your VM start.

  # man losetup 

hth,

thomas

> 
> AND
> 
> localhost:/var/log/xen# cat qemu-dm-router-dm.log
> 
> domid: 2
> Warning: vlan 0 is not connected to host network
> Watching /local/domain/0/device-model/2/logdirty/next-active
> Watching /local/domain/0/device-model/2/command
> char device redirected to /dev/pts/2
> /usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
> Init blktap pipes
> bind() failed    <<-- This was also the last line in the log when
> using Xen-3.4.2
> 
> 
> AND
> 
> 
> localhost:~/XENSTORE/router# xm info
> host                   : localhost.site
> release                : 2.6.33-xen
> version                : #2 SMP Sat Mar 6 15:26:37 EST 2010
> machine                : x86_64
> nr_cpus                : 8
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 2
> cpu_mhz                : 2800
> hw_caps                :
> bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
> virt_caps              : hvm
> total_memory           : 8182
> free_memory            : 7061
> node_to_cpu            : node0:0-7
> node_to_memory         : node0:7061
> xen_major              : 3
> xen_minor              : 4
> xen_extra              : .3-rc4-pre
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : Tue Mar 09 18:15:52 2010 +0000
> 19924:6e72f8c3c017
> cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
> cc_compile_by          : root
> cc_compile_domain      : site
> cc_compile_date        : Wed Mar 10 08:46:50 EST 2010
> xend_config_format     : 4
> 
> 
> AND the configuration file
> 
> 
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory = 1024
> name = "router"
> vcpus=1
> pae=1
> acpi=1
> apic=1
> vif = [ ''type=ioemu, mac=00:16:3e:11:11:01,
bridge=br100'',
>         ''type=ioemu, mac=00:16:3e:11:11:02,
bridge=br101'',
>         ''type=ioemu, mac=00:16:3e:11:11:03,
bridge=br200'',
>         ''type=ioemu, mac=00:16:3e:11:11:04,
bridge=br300'',
>         ''type=ioemu, mac=00:16:3e:11:11:05, bridge=br400''
]
> disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',
> 
>
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
> hdc:cdrom,r'' ]
> device_model = ''/usr/lib/xen/bin/stubdom-dm''
> boot="cda"
> sdl=0
> opengl=1
> vnc=1
> vnclisten="10.254.2.81"
> vncdisplay=0
> vncunused=0
> vncpasswd=''router''
> stdvga=0
> 
> 
> LASTLY the router-dm file
> 
> #This file is autogenerated, edit router instead!
> kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''
> vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
> vncdisplay=0, vnclisten=10.254.2.81, vncunused=0,
vncpasswd=router'']
> disk > [
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
]
> vif > [
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
]
> 
> 
> 
> Can someone suggest what I might have done wrong, thanks!
> 
> 
> -M
> 
> 
> 
> ______________________________________________________________________
> Live connected with Messenger on your phone Learn more.
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Viau

2010-Mar-10 15:57 UTC

head link

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

> Subject: Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre
> From: lists@thohal.de
> To: mike.viau@sheridanc.on.ca
> Date: Wed, 10 Mar 2010 16:29:35 +0100
> CC: xen-users@lists.xensource.com
> 
> Hi Mike,
> 
> Am Mittwoch, den 10.03.2010, 09:45 -0500 schrieb Mike Viau:
> > Hi there,
> > 
> > Last night I was trying to start a HVM domU via stubdom-dm device
> > model. Initially I did not receive any error to stdout when I did so
> > with Xen-3.4.2.
> > 
> > My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
> > guests). The stubdom-dm guest I was trying to create did not really
> > operate as I was unable to connect to the VNC console. The output of
> > xm list showed the DomU was there, but it did not show it was actively
> > running, almost like it was pause at 0:00:00.
> > 
> > This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
> > stubdom configuration and got this message.
> > 
> > localhost:~/XENSTORE/router#xm create router
> > 
> > Using config file "./router".
> > Error: Device 768 (vbd) could not be connected.
> > File /root/XENSTORE/router/hd.img is loopback-mounted
> > through /dev/loop1,
> > which is mounted in a guest domain,
> > and so cannot be mounted now.
> 
> So, your domU has this disk mounted or used as loop-device, which 
> 
> losetup -a
> 
> should show. The Disk can be detached through 
> 
> losetup -d
> 
> This should help getting your VM start.
> 
>   # man losetup 
> 
> hth,
> 
> thomas
> 
>
I was unaware or the losetup but unfortunately this did not solve the problem.
It appears that the loop device is freed up after the error appears.

localhost:~/XENSTORE/router# xm create router
Using config file "./router".
Error: Device 768 (vbd) could not be connected.
File /root/XENSTORE/router/hd.img is loopback-mounted through /dev/loop1,
which is mounted in a guest domain,
and so cannot be mounted now.
localhost:~/XENSTORE/router# losetup -a
localhost:~/XENSTORE/router# 


 > > 
> > AND
> > 
> > localhost:/var/log/xen# cat qemu-dm-router-dm.log
> > 
> > domid: 2
> > Warning: vlan 0 is not connected to host network
> > Watching /local/domain/0/device-model/2/logdirty/next-active
> > Watching /local/domain/0/device-model/2/command
> > char device redirected to /dev/pts/2
> > /usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
> > Init blktap pipes
> > bind() failed    <<-- This was also the last line in the log
when
> > using Xen-3.4.2
> > 
> > 
> > AND
> > 
> > 
> > localhost:~/XENSTORE/router# xm info
> > host                   : localhost.site
> > release                : 2.6.33-xen
> > version                : #2 SMP Sat Mar 6 15:26:37 EST 2010
> > machine                : x86_64
> > nr_cpus                : 8
> > nr_nodes               : 1
> > cores_per_socket       : 4
> > threads_per_core       : 2
> > cpu_mhz                : 2800
> > hw_caps                :
> >
bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
> > virt_caps              : hvm
> > total_memory           : 8182
> > free_memory            : 7061
> > node_to_cpu            : node0:0-7
> > node_to_memory         : node0:7061
> > xen_major              : 3
> > xen_minor              : 4
> > xen_extra              : .3-rc4-pre
> > xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> > hvm-3.0-x86_32p hvm-3.0-x86_64
> > xen_scheduler          : credit
> > xen_pagesize           : 4096
> > platform_params        : virt_start=0xffff800000000000
> > xen_changeset          : Tue Mar 09 18:15:52 2010 +0000
> > 19924:6e72f8c3c017
> > cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
> > cc_compile_by          : root
> > cc_compile_domain      : site
> > cc_compile_date        : Wed Mar 10 08:46:50 EST 2010
> > xend_config_format     : 4
> > 
> > 
> > AND the configuration file
> > 
> > 
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder=''hvm''
> > memory = 1024
> > name = "router"
> > vcpus=1
> > pae=1
> > acpi=1
> > apic=1
> > vif = [ ''type=ioemu, mac=00:16:3e:11:11:01,
bridge=br100'',
> >         ''type=ioemu, mac=00:16:3e:11:11:02,
bridge=br101'',
> >         ''type=ioemu, mac=00:16:3e:11:11:03,
bridge=br200'',
> >         ''type=ioemu, mac=00:16:3e:11:11:04,
bridge=br300'',
> >         ''type=ioemu, mac=00:16:3e:11:11:05,
bridge=br400'' ]
> > disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',
> > 
> >
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
> > hdc:cdrom,r'' ]
> > device_model = ''/usr/lib/xen/bin/stubdom-dm''
> > boot="cda"
> > sdl=0
> > opengl=1
> > vnc=1
> > vnclisten="10.254.2.81"
> > vncdisplay=0
> > vncunused=0
> > vncpasswd=''router''
> > stdvga=0
> > 
> > 
> > LASTLY the router-dm file
> > 
> > #This file is autogenerated, edit router instead!
> > kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''
> > vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
> > vncdisplay=0, vnclisten=10.254.2.81, vncunused=0,
vncpasswd=router'']
> > disk > > [
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
]
> > vif > > [
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
]
> > 
> > 
> > 
> > Can someone suggest what I might have done wrong, thanks!
> > 
> > 
> > -M
> > 
> > 
> > 
> > ______________________________________________________________________
> > Live connected with Messenger on your phone Learn more.
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users 		 	   		  
_________________________________________________________________
Stay in touch.
http://go.microsoft.com/?linkid=9712959

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Viau

2010-Mar-11 04:55 UTC

head link

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

I found this link:

http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00698.html

Was Xen 3.4.x ever fixed to used phy:/ disk entries?

And also:

http://lists.xensource.com/archives/html/xen-devel/2009-10/msg00169.html

Is Xen still prone to crashing when using stubdoms?


I have yet to get stubdom HVM guest running? Could someone please post a working
hvm-stubdom example... I have been using /etc/xen/xmexample.hvm-stubdom with no
luck.

 
Thanks.
 


-M



From: viaum@sheridanc.on.ca
To: lists@thohal.de
Subject: RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre
Date: Wed, 10 Mar 2010 10:57:10 -0500
CC: xen-users@lists.xensource.com







> Subject: Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre
> From: lists@thohal.de
> To: viaum@sheridanc.on.ca
> Date: Wed, 10 Mar 2010 16:29:35 +0100
> CC: xen-users@lists.xensource.com
> 
> Hi Mike,
> 
> Am Mittwoch, den 10.03.2010, 09:45 -0500 schrieb Mike Viau:
> > Hi there,
> > 
> > Last night I was trying to start a HVM domU via stubdom-dm device
> > model. Initially I did not receive any error to stdout when I did so
> > with Xen-3.4.2.
> > 
> > My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
> > guests). The stubdom-dm guest I was trying to create did not really
> > operate as I was unable to connect to the VNC console. The output of
> > xm list showed the DomU was there, but it did not show it was actively
> > running, almost like it was pause at 0:00:00.
> > 
> > This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
> > stubdom configuration and got this message.
> > 
> > localhost:~/XENSTORE/router#xm create router
> > 
> > Using config file "./router".
> > Error: Device 768 (vbd) could not be connected.
> > File /root/XENSTORE/router/hd.img is loopback-mounted
> > through /dev/loop1,
> > which is mounted in a guest domain,
> > and so cannot be mounted now.
> 
> So, your domU has this disk mounted or used as loop-device, which 
> 
> losetup -a
> 
> should show. The Disk can be detached through 
> 
> losetup -d
> 
> This should help getting your VM start.
> 
>   # man losetup 
> 
> hth,
> 
> thomas
> 
>
I was unaware or the losetup but unfortunately this did not solve the problem.
It appears that the loop device is freed up after the error appears.

localhost:~/XENSTORE/router# xm create router
Using config file "./router".
Error: Device 768 (vbd) could not be connected.
File /root/XENSTORE/router/hd.img is loopback-mounted through /dev/loop1,
which is mounted in a guest domain,
and so cannot be mounted now.
localhost:~/XENSTORE/router# losetup -a
localhost:~/XENSTORE/router# 


 > > 
> > AND
> > 
> > localhost:/var/log/xen# cat qemu-dm-router-dm.log
> > 
> > domid: 2
> > Warning: vlan 0 is not connected to host network
> > Watching /local/domain/0/device-model/2/logdirty/next-active
> > Watching /local/domain/0/device-model/2/command
> > char device redirected to /dev/pts/2
> > /usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
> > Init blktap pipes
> > bind() failed    <<-- This was also the last line in the log
when
> > using Xen-3.4.2
> > 
> > 
> > AND
> > 
> > 
> > localhost:~/XENSTORE/router# xm info
> > host                   : localhost.site
> > release                : 2.6.33-xen
> > version                : #2 SMP Sat Mar 6 15:26:37 EST 2010
> > machine                : x86_64
> > nr_cpus                : 8
> > nr_nodes               : 1
> > cores_per_socket       : 4
> > threads_per_core       : 2
> > cpu_mhz                : 2800
> > hw_caps                :
> >
bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
> > virt_caps              : hvm
> > total_memory           : 8182
> > free_memory            : 7061
> > node_to_cpu            : node0:0-7
> > node_to_memory         : node0:7061
> > xen_major              : 3
> > xen_minor              : 4
> > xen_extra              : .3-rc4-pre
> > xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> > hvm-3.0-x86_32p hvm-3.0-x86_64
> > xen_scheduler          : credit
> > xen_pagesize           : 4096
> > platform_params        : virt_start=0xffff800000000000
> > xen_changeset          : Tue Mar 09 18:15:52 2010 +0000
> > 19924:6e72f8c3c017
> > cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
> > cc_compile_by          : root
> > cc_compile_domain      : site
> > cc_compile_date        : Wed Mar 10 08:46:50 EST 2010
> > xend_config_format     : 4
> > 
> > 
> > AND the configuration file
> > 
> > 
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder=''hvm''
> > memory = 1024
> > name = "router"
> > vcpus=1
> > pae=1
> > acpi=1
> > apic=1
> > vif = [ ''type=ioemu, mac=00:16:3e:11:11:01,
bridge=br100'',
> >         ''type=ioemu, mac=00:16:3e:11:11:02,
bridge=br101'',
> >         ''type=ioemu, mac=00:16:3e:11:11:03,
bridge=br200'',
> >         ''type=ioemu, mac=00:16:3e:11:11:04,
bridge=br300'',
> >         ''type=ioemu, mac=00:16:3e:11:11:05,
bridge=br400'' ]
> > disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',
> > 
> >
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
> > hdc:cdrom,r'' ]
> > device_model = ''/usr/lib/xen/bin/stubdom-dm''
> > boot="cda"
> > sdl=0
> > opengl=1
> > vnc=1
> > vnclisten="10.254.2.81"
> > vncdisplay=0
> > vncunused=0
> > vncpasswd=''router''
> > stdvga=0
> > 
> > 
> > LASTLY the router-dm file
> > 
> > #This file is autogenerated, edit router instead!
> > kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''
> > vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
> > vncdisplay=0, vnclisten=10.254.2.81, vncunused=0,
vncpasswd=router'']
> > disk > > [
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
]
> > vif > > [
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
]
> > 
> > 
> > 
> > Can someone suggest what I might have done wrong, thanks!
> > 
> > 
> > -M 		 	   		  
_________________________________________________________________
Live connected with Messenger on your phone
http://go.microsoft.com/?linkid=9712958

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Andrew Evans

2010-Mar-15 22:27 UTC

head link

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Hi Mike,

I''ve just gone through stubdom initiation myself. Most of my problems
were caused by not following stubdom/README (from the Xen source tree)
to the letter, and trying to mix and match stub domains and PV on HVM. I
am using phy devices (logical volumes) for storage.

You don''t say whether you''ve started fs-backend per the
README. That
would certainly cause problems trying to create a domain.

I had to build the 2.6.18.8 xen.org dom0 kernel as the RHEL 5 dom0
kernel I normally use doesn''t have gntdev, which is necessary for stub
domains to work.

-Andrew

On 03/10/10 06:45, Mike Viau wrote:> Hi there,
>
> Last night I was trying to start a HVM domU via stubdom-dm device
> model. Initially I did not receive any error to stdout when I did so
> with Xen-3.4.2.
>
> My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
> guests). The stubdom-dm guest I was trying to create did not really
> operate as I was unable to connect to the VNC console. The output of
> xm list showed the DomU was there, but it did not show it was actively
> running, almost like it was pause at 0:00:00.
>
> This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
> stubdom configuration and got this message.
>
> localhost:~/XENSTORE/router#xm create router
>
> Using config file "./router".
> Error: Device 768 (vbd) could not be connected.
> File /root/XENSTORE/router/hd.img is loopback-mounted through /dev/loop1,
> which is mounted in a guest domain,
> and so cannot be mounted now.
>
> AND
>
> localhost:/var/log/xen# cat qemu-dm-router-dm.log
>
> domid: 2
> Warning: vlan 0 is not connected to host network
> Watching /local/domain/0/device-model/2/logdirty/next-active
> Watching /local/domain/0/device-model/2/command
> char device redirected to /dev/pts/2
> /usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
> Init blktap pipes
> bind() failed    <<-- This was also the last line in the log when
> using Xen-3.4.2
>
>
> AND
>
>
> localhost:~/XENSTORE/router# xm info
> host                   : localhost.site
> release                : 2.6.33-xen
> version                : #2 SMP Sat Mar 6 15:26:37 EST 2010
> machine                : x86_64
> nr_cpus                : 8
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 2
> cpu_mhz                : 2800
> hw_caps                :
> bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
> virt_caps              : hvm
> total_memory           : 8182
> free_memory            : 7061
> node_to_cpu            : node0:0-7
> node_to_memory         : node0:7061
> xen_major              : 3
> xen_minor              : 4
> xen_extra              : .3-rc4-pre
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : Tue Mar 09 18:15:52 2010 +0000 19924:6e72f8c3c017
> cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
> cc_compile_by          : root
> cc_compile_domain      : site
> cc_compile_date        : Wed Mar 10 08:46:50 EST 2010
> xend_config_format     : 4
>
>
> AND the configuration file
>
>
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory = 1024
> name = "router"
> vcpus=1
> pae=1
> acpi=1
> apic=1
> vif = [ ''type=ioemu, mac=00:16:3e:11:11:01,
bridge=br100'',
>         ''type=ioemu, mac=00:16:3e:11:11:02,
bridge=br101'',
>         ''type=ioemu, mac=00:16:3e:11:11:03,
bridge=br200'',
>         ''type=ioemu, mac=00:16:3e:11:11:04,
bridge=br300'',
>         ''type=ioemu, mac=00:16:3e:11:11:05, bridge=br400''
]
> disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',
>         
>
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
> hdc:cdrom,r'' ]
> device_model = ''/usr/lib/xen/bin/stubdom-dm''
> boot="cda"
> sdl=0
> opengl=1
> vnc=1
> vnclisten="10.254.2.81"
> vncdisplay=0
> vncunused=0
> vncpasswd=''router''
> stdvga=0
>
>
> LASTLY the router-dm file
>
> #This file is autogenerated, edit router instead!
> kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''
> vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
> vncdisplay=0, vnclisten=10.254.2.81, vncunused=0,
vncpasswd=router'']
> disk = [
>
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
> ]
> vif = [
>
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
> ]
>
>
>
> Can someone suggest what I might have done wrong, thanks!
>
>
> -M
>
>
> ------------------------------------------------------------------------
> Live connected with Messenger on your phone Learn more.
> <http://go.microsoft.com/?linkid=9712957>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Viau

2010-Mar-15 22:52 UTC

head link

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

On Mon, 15 Mar 2010 15:27:44 -0700 andrewe@yahoo-inc.com wrote:






  


Hi Mike,


>I''ve just gone through stubdom initiation myself. Most of my
problemswere caused by not following stubdom/README (from the Xen source tree)
to the letter, and trying to mix and match stub domains and PV on HVM.
I am using phy devices (logical volumes) for storage.

I gave up on loop devices as well. I realized that creating logical volumes with
lvm2 was just as easy to manage. Just to clarify you used the disk option like:

phy:/full/path/to/dev,DEV,MODE ?

Perhaps you could post a working DomU config???



>You don''t say whether you''ve started fs-backend per the
README. Thatwould certainly cause problems trying to create a domain.

Indeed. I created a script to start my domU:

#!/bin/sh

mkdir -p /exports/usr/share/xen/qemu
ln -s /usr/share/xen/qemu/keymaps /exports/usr/share/xen/qemu
mkdir -p /exports/var/lib
ln -s /var/lib/xen /exports/var/lib
/usr/sbin/fs-backend &
xm create (name on domU config)



>I had to build the 2.6.18.8 xen.org dom0 kernel as the RHEL 5 dom0kernel I normally use doesn''t have gntdev, which is necessary for stub
domains to work.


This I did not know. May I ask where you acquired this knowledge?

Thanks

-M


>-Andrew


On 03/10/10 06:45, Mike Viau wrote:

  Hi
there,

  

Last night I was trying to start a HVM domU via stubdom-dm device
model. Initially I did not receive any error to stdout when I did so
with Xen-3.4.2.

  

My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
guests). The stubdom-dm guest I was trying to create did not really
operate as I was unable to connect to the VNC console. The output of xm
list showed the DomU was there, but it did not show it was actively
running, almost like it was pause at 0:00:00.

  

This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
stubdom configuration and got this message.

  

localhost:~/XENSTORE/router#xm create router

  

Using config file "./router".

Error: Device 768 (vbd) could not be connected.

File /root/XENSTORE/router/hd.img is loopback-mounted through
/dev/loop1,

which is mounted in a guest domain,

and so cannot be mounted now.

  

AND

  

localhost:/var/log/xen# cat qemu-dm-router-dm.log

  

domid: 2

Warning: vlan 0 is not connected to host network

Watching /local/domain/0/device-model/2/logdirty/next-active

Watching /local/domain/0/device-model/2/command

char device redirected to /dev/pts/2

/usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
Init blktap pipes

bind() failed    <<-- This was also the last line in the log when
using Xen-3.4.2

  

  

AND

  

  

localhost:~/XENSTORE/router# xm info

host                   : localhost.site

release                : 2.6.33-xen

version                : #2 SMP Sat Mar 6 15:26:37 EST 2010

machine                : x86_64

nr_cpus                : 8

nr_nodes               : 1

cores_per_socket       : 4

threads_per_core       : 2

cpu_mhz                : 2800

hw_caps                :
bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000

virt_caps              : hvm

total_memory           : 8182

free_memory            : 7061

node_to_cpu            : node0:0-7

node_to_memory         : node0:7061

xen_major              : 3

xen_minor              : 4

xen_extra              : .3-rc4-pre

xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64

xen_scheduler          : credit

xen_pagesize           : 4096

platform_params        : virt_start=0xffff800000000000

xen_changeset          : Tue Mar 09 18:15:52 2010 +0000
19924:6e72f8c3c017

cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)

cc_compile_by          : root

cc_compile_domain      : site

cc_compile_date        : Wed Mar 10 08:46:50 EST 2010

xend_config_format     : 4

  

  

AND the configuration file

  

  

kernel = "/usr/lib/xen/boot/hvmloader"

builder=''hvm''

memory = 1024

name = "router"

vcpus=1

pae=1

acpi=1

apic=1

vif = [ ''type=ioemu, mac=00:16:3e:11:11:01, bridge=br100'',

        ''type=ioemu, mac=00:16:3e:11:11:02, bridge=br101'',

        ''type=ioemu, mac=00:16:3e:11:11:03, bridge=br200'',

        ''type=ioemu, mac=00:16:3e:11:11:04, bridge=br300'',

        ''type=ioemu, mac=00:16:3e:11:11:05, bridge=br400'' ]

disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',

        
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,

hdc:cdrom,r'' ]

device_model = ''/usr/lib/xen/bin/stubdom-dm''

boot="cda"

sdl=0

opengl=1

vnc=1

vnclisten="10.254.2.81"

vncdisplay=0

vncunused=0

vncpasswd=''router''

stdvga=0

  

  

LASTLY the router-dm file

  

#This file is autogenerated, edit router instead!

kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''

vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
vncdisplay=0, vnclisten=10.254.2.81, vncunused=0, vncpasswd=router'']

disk = [
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
]

vif = [
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
]

  

  

  

Can someone suggest what I might have done wrong, thanks!

  

  

-M

  

  

  Live connected with Messenger on your phone Learn more.
  
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users


 		 	   		  
_________________________________________________________________
Check your Hotmail from your phone. 
http://go.microsoft.com/?linkid=9712957

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Andrew Evans

2010-Mar-16 00:58 UTC

head link

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

On 03/15/10 15:52, Mike Viau wrote:> *On Mon, 15 Mar 2010 15:27:44 -0700 andrewe@yahoo-inc.com wrote:*
>
<snip>
> phy:/full/path/to/dev,DEV,MODE ?
>
> Perhaps you could post a working DomU config???
My config is in libvirt XML form, sorry. Here''s an excerpt of the
serialized device config from xend.log:

        ''07f11f37-944d-bbed-6f56-bf9279b39d9d'': (
            ''vbd'', {
                ''uuid'':
''07f11f37-944d-bbed-6f56-bf9279b39d9d'',
                ''bootable'': 1,
                ''driver'': ''paravirtualised'',
                ''dev'': ''hda:disk'',
                ''uname'': ''phy:/dev/sys/lv0'',
                ''mode'': ''w''
                }
            ),
>
> >You don''t say whether you''ve started fs-backend per
the README. That
> would certainly cause problems trying to create a domain.
>
> Indeed. I created a script to start my domU:
>
> #!/bin/sh
>
> mkdir -p /exports/usr/share/xen/qemu
> ln -s /usr/share/xen/qemu/keymaps /exports/usr/share/xen/qemu
> mkdir -p /exports/var/lib
> ln -s /var/lib/xen /exports/var/lib
> /usr/sbin/fs-backend &
You might want to sleep a few seconds in here...
> xm create (name on domU config)
>
>
> >I had to build the 2.6.18.8 xen.org dom0 kernel as the RHEL 5 dom0
> kernel I normally use doesn''t have gntdev, which is necessary for
stub
> domains to work.
>
> This I did not know. May I ask where you acquired this knowledge?
I was getting this error on the terminal where I''d started fs-backend:

virsh # start cg3.c803.mail.sp2.yahoo.com
Domain cg3.c803.mail.sp2.yahoo.com started

virsh # Path changed backend/vfs/exports/requests/7/0/frontend
Handling connection from dom=7, for export=0
Frontend found at: /local/domain/7/device/vfs/0 (gref=2047, evtchn=4)
ERROR Internal error: Could not open grant table interface (22 = Invalid
argument)
ERROR: Couldn''t open gnttab!
Awaiting next connection.
Path changed backend/vfs/exports/requests/7/0/frontend
Awaiting next connection.

Did some web searching on "Could not open grant table interface (22 Invalid
argument)" and turned up the gntdev.ko solution. grepped the
RHEL 5 dom0 kernel''s System.map for gntdev symbols, turned up nothing.
Built/installed/booted 2.6.18.8 from xen-unstable, problem solved.

-Andrew
>
> Thanks
>
> -M
>
>
> >-Andrew
>
> On 03/10/10 06:45, Mike Viau wrote:
>
>     Hi there,
>
>     Last night I was trying to start a HVM domU via stubdom-dm device
>     model. Initially I did not receive any error to stdout when I did
>     so with Xen-3.4.2.
>
>     My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
>     guests). The stubdom-dm guest I was trying to create did not
>     really operate as I was unable to connect to the VNC console. The
>     output of xm list showed the DomU was there, but it did not show
>     it was actively running, almost like it was pause at 0:00:00.
>
>     This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
>     stubdom configuration and got this message.
>
>     localhost:~/XENSTORE/router#xm create router
>
>     Using config file "./router".
>     Error: Device 768 (vbd) could not be connected.
>     File /root/XENSTORE/router/hd.img is loopback-mounted through
>     /dev/loop1,
>     which is mounted in a guest domain,
>     and so cannot be mounted now.
>
>     AND
>
>     localhost:/var/log/xen# cat qemu-dm-router-dm.log
>
>     domid: 2
>     Warning: vlan 0 is not connected to host network
>     Watching /local/domain/0/device-model/2/logdirty/next-active
>     Watching /local/domain/0/device-model/2/command
>     char device redirected to /dev/pts/2
>     /usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
>     Init blktap pipes
>     bind() failed    <<-- This was also the last line in the log when
>     using Xen-3.4.2
>
>
>     AND
>
>
>     localhost:~/XENSTORE/router# xm info
>     host                   : localhost.site
>     release                : 2.6.33-xen
>     version                : #2 SMP Sat Mar 6 15:26:37 EST 2010
>     machine                : x86_64
>     nr_cpus                : 8
>     nr_nodes               : 1
>     cores_per_socket       : 4
>     threads_per_core       : 2
>     cpu_mhz                : 2800
>     hw_caps                :
>     bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
>     virt_caps              : hvm
>     total_memory           : 8182
>     free_memory            : 7061
>     node_to_cpu            : node0:0-7
>     node_to_memory         : node0:7061
>     xen_major              : 3
>     xen_minor              : 4
>     xen_extra              : .3-rc4-pre
>     xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
>     hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
>     xen_scheduler          : credit
>     xen_pagesize           : 4096
>     platform_params        : virt_start=0xffff800000000000
>     xen_changeset          : Tue Mar 09 18:15:52 2010 +0000
>     19924:6e72f8c3c017
>     cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)
>     cc_compile_by          : root
>     cc_compile_domain      : site
>     cc_compile_date        : Wed Mar 10 08:46:50 EST 2010
>     xend_config_format     : 4
>
>
>     AND the configuration file
>
>
>     kernel = "/usr/lib/xen/boot/hvmloader"
>     builder=''hvm''
>     memory = 1024
>     name = "router"
>     vcpus=1
>     pae=1
>     acpi=1
>     apic=1
>     vif = [ ''type=ioemu, mac=00:16:3e:11:11:01,
bridge=br100'',
>             ''type=ioemu, mac=00:16:3e:11:11:02,
bridge=br101'',
>             ''type=ioemu, mac=00:16:3e:11:11:03,
bridge=br200'',
>             ''type=ioemu, mac=00:16:3e:11:11:04,
bridge=br300'',
>             ''type=ioemu, mac=00:16:3e:11:11:05,
bridge=br400'' ]
>     disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',
>             
>    
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
>     hdc:cdrom,r'' ]
>     device_model = ''/usr/lib/xen/bin/stubdom-dm''
>     boot="cda"
>     sdl=0
>     opengl=1
>     vnc=1
>     vnclisten="10.254.2.81"
>     vncdisplay=0
>     vncunused=0
>     vncpasswd=''router''
>     stdvga=0
>
>
>     LASTLY the router-dm file
>
>     #This file is autogenerated, edit router instead!
>     kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''
>     vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
>     vncdisplay=0, vnclisten=10.254.2.81, vncunused=0,
vncpasswd=router'']
>     disk = [
>    
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
>     ]
>     vif = [
>    
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
>     ]
>
>
>
>     Can someone suggest what I might have done wrong, thanks!
>
>
>     -M
>
>
>    
------------------------------------------------------------------------
>     Live connected with Messenger on your phone Learn more.
>     <http://go.microsoft.com/?linkid=9712957>
>
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
>     http://lists.xensource.com/xen-users
>
>
>
> ------------------------------------------------------------------------
> Live connected with Messenger on your phone Learn more.
> <http://go.microsoft.com/?linkid=9712957>


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Viau

2010-Mar-16 02:15 UTC

head link

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

A working libvirt XML formatted DomU would surfice. 



I was looking at http://libvirt.org/drvxen.html



And realized that "virsh
domxml-to-native" may be used to convert the domU configuration to native
if
necessary.



I am interested in knowing how you incorporated the stubdom-dm loader.



The link above demonstrates Fullyvirtualized guest direct kernel boots,
Fullyvirtualized guest BIOS boots, Paravirtualized guest direct kernel boots,
and Paravirtualized guest bootloader with pygrub examples.



Non of the examples feature the stubdom-dm loader.



I would greatly appreciate it if you could post a complete and working stubdom
HVM domU configuration.



Thanks.


 

-M




Date: Mon, 15 Mar 2010 17:58:39 -0700
From: andrewe@yahoo-inc.com
To: mike.viau@sheridanc.on.ca
Subject: Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre
CC: xen-users@lists.xensource.com






  


On 03/15/10 15:52, Mike Viau wrote:

  On
Mon, 15 Mar 2010 15:27:44 -0700 andrewe@yahoo-inc.com wrote:

  




<snip>



phy:/full/path/to/dev,DEV,MODE ?

  

Perhaps you could post a working DomU config???




My config is in libvirt XML form, sorry. Here''s an excerpt of the
serialized device config from xend.log:



        ''07f11f37-944d-bbed-6f56-bf9279b39d9d'': (

            ''vbd'', {

                ''uuid'':
''07f11f37-944d-bbed-6f56-bf9279b39d9d'',

                ''bootable'': 1,

                ''driver'': ''paravirtualised'',

                ''dev'': ''hda:disk'',

                ''uname'': ''phy:/dev/sys/lv0'',

                ''mode'': ''w''

                }

            ),




>You don''t say whether you''ve started fs-backend per the
README.That
would certainly cause problems trying to create a domain.

  

Indeed. I created a script to start my domU:

  

#!/bin/sh

  

mkdir -p /exports/usr/share/xen/qemu

ln -s /usr/share/xen/qemu/keymaps /exports/usr/share/xen/qemu

mkdir -p /exports/var/lib

ln -s /var/lib/xen /exports/var/lib

/usr/sbin/fs-backend &




You might want to sleep a few seconds in here...



xm create (name on domU config)

  

  
>I had to build the 2.6.18.8 xen.org dom0 kernel as the RHEL 5 dom0kernel I normally use doesn''t have gntdev, which is necessary for stub
domains to work.

  

This I did not know. May I ask where you acquired this knowledge?




I was getting this error on the terminal where I''d started fs-backend:



virsh # start cg3.c803.mail.sp2.yahoo.com

Domain cg3.c803.mail.sp2.yahoo.com started



virsh # Path changed backend/vfs/exports/requests/7/0/frontend

Handling connection from dom=7, for export=0

Frontend found at: /local/domain/7/device/vfs/0 (gref=2047, evtchn=4)

ERROR Internal error: Could not open grant table interface (22 Invalid argument)

ERROR: Couldn''t open gnttab!

Awaiting next connection.

Path changed backend/vfs/exports/requests/7/0/frontend

Awaiting next connection.



Did some web searching on "Could not open grant table interface (22 Invalid
argument)" and turned up the gntdev.ko solution. grepped the
RHEL 5 dom0 kernel''s System.map for gntdev symbols, turned up nothing.
Built/installed/booted 2.6.18.8 from xen-unstable, problem solved.



-Andrew





Thanks

  

-M

  

  
>-Andrew
  

On 03/10/10 06:45, Mike Viau wrote:
  
    Hi
there,

    

Last night I was trying to start a HVM domU via stubdom-dm device
model. Initially I did not receive any error to stdout when I did so
with Xen-3.4.2.

    

My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
guests). The stubdom-dm guest I was trying to create did not really
operate as I was unable to connect to the VNC console. The output of xm
list showed the DomU was there, but it did not show it was actively
running, almost like it was pause at 0:00:00.

    

This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
stubdom configuration and got this message.

    

localhost:~/XENSTORE/router#xm create router

    

Using config file "./router".

Error: Device 768 (vbd) could not be connected.

File /root/XENSTORE/router/hd.img is loopback-mounted through
/dev/loop1,

which is mounted in a guest domain,

and so cannot be mounted now.

    

AND

    

localhost:/var/log/xen# cat qemu-dm-router-dm.log

    

domid: 2

Warning: vlan 0 is not connected to host network

Watching /local/domain/0/device-model/2/logdirty/next-active

Watching /local/domain/0/device-model/2/command

char device redirected to /dev/pts/2

/usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
Init blktap pipes

bind() failed    <<-- This was also the last line in the log when
using Xen-3.4.2

    

    

AND

    

    

localhost:~/XENSTORE/router# xm info

host                   : localhost.site

release                : 2.6.33-xen

version                : #2 SMP Sat Mar 6 15:26:37 EST 2010

machine                : x86_64

nr_cpus                : 8

nr_nodes               : 1

cores_per_socket       : 4

threads_per_core       : 2

cpu_mhz                : 2800

hw_caps                :
bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000

virt_caps              : hvm

total_memory           : 8182

free_memory            : 7061

node_to_cpu            : node0:0-7

node_to_memory         : node0:7061

xen_major              : 3

xen_minor              : 4

xen_extra              : .3-rc4-pre

xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64

xen_scheduler          : credit

xen_pagesize           : 4096

platform_params        : virt_start=0xffff800000000000

xen_changeset          : Tue Mar 09 18:15:52 2010 +0000
19924:6e72f8c3c017

cc_compiler            : gcc version 4.3.2 (Debian 4.3.2-1.1)

cc_compile_by          : root

cc_compile_domain      : site

cc_compile_date        : Wed Mar 10 08:46:50 EST 2010

xend_config_format     : 4

    

    

AND the configuration file

    

    

kernel = "/usr/lib/xen/boot/hvmloader"

builder=''hvm''

memory = 1024

name = "router"

vcpus=1

pae=1

acpi=1

apic=1

vif = [ ''type=ioemu, mac=00:16:3e:11:11:01, bridge=br100'',

        ''type=ioemu, mac=00:16:3e:11:11:02, bridge=br101'',

        ''type=ioemu, mac=00:16:3e:11:11:03, bridge=br200'',

        ''type=ioemu, mac=00:16:3e:11:11:04, bridge=br300'',

        ''type=ioemu, mac=00:16:3e:11:11:05, bridge=br400'' ]

disk = [ ''file:/root/XENSTORE/router/hd.img,hda,w'',

        
''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,

hdc:cdrom,r'' ]

device_model = ''/usr/lib/xen/bin/stubdom-dm''

boot="cda"

sdl=0

opengl=1

vnc=1

vnclisten="10.254.2.81"

vncdisplay=0

vncunused=0

vncpasswd=''router''

stdvga=0

    

    

LASTLY the router-dm file

    

#This file is autogenerated, edit router instead!

kernel = ''/usr/lib/xen/boot/ioemu-stubdom.gz''

vfb = [''sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
vncdisplay=0, vnclisten=10.254.2.81, vncunused=0, vncpasswd=router'']

disk = [
''file:/root/XENSTORE/router/hd.img,hda:disk,w'',''file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r''
]

vif = [
''mac=00:16:3e:11:11:01,bridge=br100'',''mac=00:16:3e:11:11:02,bridge=br101'',''mac=00:16:3e:11:11:03,bridge=br200'',''mac=00:16:3e:11:11:04,bridge=br300'',''mac=00:16:3e:11:11:05,bridge=br400''
]

    

    

    

Can someone suggest what I might have done wrong, thanks!

    

    

-M

    

    

    Live connected with Messenger on your phone Learn
more.
    
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
  
  

  

  Live connected with Messenger on your phone Learn more.

 		 	   		  
_________________________________________________________________
Stay in touch.
http://go.microsoft.com/?linkid=9712959

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Andrew Evans

2010-Mar-16 02:26 UTC

head link

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

On 03/15/10 19:15, Mike Viau wrote:>
> A working libvirt XML formatted DomU would surfice.
>
Here you go:

<domain type=''xen''>
  <name>test</name>
  <os>
    <type>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev=''hd''/>
  </os>

  <memory>7340032</memory>
  <vcpu>7</vcpu>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <features>
     <pae/>
     <acpi/>
     <apic/>
  </features>
  <clock offset=''utc''/>

  <devices>
    <emulator>/usr/lib/xen/bin/stubdom-dm</emulator>

    <interface type=''bridge''>
      <source bridge=''eth0''/>
      <mac address=''00:50:56:0f:dd:02''/>
    </interface>

    <disk type=''block'' device=''disk''>
      <source dev=''/dev/sys/lv0''/>
      <target dev=''hda''/>
    </disk>
    <disk type=''block'' device=''disk''>
      <source dev=''/dev/sys/lv1''/>
      <target dev=''hdb''/>
    </disk>
    <disk type=''block'' device=''disk''>
      <source dev=''/dev/sys/lv2''/>
      <target dev=''hdc''/>
    </disk>

<!-- stub domains don''t have access to dom0''s ptys, so this
is not possible
    <serial type=''pty''>
    </serial>
-->

    <graphics type=''vnc''
autoport=''yes''/>

  </devices>
</domain>
> I was looking at http://libvirt.org/drvxen.html
>
> And realized that "|virsh domxml-to-native" |may be used to
convert
> the domU configuration to native if necessary.
>
> I am interested in knowing how you incorporated the stubdom-dm loader.
>
> The link above demonstrates Fullyvirtualized guest direct kernel
> boots, Fullyvirtualized guest BIOS boots, Paravirtualized guest direct
> kernel boots, and Paravirtualized guest bootloader with pygrub examples.
>
> Non of the examples feature the stubdom-dm loader.
>
> I would greatly appreciate it if you could post a complete and working
> stubdom HVM domU configuration.
>
Sorry, I just assumed libvirt was a non-starter. Hope this helps.

-Andrew



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Viau

2010-Mar-19 23:15 UTC

head link

[libvirt-users] virsh domxml-to-native xen-xm request

Hello,

I was looking at http://libvirt.org/drvxen.html

  

And realized that "virsh
domxml-to-native" may be used to convert the  libvirt xml formatted domU
configuration to native. 

The configuration is for stubdom-dm Xen guests.

Syntax appears to be virsh domxml-to-native xen-xm new_vm1.xml >
/etc/xen/new_vm1 but I get an error.

error: invalid argument in unsupported config type xen-xm


Can someone please post their output of the command: virsh domxml-to-native
xen-xm new_vm1.xml


The working libvirt XML formatted Xen DomU config (new_vm1.xml)
  




<domain type='xen'>

  <name>test</name>

  <os>

    <type>hvm</type>

    <loader>/usr/lib/xen/boot/hvmloader</loader>

    <boot dev='hd'/>

  </os>



  <memory>7340032</memory>

  <vcpu>7</vcpu>

  <on_poweroff>destroy</on_poweroff>

  <on_reboot>restart</on_reboot>

  <on_crash>restart</on_crash>

  <features>

     <pae/>

     <acpi/>

     <apic/>

  </features>

  <clock offset='utc'/>



  <devices>

    <emulator>/usr/lib/xen/bin/stubdom-dm</emulator>



    <interface type='bridge'>

      <source bridge='eth0'/>

      <mac address='00:50:56:0f:dd:02'/>

    </interface>



    <disk type='block' device='disk'>

      <source dev='/dev/sys/lv0'/>

      <target dev='hda'/>

    </disk>

    <disk type='block' device='disk'>

      <source dev='/dev/sys/lv1'/>

      <target dev='hdb'/>

    </disk>

    <disk type='block' device='disk'>

      <source dev='/dev/sys/lv2'/>

      <target dev='hdc'/>

    </disk>



<!-- stub domains don't have access to dom0's ptys, so this is not
possible

    <serial type='pty'>

    </serial>

-->



    <graphics type='vnc' autoport='yes'/>



  </devices>

</domain>



-M
 		 	   		  
_________________________________________________________________
IM on the go with Messenger on your phone
http://go.microsoft.com/?linkid=9712960
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20100319/d3670daa/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20100319/d3670daa/attachment.ksh>

Possibly Parallel Threads

Search for more apparently analagous threads

libvirt users - Mar 2010 - Error starting stubdom HVM on Xen-3.4.3-rc4-pre

[Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

RE: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre

[libvirt-users] virsh domxml-to-native xen-xm request

Possibly Parallel Threads