vpn

[scottgus1]

not able to start any vbox instance. admittedly, i am no expert a may have gone beyond my means. was looking to set up a vpn on aws, first in the guest without success then on the host. did some code edits in admin to change windows so i could use Linux. not sure if the edits to use ubuntu in windows were the problem or an upgrade of vbox. what is the problem and or solution?

(Mod edit: the walls of text and clipped logs unfortunately don't help. Zipped files can be uploaded and a zipped log almost always fits.)

[scottgus1]

Please right-click the VM in the main Virtualbox window's VM list, choose Show Log.

Search the far left tab's log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

[7787]

"Or it might guru-meditate..." Lol, LOL
Was advised a reinstatement of windows on the host would work, is that correct?
Did the reg edits and no luck (was that a reversion back to before I enabled hyper-v on the host), what next?

[7787]

reinstalled windows 10 on the host, fixed the windows problems and i thought i had ubuntu 20.04 working. when i turned off and started the Linux guest -- after updates and other maintenance -- it would not start after the login password screen (tried changing to any other paravirtualization interface but that did not work) , what can i do?

[mpack]

We await a zipped log, as asked above.

[7787]

sorry, i deleted the instance and started agian, the logs are all gone now. still having a world of problems. ubuntu will ask for a password than just a black screen ( i think waiting for command line inputs but the keyboard is not captured). Been looking at an cloud machine because I think part of my problem is I am reaching the Max of my memory physically, would that help?

[scottgus1]

You don't have the offending "Attempting fall back to NEM", so the usual suspect for your origianl problem "not able to start any vbox instance", if described correctly, is not caused by Hyper-V on the Windows 10 host PC.

However:

00:00:04.525426 Installed Extension Packs:
00:00:04.525436 Heidenhain VBoxJHIO Extension Pack (Version: 4.3.0 r6; VRDE Module: )

What on God's green earth is this?
Try uninstalling this extension pack as a test, reboot, then try Virtualbox again.

00:00:04.682450 Guest OS type: 'Ubuntu_64'
Paravirtualization:
00:00:05.316453 GIM: Using provider 'HyperV' (Implementation version: 0)

The VM's System settings, Acceleration tab, Paravirtualization Interface has been modified from the default. Modify it back. Ubuntu definitely does not speak Hyper-V. Default or KVM should work.

Send us a new log if you change these and still have troubles.

[scottgus1]

To be clear I did have that NEM issue and reset windows.

as for clearing, can not start to get rid of the offending party so I think I will try another distro.

[scottgus1]

can not start to get rid of the offending party

Which is "the offending party" and what trouble are you having?

[mpack]

I can tell you that random and irrelevant settings changes (such as telling Ubuntu that it has to use a Windows hypervisor API) are not going to lead to a stable VM. You would be well advised to stick to a standard template until you know what the settings mean, and then only change them when you already know what the result will be.

As to the extension pack, the only reference I can find is this one:
https://www.heidenhain.de/de_DE/service ... rtual-box/

Unless you need the "bin programming" (CNC?) feature provided by Heidenhain, this "extension pack" should be deleted immediately, if for no other reason than it's clearly intended for VirtualBox 4.3.0, not VirtualBox 6.1.18.

[7787]

Good day. the extension for this cnc simulation program is gone, these type of programs was the reason i first started with virtualbox but the way they list program is not clear. was not aware of which one i was trying to start, in any case part of the appeal of vbox is you can brake the machine without destroying your computer, i want things to work but that is still my mindset; nevertheless, i will be more careful.

[scottgus1]

Is your VM working now?

If not, please post a new vbox.log.

[7787]

yah, thanks, windows work. i gave up on ubuntu and started a fedora vm, deleted all the old. good day.