Xen users - Aug 2009 - Unable to start domU because losetup fails

Hi,

I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to
"xm
destroy" my domU. Now when I try to start it again it fails like this:

# xm list | grep n39
#
# xm create -c /xen/conf/n39
Using config file "/xen/conf/n39".
ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r
/dev/loop1
/xen/iso/amd64-netbsd-6.iso failed

# losetup -a
/dev/loop0: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop100: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop101: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop102: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop103: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop104: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop105: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop106: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop107: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)

# losetup -d /dev/loop1
ioctl: LOOP_CLR_FD: Device or resource busy

# lsof | grep "loop1 "
loop1     15416       root  cwd       DIR              254,0    4096 
         2 /
loop1     15416       root  rtd       DIR              254,0    4096 
         2 /
loop1     15416       root  txt   unknown 
           /proc/15416/exe

# ps axww | grep 15416
  9973 pts/7    R+     0:00 grep 15416
15416 ?        S<     0:00 [loop1]

# kill -9 15416
# ps axww | grep 15416
  9975 pts/7    R+     0:00 grep 15416
15416 ?        S<     0:00 [loop1]

# mount
/dev/mapper/vg0-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
storage:/xen on /xen type nfs (rw,addr=172.16.17.1)


Any ideas how to get rid of loop1 without rebooting?

Another thing, (and not a real solution but) why doesn''t Xen use
"losetup -f" to
find the first device?

# losetup -f
/dev/loop2

PS. Is there any target date for 3.3.2 and 3.4.1 releases?

Martti

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Martti Kuparinen wrote:
> Any ideas how to get rid of loop1 without rebooting?
Just a clarification, I know reboot will solve this but I can''t reboot
dom0 today...

Martti

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Aug 5, 2009 at 2:20 AM, Martti Kuparinen<martti.kuparinen@iki.fi>
wrote:
> Hi,
>
> I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to
> "xm destroy" my domU. Now when I try to start it again it fails
like this:
>
> # xm list | grep n39
> #
> # xm create -c /xen/conf/n39
> Using config file "/xen/conf/n39".
> ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r
> /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed
>
Manually mount your iso using losetup then specify the loop device in
your domU config to bypass this issue.
>
> PS. Is there any target date for 3.3.2 and 3.4.1 releases?
>
The releases are very close and should go final at the end of this week.


Keith Coleman

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users