I was running a VM on a different machine and needed to change machines because WSV3 would not run with virtualization enabled.
When I try to start the VM, it hangs with the following errors:
Virtual Box: Version 7.2.0_BETA1 r169020 (Qt6.8.0 on windows)
Windows: Windows 11 Pro Insider Preview 27881.1000
(Same as on the previous system)
Any suggestions?
VM: Not loading
Moderator: Mattk
Re: VM: Not loading
When I get you right it was working and when porting a snapshot to a new VM environment it does not work anymore? Can you build from scratch (as your snapshot might be faulty or at least incompatible with the new host)?
Re: VM: Not loading
Yes, I can build from scratch. Thanks for the suggestion.
Meteobridge VM | GW3000
-
AA5H_AX088
- Junior Boarder
- Posts: 36
- Joined: Mon May 12, 2025 7:10 pm
Re: VM: Not loading
I realize this post is three weeks old, but here’s some info to help others in the future.
For what it’s worth, I’ve hit this same error during VM builds with both Proxmox and Synology VMM
It occurs right after the VM provisions the virtual NIC card: spanning-tree checks for Ethernet loops, once complete the port changes from a blocking to forwarding state, at that point a DHCP request is sent, and a timer set for a DHCP reply. If no DHCP packet is received at timer expiration, vm virtual adapters will fallback to 127.0.0.1; IPv6 can usually self-set fast enough for the script to complete, but IPv4 dhcp timers are too slow for most vm scripts.
The Meteobridge VM boot process will hang until a DHCP response is provided from the network. Attach a laptop with wireshark on your
LAN segment to view the DHCP transactions, verify your DHCP server’s scope is functioning and the server is reachable on the same lan segment/VLAN.
I’m not saying that your issue is 100% the same as mine, but my failure was at the same point in the VM boot process; in my case my dhcp scope was out of addresses, expanding the scope allowed the script to finish.
For what it’s worth, I’ve hit this same error during VM builds with both Proxmox and Synology VMM
It occurs right after the VM provisions the virtual NIC card: spanning-tree checks for Ethernet loops, once complete the port changes from a blocking to forwarding state, at that point a DHCP request is sent, and a timer set for a DHCP reply. If no DHCP packet is received at timer expiration, vm virtual adapters will fallback to 127.0.0.1; IPv6 can usually self-set fast enough for the script to complete, but IPv4 dhcp timers are too slow for most vm scripts.
The Meteobridge VM boot process will hang until a DHCP response is provided from the network. Attach a laptop with wireshark on your
LAN segment to view the DHCP transactions, verify your DHCP server’s scope is functioning and the server is reachable on the same lan segment/VLAN.
I’m not saying that your issue is 100% the same as mine, but my failure was at the same point in the VM boot process; in my case my dhcp scope was out of addresses, expanding the scope allowed the script to finish.