|
|
|
|
|
|
|
|
|
|
xen-users
RE: [Xen-users] Device /dev/mapper/vg00-virt--linuxtest_32--0 ismounted
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> James Harper
> Sent: 13 June 2007 13:42
> To: James Harper; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Device
> /dev/mapper/vg00-virt--linuxtest_32--0 ismounted in a guest
> domain, and so cannot be mounted now.
>
> >
> > I tried to start a linux hvm domain (just for testing some things
> > compared to a pv domain), and it didn't start up. I then did a 'xm
> > shutdown', which didn't work, then a 'xm destroy', and from then the
> 'xm
> > list' function just hung.
>
> The reason it hung is that my config was still using the 3.0.4
> hvmbuilder stuff... I guess that's allowed although I would have hoped
> that xend wouldn't have suffered such a panic attack...
That's strange indeed.
>
> >
> > I then restarted xend, and 'xm list' works, but now when I try to
> start
> > the linux hvm domain (linuxtest_32), it says this:
> >
> > "
> > Using config file "./linuxtest_32".
> > Error: Device 768 (vbd) could not be connected.
> > Device /dev/mapper/vg00-virt--linuxtest_32--0 is mounted in a guest
> > domain,
> > and so cannot be mounted now.
> > "
> >
> > So I guess xend got broken and didn't clean something up
> after itself.
> > Any suggestions as to how I can clean up that record without
> rebooting?
> >
>
> I removed the entry using xenstore-rm... seemed to work... was it the
> right thing to do in that case?
That is what the "xm" tools would do (obviously not running the
xenstore-rm command as such, but removing the entry in xenstore).
--
Mats
>
> Thanks
>
> James
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|