virtualbox.org

Windows server 2012. Virtualbox 5.2
Виртуальный диск с Ubuntu 20.04
Физический сетевой адаптер Intel(R) 82579LM Gigabit. Нет возможности пустит виртуальную ОС в сеть. Перепробовал Мост, НАТ, и т.д.. ни чего не выходит. Адаптер на Ubuntu активирован. Получение ip адреса динамическое, т.е. адрес должен получить по сети. Куда еще копать - не знаю. Пробовал перекинуть виртуальный диск на другой компьютер с Windows 10, там все заработало.

"Network doesn't work"

Windows server 2012. Virtualbox 5.2
Virtual disk with Ubuntu 20.04
Intel(R) 82579LM Gigabit physical network adapter. No way to let the virtual OS into the network. Tried bridging, NAT, etc... nothing works. Adapter on Ubuntu is activated. Get ip address is dynamic, ie, the address must get on the network. Where else to dig - do not know. I tried to transfer virtual drive to another computer with Windows 10, everything worked there.

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

обновил версию до 5.22.44

Note that the entire 5.2.x branch is obsolete and support for it ended in July 2020.

VirtualBox VM 5.2.44 r139111 win.amd64 (Jul 9 2020 19:02:39) release log
...
00:00:02.594233 Oracle VM VirtualBox Extension Pack (Version: 5.2.20 r125813; VRDE Module: VBoxVRDP)

It is not allowed for the extension pack version to differ from the software it extends. I don't know if that would cause your problem - presumably not since I assume you had the problem before the upgrade.

00:00:02.648678 File system of 'D:\Virtual\Zabbix\VMware\convert\zabbix.vdi' is ntfs

That filename implies that this disk is not originally part of this VM, but was converted from a VMware VM. Did the VirtualBox VM ever work? Also it is not good idea for the VDI to be outside the VM folder. If disk space is a problem then you should locate the entire VM on the other drive.

The configuration of your network (Bridged Networking) looks fine for me. The language barrier is making it a little difficult for me to properly understand the nature of the problem. As I understand it, networking in fact does work, you are being assigned an IP address by DHCP on your physical network which would not happen unless you can successfully communicate with the network.

I have tried all network connectivity options in VirtualBox. In all modes, the network is not available. There was also a problem in 5.2.22. There was no such problem on another PC with Windows 10 operating system with vmware. But here I can’t deploy VMware, so I did the conversion.

It doesn't really make sense that ALL networking modes fail (not available). For example NAT mode simply uses the host Internet connection, so the only way that can fail is if the host itself does not have an Internet connection.

What do you want to do with the network? NAT is fine for basic Internet. It's only if you wanted to set up a server inside the VM, or enable printer/folder sharing that you need to get more complex.

How have you determined that the network is not available?

All modes do not work. More precisely, they do not give the virtual server an exit. There is a connection on the server where VirtualBox is running. I connect to it remotely. NAT would suit me, but it does not work either.