From: tgh <tianguanhua@ncic.ac.cn>
To: Kasai Takanori <kasai.takanori@jp.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: [PATCH] fix free of event channel in blkfront
Date: Thu, 01 Feb 2007 10:56:44 +0800 [thread overview]
Message-ID: <45C156EC.7020400@ncic.ac.cn> (raw)
In-Reply-To: <071e01c733b6$0845e010$dab2220a@VF03007L>
Hi
I am using the xen-3.0.3 on paravirtualVM
and I try to use xm block-attach dom6 /vm1/tp.img sda2 w
It seems to be ok, no error ,
but in the dom6 there is no sda2
and xm block-detach dom6 2050,it does not work
and xm block-list dom6 as follows ,
[root@= dev]# xm block-list dom6
Vdev BE handle state evt-ch ring-ref BE-path
2049 0 0 4 7 8 /local/domain/0/backend/vbd/127/2049
2050 0 0 3 8 665 /local/domain/0/backend/vbd/127/2050
I am confused about the function of these commands and how to use these
commands correctly
could you give me a help
Thanks in advance
Kasai Takanori 写道:
> Hi Steven,
>
>>>> We tested the xm block-attach/detach command.
>>>> It repeats block-attach/detach command for DomU and pv-on-hvm on
>>>> HVM Domain.
>>>> (block-attach -> block-detach -> block-attach -> block-detach -> ...)
>>>>
>>>> The block-attach command failed when repeating 256 times.
>>>
>>> I can't reproduce this - just tested 500 or so attach/detach pairs in
>>> a tight loop and worked for me. However I was using a regular domU -
>>> is it pv-on-hvm only? Can you give a more detailed repro case (or a
>>> script)?
>>
>> We tested only pv-on-hvm.
>> The script used when testing is appended.
>
> Sorry, the appended script was for network.
> It tested in the following scripts.
>
> -------------------------------------------------
> #!/bin/sh
> DomainID=25
> DevID=8448
> Count=0
>
> while :
> do
> echo "##### block-attach ##### $Count"
> xm block-attach $DomainID phy:/dev/sdc1 hde w
> sleep 1
> xm block-list $DomainID
> sleep 1
> echo "##### block-detach #####"
> xm block-detach $DomainID $DevID
> Count=`expr $Count + 1`
> #DevID=`expr $DevID + 1`
> sleep 1
> xm block-list $DomainID
> sleep 1
> done
> exit 0
> -------------------------------------------------
>
>
>> We will confirm it again with latest xen-unstable.hg.
>
> I confirmed it with up-to-date xen-unstable.hg. (cs 13282)
>
> It did not reproduce it in DomU.
> Because VBD was not able to be used, pv-on-hvm was not able to confirm
> it.
> The following errors occur.
>
> # insmod xen-vbd.ko
> xen-vbd: Unknown symbol irq_to_evtchn_port
> insmod: error inserting 'xen-vbd.ko': -1 Unknown symbol in module
>
>
> When reproducing it with pv-on-hvm, evtchn had not been liberated as
> follows.
>
> # xm block-attach <DomID> file:/test.img hde w
> # xm block-list <DomID>
> Vdev BE handle state evt-ch ring-ref BE-path
> 2049 0 0 4 6 8 /local/domain/0/backend/vbd/6/2049
> 8448 0 0 4 7 306 /local/domain/0/backend/vbd/6/8448
> # xm block-detach <DomID> 8448
> # xm block-list <DomID>
> Vdev BE handle state evt-ch ring-ref BE-path
> 2049 0 0 4 6 8 /local/domain/0/backend/vbd/6/2049
> # xm block-attach <DomID> file:/test.img hde w
> # xm block-list <DomID>
> Vdev BE handle state evt-ch ring-ref BE-path
> 2049 0 0 4 6 8 /local/domain/0/backend/vbd/6/2049
> 8448 0 0 4 8 306 /local/domain/0/backend/vbd/6/8448
> ^^^<= not 7
>
> If the evtchn number is liberated, it is sure to become the same number.
> The evtchn number keeps increase if it repeats.
> I will confirm whether to be liberated as follows and correctly.
>
> ・xen-unstable.hg : cs 13192
> Revert cset 13181:f087c013cf12 since the event channel is already
> unbound via
> blkif_free() -> unbind_from_irqhandler() -> unbind_from_irq()
>
>
> Thanks,
>
> --
> Takanori Kasai
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2007-02-01 2:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 12:01 [PATCH] fix free of event channel in blkfront Kasai Takanori
2006-12-29 17:54 ` Steven Hand
2007-01-09 0:33 ` Kasai Takanori
2007-01-09 6:18 ` Kasai Takanori
2007-01-09 10:48 ` Kasai Takanori
2007-02-01 2:56 ` tgh [this message]
2007-02-01 4:22 ` Kasai Takanori
2007-02-01 7:46 ` tgh
2007-02-01 9:03 ` Kasai Takanori
2007-02-01 13:22 ` tgh
2007-02-02 0:18 ` Kasai Takanori
2007-02-02 1:42 ` tgh
2007-02-02 3:39 ` Kasai Takanori
2007-02-02 6:24 ` tgh
2007-04-11 2:22 ` tgh
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=45C156EC.7020400@ncic.ac.cn \
--to=tianguanhua@ncic.ac.cn \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=kasai.takanori@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.