![]() ![]() I don't know what the v.gui = true config does, but I would assume it tries to make some kind of frame buffer available for the graphics system to connect to, and there should not be any such activity taking place, that I know of. ![]() I just created a plain server image with no gui packages installed. I think I removed all lock files I could find, at least.Īlthough I can see the VM has booted with the GUI enabled. => default: Waiting for the VM to receive an This is very promising! At least that's the farthest I have seen anyone come to something working, at least □ Btw, this "Error: The file is already in use" thing, is this somehow caused by me not creating the box properly or is it something else? It's my second attempt at creating a box (all related to this issue), but I just followed a general guide, but I might have missed something. WARNING: config.vm.provider :vmware_desktop do |vmware| WARNING: If networking fails to properly configure, it may require this VMX setting. WARNING: prevent proper networking setup. Vagrant will stop overwriting this setting in an upcoming release which may WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant => default: Verifying vmnet devices are healthy. => default: Cloning VMware VM: 'fatso83/impish64-arm'. Vmware fusion m1 ubuntu download#Parallels got here a year ago, so they have at least some arm boxes.ĪFAIK, it seems the most likely route is to download the ARM image for Ubuntu and create a box based on that.īringing machine 'default' up with 'vmware_desktop' provider. ![]() There are no images for ARM supported by the vmware provider.It does not help that an image is available for the vmware_desktop provider, if the underlying architecture itself is unsupported. The vmware provider should be able to tell the user that the cpu platform is unsupported for that box, just like the Fusion Desktop product tells me. "Some error occurred" is not really helping anyone.This should be fixed in the Vagrant Cloud interface. I cannot tell if a box is x86-64 or ARM64 when it is called bionic64. There is no metadata for the Vagrant boxes available that tells me what the underlying architecture is.There are three issues here from a user perspective that needs to be fixed: I am suspecting this basically comes down to dealing with running an unsupported architecture (running x86-64 on ARM64), as mentioned in VMWare knowledge article 84273.įor instance, using VMware Fusion, an Arm Linux guest must be created and run on an Apple silicon Macintosh, not an X86_64 Macintosh. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |