From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id B94E31FF170
for <inbox@lore.proxmox.com>; Tue, 19 Nov 2024 09:40:10 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 87D1B1D2C4;
Tue, 19 Nov 2024 09:40:04 +0100 (CET)
From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Tue, 19 Nov 2024 09:39:55 +0100
Message-Id: <20241119083958.513287-2-d.csapak@proxmox.com>
X-Mailer: git-send-email 2.39.5
In-Reply-To: <20241119083958.513287-1-d.csapak@proxmox.com>
References: <20241119083958.513287-1-d.csapak@proxmox.com>
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.015 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DMARC_MISSING 0.1 Missing DMARC policy
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
Subject: [pve-devel] [PATCH docs 1/1] qm: adapt import section to newly
added OVA/OVF import
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
remove reference to future ova support and only esxi as supported.
Add extra OVA/OVF section explaining some caveats.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
qm.adoc | 35 ++++++++++++++++++++++++++++-------
1 file changed, 28 insertions(+), 7 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index bf53e11..2ffa4ef 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1650,8 +1650,7 @@ model and reduced downtime.
NOTE: The import wizard was added during the {pve} 8.2 development cycle and is
in tech preview state. While it's already promising and working stable, it's
-still under active development, focusing on adding other import-sources, like
-for example OVF/OVA files, in the future.
+still under active development.
To use the import wizard you have to first set up a new storage for an import
source, you can do so on the web-interface under _Datacenter -> Storage -> Add_.
@@ -1666,17 +1665,39 @@ wizard. You can modify a subset of the available options here and then start the
import. Please note that you can do more advanced modifications after the import
finished.
-TIP: The import wizard is currently (2024-03) available for ESXi and has been
-tested with ESXi versions 6.5 through 8.0. Note that guests using vSAN storage
-cannot be directly imported directly; their disks must first be moved to another
-storage. While it is possible to use a vCenter as the import source, performance
-is dramatically degraded (5 to 10 times slower).
+TIP: The ESXi import wizard has been tested with ESXi versions 6.5 through
+8.0. Note that guests using vSAN storage cannot be directly imported directly;
+their disks must first be moved to another storage. While it is possible to use
+a vCenter as the import source, performance is dramatically degraded (5 to 10
+times slower).
For a step-by-step guide and tips for how to adapt the virtual guest to the new
hyper-visor see our
https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Migration[migrate to {pve}
wiki article].
+OVA/OVF Import
+^^^^^^^^^^^^^^
+
+To import OVA/OVF files, you first need a File-based storage with the 'import'
+content type. On this storage, there will be an 'import' folder where you can
+put OVA files or OVF files with the corresponding images in a flat structure.
+Alternatively you can use the web ui to upload or download OVA files directly.
+You can then use the web ui to select those and use the import wizard to import
+the guests.
+
+For OVA files, there is additional space needed to temporarily extract the
+image. This needs a file-based storage that has the 'images' content type
+configured. By default the source storage is selected for this, but you can
+specify a 'Import Working Storage' on which the images will be extracted before
+importing to the actual target storage.
+
+NOTE: Since OVA/OVF file structure and content are not always well maintained
+or defined, it might be necessary to adapt some guest settings manually. For
+example the SCSI controller type is almost never defined in OVA/OVF files, but
+the default is unbootable with OVMF (UEFI), so you should select 'Virtio SCSI'
+or 'VMware PVSCSI' for these cases.
+
Import OVF/OVA Through CLI
~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel