WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1124] New: XenAPI shutdown won't delete VM

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1124] New: XenAPI shutdown won't delete VM
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 9 Dec 2007 08:19:35 -0800
Delivery-date: Sun, 09 Dec 2007 08:20:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1124

           Summary: XenAPI shutdown won't delete VM
           Product: Xen
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: skinkie@xxxxxxxxx


An XenAPI shutdown won't remove the VM and leaves it in an unknown state.

xen01 external # xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  7803     8     r-----
54.6
klant1_gentoo                                2   256     1     ------
6.4

This causes the xend daemon to generate an error:

2007-12-09 07:31:00 4803] ERROR (__init__:1094) Internal error handling
VM.get_record
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/xen/util/xmlrpclib2.py", line
131, in _marshaled_dispatch
    response = self._dispatch(method, params)
  File "/usr/lib64/python2.5/SimpleXMLRPCServer.py", line 415, in
_dispatch
    return func(*params)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendAPI.py", line 219,
in f
    return func(self, *args, **kwargs)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendAPI.py", line 254,
in check_session
    return func(self, session, *args, **kwargs)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendAPI.py", line 310,
in <lambda>
    'VM', func, *args, **kwargs)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendAPI.py", line 266,
in _check_ref
    return func(api, session, ref, *args, **kwargs)
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendAPI.py", line
1633, in VM_get_record
    'VCPUs_params': xeninfo.get_vcpus_params(),
  File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line 2261, in get_vcpus_params
    retval = xc.sched_credit_domain_get(self.getDomid())
Error: (3, 'No such process')


It can only be fixed if on the local machine xm delete [vm] is issued.

XenTools 3.1.2


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>