[GRLUG] No network in VB

[Grand Rapids Linux Users Group]

Thanks. I'll try it. Should that have different results than running 
these 2 commands after the kernel loads?

sudo modprobe -r kvm_intel

sudo modprobe -r kvm


Eric Beversluis
www.ericbeversluis.com
2x Honorable Mention--Writer's Digest Contest


On 2/17/25 8:43 AM, Grand Rapids Linux Users Group wrote:
> Does it work if you blacklist the KVM modules and reboot?
>
> Warm Regards,
> Kyle Maas
>
>
>
> On 2/16/25 10:18 PM, Grand Rapids Linux Users Group wrote:
>> I agree with Kyle certain kinds of Linux support being less needed, 
>> but new things keep cropping up.
>>
>> In last December, my Win 10 VM running in VirtualBox 7.x on Fedora 40 
>> suddenly lost network connectivity.
>> Windows tells me: "Unidentified Network/No network access."
>>
>> From the command prompt:
>>
>>         Microsoft Windows [Version 10.0.19045.5131]
>>         (c) Microsoft Corporation. All rights reserved.
>>
>>         C:\Windows\system32>ping 192.168.0.1 [My wireless router]
>>
>>         Pinging 192.168.0.1 with 32 bytes of data:
>>         PING: transmit failed. General failure.
>>         PING: transmit failed. General failure.
>>         PING: transmit failed. General failure.
>>         PING: transmit failed. General failure.
>>
>>         Ping statistics for 192.168.0.1:
>>             Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>>
>>         C:\Windows\system32>
>>
>>         C:\Windows\system32>ipconfig
>>
>>         Windows IP Configuration
>>
>>
>>         Ethernet adapter Ethernet:
>>
>>            Connection-specific DNS Suffix  . :
>>            Link-local IPv6 Address . . . . . :
>>         fe80::a6c5:72ec:2bb3:85b4%11
>>            Autoconfiguration IPv4 Address. . : 169.254.244.232
>>            Subnet Mask . . . . . . . . . . . : 255.255.0.0
>>            Default Gateway . . . . . . . . . :
>>
>>         Ethernet adapter Ethernet 2:
>>
>>            Connection-specific DNS Suffix  . :
>>            Link-local IPv6 Address . . . . . :
>>         fe80::5e36:9bde:16cf:301c%15
>>            Autoconfiguration IPv4 Address. . : 169.254.223.53
>>            Subnet Mask . . . . . . . . . . . : 255.255.0.0
>>            Default Gateway . . . . . . . . . :
>>
>>
>> I haven't been able to find anything that restores the internet 
>> connectivity. In fact, when I tried opening an earlier snapshot of 
>> the Windows VM, one from a time at which there was internet 
>> connectivity, that snapshot now also had no internet connectivity.
>>
>> Also, I thought maybe the December Windows updates had caused the 
>> problem. But rolling back the updates in the VM did not help.
>>
>> One idea has just come to me. About the same time the VM network 
>> failed, I started getting warnings that
>> "VirtualBox can’t operate in VMX root mode." I found that running 
>> these two commands turn off KVM without needing to recompile the kernel:
>>
>> sudo modprobe -r kvm_intel
>>
>> sudo modprobe -r kvm
>>
>> This seems to work fine until the next time I reboot the computer. 
>> Then I have to run it again.
>>
>> Is there any chance that this step, to turn off KVM, somehow 
>> interferes with the VB VM network connectivity?
>> Does anyone have any suggestions for other solutions?
>>
>> Thanks.
>>
>>
>>
>>
>> -- 
>> Eric Beversluis
>> www.ericbeversluis.com
>> 2x Honorable Mention--Writer's Digest Contest
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20250217/ad8f78d1/attachment.htm>