Wherever you found the vhd do (I.e the original location of it):

vhd-util scan -p -v -f -m /path/to/vhd

This (p)rints (v)erbose (f)ast scan results. This works for me with the 
vhd-util that is part of blktap-utils on Ubuntu (which is what I run my NSF 
server on hence the files being there) but I believe should work on other 
platforms too. Otherwise do vhd-util scan -h to see if any of the options are 
different. 





> On Aug 11, 2014, at 9:49 PM, Tejas Gadaria <[email protected]> wrote:
> 
> Hi Carlos,
> 
> Yes I am trying to run vhd file of template or root  volume on standalone
> XS server not under CS control.
> how can i make sure it's complete file & not part of chain.?
> 
> Let me correct myself I am using *ACS 4.3 not 4.2*
> 
> Regards,
> Tejas
> 
> 
> 
> On Tue, Aug 12, 2014 at 5:20 AM, Carlos Reategui <[email protected]>
> wrote:
> 
>> Andrei, I think what he is trying to do is take the vhd from an instance on
>> CS+XS and take it to a standalone XS server not under CS control, so doubt
>> that is the prob.
>> 
>> 
>> On Mon, Aug 11, 2014 at 4:31 PM, Andrei Mikhailovsky <[email protected]>
>> wrote:
>> 
>>> Not sure if this is related, but the only time i've had issues with
>>> starting vms with XenServer + CloudStack was vhd-utils were not copied to
>>> /opt/xensource/bin folder. Make sure the file is there.
>>> 
>>> Andrei
>>> 
>>> 
>>> 
>>> ----- Original Message -----
>>> From: "Tejas Gadaria" <[email protected]>
>>> To: [email protected], [email protected]
>>> Sent: Monday, 11 August, 2014 1:27:43 PM
>>> Subject: Template or root Volume VHD not able to run on standalone
>>> xenserver
>>> 
>>> Hi,
>>> 
>>> I am using ACS 4.2 with Xenserver 6.2 SP1..
>>> Also I have .vhd of template & root volume & want to run on standalone
>> xen
>>> server but, while trying to import vhd from import wizard in xencenter it
>>> says, 'VHD is not suitable for xenserver' .
>>> 
>>> Is it related to vhd-util, what we are importing in CS Management server?
>>> How can i resolve this issue?
>>> 
>>> Regards,
>>> Tejas
>>> 
>> 

Reply via email to