Well, that really helped to understand what is going on with the
storage resources. The tab completion of "xe" is just outstanding,
Many thanks for the help, I'll let you know if I bump into any other issue.
Have a good weekend,
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor / Cloud Researcher
www.OpenNebula.org | @tinova79
On Thu, Feb 17, 2011 at 10:46 AM, Jonathan Ludlam
> On 11 Feb 2011, at 11:46, Tino Vazquez wrote:
>> Hi Tim,
>> Many thanks for the hint, I've added myself to the xen-api list. I'll
>> repeat my questions here for clarity shake:
>> * Is it possible to add users other than with Active Directory? How
>> can I achieve that using the API? Is it possible to do so xi "xe"?
> Not currently, but it should be possible to achieve - I think there's a google
> summer of code proposal to address this.
>> * Is it possible to create a VM from previously existing VDIs? What
>> parameters should I fill? In my tests, the created VM doesn't find the
>> hard disk, these are my steps:
>> * Create vm with xe vm-create
>> * Attach a disk via XenCenter (how can I perform this operation with xe?)
> xe vbd-create vm-uuid=<foo> vdi-uuid=<bar> device=<device number>
>> * Set a PV-kernel (do it need to be in /boot/guest/?)
> Yes - you need to mkdir this. You can use pygrub to boot a kernel present on
> the disk.
>> * Do I need to create VMs off templates?
>> * Can I attach a CDROM device using xe?
> xe vbd-create type=CD vdi-uuid=... vm=...
> You can do almost everything with the CLI that you can with XenCenter, and
> the CLI commands are much more close in naming to the underlying API than the
> GUI operations. If you want to see what the GUI is doing during a particular
> operation, tail /var/log/xensource.log or audit.log, and you should see the
> API calls it's making. The CLI commands will be very similar to the names of
> the APIs.
> For most xe commands, don't forget that you can tab-complete your way to
> success :-)
xen-api mailing list