Lỗi the virtual device got not ip address năm 2024

Unfortunately, It is not working, I tried Bridge mode with Nat enabled and disabled in adapter 2, Nothing. I deleted host-only completely. But still receiving same error.

Luckily i had backup of Genymotion VM (moto x ) that i created when i uninstalled it, (Thought it would delete VM too, but it didn't, So didn't need to download it again)

I'd backup of genymotion i've Old log files when my genymotion vm was working with Virtualbox, They are Logcat.txt and vbox.log

Here it's seems to offer DHCP

##################################################### Start Logcat.txt

Code:

--------- beginning of /dev/log/main
D/DHCP    (   70): ===== DHCP message:
D/DHCP    (   70): op = BOOTREQUEST (1), htype = 1, hlen = 6, hops = 0
D/DHCP    (   70): xid = 0x330c0000 secs = 0, flags = 0x8000 optlen = 14
D/DHCP    (   70): ciaddr = 0.0.0.0
D/DHCP    (   70): yiaddr = 0.0.0.0
D/DHCP    (   70): siaddr = 0.0.0.0
D/DHCP    (   70): giaddr = 0.0.0.0
D/DHCP    (   70): chaddr = { 08  00  27  4d  57  9a }
D/DHCP    (   70): sname = ''
D/DHCP    (   70): file = ''
D/DHCP    (   70): op 53 len 1 { 01 } discover
D/DHCP    (   70): op 55 len 4 { 01  03  06  1c } 
D/DHCP    (   70): ===== DHCP message:
D/DHCP    (   70): op = BOOTREPLY (2), htype = 1, hlen = 6, hops = 0
D/DHCP    (   70): xid = 0x330c0000 secs = 0, flags = 0x0000 optlen = 312
D/DHCP    (   70): ciaddr = 0.0.0.0
D/DHCP    (   70): yiaddr = 192.168.56.101
D/DHCP    (   70): siaddr = 0.0.0.0
D/DHCP    (   70): giaddr = 0.0.0.0
D/DHCP    (   70): chaddr = { 08  00  27  4d  57  9a }
D/DHCP    (   70): sname = ''
D/DHCP    (   70): file = ''
D/DHCP    (   70): op 53 len 1 { 02 } offer
D/DHCP    (   70): op 54 len 4 { c0  a8  38  64 } 
D/DHCP    (   70): op 51 len 4 { 00  00  0e  10 } 
D/DHCP    (   70): op 1 len 4 { ff  ff  ff  00 } 
D/DHCP    (   70): --- dhcp offer (2) ---
D/DHCP    (   70): ip 192.168.56.101 gw 0.0.0.0 prefixLength 24
D/DHCP    (   70): server 192.168.56.100, lease 3600 seconds
D/DHCP    (   70): ===== DHCP message:
D/DHCP    (   70): op = BOOTREQUEST (1), htype = 1, hlen = 6, hops = 0
D/DHCP    (   70): xid = 0x340c0000 secs = 0, flags = 0x8000 optlen = 26
D/DHCP    (   70): ciaddr = 0.0.0.0
D/DHCP    (   70): yiaddr = 0.0.0.0
D/DHCP    (   70): siaddr = 0.0.0.0
D/DHCP    (   70): giaddr = 0.0.0.0
D/DHCP    (   70): chaddr = { 08  00  27  4d  57  9a }
D/DHCP    (   70): sname = ''
D/DHCP    (   70): file = ''
D/DHCP    (   70): op 53 len 1 { 03 } request
D/DHCP    (   70): op 55 len 4 { 01  03  06  1c } 
D/DHCP    (   70): op 50 len 4 { c0  a8  38  65 } 
D/DHCP    (   70): op 54 len 4 { c0  a8  38  64 } 
D/DHCP    (   70): ===== DHCP message:
D/DHCP    (   70): op = BOOTREPLY (2), htype = 1, hlen = 6, hops = 0
D/DHCP    (   70): xid = 0x340c0000 secs = 0, flags = 0x0000 optlen = 312
D/DHCP    (   70): ciaddr = 0.0.0.0
D/DHCP    (   70): yiaddr = 192.168.56.101
D/DHCP    (   70): siaddr = 0.0.0.0
D/DHCP    (   70): giaddr = 0.0.0.0
D/DHCP    (   70): chaddr = { 08  00  27  4d  57  9a }
D/DHCP    (   70): sname = ''
D/DHCP    (   70): file = ''
D/DHCP    (   70): op 53 len 1 { 05 } ack
D/DHCP    (   70): op 54 len 4 { c0  a8  38  64 } 
D/DHCP    (   70): op 51 len 4 { 00  00  0e  10 } 
D/DHCP    (   70): op 1 len 4 { ff  ff  ff  00 } 
D/DHCP    (   70): --- dhcp ack (5) ---
D/DHCP    (   70): ip 192.168.56.101 gw 0.0.0.0 prefixLength 24
D/DHCP    (   70): server 192.168.56.100, lease 3600 seconds
D/DHCP    (   70): configuring eth0
D/NetUtils(   70): Don't create null default route on eth0
E/vinput-seamless(  107): found PS2 device
E/vinput-seamless(  107): found seamless mouse device
I/installd(  119): installd firing up
--------- beginning of /dev/log/system

################################################## Logcat.txt finish

It seems to get different IP address in Vbox.log (i don't know why ?. maybe it's something different)

Genymotion is an amazing tool to speed up Android development and testing. It is much faster and stable than those crappy and slow Android AVD that Google still can’t get to work right almost a decade since Android was released.

However, there is one very common issue that plagues Genymotion from time to time, which is the unfamous “The virtual device got no IP address” error when starting the emulator.

Genymotion runs on top of VirtualBox and use its infrastructure and virtualization support in order to run Android, including all networking. From reasons that are not very clear (to me), sometimes it fails to assign an IP address to the device, and gives the following message:

The virtual device got no IP address

How to fix it

There are countless posts about it in the interwebs (including this one). The solution – or, better, workaround – that works most of the time for me is to remove the network adapter from VirtualBox, and let Genymotion recreate it in the next run. Here’s what you have to do:

Open Virtualbox and go to “File » Preferences” (CTRL+G), then head over “Network » Host-only adapters“, and click the “minus” button. Confirm it, and try to start the emulator again.

Remove the network adapter

Ps: if you have more than one network adapter, remove them all.

Confirm

This trick is not 100% effective, but work mot of the time. Sometimes, as a last resort, I restart my computer after the adapter is removed.