Yep, the file vdisk.xml describes most likely the vmdk structure. You may try to create similar guest, dump its configuration and change disk devices, name, whatever to the original one and it should boot. I did it many times.
Petr On 10/09/2009, taiyo K <[email protected]> wrote: > Hello Fajar, > > I tried the command based on your advice, but this error popps up. > > > hits...@cubeville02:~# ls -l /pool01/xVM/Sola10u6_01/Sola10u6_01.img/ > total 9144306 > -rw------- 1 xvm root 4678287360 8月 20 22:55 vdisk.vmdk > -rw-r--r-- 1 xvm root 613 8月 20 22:55 vdisk.xml > hits...@cubeville02:~# > hits...@cubeville02:~# virsh define > /pool01/xVM/Sola10u6_01/Sola10u6_01.img/vdisk.xml > libvir: Xen Daemon error : XML description for domain is not well formed or > invalid > error: Failed to define domain from > /pool01/xVM/Sola10u6_01/Sola10u6_01.img/vdisk.xml > > > Also this is the outcome of "virsh define" command. > > hits...@cubeville02:~# virsh define > /pool01/xVM/Sola10u6_01/Sola10u6_01.img/vdisk.xml > libvir: Xen Daemon error : XML description for domain is not well formed or > invalid > error: Failed to define domain from > /pool01/xVM/Sola10u6_01/Sola10u6_01.img/vdisk.xml > > > Did I use a wrong xml file? > > Robinky > -- > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > [email protected] _______________________________________________ xen-discuss mailing list [email protected]
