Hi Keir,
Sorry. I didn't test the patch on a server to which XenAPI mode was
invalid. I will send a new patch.
Best regards,
Kan
Fri, 18 Sep 2009 14:43:55 +0100, Keir Fraser wrote:
>Applied as c/s 20221, but it produces the following backtrace, so I reverted
>it:
>Traceback (most recent call last):
> File "/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
>165, in save
> dominfo.destroy()
> File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
>2855, in destroy
> XendDomain.instance().remove_domain(self)
> File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 468,
>in remove_domain
> self._remove_domain(info, domid)
> File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 489,
>in _remove_domain
> info.unlink_xapi_instances()
> File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
>4054, in unlink_xapi_instances
> vdi = XendNode.instance().get_vdi_by_uuid(dev_info['VDI'])
>KeyError: 'VDI'
>
> -- Keir
>
>
>On 17/09/2009 08:32, "Masaki Kanno" <kanno.masaki@xxxxxxxxxxxxxx> wrote:
>
>> Hi,
>>
>> When VBD instances are destroyed by xm delete command, VDI instances
>> keep linking to the VBD instances unilaterally.
>> This patch eliminates the unilateral linking.
>>
>> Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
>>
>> Best regards,
>> Kan
>>
>
>
>
>_______________________________________________
>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
|