From: Timo Veith <timo.veith@uni-tuebingen.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: pve-user@pve.proxmox.com
Subject: Re: [PVE-User] Import OVA, exported from RHV
Date: Thu, 24 Aug 2023 13:34:22 +0200 [thread overview]
Message-ID: <B03B240E-60D1-4537-8F4E-6AD01339C4B7@uni-tuebingen.de> (raw)
In-Reply-To: <DA8C4646-CE7A-4FC2-B7F4-F7AD1D3A8E73@uni-tuebingen.de>
[-- Attachment #1: Type: text/plain, Size: 3075 bytes --]
Helo everyone,
for the record, I ignored that „error“ and went on.
I was able to import the image file into the storage area with
sm0201:~/ova# qm importdisk 101 cbd17719-b318-4551-b0aa-54a122c59671 cephpool01
importing disk 'cbd17719-b318-4551-b0aa-54a122c59671' to VM 101 ...
transferred 0.0 B of 50.0 GiB (0.00%)
transferred 537.6 MiB of 50.0 GiB (1.05%)
transferred 1.1 GiB of 50.0 GiB (2.11%)
...
transferred 49.3 GiB of 50.0 GiB (98.67%)
transferred 49.9 GiB of 50.0 GiB (99.73%)
transferred 50.0 GiB of 50.0 GiB (100.00%)
transferred 50.0 GiB of 50.0 GiB (100.00%)
Successfully imported disk as 'unused0:cephpool01:vm-101-disk-0'
sm0201:~/ova#
I had to manually asign the disk within the vm settings. The wiki article describes that, but I didn’t read that up until now. I was impatient in the first place and tried to start.
So, then I got a „Boot from ...“ message in the console. But it sat there and was stuck.
Using GRML I checked it the data was there, and it was.
So I checked the settings of the vm again. I had to enable the boot order and switch from SeaBIOS to UEFI. The vm was installed with UEFI. That brought me a little further. I saw the grub screen and then the kernel booting. But it crashed with „Fatal glibc error: CPU does not support x86-64-v2“. Ok, one google search later I changed the emulated CPU from kvm64 to x86-64-v2. With that the vm booted.
After I logged in, I noticed that there is no network interface. I added one and I had to edit the NetworkManager profile in order to reflect the change of the device name from enp1s0 to ens18.
I thought there would be more information about the vm config in the ova file. Like bios/uefi, cpu type and network interface etc. It’s suprising to me that I had to configure that manually after importing the ova file.
And I am still curious about the "invalid or missing controller: , skipping“ thing.
Cheers,
Timo
> Am 23.08.2023 um 14:21 schrieb Timo Veith <timo.veith@uni-tuebingen.de>:
>
> Dear Proxmox Users,
>
> I am trying to import a vm which was exported from a RHV environment. There is a wiki article which describes the process here https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#RHEV
>
> However, when I do that, I get the following error message:
>
> sm0201:~/ova# qm importovf 101 vm.ovf cephpool01
> invalid or missing controller: , skipping
>
> Then I thought I could just try it with the local-lvm and issued:
>
> sm0201:~/ova# qm importovf 101 vm.ovf local-lvm
> invalid or missing controller: , skipping
> Reserving empty config for OVF import to VM 101 failed: VM 101 already exists on node ‚sm0201'
>
> Switching over to the WebUI I saw that I now have two new VMs. Can somebody tell my what that message „invalid or missing controller ...“ means?
>
> Thanks and greetings
> Timo_______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2023-08-24 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 12:21 Timo Veith
2023-08-24 11:34 ` Timo Veith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B03B240E-60D1-4537-8F4E-6AD01339C4B7@uni-tuebingen.de \
--to=timo.veith@uni-tuebingen.de \
--cc=pve-user@lists.proxmox.com \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.