Linux

50411 readers

2171 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Can't import OVA file or unpack it with tar (sopuli.xyz)

submitted 1 year ago by PrivateNoob@sopuli.xyz to c/linux@lemmy.ml

9 comments fedilink hide all child comments

I'm on an Arch-based Linux with VirtualBox (generic installer, couldn't load modules with host-modules-arch) and I get this error whenever I try to import this OVA file:

Error reading OVA '.../coa-aio-newton.ova' (VERR_TAR_UNEXPECTED_EOS) Result Code: VBOX_E_IPRT_ERROR (0X80BB0005) Component: ApplianceWrap Interface: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}

Apparently, these OVA files should be unpackable but tar doesn't recognize it, and neither Ark or PeaZip can unzip this, but importing this OVA file works on Win 10.

I've tried using VMWare but that gave me an import error too. Why can't virtualization work at all on Arch-based systems?

you are viewing a single comment's thread
view the rest of the comments

[–] bizdelnick@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

It looks like typical M$ EEE strategy, stage 2: extend standard to break compatibility. But OVA images produced by different virtualization systems are almost always incompatible to each other on the level of xml metadata. Seems that just one more level of incompatibility was added in archive format.

What does the command file your_image.ova say?

[–] bizdelnick@lemmy.ml 2 points 1 year ago (1 children)

Well, I've downloaded the file and it is a correct tar archive.

% file coa-aio-newton.ova          
coa-aio-newton.ova: POSIX tar archive (GNU)
% tar -tf coa-aio-newton.ova 
coa-aio-newton.ovf
coa-aio-newton_2_1-disk001.vmdk
% sha256sum coa-aio-newton.ova 
025fcb6e635e30d6592834aeba1649ef24a8c0fa079d1bbc9aa6290a8aa5e614  coa-aio-newton.ova

According to coa-aio-newton.ovf, it is created in virtualbox.

[–] PrivateNoob@sopuli.xyz 1 points 1 year ago (1 children)

$ file coa-aio-newton.ova
coa-aio-newton.ova: ASCII text
$ tar -tf coa-aio-newton.ova
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

Hmm interesting. Nevermind I have unpacked the ova file and exported the vmdk and ovf back to Linux. Thank you for your observation tho!

[–] bizdelnick@lemmy.ml 2 points 1 year ago (1 children)

That file was downloaded wrong. I can guess that you used the broken dropbox link and this file contains a 404 page or you used git clone without git-lfs installed.

[–] PrivateNoob@sopuli.xyz 1 points 1 year ago

Absolutely right, I have only used git clone. Thank you for showing git-lfs, never heard of it before.