virtualbox.org

Hiho,
just wanted to check, if somebody else has the problem. Since a few releases (Not sure since when exactly), I get network errors with my Killer Networking card. The Problem does not happen with the same VM on the same hardware on Debian Testing.
I tried to remove all Killer Software and also disabled the Killer tunings, nogo.
Under Debian now my Virtualbox also refuses to work anymore, since a dependency to python 2 removes the package, which is sad, since python 3 should be the real requirement.
I tried to remove the python2 dependencies and also removed the python dependency in the dpkg status, but it won't work, also not --ignore-deps.
Any chance for a hint or a fix here?
Cheers,
Kee.
Edit:
The deactivation of Hyper-V did the job, I guess, two virtualizations aren't the best idea. I never activated hyper-v, but Windows pro did that.
Thanks a ton for the solution!!

Sounds like you have a Debian PC with Virtualbox installed, which should be in Linux hosts, not Windows Hosts. If I read wrongly please let us know and we'll move this again appropriately.

At the present moment Python 2 is a required dependency of Virtualbox and as best as I see from the manual cannot be removed on a Linux host. Though Python 2 has been deprecated, many businesses will likely use it for some time, and it will be Oracle's business customers that will keep in or drive out Python 2 from Virtualbox. It should be possible to let Python 2 be in a computer but force Python scripts to always run on Python 3.

I have heard of 'Killer' network parts and drivers, but the forum does not mention them much for some time that I have noticed. A vbox.log and guest .vbox 'recipe' file during the issue might help.

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Also, right-click the guest in the main Virtualbox window's guest list, choose Show in Explorer. Zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab.

Thank you for your reply, it is very much appreciated.
Maybe I should have created two of those Forum Posts. I have a Windows 10 and a Linux Debian bullseye in the same laptop installed.
Both installations do carry a Virtualbox installation and are running a Linux Mint guest (actually the same). The latest patches of bullseye removed virtualbox 6.1, because of dependency problems with python2. Debian maintainer are sometimes rough, when it's about depreciated stuff, at least on testing. It is actually not that hard to include also python3 as alternative, but well, it is yet testing and not yet stable. You will run into the problem again, when bullseye gets released.
Linux was working fine, until the python dependency problem, I wanted to make sure, the Killer Networking Problem is not a hardware problem.
Back to my Windows Killer Networking problem:
I will collect that log for the Linux Mint guest, hopefully one can see my problem. I see broken packages, downloads fail the md5sum check.
I will update this a bit later.
Update:
There are my logs for the Mint Box under Windows 10.
Thanks again for your help.

The Windows host OS has Hyper-V enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active). (The new test builds might have a fix for this problem. If you try a test build and it works, report here: viewtopic.php?f=6&t=90853, and save the installer file.)

The Test builds didn't work, because of secure boot, which is activated on my rig. But deactivation of hyper-v did the job. Thanks a ton.

Great! Glad you're up and running.