thr3ads.net - Xen users - Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree [May 2005]

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

Mike Wray

2005-May-16 20:29 UTC

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Ian Pratt wrote:>  
> Mike, please can you take a look at this.
> Thanks,
> Ian
> 
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Li Ge
> Sent: 16 May 2005 20:16
> To: xen-devel@lists.xensource.com
> Subject: [Xen-devel] Creating domain crashes xend with the latest
> xenunstable tree
> 
> I was able to build and boot Xen using May 16 unstable tree. But the
> xend crashes when I create new domain on Fedora Core 3:
See comments below. Will need more info to diagnose this.
> [root@bl3-2 ~]# xm create /images/xen-sarge/xen-sarge.config -c Using
> config file "/images/xen-sarge/xen-sarge.config".
> Traceback (most recent call last):
> File "/usr/sbin/xm", line 10, in ?
> main.main(sys.argv)
> File "/usr/lib/python/xen/xm/main.py", line 901, in main
> xm.main(args)
> File "/usr/lib/python/xen/xm/main.py", line 133, in main
> self.main_call(args)
> File "/usr/lib/python/xen/xm/main.py", line 151, in main_call
> p.main(args[1:])
> File "/usr/lib/python/xen/xm/main.py", line 286, in main
> create.main(args)
> File "/usr/lib/python/xen/xm/create.py", line 623, in main (dom,
> console) = make_domain(opts, config) File
> "/usr/lib/python/xen/xm/create.py", line 578, in make_domain
dominfo > server.xend_domain_create(config) File
> "/usr/lib/python/xen/xend/XendClient.py", line 192, in
> xend_domain_create {''op'' : ''create'',
File
> "/usr/lib/python/xen/xend/XendClient.py", line 141, in xendPost
return
> self.client.xendPost(url, data) File
> "/usr/lib/python/xen/xend/XendProtocol.py", line 80, in xendPost
return
> self.xendRequest(url, "POST", args) File
> "/usr/lib/python/xen/xend/XendProtocol.py", line 151, in
xendRequest
> resp = conn.getresponse() File "/usr/lib/python2.3/httplib.py",
line
> 778, in getresponse
> response.begin()
> File "/usr/lib/python2.3/httplib.py", line 273, in begin version,
> status, reason = self._read_status() File
> "/usr/lib/python2.3/httplib.py", line 237, in _read_status raise
> BadStatusLine(line) httplib.BadStatusLine
> [root@bl3-2 ~]# ps -ef|grep xend
> root 3833 1 0 13:33 ? 00:00:00 python /usr/sbin/xend start root 3834
> 3833 0 13:33 ? 00:00:00 python /usr/sbin/xend start root 3835 3834 0
> 13:33 ? 00:00:00 python /usr/sbin/xend start root 3836 3834 0 13:33 ?
> 00:00:00 python /usr/sbin/xend start root 4523 3834 0 13:35 ? 00:00:00
> python /usr/sbin/xend start root 4525 4478 0 13:35 ttyS0 00:00:00 grep
> xend
> [root@bl3-2 ~]# xm list
> (111, ''Connection refused'')
> Error: Error connecting to xend, is xend running?
> [root@bl3-2 ~]# xend start
> 4547 [DBG] XFRD>main>
> 4547 [DBG] XFRD>xfrd_main>
> 4547 [DBG] XFRD>xfrd_listen_socket>
> 4547 [DBG] XFRD>create_socket>
> 4547 [DBG] XFRD>create_socket> port=8002
> 4547 [DBG] XFRD>create_socket< err=0
> 4547 [DBG] XFRD>xfrd_listen_socket> listen...
> 4547 [DBG] XFRD>xfrd_listen_socket< err=0
> 4547 [DBG] XFRD>xfrd_select> socks: 3
> [xend] INFO (__init__:988) Xend Daemon started [xend] INFO
> (__init__:988) Virq 0 on port 3 [xend] INFO (__init__:988) Virq 1 on
> port 6 [xend] INFO (__init__:988) Virq 2 on port 5 [xend] INFO
> (__init__:988) Virq 3 on port 10 [xend] INFO (__init__:988) Virq 4 on
> port 11 vm_recreate> savedinfo= (domain (id 0) (name Domain-0) (memory
> 495)) info= {''vcpu_to_cpu'': [0, -1, -1, -1, -1, -1, -1,
-1, -1, -1, -1,
> -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1, -1], ''cpu_time'': 28740382934L,
> ''shutdown_reason'': 0, ''dying'': 0,
''dom'': 0, ''running'': 1,
''maxmem_kb'':
> -4096,
> ''paused'': 0, ''crashed'': 0,
''vcpus'': 1, ''shutdown'': 0,
''mem_kb'': 506952,
> ''cpumap'': [-1,
> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0} 

The stuff below here shows that xend found domain-1 in the list from xc,
but had no saved info for it. So showing 2 domains in the xm list is correct.
Something bad probably happened during domain create though.

Need to see the config used for the domain and the output from
/var/log/xend.log.
If the problem is reproducible then starting ''xend
trace_start''
and posting /var/log/xend.trace would also help.
> [xend] INFO (__init__:988) Creating
> entry for unknown domain: id=1 vm_recreate> savedinfo=
''None''
> info= {''vcpu_to_cpu'': [3, -1, -1, -1, -1, -1, -1, -1, -1,
-1, -1, -1,
> -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1], ''cpu_time'': 0L,
''shutdown_reason'': 0,
> ''dying'': 0, ''dom'': 1,
''running'': 0, ''maxmem_kb'': 268435456,
''paused'': 1,
               ^^^^^^^^^^
> ''crashed'': 0, ''vcpus'': 1,
''shutdown'': 0, ''mem_kb'': 262144,
''cpumap'':
> [-1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0} unix path>
/var/lib/xend/xend-socket network start bridge=xen-br0 netdev=eth1
> antispoof=no [xend] INFO (__init__:988) EVENT> xend.domain.create
> [''Domain-1'', ''1''] [xend] INFO
(__init__:988) EVENT> xend.start 0
> [root@bl3-2 ~]# xm list
> Name Id Mem(MB) CPU VCPU(s) State Time(s) Console Domain-0 0 495 0 1
> r---- 29.6
> Domain-1 1 256 3 1 --p-- 0.0
> 
> Another problem I see here is just after I restarted xend, it showed
> there were
> two domains (Domain-0 and Domain-1) in the list which should be only one
> (Domain-0).	
> 
> 
> Thanks,
> 
> Li Ge
> 
> Linux Technology Center, IBM
Mike

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

Li Ge

2005-May-16 21:53 UTC

head link

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Here are some more information :

1. Yes. The problem is reproducible. But the weird thing is if I start xend
using" xend trace_start", the problem goes away and I can get the new
domain created. I''ve tried both "xend start" and "xend
trace_start" a
couple of times. It always works with "xend trace_start" but not with
"xend
start".
2. The domain config file: (See attached file: xen-sarge.config)
3:  /var/log/xend.log file: (See attached file: xend.log)
4. The /var/log/xend.trace file is quite big (2+MB), so I am not putting it
here. If you still think it might help, I can send it to you.


Thanks,
Li Ge

Linux Technology Center, IBM




                                                                           
             Mike Wray                                                     
             <mike.wray@hp.com                                             
             >                                                          To 
             Sent by:                  Ian Pratt                           
             xen-devel-bounces         <m+Ian.Pratt@cl.cam.ac.uk>
             @lists.xensource.                                          cc 
             com                       Li Ge/Austin/IBM@IBMUS,             
                                       xen-devel@lists.xensource.com       
                                                                   Subject 
             05/16/2005 03:29          Re: FW: [Xen-devel] Creating domain 
             PM                        crashes xend with the latest        
                                       xenunstable tree                    
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Ian Pratt wrote:>
> Mike, please can you take a look at this.
> Thanks,
> Ian
>
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Li Ge
> Sent: 16 May 2005 20:16
> To: xen-devel@lists.xensource.com
> Subject: [Xen-devel] Creating domain crashes xend with the latest
> xenunstable tree
>
> I was able to build and boot Xen using May 16 unstable tree. But the
> xend crashes when I create new domain on Fedora Core 3:
See comments below. Will need more info to diagnose this.
> [root@bl3-2 ~]# xm create /images/xen-sarge/xen-sarge.config -c Using
> config file "/images/xen-sarge/xen-sarge.config".
> Traceback (most recent call last):
> File "/usr/sbin/xm", line 10, in ?
> main.main(sys.argv)
> File "/usr/lib/python/xen/xm/main.py", line 901, in main
> xm.main(args)
> File "/usr/lib/python/xen/xm/main.py", line 133, in main
> self.main_call(args)
> File "/usr/lib/python/xen/xm/main.py", line 151, in main_call
> p.main(args[1:])
> File "/usr/lib/python/xen/xm/main.py", line 286, in main
> create.main(args)
> File "/usr/lib/python/xen/xm/create.py", line 623, in main (dom,
> console) = make_domain(opts, config) File
> "/usr/lib/python/xen/xm/create.py", line 578, in make_domain
dominfo > server.xend_domain_create(config) File
> "/usr/lib/python/xen/xend/XendClient.py", line 192, in
> xend_domain_create {''op'' : ''create'',
File
> "/usr/lib/python/xen/xend/XendClient.py", line 141, in xendPost
return
> self.client.xendPost(url, data) File
> "/usr/lib/python/xen/xend/XendProtocol.py", line 80, in xendPost
return
> self.xendRequest(url, "POST", args) File
> "/usr/lib/python/xen/xend/XendProtocol.py", line 151, in
xendRequest
> resp = conn.getresponse() File "/usr/lib/python2.3/httplib.py",
line
> 778, in getresponse
> response.begin()
> File "/usr/lib/python2.3/httplib.py", line 273, in begin version,
> status, reason = self._read_status() File
> "/usr/lib/python2.3/httplib.py", line 237, in _read_status raise
> BadStatusLine(line) httplib.BadStatusLine
> [root@bl3-2 ~]# ps -ef|grep xend
> root 3833 1 0 13:33 ? 00:00:00 python /usr/sbin/xend start root 3834
> 3833 0 13:33 ? 00:00:00 python /usr/sbin/xend start root 3835 3834 0
> 13:33 ? 00:00:00 python /usr/sbin/xend start root 3836 3834 0 13:33 ?
> 00:00:00 python /usr/sbin/xend start root 4523 3834 0 13:35 ? 00:00:00
> python /usr/sbin/xend start root 4525 4478 0 13:35 ttyS0 00:00:00 grep
> xend
> [root@bl3-2 ~]# xm list
> (111, ''Connection refused'')
> Error: Error connecting to xend, is xend running?
> [root@bl3-2 ~]# xend start
> 4547 [DBG] XFRD>main>
> 4547 [DBG] XFRD>xfrd_main>
> 4547 [DBG] XFRD>xfrd_listen_socket>
> 4547 [DBG] XFRD>create_socket>
> 4547 [DBG] XFRD>create_socket> port=8002
> 4547 [DBG] XFRD>create_socket< err=0
> 4547 [DBG] XFRD>xfrd_listen_socket> listen...
> 4547 [DBG] XFRD>xfrd_listen_socket< err=0
> 4547 [DBG] XFRD>xfrd_select> socks: 3
> [xend] INFO (__init__:988) Xend Daemon started [xend] INFO
> (__init__:988) Virq 0 on port 3 [xend] INFO (__init__:988) Virq 1 on
> port 6 [xend] INFO (__init__:988) Virq 2 on port 5 [xend] INFO
> (__init__:988) Virq 3 on port 10 [xend] INFO (__init__:988) Virq 4 on
> port 11 vm_recreate> savedinfo= (domain (id 0) (name Domain-0) (memory
> 495)) info= {''vcpu_to_cpu'': [0, -1, -1, -1, -1, -1, -1,
-1, -1, -1, -1,
> -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1, -1], ''cpu_time'': 28740382934L,
> ''shutdown_reason'': 0, ''dying'': 0,
''dom'': 0, ''running'': 1,
''maxmem_kb'':
> -4096,
> ''paused'': 0, ''crashed'': 0,
''vcpus'': 1, ''shutdown'': 0,
''mem_kb'': 506952,
> ''cpumap'': [-1,
> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0}

The stuff below here shows that xend found domain-1 in the list from xc,
but had no saved info for it. So showing 2 domains in the xm list is
correct.
Something bad probably happened during domain create though.

Need to see the config used for the domain and the output from
/var/log/xend.log.
If the problem is reproducible then starting ''xend
trace_start''
and posting /var/log/xend.trace would also help.
> [xend] INFO (__init__:988) Creating
> entry for unknown domain: id=1 vm_recreate> savedinfo=
''None''
> info= {''vcpu_to_cpu'': [3, -1, -1, -1, -1, -1, -1, -1, -1,
-1, -1, -1,
> -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
> -1, -1], ''cpu_time'': 0L,
''shutdown_reason'': 0,
> ''dying'': 0, ''dom'': 1,
''running'': 0, ''maxmem_kb'': 268435456,
''paused'': 1,
               ^^^^^^^^^^
> ''crashed'': 0, ''vcpus'': 1,
''shutdown'': 0, ''mem_kb'': 262144,
''cpumap'':
> [-1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0], ''blocked'': 0} unix path>
/var/lib/xend/xend-socket network start bridge=xen-br0 netdev=eth1
> antispoof=no [xend] INFO (__init__:988) EVENT> xend.domain.create
> [''Domain-1'', ''1''] [xend] INFO
(__init__:988) EVENT> xend.start 0
> [root@bl3-2 ~]# xm list
> Name Id Mem(MB) CPU VCPU(s) State Time(s) Console Domain-0 0 495 0 1
> r---- 29.6
> Domain-1 1 256 3 1 --p-- 0.0
>
> Another problem I see here is just after I restarted xend, it showed
> there were
> two domains (Domain-0 and Domain-1) in the list which should be only one
> (Domain-0).
>
>
> Thanks,
>
> Li Ge
>
> Linux Technology Center, IBM
Mike

_______________________________________________
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

Mike Wray

2005-May-17 09:05 UTC

head link

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Li Ge wrote:> Here are some more information :
> 
> 1. Yes. The problem is reproducible. But the weird thing is if I start 
> xend using" xend trace_start", the problem goes away and I can
get the
> new domain created. I''ve tried both "xend start" and
"xend trace_start"
> a couple of times. It always works with "xend trace_start" but
not with
> "xend start".
> 2. The domain config file: /(See attached file: xen-sarge.config)/
> 3: /var/log/xend.log file: /(See attached file: xend.log)/
> 4. The /var/log/xend.trace file is quite big (2+MB), so I am not putting 
> it here. If you still think it might help, I can send it to you.
The xend.log appears to be of a restarted xend.
Is it the log including the initial domain create?

Could you send the xend.trace direct to me?
Don''t copy the list as it''s so big.

Thanks,

Mike

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

Cherie Cheung

2005-May-19 00:51 UTC

head link

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Hi,

I am new to Xen. I also got problem when creating domain in Xen
3.0(unstable version)

I got the following errors:

Using config file "/etc/xen/vcluster.py".
[xend] DEBUG (XendDomainInfo:696) init_domain> Created domain=9
name=vm3 memory=131072
[xend] DEBUG (XendDomainInfo:1117) creating linux domain with cmdline:
 ip=172.19.222.202:1.2.3.4:172.19.222.250:255.255.255.0:vm3:eth0:off
root=/dev/sda1 ro
[xend] WARNING (XendDomainInfo:725) building dom with 1 vcpus
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c0338884
 Init. ramdisk: c0339000->c0442400
 Phys-Mach map: c0443000->c0463000
 Page tables:   c0463000->c0466000
 Start info:    c0466000->c0467000
 Boot stack:    c0467000->c0468000
 TOTAL:         c0000000->c0800000
 ENTRY ADDRESS: c0100000
 VCPUS:         1
[xend] WARNING (XendDomainInfo:1062) Unknown config field memmap
[xend] WARNING (XendDomainInfo:1062) Unknown config field device_model
[xend] WARNING (XendDomainInfo:1062) Unknown config field device_config
[xend] INFO (console:100) Created console id=0 domain=9 port=9609
[xend] INFO (XendRoot:122) EVENT> xend.domain.create
[''vm3'', ''9'']
[xend] INFO (XendRoot:122) EVENT> xend.console.create [0, 9, 9609]
Domain construction error: global name ''log'' is not defined
Traceback (most recent call last):
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 513, in
construct
    self.configure()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1003, in
configure
    self.create_devices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 795, in
create_devices
    self.create_configured_devices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 784, in
create_configured_devices
    self.createDevice(ctrl_type, dev_config, recreate=recreate)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 362, in
createDevice
    return ctrl.createDevice(devconfig, recreate=self.recreate)
  File "/usr/lib/python/xen/xend/server/controller.py", line 236, in
createDevice
    dev.attach(recreate=recreate, change=change)
  File "/usr/lib/python/xen/xend/server/blkif.py", line 219, in attach
    self.setNode(node)
  File "/usr/lib/python/xen/xend/server/blkif.py", line 254, in
setNode
    segment = blkif.blkdev_segment(node)
  File "/usr/lib/python/xen/util/blkif.py", line 52, in blkdev_segment
    n = blkdev_name_to_number(name)
  File "/usr/lib/python/xen/util/blkif.py", line 24, in
blkdev_name_to_number
    log.debug("exception looking up device number for %s: %s", name,
ex)
NameError: global name ''log'' is not defined
ConsoleController>destroyController>
<xen.xend.server.console.ConsoleController instance at 0xb76d1e8c>
False
ConsoleDev>destroy> <xen.xend.server.console.ConsoleDev instance at
0xb76d1f6c> False
[xend] DEBUG (blkif:420) Destroying blkif domain=9
[xend] DEBUG (blkif:309) Destroying vbd domain=9 id=0
op_create> Exception creating domain:
Traceback (most recent call last):
  File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 63, in
op_create
    dominfo = self.xd.domain_create(config)
  File "/usr/lib/python/xen/xend/XendDomain.py", line 401, in
domain_create
    dominfo = XendDomainInfo.vm_create(config)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 184, in
vm_create
    vm.construct(config)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 513, in
construct
    self.configure()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1003, in
configure
    self.create_devices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 795, in
create_devices
    self.create_configured_devices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 784, in
create_configured_devices
    self.createDevice(ctrl_type, dev_config, recreate=recreate)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 362, in
createDevice
    return ctrl.createDevice(devconfig, recreate=self.recreate)
  File "/usr/lib/python/xen/xend/server/controller.py", line 236, in
createDevice
    dev.attach(recreate=recreate, change=change)
  File "/usr/lib/python/xen/xend/server/blkif.py", line 219, in attach
    self.setNode(node)
  File "/usr/lib/python/xen/xend/server/blkif.py", line 254, in
setNode
    segment = blkif.blkdev_segment(node)
  File "/usr/lib/python/xen/util/blkif.py", line 52, in blkdev_segment
    n = blkdev_name_to_number(name)
  File "/usr/lib/python/xen/util/blkif.py", line 24, in
blkdev_name_to_number
    log.debug("exception looking up device number for %s: %s", name,
ex)
NameError: global name ''log'' is not defined
Error: Error creating domain: global name ''log'' is not defined
[xend] INFO (XendRoot:122) EVENT> xend.domain.died [''vm3'',
''9'']

Namely, the errors are
Unknown config field memmap
Unknown config field device_model
Unknown config field device_config
[xend] INFO (XendRoot:122) EVENT> xend.console.create [0, 9, 9609]
Domain construction error: global name ''log'' is not defined

Can anyone help me please?

Thanks.

Cherie

On 5/17/05, Mike Wray <mike.wray@hp.com> wrote:> Li Ge wrote:
> > Here are some more information :
> >
> > 1. Yes. The problem is reproducible. But the weird thing is if I start
> > xend using" xend trace_start", the problem goes away and I
can get the
> > new domain created. I''ve tried both "xend start"
and "xend trace_start"
> > a couple of times. It always works with "xend trace_start"
but not with
> > "xend start".
> > 2. The domain config file: /(See attached file: xen-sarge.config)/
> > 3: /var/log/xend.log file: /(See attached file: xend.log)/
> > 4. The /var/log/xend.trace file is quite big (2+MB), so I am not
putting
> > it here. If you still think it might help, I can send it to you.
> 
> The xend.log appears to be of a restarted xend.
> Is it the log including the initial domain create?
> 
> Could you send the xend.trace direct to me?
> Don''t copy the list as it''s so big.
> 
> Thanks,
> 
> Mike
> 
> _______________________________________________
> 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

Cherie Cheung

2005-May-20 10:06 UTC

head link

[Xen-users] Creating domain crashes xend with the latest xenunstable tree

Hi,

I am new to Xen. I also got problem when creating domain in Xen
3.0(unstable version)

I got the following errors:

Using config file "/etc/xen/vcluster.py".
[xend] DEBUG (XendDomainInfo:696) init_domain> Created domain=9
name=vm3 memory=131072
[xend] DEBUG (XendDomainInfo:1117) creating linux domain with cmdline:
 ip=172.19.222.202:1.2.3.4:172.19.222.250:255.255.255.0:vm3:eth0:off
root=/dev/sda1 ro
[xend] WARNING (XendDomainInfo:725) building dom with 1 vcpus
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c0338884
 Init. ramdisk: c0339000->c0442400
 Phys-Mach map: c0443000->c0463000
 Page tables:   c0463000->c0466000
 Start info:    c0466000->c0467000
 Boot stack:    c0467000->c0468000
 TOTAL:         c0000000->c0800000
 ENTRY ADDRESS: c0100000
 VCPUS:         1
[xend] WARNING (XendDomainInfo:1062) Unknown config field memmap
[xend] WARNING (XendDomainInfo:1062) Unknown config field device_model
[xend] WARNING (XendDomainInfo:1062) Unknown config field device_config
[xend] INFO (console:100) Created console id=0 domain=9 port=9609
[xend] INFO (XendRoot:122) EVENT> xend.domain.create
[''vm3'', ''9'']
[xend] INFO (XendRoot:122) EVENT> xend.console.create [0, 9, 9609]
Domain construction error: global name ''log'' is not defined
Traceback (most recent call last):
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 513, in
construct
   self.configure()
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1003, in
configure
   self.create_devices()
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 795, in
create_devices
   self.create_configured_devices()
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 784, in
create_configured_devices
   self.createDevice(ctrl_type, dev_config, recreate=recreate)
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 362, in
createDevice
   return ctrl.createDevice(devconfig, recreate=self.recreate)
 File "/usr/lib/python/xen/xend/server/controller.py", line 236, in
createDevice
   dev.attach(recreate=recreate, change=change)
 File "/usr/lib/python/xen/xend/server/blkif.py", line 219, in attach
   self.setNode(node)
 File "/usr/lib/python/xen/xend/server/blkif.py", line 254, in setNode
   segment = blkif.blkdev_segment(node)
 File "/usr/lib/python/xen/util/blkif.py", line 52, in blkdev_segment
   n = blkdev_name_to_number(name)
 File "/usr/lib/python/xen/util/blkif.py", line 24, in
blkdev_name_to_number
   log.debug("exception looking up device number for %s: %s", name,
ex)
NameError: global name ''log'' is not defined
ConsoleController>destroyController>
<xen.xend.server.console.ConsoleController instance at 0xb76d1e8c>
False
ConsoleDev>destroy> <xen.xend.server.console.ConsoleDev instance at
0xb76d1f6c> False
[xend] DEBUG (blkif:420) Destroying blkif domain=9
[xend] DEBUG (blkif:309) Destroying vbd domain=9 id=0
op_create> Exception creating domain:
Traceback (most recent call last):
 File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 63, in
op_create
   dominfo = self.xd.domain_create(config)
 File "/usr/lib/python/xen/xend/XendDomain.py", line 401, in
domain_create
   dominfo = XendDomainInfo.vm_create(config)
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 184, in
vm_create
   vm.construct(config)
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 513, in
construct
   self.configure()
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1003, in
configure
   self.create_devices()
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 795, in
create_devices
   self.create_configured_devices()
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 784, in
create_configured_devices
   self.createDevice(ctrl_type, dev_config, recreate=recreate)
 File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 362, in
createDevice
   return ctrl.createDevice(devconfig, recreate=self.recreate)
 File "/usr/lib/python/xen/xend/server/controller.py", line 236, in
createDevice
   dev.attach(recreate=recreate, change=change)
 File "/usr/lib/python/xen/xend/server/blkif.py", line 219, in attach
   self.setNode(node)
 File "/usr/lib/python/xen/xend/server/blkif.py", line 254, in setNode
   segment = blkif.blkdev_segment(node)
 File "/usr/lib/python/xen/util/blkif.py", line 52, in blkdev_segment
   n = blkdev_name_to_number(name)
 File "/usr/lib/python/xen/util/blkif.py", line 24, in
blkdev_name_to_number
   log.debug("exception looking up device number for %s: %s", name,
ex)
NameError: global name ''log'' is not defined
Error: Error creating domain: global name ''log'' is not defined
[xend] INFO (XendRoot:122) EVENT> xend.domain.died [''vm3'',
''9'']

Namely, the errors are
Unknown config field memmap
Unknown config field device_model
Unknown config field device_config
[xend] INFO (XendRoot:122) EVENT> xend.console.create [0, 9, 9609]
Domain construction error: global name ''log'' is not defined

Can anyone help me please?

Thanks.

Cherie

On 5/17/05, Mike Wray <mike.wray@hp.com> wrote:> Li Ge wrote:
> > Here are some more information :
> >
> > 1. Yes. The problem is reproducible. But the weird thing is if I start
> > xend using" xend trace_start", the problem goes away and I
can get the
> > new domain created. I''ve tried both "xend start"
and "xend trace_start"
> > a couple of times. It always works with "xend trace_start"
but not with
> > "xend start".
> > 2. The domain config file: /(See attached file: xen-sarge.config)/
> > 3: /var/log/xend.log file: /(See attached file: xend.log)/
> > 4. The /var/log/xend.trace file is quite big (2+MB), so I am not
putting
> > it here. If you still think it might help, I can send it to you.
>
> The xend.log appears to be of a restarted xend.
> Is it the log including the initial domain create?
>
> Could you send the xend.trace direct to me?
> Don''t copy the list as it''s so big.
>
> Thanks,
>
> Mike
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - May 2005 - Re: FW: Creating domain crashes xend with the latest xenunstable tree

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

Re: FW: [Xen-devel] Creating domain crashes xend with the latest xenunstable tree

[Xen-users] Creating domain crashes xend with the latest xenunstable tree