VirtualBox 6.1.36 - has VM Mac OS X Options

[lse123]

In Windows 11 after installing: VirtualBox 6.1.36 - take a look and saw that has VM Mac OS X Options

Can use as VM the macOS VM...????

[scottgus1]

A Mac guest is only allowed if the physical computer is real Apple hardware.
OSX guests on non-Apple hardware

Anytime we have help requests on a Mac guest we also need the guest's vbox.log, zipped and uploaded using the forum's Upload Attachment tab. If the physical computer is not an Apple computer, then we cannot help and have to lock the topic.

[lse123]

Thanks for your reply

As i remember well i have download VirtualBox Windows version

Since,
I am in Windows, isn't have to Not having MacOS guest options like prior versions of VirtualBox...?

[BillG]

It really has nothing to do with VirtualBox. It is a matter of Apple licensing.

You cannot legally run OSX on a non-Apple device - not even as a virtual machine.

[lse123]

1
YES,
I know this
but
I think old versions of Virtual Box for windows DOES NOT HAVE an Option for macOS - because of this... why this version have, as you can not install as VM the macOS...?

2
Is the FydeOS-VMware-v15.0-Preview1.ova ONLY for VMware, or does it need SSD??? I have tried importing with VirtualBox [host Windows 11] ... HDD...

Failed to import appliance E:\ISOs\FydeOS-VMware-v15.0-Preview1.ova.

Error reading "E:\ISOs\FydeOS-VMware-v15.0-Preview1.ova": Host resource of type "Other Storage Device (20)" is supported with SATA AHCI controllers only, line 48 (subtype:vmware.nvme.controller).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}

screenshot here:

[mpack]

I think old versions of Virtual Box for windows DOES NOT HAVE an Option for macOS

That would be incorrect. VirtualBox is a cross platform Qt app, the menu items are the same for everybody - and always have been. If creating MacOS guests on Windows hosts was previously disabled in the software then why do you suppose we have those FAQ links telling people not to?

Regarding your appliance, the error message is telling you that it configures an unsupported combination of hardware features (basically "Other storage device" looks wrong and the choice of nvme is unusual). ... but I don't see what this has to do with the MacOS question. Please keep to one question per topic.

[lse123]

Yes, the second Question is another topic

Can you suggest anything to try, ... for this second topic...? may PC is too old ... btw is over a decade years old... just experimenting...

[lse123]

In addition, is any way edit file.ova...?

[mpack]

An OVA is just a tar archive, it can be unpacked using most archiving tools. It contains an OVF file which contains the recipe for the VM and which VirtaulBox also accepts for import purposes. The appliance package also contains a compressed VMDK which you should not attempt to use directly. However as a last resort it can be cloned to VDI (which ensures that it is uncompressed) and from there you can create the VM recipe manually.

[lse123]

Do you have any idea, how make the fileVMware.ova compatible with VirtualBox,...? I think is a Vmware Workstation pro 16.x ova file...

[mpack]

Sorry, no. I don't use VMWare, or OVAs, I have never used an nvme controller and don't know what the effect would be of changing it. But there is no harm for you in finding out. I would export another (working) VM to examine and use as a reference.

[lse123]

Vmware Workstation pro 15.x
TRIED ON VMWARE SUCCESS --- I think is only for vmware

[mpack]

It stands to reason that an OVA created to be compatible with VMWare is compatible with VMWare. But that doesn't mean it can't be made to work elsewhere - which I gathered was the point at issue in the latter part of this discussion?

Actually, this topic is a mess. The topic title does not match the current discussion. I'm going to lock this topic now, if you want to continue the discussion then please create a new topic with an appropriate title and stick to the subject indicated by the title.