Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
hypervisor:toolstack:gui [2014/04/30 00:31] admin [Connect the VM to the Desired Network] |
hypervisor:toolstack:gui [2015/03/05 14:13] (current) admin Links adapted because of a move operation |
||
---|---|---|---|
Line 2: | Line 2: | ||
There are quite a few solutions that can act as a GUI for XCP-XAPI. | There are quite a few solutions that can act as a GUI for XCP-XAPI. | ||
- | Note that prior to installing a virtual machine, you'll need to **setup your [[:hypervisor:vms:storage-repository|storage repositories]]**. | + | Note that prior to installing a virtual machine, you'll need to **setup your [[hypervisor:base:storage|storage repositories]]**. |
===== Xen Orchestra ===== | ===== Xen Orchestra ===== | ||
Can be installed as an "appliance": | Can be installed as an "appliance": | ||
Line 49: | Line 49: | ||
> xe vif-create vm-uuid=<uuid_of_vm> network-uuid=<uuid_of_network> device=0 | > xe vif-create vm-uuid=<uuid_of_vm> network-uuid=<uuid_of_network> device=0 | ||
</code> | </code> | ||
+ | |||
+ | ==== Run the Appliance on a Selected Host ==== | ||
Now, find the UUID of the host serveur you're willing to run the appliance on: | Now, find the UUID of the host serveur you're willing to run the appliance on: | ||
Line 63: | Line 65: | ||
To display appliance's (VM) console from your login session on this host server | To display appliance's (VM) console from your login session on this host server | ||
<code> | <code> | ||
- | > xe vm-list params=dom-id uuid=<uuid_of_vm> --minimal | + | > xe vm-list params=dom-id name-label=XOA |
- | > /usr/lib/xen/bin/xenconsole <dom_id> | + | > /usr/lib/xen-4.1/bin/xenconsole <dom_id> |
</code> | </code> | ||
+ | |||
+ | Login as "root" user (passwd: root).\\ | ||
+ | Issuing an **ifconfig** command will let you find out the DHCP allocated IP of your VM... | ||
<WRAP center round tip 90%> | <WRAP center round tip 90%> | ||
- | Pay attention to the fact that connecting to the VM's console is a **one way ticket** to it. This means that **once in the VM's console, you won't be able to get back to the host's console**. | + | Pay attention to the fact that connecting to the VM's console is a **one way ticket**. This means that **once in the VM's console, you won't be able to get back to the host's console**. |
In case you're working directly from the server's keyboard and screen (not over ssh), this might lock you out! | In case you're working directly from the server's keyboard and screen (not over ssh), this might lock you out! | ||
Line 75: | Line 80: | ||
</WRAP> | </WRAP> | ||
- | To have a quick overview of what screen can do, look at this page: [[http://www.tecmint.com/screen-command-examples-to-manage-linux-terminals/]] | + | To have a quick overview of what screen can do, have a look at this page: [[http://www.tecmint.com/screen-command-examples-to-manage-linux-terminals/]] |
+ | |||
+ | ==== Autostart a VM ==== | ||
+ | First activate auto-start option on the pool you need it: the process is to identify the pool on which you want to activate auto-start and modify the auto_poweron parameter. | ||
+ | <code> | ||
+ | > xe pool-list | ||
+ | uuid ( RO) : <YOUR-POOL-UUID> | ||
+ | |||
+ | > xe pool-param-set uuid=<YOUR-POOL-UUID> other-config:auto_poweron=true | ||
+ | </code> | ||
+ | |||
+ | Then identify the VM you want to auto-start and also modify it's auto_poweron parameter: | ||
+ | <code> | ||
+ | > xe vm-list name-label=XOA | ||
+ | uuid ( RO) : <YOUR-VM-UUID> | ||
+ | |||
+ | > xe vm-param-set uuid=<YOUR-VM-UUID> other-config:auto_poweron=true | ||
+ | </code> |