RE: [Xen-devel] can't start domains

[James Harper <JamesH@xxxxxxxxxxxxxxxx>]

make uninstall does this:

        cp -a /etc/xen /etc/xen.old && rm -rf /etc/xen
        rm -rf "/usr/lib/python2.2/site-packages/xen* /usr/lib/libxc* /usr/lib/python2.2/site-packages/Xc*"

which might make more sense if i wasn't using python 2.3. also, there's something funny going on with /usr/lib/libxc, I get:

libxc.so
libxc.so.1.3
libxc.so.1.3.0

I think the first two should be symlinks to the third?

 

but that's irrelevant to my situation. you'll see in the output below, the error occurs in /usr/lib/python2.3/site-packages/xen/xend/server/blkif.py:228. At this point, backend.handle = 0. is that right?

 

i'll recompile with the debug flag set shortly and send the output in the morning (AEST)

 

here's the output:

 

config: (vm (name gaia2) (memory 128) (cpu 3) (image (linux (kernel /boot/vmlinuz-2.6.7-xenU) (root '/dev/sda1 ro') (args ' 4 VMID=3 '))) (device (vbd (uname phy:ida/c0d0p5) (dev sda1) (mode w))))
[xend] DEBUG (XendDomainInfo:726) init_domain> Created domain=4 name=gaia2 memory=128
[xend] INFO (console:93) Created console id=17 domain=4 port=9604
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c02fbf44
 Init. ramdisk: c02fc000->c02fc000
 Phys-Mach map: c02fc000->c031c000
 Page tables:   c031c000->c031e000
 Start info:    c031e000->c031f000
 Boot stack:    c031f000->c0320000
 TOTAL:         c0100000->c0400000
 ENTRY ADDRESS: c0100000
[xend] DEBUG (blkif:52) Connecting blkif <BlkifBackendController 4 0>
CtrlMsgRcvr>writeRequest> message: type= blkif_be_create_t 1:0 id=1
payload= {'status': 1852731203, 'blkif_handle': 0, 'domid': 4}
EVENT> xend.console.create [17, 4, 9604]
responseReceived> message: type= blkif_be_create_t 1:0 id=1
payload= {'status': 0, 'blkif_handle': 0, 'domid': 4}
respond_be_create> {'status': 0, 'blkif_handle': 0, 'domid': 4}
[xend] DEBUG (XendDomainInfo:1083) Creating vbd dom=4 uname=phy:ida/c0d0p5 dev=sda1
[xend] DEBUG (blkif:52) Connecting blkif <BlkifBackendController 4 0>
Unhandled error in Deferred:
Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 205, in addCallbacks
    self._runCallbacks()
  File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 252, in callback
    self._startRunCallbacks(result)
  File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 313, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py", line 228, in send_be_vbd_create
    { 'domid'        : self.controller.dom,
  File "/usr/lib/python2.3/site-packages/xen/xend/server/messages.py", line 217, in packMsg
    msg = xu.message(major, minor, msgid, args)
exceptions.TypeError: payload contains bad items
[xend] DEBUG (XendDomainInfo:680) Destroying vbds for domain 4
[xend] DEBUG (blkif:364) Destroying blkif domain=4
op_create> Deferred Exception creating domain: [Failure instance: Traceback: exceptions.TypeError, int argument required
/usr/lib/python2.3/site-packages/twisted/internet/defer.py:338:_runCallbacks
/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py:512:cberr
/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py:619:destroy
/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py:647:cleanup
/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py:658:release_devices
/usr/lib/python2.3/site-packages/xen/xend/XendDomainInfo.py:681:release_vbds
/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py:365:destroy
/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py:372:destroyDevices
/usr/lib/python2.3/site-packages/xen/xend/server/blkif.py:209:destroy
/usr/lib/python2.3/logging/__init__.py:879:debug
/usr/lib/python2.3/logging/__init__.py:994:_log
/usr/lib/python2.3/logging/__init__.py:1004:handle
/usr/lib/python2.3/logging/__init__.py:1037:callHandlers
/usr/lib/python2.3/logging/__init__.py:592:handle
/usr/lib/python2.3/logging/handlers.py:102:emit
/usr/lib/python2.3/logging/__init__.py:567:format
/usr/lib/python2.3/logging/__init__.py:362:format
/usr/lib/python2.3/logging/__init__.py:233:getMessage
]

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

---

From: Ian Pratt
Sent: Sun 22/08/2004 8:33 PM
To: James Harper
Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxxxx; mike.wray@xxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] can't start domains

 
> If I change the disk line to use my swap partition instead (the only other partition I can usefully point to), it still breaks in the same way as when I was using /dev/vg00/gaia2

If I understand correctly, you're saying it breaks in the same
way (with a similar python traceback) even if you have the
simplest possible setup of a single VBD exporting a physical
partition.

This means we can ignore the LVM issue.

Can you post the traceback for this simple case, and also the
debug output from dom0 having enabled the debug prints in blkback/common.h

> So for some reason, I have a problem using any block device from xen!!!

I think we'd have noticed this if it were a general problem ;-)

Are you fully up to date with your repo? There have been a few
duff ones in the last couple of weeks, but things seem stable
now.  We came very close to putting a "Xen 2.0-rc1" designation on
the tree Friday afternoon, but thought we leave a few tests
running over the weekend.

I just noticed that 2.4.27 and 2.6.8 have just come out, so I
guess we should upgrade before declaring the 2.0 release
candidate. Oh well...

> One mistake I made earlier was having some old 1.2 files lying around from when I tested this server a while ago. I think I have cleaned them up, but apart from the possibility of 2.6 causing a problem, that's my most likely cause. Where should I look for stale files?

'make uninstall' is fairly brutal but should clear things out.

Ian