virtualbox.org

Hello all,
I have seen a few discussions similar to this topic but none that have helped. My issue is my host machine can and will connect to the internet, but my guest machine, through Virtualbox VM cannot. When I check the status of my bridged connection it doesn't show any traffic either way and when I check the status on my host machine it shows traffic moving through it. My main reason for trying to set this up is for Home Assistant with hassos on a virtual machine. I get all the way to connecting through the hassos.local page and it never finishes the configuration process. Any ideas would be great. Thanks!

There is nothing magical about the way networking goes in a VirtualBox guest. Have you done the normal networking checks?

If you are using bridged networking, does the guest get a sensible IP and gateway address (hint - compare it to the host's config). If that looks reasonable, can you ping the gateway? If you can ping the gateway, can you ping an valid Internet address like 8.8.8.8 ?

There's no proper way to answer this until you reveal what the guest OS is. Typically people ask this question right after installing XP and discovering that in fact, network access works just fine, but the built-in Internet browser is two decades obsolete.

BillG wrote:There is nothing magical about the way networking goes in a VirtualBox guest. Have you done the normal networking checks?

If you are using bridged networking, does the guest get a sensible IP and gateway address (hint - compare it to the host's config). If that looks reasonable, can you ping the gateway? If you can ping the gateway, can you ping an valid Internet address like 8.8.8.8 ?

Bill how would I check and or ping through the Ubuntu interface? When I start my VM for the hassos it loads but doesnt seem to fully configure on the VM. If I try and access the command section it just asks for user name and password, in which I can enter the generic root for user and gain access to the hassos info. But I cannot access any network info from there it tells me invalid command. Thanks again for the response.

mpack wrote:There's no proper way to answer this until you reveal what the guest OS is. Typically people ask this question right after installing XP and discovering that in fact, network access works just fine, but the built-in Internet browser is two decades obsolete.

Mpack the main OS is WIN 10 and the guest is Linux Ubuntu. My main goal is just to get a VM with home assistant on it running off my main computer. Thanks for the reply.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab.

scottgus1 wrote:Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab.

Scott I believe I have added the attachment

As long as your host has access to the local network and you remember to set the networking option to bridged, Home Assistant should work fine.

Are you on a wireless network? VirtualBox has trouble with some wireless networks. The only other problem I am aware of was a very strange problem which took a lot of tracking down.

viewtopic.php?f=6&t=100860

Hassos on my system gets its IP from DHCP just like the other physical and virtual machines on the LAN.

JonE, you sent a vbox.log file, not the .vbox file. Try my instructions again, please.

scottgus1 wrote:JonE, you sent a vbox.log file, not the .vbox file. Try my instructions again, please.

Sorry Scott, when I followed your instructions the files that populated were .vbox-prev (which you didn't want) and a .nvram file which I figured was not the .vbox. The only place I thought I saw one was the one I uploaded. I will upload a picture of what I am able to send/open when I right click and show in explorer.

Your Windows host is set to hide known extensions. Configure it to show all extensions and you'll find the .vbox file.

scottgus1 wrote:Your Windows host is set to hide known extensions. Configure it to show all extensions and you'll find the .vbox file.

Scott, again sorry for being ignorant but how would I do that?
Never mind I found it but it did not change anything the same files are the only ones I see.

Web-search for it, please, it's common Windows stuff.

He's definitely bridging to a wireless NIC.

00:00:04.569166 Network <string> = "HostInterfaceNetworking-Intel(R) Dual Band Wireless-AC 8260" (cb=60)

Before we go thinking up weird and complex problems, I'm wondering if it isn't something simple: could there be more than one WiFi on this PC? Could the VM be bridging to the wrong one?

Also, I see that the VM is on drive D while the primary VDI is in the Downloads folder in drive C. This is not a stable, long term solution, in fact it's a future disaster waiting to happen. The VDI needs to be inside the VM folder. And hopefully D is still an internal drive.

As a temporary solution or test, I would suggest plugging this PC directly into the router using an Ethernet cable. Then bridge to the PC's Ethernet NIC. That should definitely work. If it still doesn't work then it's a problem of the network config, not a VirtualBox config problem.

That would be my first move too.

@scottgus1@JonE Even if the extensions are not displayed, the .vbox file is pretty easy to see. It has a blue box and the file type is VirtualBox Machine Definition. It is quite clearly shown in the screenshot posted by JonE.