M1/M2 Mac 7.04 Host Adapter

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
redpath
Posts: 2
Joined: 28. Nov 2022, 19:21

M1/M2 Mac 7.04 Host Adapter

Post by redpath »

Network Host Adapter is deprecated and so Network was setup for adapter. But the docker-machine command and the starting of VM complain No Network Host Adapter?
The network settings was set and I noticed the setup page has the DNS stuff removed and I assume not needed anyway.

So anyone get this VM to work on MacOS M1 running Monterey?
What do I need to do here iMac (24-inch, M1, 2021).
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: M1/M2 Mac 7.04 Host Adapter

Post by scottgus1 »

redpath wrote:Network Host Adapter is deprecated
I'm going to guess that you mean "Host-Only", since that's the only Virtualbox network type with the word "host" in it. Proper terminology can help others help you. If you did not mean Host-Only, please clarify.

The Changelog says that 7.0.0 had trouble with Internal networking, and that 7.0.2 reintroduced Internal. If Internal is the structure on which Host-Only works, then a problem could be there. I don't know if Host-Only is or is not working in 7.0.4.
redpath wrote:so Network was setup for adapter
Again, terminology. Every Virtualbox network type has an adapter in the VM, and some use host adapters. What exactly is the Virtualbox network type you mean here?
redpath wrote: anyone get this VM to work on MacOS M1 running Monterey?
This is a BBBBIIIIIGGGGG problem. See the M1/M2 Sticky on Mac Hosts. This project may be a dead end, unless the VM OS is a really old 32-bit Linux.
redpath wrote:the docker-machine command
Virtualbox influenced by other driver apps like Docker aren't supported here. Docker supports their VMs. You can demonstrate the problem on a Virtualbox-only-controlled VM, then we may be able to help.

But that M1 is a hump over which we may not be able to pass.
redpath
Posts: 2
Joined: 28. Nov 2022, 19:21

Re: M1/M2 Mac 7.04 Host Adapter

Post by redpath »

Okay fair enough, the Devil is in the details.

1) I installed VirtualBox 7.0.2 and the extension Pack
2) I have a template setup for Host-only Networks using the
Network settings page and fields say
Mask 255.255.255.0
Low 192.168.56.1
Upper 192.168.56.199

3) I use this command to create the virtual machine

docker-machine create --driver virtualbox --virtualbox-no-vtx-check linuxdefault

Running pre-create checks...
Creating machine...
(linuxdefault) Copying /Users/richardredpath/.docker/machine/cache/boot2docker.iso to /Users/richardredpath/.docker/machine/machines/linuxdefault/boot2docker.iso...
(linuxdefault) Creating VirtualBox VM...
(linuxdefault) Creating SSH key...
(linuxdefault) Starting the VM...
(linuxdefault) Check network to re-create if needed...
(linuxdefault) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed:
(linuxdefault) 0%...NS_ERROR_FAILURE
(linuxdefault) VBoxManage: error: Failed to create the host-only adapter
(linuxdefault) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(linuxdefault) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(linuxdefault) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 105 of file VBoxManageHostonly.cpp
(linuxdefault)
(linuxdefault) This is a known VirtualBox bug. Let's try to recover anyway...
Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

4) Though It shows up nicely on the virtualBox GUI as entry linuxdefault
The settings say
Type Linux
Version Linux 2.6 / 3.x /4.x /5.x (64-bit)

Network settings says NAT
Enable Network Adapter (checked)
Attached to: NAT
Advanced Intel PRO/1000 MT Desktop (82540EM) <== ?? Intel??


5) I try to start it on the VirtualBox GUI and it says in the Log

00:00:01.104702 GIM: Using provider 'KVM' (Implementation version: 0)
00:00:01.104714 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:01.104760 AssertLogRel /Users/vbox/tinderbox/mac-rel/src/VBox/VMM/VMMR3/GIMKvm.cpp(302) int gimR3KvmInit(PVM): RT_SUCCESS_NP(rc)
00:00:01.104770 VERR_UNSUPPORTED_CPU (-1002) - Unsupported CPU.
00:00:01.105351 VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/VMM/VMMR3/VM.cpp(336) int VMR3Create(uint32_t, PCVMM2USERMETHODS, PFNVMATERROR, void *, PFNCFGMCONSTRUCTOR, void *, PVM *, PUVM *); rc=VERR_UNSUPPORTED_CPU
00:00:01.105355 VMSetError: Unsupported CPU.
00:00:01.105870 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Unsupported CPU. (VERR_UNSUPPORTED_CPU)}, preserve=false aResultDetail=-1002
00:00:01.106068 Console: Machine state changed to 'PoweredOff'
00:00:01.108010 Power up failed (vrc=VERR_UNSUPPORTED_CPU, rc=NS_ERROR_FAILURE (0X80004005))
00:00:01.503156 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:01.503216 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (setVideoModeHint)}, preserve=false aResultDetail=0
00:00:01.503256 GUI: Aborting startup due to power up progress issue detected...
00:00:01.503307 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.514490 GUI: UICommon: Commit data request...
00:00:01.527594 GUI: UICommon: Handling aboutToQuit request..
00:00:02.238298 GUI: UICommon: aboutToQuit request handled!


6) I remove the linuxdefault virtualbox

docker-machine rm linuxdefault

and indeed it is removed in the VirtualBox GUI

7) SO I DECIDE to create a virtualbox using the GUI only.
I open the Network Settings and see this option which does not allow me to select a network I created.
Host-only Adapter [DEPRECATED]

So lots of stuff has changed.

I basically want to use the VirtualBox to enable use of a USB from a Docker image which was
possible under the INTEL Apple not an Apple M1.

SO any instructions would be nice to have as lots of stuff has changed
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: M1/M2 Mac 7.04 Host Adapter

Post by scottgus1 »

redpath wrote:2) I have a template setup for Host-only Networks using the
Network settings page and fields say
Mask 255.255.255.0
Low 192.168.56.1
Upper 192.168.56.199
Here is possibly one problem: If Low and Upper refer to the Host-Only DHCP range, and no typos are present, then Low is too low. 192.168.56.1 is the default IP address of the Host-Only network adapter on the host OS. You can't also serve that same IP address in the network. A Low of 192.168.56.100 is the default for the DHCP range.
redpath wrote:Host-only Adapter [DEPRECATED]
This may be a bigger problem. Virtualbox 7.0 is having to jump through hoops on Apple's new no-kexts Mac OS, so somethings may not work for a while.
redpath wrote:I basically want to use the VirtualBox to enable use of a USB from a Docker image which was
possible under the INTEL Apple not an Apple M1.
redpath wrote:00:00:01.105355 VMSetError: Unsupported CPU.
This is back to the BBBBIIIIGGGG problem. M1/M2 Virtualbox is really not going to work well yet, not for some time. There might be some nuances in the "Unsupported CPU" aspect, but I can't remember what at this moment.

Essentially, you'll need to get a different host computer for this project.


***********************
One other thing:
redpath wrote:Advanced Intel PRO/1000 MT Desktop (82540EM) <== ?? Intel??
Yes, that's OK. Virtualbox simulates a couple Intel network cards. The VM 'hardware' can be different than the host hardware.
Post Reply