[Xen-bugs] [Bug 408] New: xm destroy/shutdown doesn't free loop-device

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=408

           Summary: xm destroy/shutdown doesn't free loop-device
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: falk@xxxxxxxxxxxx


Hi, 

I'm using xen unstable with xen_changeset Fri Nov 11 19:11:13 2005 +0100 
7772:995e94c4802e, 
compiled with gcc 4.0.2 on Debian with kernel 2.6.12.6. 

When I quit a VM with "xm shutdown" or "xm destroy" the loop-device used for 
root-fs of the domain 
isn't freed so after 3 VM restarts all my loopdevices are used up. 

config file for domU: 
----8<----
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 128
name = "foobar"
disk = [ 
'file:/systems/xen-test1.root.fs,hda1,w','file:/systems/xen-test1.swap.fs,hda2,w'
 ]
----8<----

(I have another domU using xen-test2...)

loop device state: 
for i in $(seq  0 7  ) ; do losetup /dev/loop$i ; done 
/dev/loop0: [0301]:3417595 (/systems/xen-test1.swap.fs)
/dev/loop1: [0301]:3417597 (/systems/xen-test2.swap.fs)
/dev/loop2: [0301]:3417594 (/systems/xen-test1.root.fs)
/dev/loop3: [0301]:3417594 (/systems/xen-test1.root.fs)
/dev/loop4: [0301]:3417596 (/systems/xen-test2.root.fs)
/dev/loop5: [0301]:3417597 (/systems/xen-test2.swap.fs)
/dev/loop6: [0301]:3417595 (/systems/xen-test1.swap.fs)
/dev/loop7: [0301]:3417596 (/systems/xen-test2.root.fs)

xm list:
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      384     1 r-----    41.9

I hope, this is enough info. If needed, I can grant access to the system. 

Have a nice day, 

Falk Stern

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- 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