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 84] New: XenU couldn't be destroied if migration failed.

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 84] New: XenU couldn't be destroied if migration failed.
From: yongkang.you@xxxxxxxxx
Date: Fri, 24 Jun 2005 10:44:26 +0000
Delivery-date: Fri, 24 Jun 2005 10:44:30 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=84

           Summary: XenU couldn't be destroied if migration failed.
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: yongkang.you@xxxxxxxxx


Environment:
------------
Service OS : ia32
Guest OS : ia32


Bug detailed description:
--------------------------
If XenU migrate failed, xenU couldn't be destroied.
Live migrage also has this problem.


Reproduce steps:
----------------
1. start xend

2. xm create /etc/xen/domU
/etc/xen/domU is like:
kernel = "/boot/vmlinuz-2.6.11-xenU"
memory = 32
name = "DOMU"
disk = [ 'file:/data/rootfs,sda1,w' ]
root = "/dev/sda1 ro"
extra = "4"

3. xm list
[root@vt-yyou ~]# xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)  Console
DOMU               3       32    0      1   -b---      1.7     9603
Domain-0           0      256    0      1   r----    104.1         

4. xm migrate -l 3 machine1
machine1 is another xen0 without the similar environment with local machine.

5. wait for a while no matter if migration is ok.

6. Ctrl+C to break the migration.

7. xm list
[root@vt-yyou ~]# xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)  Console
DOMU               3       32    0      1   ---s-      4.3     9603
Domain-0           0      256    0      1   r----    139.5         

8. try to destroy domU. But domU couldn't be destroied. But after destroying, 
tts memory only contain 4MB.
[root@vt-yyou ~]# xm destroy 3
[root@vt-yyou ~]# xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)  Console
DOMU               3        4    0      1   ---s-      4.3     9603
Domain-0           0      256    0      1   r----    142.1         

9. Try to create domU again. Of course it couldn't be create.
[root@vt-yyou ~]# xm create /etc/xen/domU 
Using config file "/etc/xen/domU".
Error: Error creating domain: vm name clash: DOMU

Current result:         
----------------
XenU couldn't be destroied, if migration failed.


Expected result:                
----------------
XenU could be destroied, not matter migration failed.



------- 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>
  • [Xen-bugs] [Bug 84] New: XenU couldn't be destroied if migration failed., yongkang . you <=