I test stubdom in xen-3.3.1, when I start it, just see the message bellow using "xm li" . It seems stubdom haven''t start. Name ID Mem VCPUs State Time(s) Domain-0 0 964 2 r----- 34.8 hvmachine 1 1024 1 ------ 0.0 the two config files : #hvmachine kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 256 name = "hvmachine" vcpus=2 vif = [ ''type=ioemu, bridge=eth0'' ] device_model = ''/usr/lib/xen/bin/stubdom-dm'' boot="cd" sdl=0 opengl=0 vnc=1 vnclisten="172.30.206.1" stdvga=0 ------------------------------------------------------------------------- #hvmachine-dm kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz" vif = [ ''ip=172.30.206.1'', ''bridge=eth0,mac=00:16:3e:21:a2:94'' ] disk = [ ''file:/home/images/opensuse11-2/disk0,hda,w'' ] what''s wrong I make? best regards, -- James best regards, -- James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
James I think you will have to either give boot options as ''c'' booting from disk or ''d'' booting from cdrom and not both, unless this is a new requirement for stubdom where you give both the options together. Bhaskar. -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of James Song Sent: Thursday, September 18, 2008 12:42 PM To: xen-devel@lists.xensource.com Subject: [Xen-devel] start stubdom issue I test stubdom in xen-3.3.1, when I start it, just see the message bellow using "xm li" . It seems stubdom haven''t start. Name ID Mem VCPUs State Time(s) Domain-0 0 964 2 r----- 34.8 hvmachine 1 1024 1 ------ 0.0 the two config files : #hvmachine kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 256 name = "hvmachine" vcpus=2 vif = [ ''type=ioemu, bridge=eth0'' ] device_model = ''/usr/lib/xen/bin/stubdom-dm'' boot="cd" sdl=0 opengl=0 vnc=1 vnclisten="172.30.206.1" stdvga=0 ------------------------------------------------------------------------- #hvmachine-dm kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz" vif = [ ''ip=172.30.206.1'', ''bridge=eth0,mac=00:16:3e:21:a2:94'' ] disk = [ ''file:/home/images/opensuse11-2/disk0,hda,w'' ] what''s wrong I make? best regards, -- James best regards, -- James _______________________________________________ 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
>-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of James Song >Sent: Thursday, September 18, 2008 3:12 PM >To: xen-devel@lists.xensource.com >Subject: [Xen-devel] start stubdom issue > >I test stubdom in xen-3.3.1, when I start it, just see the >message bellow using "xm li" . It seems stubdom haven''t start. > >Name ID Mem VCPUs > State Time(s) >Domain-0 0 964 2 >r----- 34.8 >hvmachine 1 1024 1 >------ 0.0 > > the two config files : >#hvmachine >kernel = "/usr/lib/xen/boot/hvmloader" >builder=''hvm'' >memory = 256 >name = "hvmachine" >vcpus=2 >vif = [ ''type=ioemu, bridge=eth0'' ]make sure that the bridged network is setup, otherwise, the stubdom will fail to acquire the tap driver, and then it aborts.>device_model = ''/usr/lib/xen/bin/stubdom-dm'' >boot="cd" >sdl=0 >opengl=0 >vnc=1 >vnclisten="172.30.206.1" >stdvga=0 >--------------------------------------------------------------- >---------- > > >#hvmachine-dm >kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz" >vif = [ ''ip=172.30.206.1'', ''bridge=eth0,mac=00:16:3e:21:a2:94'' ] >disk = [ ''file:/home/images/opensuse11-2/disk0,hda,w'' ] > > > >what''s wrong I make? > > >best regards, >-- James > >best regards, >-- James > >_______________________________________________ >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