From: Jim Fehlig <jfehlig@novell.com>
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix xm block/network-detach command (take2)
Date: Fri, 10 Aug 2007 16:08:23 -0600 [thread overview]
Message-ID: <46BCE1D7.7050606@novell.com> (raw)
In-Reply-To: <46BB61A3.7010903@novell.com> 29C7DB2CBD08C6kanno.masaki@jp.fujitsu.com
Masaki Kanno wrote:
> Hi Jim,
>
> Thanks for your tests.
>
>
>> I tested your patch briefly on c/s 15672.
>>
> <snip>
>
>> The device was unplugged but its config not removed. From xend.log:
>>
>> File "/usr/lib64/python2.4/xen/xend/XendDomainInfo.py", line 615, in
>> destroyDevice
>> self.info['%s_refs' % deviceClass].remove(dev_uuid)
>> KeyError: 'tap_refs'
>>
>> I think refs for the various disk types all fall under 'vbd_refs'.
>>
>
> I tested blktap with the same way as your operation. But I did not
> encounter the command error as follows.
> But your thinking is right, so I wrote a small patch to remove the
> error message. Could you test the patch again?
>
Looks good with your additional patch. Thanks.
<snip>
>> The behavior is fine (i.e. the disk is still attached and remains in
>> stored config) but the error message is misleading. xvbd is connected,
>> its just the front-end won't let go AFAIK.
>>
>
> I'd like to improve the error message. Could you give me thinking
> time about 2 weeks?
>
Sure. I just noticed it while testing but spent no time investigating.
Regards,
Jim
next prev parent reply other threads:[~2007-08-10 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 18:49 [PATCH] Fix xm block/network-detach command (take2) Jim Fehlig
2007-08-10 8:59 ` Masaki Kanno
2007-08-17 8:25 ` Masaki Kanno
2007-08-10 22:08 ` Jim Fehlig [this message]
2007-08-17 8:24 ` Masaki Kanno
-- strict thread matches above, loose matches on Subject: below --
2007-08-09 13:12 Masaki Kanno
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=46BCE1D7.7050606@novell.com \
--to=jfehlig@novell.com \
--cc=kanno.masaki@jp.fujitsu.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.