|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Re: Device already mounted in guest domain problem
Got this fixed after hours of pulling my hair out ! I'm posting the answer so others won't go bald :) Basically, you need to deallocate the ressource from the previous vm using the xenstore utility which is installed alongside Xen.
In my case, the previous VM's ID was 16 and the device that could not be connected was 768. I had to type this command to get it to work : xenstore-rm /local/domain/0/backend/vbd/16/768 You can use xenstore-ls to find the right number if you don't know it.
Antoine On Mon, Sep 15, 2008 at 5:44 PM, Antoine Benkemoun <antoine@xxxxxxxxxxxxx> wrote:
Hello,
My first windows VM works perfectly and is nearing pre-prod but the second VM still doesn't quite want cooperate...
The error I get is the following :
xen1:~# xm create -c /etc/xen/examu.cfg
Using config file "/etc/xen/examu.cfg". Error: Device 768 (vbd) could not be connected. Device /data/domains/examu/hdd.img is mounted in a guest domain, and so cannot be mounted now.
I didn't mount this image in any other guest... I googled around and I have seen that people have been having the same problem but without mentionning any fixes. Have you encountered this error before and found a way to fix this ?
Thank you in advance for your help,
Antoine
-- Antoine Benkemoun Tel : 03.51.53.57.00 Port : 06.32.88.59.35
-- Antoine Benkemoun Tel : 03.51.53.57.00 Port : 06.32.88.59.35
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|