Once I upgraded my engine and nodes it seemed to work, thank you Liran.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
On Fri, May 13, 2022 at 7:21 AM Abe E wrote:
> Anyone getting issues with OVA Imports on 4.4?
> I exported this from ovirt back in March although now importing again it
> is failing.
>
> My engine logs show it erroring out here:
> Command, return: StatusReturn:{status='Status [code=0,
The last oVirt 4.3 release contains a bug which will export OVAs with empty
disks. Just do a du -h to see if it contains more than the XML
header and tons of zeros.
Hopefully the orignal VMs are still with you because you'll need to fix the
python code that does the export: It's a single line
I'm extracting the ova into vm and disk. The disk does not have a file
extension but am importing it into ovirt.
If this works, I'll let you know.
However, the fact that it thin provisions the drive even though I chose
preallocated bothers me. WHen extracted, the disk file is the right size.
On Thu, Apr 8, 2021 at 12:04 PM Gianluca Cecchi
wrote:
> On Thu, Apr 8, 2021 at 10:49 AM Arik Hadas wrote:
>
>>
>> On Thu, Apr 8, 2021 at 3:50 AM wrote:
>>
>>> I am running Ovirt 4.3 and exported machines as ova which includes
>>> disks. When I re import them. the disks are thin provisioned
On Thu, Apr 8, 2021 at 10:49 AM Arik Hadas wrote:
>
> On Thu, Apr 8, 2021 at 3:50 AM wrote:
>
>> I am running Ovirt 4.3 and exported machines as ova which includes disks.
>> When I re import them. the disks are thin provisioned and the vm will not
>> boot.
>> Any idea how to get the import to
On Thu, Apr 8, 2021 at 3:50 AM wrote:
> I am running Ovirt 4.3 and exported machines as ova which includes disks.
> When I re import them. the disks are thin provisioned and the vm will not
> boot.
> Any idea how to get the import to preallocate disks? I have vms that
> will not boot.
>
It
I have the same issue, it seems, but AFAIK the problem is on the export side:
While the OVA logical file size matches the size of the VM's disk, the actual
storage usage on the VDO compressed and deduplicated NFS I use as export target
per 'du -h *.ova' is a mere 28KB, while 'strings .ova'
Thanks, I'll try VMware ova.
Regards
El lun., 2 de marzo de 2020 12:47 p. m., Michal Skrivanek <
michal.skriva...@redhat.com> escribió:
>
>
> On 28 Feb 2020, at 19:37, Juan Pablo Lorier wrote:
>
> So far nor virtualbox ova in any format nor EXi work :-(
>
> yes, because none of those are
> On 28 Feb 2020, at 19:37, Juan Pablo Lorier wrote:
>
> So far nor virtualbox ova in any format nor EXi work :-(
>
>
yes, because none of those are supported. OVA doesn’t mean much, it’s just a
generic “wrapper” for anything inside, you need to specifically support OVA
which some other
So far nor virtualbox ova in any format nor EXi work :-(
Thanks
El 28/2/20 a las 12:25, Edward Berger escribió:
I haven't tried many but for one I just untarred the thing to get the
disk image file and created a new VM with that.
Sometimes the ova file is compressed/assembled in some way that
This is not a disk upload, which works fine, this is an import. It loads
locally from one hypervisor, and the same problem happens on the other
nodes. I can load the ova, select the vm to import and see all the
params, then in the import process, it fails.
Regards
El 28/2/20 a las 03:11,
I haven't tried many but for one I just untarred the thing to get the disk
image file and created a new VM with that.
Sometimes the ova file is compressed/assembled in some way that might not
be compatible.
On Fri, Feb 28, 2020 at 1:12 AM Jayme wrote:
> If the problem is with the upload process
If the problem is with the upload process specifically it’s likely that you
do not have the ovirt engine certificate installed in your browser.
On Thu, Feb 27, 2020 at 11:34 PM Juan Pablo Lorier
wrote:
> Hi,
>
> I'm running 4.3.8.2-1.el7 (just updated engine to see if it helps) and I
> haven't
14 matches
Mail list logo
