çåï RE: çåï RE: [Xen-devel] start stubdom issue

["James Song" <jsong@xxxxxxxxxx>]

Hi all
Yes , It seems that I can boot stubdom with that configure file after I copy 
the x.dm file to /etc/xen...  but I met an error wite message :

Path changed backend/vfs/exports/requests/10/0/frontend
Handling connection from dom=10, for export=0
Frontend found at: /local/domain/10/device/vfs/0 (gref=1789, evtchn=5)
Our own dom_id=0
ERROR Internal error: Could not open grant table interface (22 = Invalid 
argument)
fs-backend: fs-backend.c:239: handle_connection: Assertion `mount->gnth != -1' 
failed.

thank you very much



best regards,
-- James
>>> "Lu, Guanqun" <guanqun.lu@xxxxxxxxx> 08å09æ18æ äå 17:00 >>>
 

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Song
>Sent: Thursday, September 18, 2008 4:53 PM
>To: xen-devel@xxxxxxxxxxxxxxxxxxx; Bhaskar.Jayaraman@xxxxxxx
>Subject: çåï RE: [Xen-devel] start stubdom issue
>
>yes, I have change "boot=c", but stubdom still not started. I 
>see xend-debug.log, finding that "Error: Unable to open config 
>file: hvmachine-dm".  That is in file "tools/python/xen/xm/opts.py "

the hvmachine config can be put anywhere, but your corresponding
hvmachine-dm config should be put in /etc/xen/, otherwise, the above
error occurs.

That's the problem i once met with. And hope it helps.

>      def load_defconfig(self, help=0):
>        """Load a defconfig script. Assumes these options set:
>        'path'    search path
>        'defconfig' script name
>        """
>        for x in [ '' ] + self.vals.path.split(':'):
>            if x:
>                p = os.path.join(x, self.vals.defconfig)
>            else:
>                p = self.vals.defconfig
>            if not p.startswith('/'):
>                p = os.path.join(os.path.curdir, p)
>            if os.path.exists(p):
>                self.info('Using config file "%s".' % p)
>
>                f = open(p)
>                is_xml = (f.read(1) == '<')
>                f.close()
>
>                if is_xml:
>                    raise XMLFileError(p)
>
>                self.load(p, help)
>                break
>        else:
>            raise OptionError('Unable to open config file: %s' % \
>                              self.vals.defconfig,
>                              self.use)
>
>
>best regards,
>-- James
>>>> "Jayaraman, Bhaskar" <Bhaskar.Jayaraman@xxxxxxx> 08å09æ18æ 
>äå 16:20 >>>
>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@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Song
>Sent: Thursday, September 18, 2008 12:42 PM
>To: xen-devel@xxxxxxxxxxxxxxxxxxx
>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
>
>___________>http://lists.xensource.com/xen-devel
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel
>


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