Ok... I missed a couple of rows....
location ( RO): 7b856647-9893-4275-8738-755046817c7b
type ( RO): User
sharable ( RO): false
read-only ( RO): false
storage-lock ( RO): false
managed ( RO): true
parent ( RO): <not in database>
missing ( RO): false
other-config (MRW):
xenstore-data (MRO):
sm-config (MRO): *vhd-parent:
65d3eb8e-76f1-4b37-965a-0d9ad3056645*
on-boot ( RW): persist
allow-caching ( RW): false
metadata-latest ( RO): false
metadata-of-pool ( RO): <not in database>
tags (SRW):
Thank you very much!!
On Mon, Jun 8, 2015 at 12:29 PM, Alessandro Caviglione <
[email protected]> wrote:
> Thank you Vladim...
> but it's a little strange... I did snapshot on the original VM but I've
> also created a new VM from that snapshot, this should clone the entire vhd,
> isn't it?
>
> However, this is the results of the command, where I can see that this VHD
> is still connected to the other VM?
>
> xe vdi-list uuid=7b856647-9893-4275-8738-755046817c7b params=all
> uuid ( RO) : 7b856647-9893-4275-8738-755046817c7b
> name-label ( RW):
> name-description ( RW):
> is-a-snapshot ( RO): false
> snapshot-of ( RO): <not in database>
> snapshots ( RO):
> snapshot-time ( RO): 19700101T00:00:00Z
> allowed-operations (SRO): forget; generate_config; update; resize;
> destroy; clone; copy; snapshot
> current-operations (SRO):
> sr-uuid ( RO): e6212223-af2c-17ed-bdf3-7954fe500073
> sr-name-label ( RO): 76ebfe94-cb9d-390d-bb6d-8dc21e977bdd
> vbd-uuids (SRO): 1a47a516-1268-d134-7161-3d37972a2be6
> crashdump-uuids (SRO):
> virtual-size ( RO): 5368709120
> physical-utilisation ( RO): 14848
>
> On Mon, Jun 8, 2015 at 12:21 PM, Vadim Kimlaychuk <
> [email protected]> wrote:
>
>> Hello Alessandro,
>>
>>
>>
>> This is OK if you did snapshot(s). The original VDI will
>> be displayed if you get VM params and looks for extra options there. There
>> are may be even more files connected to VM. Don’t bother about this.
>>
>> Roughly you should do the following steps:
>>
>> 1. Stop the VM
>>
>> 2. Make export with “xe vm-export” to XVA file
>>
>> 3. Extract VHD file from XVA using XenConvert (look here
>> http://marcusdaniels.net/quick-and-easy-xenserver-to-hyper-v-conversion/)
>>
>> 4. Put VHD file on HTTP server
>>
>> 5. Register template in Cloudstack from URL at p.4
>>
>>
>>
>> Vadim.
>>
>>
>>
>> -----Original Message-----
>> From: Alessandro Caviglione [mailto:[email protected]]
>> Sent: Monday, June 08, 2015 1:12 PM
>> To: [email protected]
>> Subject: Help in importing VM
>>
>>
>>
>> Hi guys,
>>
>> I've a little question about how to import a VM in ACS.
>>
>> A my client has a VM running on XenServer 6.2 SP1, now he wants to
>> migrate to our Cloud platform and we should import that VM in his account.
>>
>> We done a snapshot of the running VM and created a new VM from that
>> snapshot, after that we found the VHD name from the commands:
>>
>>
>>
>> xe vm-list name-label=TOMIGRATE
>>
>> uuid ( RO) : 9ab667ef-32b9-d61b-73ef-4d6c40196c43
>>
>> name-label ( RW): TOMIGRATE
>>
>> power-state ( RO): halted
>>
>>
>>
>>
>>
>> xe vm-disk-list uuid=9ab667ef-32b9-d61b-73ef-4d6c40196c43
>>
>> Disk 0 VBD:
>>
>> uuid ( RO) : 1a47a516-1268-d134-7161-3d37972a2be6
>>
>> vm-name-label ( RO): TOMIGRATE
>>
>> userdevice ( RW): 0
>>
>>
>>
>>
>>
>> Disk 0 VDI:
>>
>> uuid ( RO) : 7b856647-9893-4275-8738-755046817c7b
>>
>> name-label ( RW):
>>
>> sr-name-label ( RO): 76ebfe94-cb9d-390d-bb6d-8dc21e977bdd
>>
>> virtual-size ( RO): 5368709120
>>
>>
>>
>> Now, browsing the NFS SR, I found the
>>
>> 7b856647-9893-4275-8738-755046817c7b.vhd file, but it's strange that the
>> size it's just 14 KB!!
>>
>>
>>
>> Why?
>>
>
>
