Differences

This shows you the differences between two versions of the page.

--- hypervisor:toolstack:domu [2014/06/04 18:03]
admin [Templated VM Specific Operations]
+++ hypervisor:toolstack:domu [2014/06/05 11:28]
admin [Connect to the Running VM]
@@ Line 164: / Line 164: @@
 <WRAP center important 90%>
-Once logged into the VM's console, you'll be "trapped" inside this console. It won't be possible for you to come back to the host's console.
+Once logged into the VM's console, you may get "trapped" inside this console. In case there is no "exit" possible, it won't be possible for you to come back to the host's console.
 This might be a problem when interacting from a plain terminal screen on the host itself, getting locked out of your host's console might force you to force a reboot in case you cannot access it via ssh from another machine to reboot it nicely!.
@@ Line 241: / Line 241: @@
 Right after successful VM start PV-bootloader is replaced from eliloader to pygrub (to boot to new VM native kernel). Of course, if user stops installation process, at next startup there will be no kernel and vm will not start again.
+<code>
+> xe vm-param-set uuid=44c68930-1192-a196-b460-5f411a689c85 PV-bootloader=
+> xe vm-param-set uuid=44c68930-1192-a196-b460-5f411a689c85 PV-kernel=/root/PVs/debian-wheezy/vmlinuz
+> xe vm-param-set uuid=44c68930-1192-a196-b460-5f411a689c85 PV-ramdisk=/root/PVs/debian-wheezy/initrd.gz
+> xe vm-start uuid=44c68930-1192-a196-b460-5f411a689c85
+</code>
+To follow the installation process:
+<code>
+> xe vm-param-get uuid=44c68930-1192-a196-b460-5f411a689c85 param-name=dom-id
+> screen -S Wheezy
+> /usr/lib/xen-4.1/bin/xenconsole 4
+</code>
+After initial installation:
+<code>
+> xe vm-param-set uuid=... PV-bootloader=pygrub
+</code>
+=== Add Xen Tools ===
+At this point you might want to [[http://wiki.strategicz.com/vhyper/doku.php?id=hypervisor:basestack:domu&#install_xen_tools|add the XenTools]] to your VM.
+----
+===== Create Template and Appliance =====
+----
+Reference: [[http://www.jansipke.nl/creating-backups-of-running-vms-in-xenserver/]]
+It seems that this operation can be performed even on a running VM.
+Pick target VM uuid:
+<code>
+> xe vm-list is-control-domain=false is-a-snapshot=false
+</code>
+Create the snapshot:
+<code>
+> xe vm-snapshot uuid=<vm-uuid> new-name-label=<snapshotname>
+<snapshot-uuid>
+</code>
+Transform the snapshot into a VM to be able to save it to a file:
+<code>
+> xe template-param-set is-a-template=false ha-always-run=false uuid=<snapshot-uuid>
+> xe vm-export vm=<snapshot-uuid> filename=<filename>.xva
+Export succeeded
+</code>
+The export operation can take a while... Be patient until you see the "Export succeeded" message.
+Finally let's get rid of the snapshot:
+<code>
+> xe vm-uninstall uuid=<snapshot-uuid> force=true
+</code>
 ----