All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Unable to start xend on sles 9 boxes
Date: Thu, 17 Aug 2006 12:40:21 -0500	[thread overview]
Message-ID: <44E4AA05.2050601@us.ibm.com> (raw)

The last couple of days I have been unable to start xend on a couple of i386
boxes with SLES 9: (Note: A box with FC4 worked just fine.)


x235:~ # xend start
x235:~ # xm list
Error: Error connecting to xend: Connection refused.  Is xend running?
x235:~ #

changeset:   11134:ec03b24a2d83
tag:         tip
user:        shand@kneesaa.uk.xensource.com
date:        Tue Aug 15 13:53:55 2006 +0100
summary:     Fix VT after hvm changes.

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=742

# tail /var/log/xend.log
[2006-08-17 08:19:37 xend 10333] ERROR (XendCheckpoint:234) Save exit rc=0
[2006-08-17 08:19:37 xend.XendDomainInfo 10331] DEBUG 
(XendDomainInfo:1409) XendDomainInfo.destroyDomain(138)
[2006-08-17 08:19:38 xend.XendDomainInfo 10387] DEBUG 
(XendDomainInfo:186) XendDomainInfo.create(['vm', ['name', 
'03_save_bogusfile_neg-1155820778'], ['memory', 64], ['vcpus', 1], 
['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16.13-xen'], 
['ramdisk', 
'/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/ramdisk/initrd.img'], 
['root', '/dev/ram0']]]])
[2006-08-17 08:19:38 xend.XendDomainInfo 10387] DEBUG 
(XendDomainInfo:292) parseConfig: config is ['vm', ['name', 
'03_save_bogusfile_neg-1155820778'], ['memory', 64], ['vcpus', 1], 
['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16.13-xen'], 
['ramdisk', 
'/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/ramdisk/initrd.img'], 
['root', '/dev/ram0']]]]
[2006-08-17 08:19:38 xend.XendDomainInfo 10387] DEBUG 
(XendDomainInfo:391) parseConfig: result is {'uuid': None, 'on_crash': 
None, 'on_reboot': None, 'localtime': None, 'image': ['linux', 
['kernel', '/boot/vmlinuz-2.6.16.13-xen'], ['ramdisk', 
'/usr/local/autobench/var/tmp/xen/xen-unstable.hg/tools/xm-test/ramdisk/initrd.img'], 
['root', '/dev/ram0']], 'on_poweroff': None, 'bootloader_args': None, 
'cpus': None, 'name': '03_save_bogusfile_neg-1155820778', 'backend': [], 
'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 
'memory': 64, 'device': [], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2006-08-17 08:19:38 xend.XendDomainInfo 10387] DEBUG 
(XendDomainInfo:1219) XendDomainInfo.construct: None
[2006-08-17 08:19:38 xend.XendDomainInfo 10387] DEBUG 
(XendDomainInfo:1251) XendDomainInfo.initDomain: 139 1.0
[2006-08-17 08:19:38 xend 10387] DEBUG (balloon:127) Balloon: 144140 KiB 
free; need 65536; done.
[2006-08-17 08:19:38 xend 10387] INFO (image:134) buildDomain os=linux 
dom=139 vcpus=1
[2006-08-17 08:19:38 xend 10387] DEBUG (image:177) dom            = 139


# tail /var/log/xend-debug.log
    self.callHandlers(record)
  File "/usr/lib/python2.3/logging/__init__.py", line 1037, in callHandlers
    hdlr.handle(record)
  File "/usr/lib/python2.3/logging/__init__.py", line 592, in handle
    self.emit(record)
  File "/usr/lib/python2.3/logging/handlers.py", line 105, in emit
    self.doRollover()
  File "/usr/lib/python/xen/xend/XendLogging.py", line 60, in doRollover
    logging.handlers.RotatingFileHandler.doRollover()
TypeError: unbound method doRollover() must be called with 
RotatingFileHandler instance as first argument (got nothing instead)

-- 

Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
	
                          Euripides

             reply	other threads:[~2006-08-17 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 17:40 David F Barrera [this message]
2006-08-18  8:57 ` Unable to start xend on sles 9 boxes Ewan Mellor
2006-08-18 12:20   ` David F Barrera

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44E4AA05.2050601@us.ibm.com \
    --to=dfbp@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.