[one-users] problem with vifs

[Tino Vazquez]

Hi,

The set up seems to be fine.

First problem
-------------------

What is the output of the following in the front-end?

bash -xv /var/lib/one/remotes/datastore/vmfs/cp
PERTX0RSSVZFUl9BQ1RJT05fREFUQT48SU1BR0U+PElEPjEwNTwvSUQ+PFVJRD4wPC9VSUQ+PEdJRD4wPC9HSUQ+PFVOQU1FPm9uZWFkbWluPC9VTkFNRT48R05BTUU+b25lYWRtaW48L0dOQU1FPjxOQU1FPnNjZW5hcmlvMi4xKHZtZnMpPC9OQU1FPjxQRVJNSVNTSU9OUz48T1dORVJfVT4xPC9PV05FUl9VPjxPV05FUl9NPjE8L09XTkVSX00+PE9XTkVSX0E+MDwvT1dORVJfQT48R1JPVVBfVT4wPC9HUk9VUF9VPjxHUk9VUF9NPjA8L0dST1VQX00+PEdST1VQX0E+MDwvR1JPVVBfQT48T1RIRVJfVT4wPC9PVEhFUl9VPjxPVEhFUl9NPjA8L09USEVSX00+PE9USEVSX0E+MDwvT1RIRVJfQT48L1BFUk1JU1NJT05TPjxUWVBFPjA8L1RZUEU+PERJU0tfVFlQRT4wPC9ESVNLX1RZUEU+PFBFUlNJU1RFTlQ+MDwvUEVSU0lTVEVOVD48UkVHVElNRT4xMzYxNTQxMTUwPC9SRUdUSU1FPjxTT1VSQ0U+PC9TT1VSQ0U+PFBBVEg+L29wZW5uZWJ1bGEvdHR5bGludXgudm1kay50YXIuYnoyPC9QQVRIPjxGU1RZUEU+PC9GU1RZUEU+PFNJWkU+MjM8L1NJWkU+PFNUQVRFPjQ8L1NUQVRFPjxSVU5OSU5HX1ZNUz4wPC9SVU5OSU5HX1ZNUz48Q0xPTklOR19PUFM+MDwvQ0xPTklOR19PUFM+PENMT05JTkdfSUQ+LTE8L0NMT05JTkdfSUQ+PERBVEFTVE9SRV9JRD4xMjU8L0RBVEFTVE9SRV9JRD48REFUQVNUT1JFPmVzY2VuYXJpbzIuMSh2bWZzX3ZtZnMpPC9EQVRBU1RPUkU+PFZNUz48L1ZNUz48VEVNUExBVEU+PERFU0NSSVBUSU9OPjwhW0NEQVRBW3ZtZnNdXT48L0RFU0NSSVBUSU9OPjxERVZfUFJFRklYPjwhW0NEQVRBW2hkXV0+PC9ERVZfUFJFRklYPjwvVEVNUExBVEU+PC9JTUFHRT48REFUQVNUT1JFPjxJRD4xMjU8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5lc2NlbmFyaW8yLjEodm1mc192bWZzKTwvTkFNRT48UEVSTUlTU0lPTlM+PE9XTkVSX1U+MTwvT1dORVJfVT48T1dORVJfTT4xPC9PV05FUl9NPjxPV05FUl9BPjA8L09XTkVSX0E+PEdST1VQX1U+MTwvR1JPVVBfVT48R1JPVVBfTT4wPC9HUk9VUF9NPjxHUk9VUF9BPjA8L0dST1VQX0E+PE9USEVSX1U+MDwvT1RIRVJfVT48T1RIRVJfTT4wPC9PVEhFUl9NPjxPVEhFUl9BPjA8L09USEVSX0E+PC9QRVJNSVNTSU9OUz48RFNfTUFEPnZtZnM8L0RTX01BRD48VE1fTUFEPnZtZnM8L1RNX01BRD48QkFTRV9QQVRIPi92YXIvbGliL29uZS9kYXRhc3RvcmVzLzEyNTwvQkFTRV9QQVRIPjxTWVNURU0+MDwvU1lTVEVNPjxESVNLX1RZUEU+MDwvRElTS19UWVBFPjxDTFVTVEVSX0lEPjEwMDwvQ0xVU1RFUl9JRD48Q0xVU1RFUj5jbHVzdGVyIzE8L0NMVVNURVI+PElNQUdFUz48L0lNQUdFUz48VEVNUExBVEU+PERJU0tfVFlQRT48IVtDREFUQVtibG9ja11dPjwvRElTS19UWVBFPjxEU19NQUQ+PCFbQ0RBVEFbdm1mc11dPjwvRFNfTUFEPjxUTV9NQUQ+PCFbQ0RBVEFbdm1mc11dPjwvVE1fTUFEPjwvVEVNUExBVEU+PC9EQVRBU1RPUkU+PC9EU19EUklWRVJfQUNUSU9OX0RBVEE+
105

Second problem
-----------------------

There is indeed no way to create swap images for VMware using the ssh
drivers. The rationale behind creating the volatile images in the virt
hosts is that one jump is saved (from wherever is create to the host). As
stated in the documentation (
http://opennebula.org/documentation:rel3.8:evmwareg)

--At the time of defining a VM, a volatile disk can be described, which
will be created in the remote ESX host. This is true for disks defined in
the VM template, and also for the file needed in the “onevm attachdisk”
operation. Here, it is not possible to format the disk, so it will appear
as a raw device on the guest, which will then need to be formatted.
Possible values for the FORMAT attribute (more info on this
here<http://communities.vmware.com/message/716009>
):

   - *vmdk_thin*
   - *vmdk_zeroedthick*
   - *vmdk_eagerzeroedthick*

--

Regards,

-Tino


--
Constantino Vázquez Blanco, PhD, MSc
Project Engineer
OpenNebula - The Open-Source Solution for Data Center Virtualization
www.OpenNebula.org | @tinova79 | @OpenNebula
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130228/415ef672/attachment-0001.htm>