|
|
|
|
|
|
|
|
|
|
xen-api
Re: [Xen-API] vm export bug in XCP 0.5
(sorry, long output)
... And even after all task cancellation, vbd between VDI and control
domain are still exsits.
xe task-list
uuid ( RO) : 34686a3e-8f50-2001-8ddd-bec12d2a3f4f
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 43c0ac9f-d79e-e495-7c60-d3e4aa2234ac
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 74fa1a43-7f60-6f5e-ecda-77f2ec987a42
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 39360f1b-6416-51ab-7801-0a8906f01b06
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 48482ec0-484c-a24b-6516-cf0f14062289
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 4d0cdbfc-2425-7329-c77a-6ebd5799e2a7
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 89c83ab0-0d80-faf6-7de2-426fd5fb73cc
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : f1243680-58f2-57e1-35d5-044eb703ae6f
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
uuid ( RO) : 885e1f24-0910-c19b-e32c-a0a2aa77d3af
name-label ( RO): Async.SR.update
name-description ( RO):
status ( RO): success
progress ( RO): 1.000
В Пн., 20/12/2010 в 15:29 +0000, Jonathan Ludlam пишет:
> Had the server noticed that the CLI had gone away after you ctrl-c'd it? If
> you run:
>
> xe task-list
>
> Does it still show the export? Does it still fail to start if you wait until
> the export task has gone away?
>
> Jon
>
> On 20 Dec 2010, at 14:34, George Shuklin wrote:
>
> > Good day.
> >
> > vbd, used by control domain for vm export does not destroyed if vm
> > export is canceled.
> >
> > Steps to reproduce (may include some unnecessary steps):
> >
> > a) Create vm with vdi on lvmoiscsi storage, and host suspend-sr on
> > lvmoiscsi-storage
> > b) Start VM on slave
> > c) suspend VM
> > d) start export to file (in my case it was NFS share) via cli directly
> > from slave host where VM was resident before suspend.
> > e) interrupt export about 20-30 sec after start by pressing Ctrl-C
> > f) Try to start VM (vm-start), got:
> > xe vm-resume vm=test
> > The server failed to handle your request, due to an internal error. The
> > given message may give details useful for debugging the problem.
> > message: Failure("The VDI 4813431c-56ee-4a68-811a-b15b69a20e57 is
> > already attached in RO mode; it can't be attached in RW mode!")
> >
> > Yes, VBD was attached to control domain:
> >
> > uuid ( RO) : b10b03c1-79f1-3406-aea1-46a13bb040aa
> > vm-uuid ( RO): d4e93255-cbc0-43a6-95cc-936c9dcdd79c
> > vm-name-label ( RO): Control domain on host: cvt-xh3
> > vdi-uuid ( RO): 4813431c-56ee-4a68-811a-b15b69a20e57
> > empty ( RO): false
> > device ( RO): xvda
> >
> >
> >
> > _______________________________________________
> > xen-api mailing list
> > xen-api@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/mailman/listinfo/xen-api
>
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
|
|
|
|
|