Bug 234878 - emulators/virtualbox-ose: Update to 6.1
Summary: emulators/virtualbox-ose: Update to 6.1
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: vbox
URL:
Keywords: needs-patch
Depends on:
Blocks:
 
Reported: 2019-01-11 18:26 UTC by kunda
Modified: 2020-07-01 02:26 UTC (History)
33 users (show)

See Also:
tobik: maintainer-feedback? (vbox)


Attachments
Update to 6.0.4. (85.88 KB, patch)
2019-02-01 18:29 UTC, Jung-uk Kim
no flags Details | Diff
Update to 6.0.6. (136.59 KB, patch)
2019-05-02 20:36 UTC, Jung-uk Kim
no flags Details | Diff
Update to 6.0.8. (141.59 KB, patch)
2019-05-17 01:10 UTC, Jung-uk Kim
no flags Details | Diff
Update to 6.0.8 (rebased) (142.17 KB, patch)
2019-05-17 14:52 UTC, Jung-uk Kim
no flags Details | Diff
Update to 6.0.8 (141.04 KB, patch)
2019-05-30 22:29 UTC, Jung-uk Kim
no flags Details | Diff
Update to 6.0.8 (fixed OpenGL issue) (149.12 KB, patch)
2019-05-31 14:40 UTC, Jung-uk Kim
no flags Details | Diff
Kernel panic (73.34 KB, text/plain)
2019-09-20 16:55 UTC, Mikhail Teterin
no flags Details
VBOX 6.1.0 port (80.53 KB, application/gzip)
2019-12-13 22:32 UTC, Mario Lobo
no flags Details
Update to 6.1.0 (316.25 KB, patch)
2019-12-13 22:50 UTC, Jung-uk Kim
no flags Details | Diff
VBOX 6.1.6 port (80.72 KB, application/gzip)
2020-04-17 14:53 UTC, Mario Lobo
no flags Details
Port of VitualBox 5.2.42 (84.69 KB, application/gzip)
2020-05-20 00:46 UTC, Mario Lobo
no flags Details
VBox 6.1.10 port files (78.40 KB, application/gzip)
2020-06-29 14:21 UTC, Mario Lobo
no flags Details
VBox 6.1.10 kmod port files (2.63 KB, application/gzip)
2020-06-29 14:22 UTC, Mario Lobo
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 VVD 2019-01-28 12:16:43 UTC
Please don't update it till www/phpvirtualbox add support of 6.0 branch.
Comment 2 Jung-uk Kim freebsd_committer 2019-02-01 18:29:24 UTC
Created attachment 201612 [details]
Update to 6.0.4.
Comment 3 VVD 2019-02-01 22:54:07 UTC
Please!!! Make 2 separate ports or wait phpvirtualbox 6.0: https://github.com/phpvirtualbox/phpvirtualbox/issues/154

Initial support already commited, but not released yet:
https://github.com/phpvirtualbox/phpvirtualbox/commit/3a5a1ce787515183788fb2e63ae83c1b00f71ffc
Comment 4 Jung-uk Kim freebsd_committer 2019-02-01 23:49:09 UTC
(In reply to VVD from comment #3)
Don't worry, I heard you. :-)
Comment 5 VVD 2019-02-03 13:51:57 UTC
(In reply to Jung-uk Kim from comment #4)
Thanks! [-:

BTW:
> Please also use version 5.2 if you still need support for 32-bit hosts, as this has been discontinued in 6.0.
https://www.virtualbox.org/wiki/Downloads
Is it mean impossibility to build VirtualBox 6 on 32bit at all, or just Oracle stop make binary packages for 32bit hosts?
Comment 6 Jung-uk Kim freebsd_committer 2019-02-04 18:24:26 UTC
(In reply to VVD from comment #5)
> Is it mean impossibility to build VirtualBox 6 on 32bit at all, or just Oracle stop make binary packages for 32bit hosts?

It builds fine for now.
Comment 7 Matthias Gamsjager 2019-04-17 14:48:21 UTC
But how long are we going to wait for a 3rd party add-on for this port? 
At some point 2 ports have to been made if one is hold hostage by phpvirtualbox imo.
Comment 8 rozhuk.im 2019-04-17 19:19:32 UTC
(In reply to Jung-uk Kim from comment #4)

We can update phpvirtualbox right now, 6.0 support already commited.
They can not do make release for a long time.
Comment 9 Samy Mahmoudi 2019-04-24 16:37:18 UTC
(In reply to Jung-uk Kim from comment #2)

I applied your patch against revision 491653 and compilation went fine on 12.0-RELEASE-amd64.

• Starting a VM graphically gets stuck at a 0% progress bar
• Using vboxmanage is not better: Waiting for VM "Win7" to power on...

While waiting, CPU usage stays close to zero.

I am now rebuilding with DEBUG on...
Comment 10 Samy Mahmoudi 2019-04-24 21:36:22 UTC
(In reply to Jung-uk Kim from comment #2)

With DEBUG on, I got an error at compilation:

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.4/src/VBox/VMM/VMMR3/APIC.cpp:1336:43: error: comparison between
      pointer and integer ('void *' and 'RTR0PTR' (aka 'unsigned long'))
            Assert(pApicCpu->pvApicPageR3 == NIL_RTR0PTR);
Comment 11 Jung-uk Kim freebsd_committer 2019-05-02 20:36:59 UTC
Created attachment 204171 [details]
Update to 6.0.6.
Comment 12 Samy Mahmoudi 2019-05-11 23:40:31 UTC
(In reply to Jung-uk Kim from comment #11)

Thank you for your effort and the time you dedicate to this. It is much appreciated.
Comment 13 Jung-uk Kim freebsd_committer 2019-05-17 01:10:15 UTC
Created attachment 204412 [details]
Update to 6.0.8.
Comment 14 Jung-uk Kim freebsd_committer 2019-05-17 14:52:17 UTC
Created attachment 204430 [details]
Update to 6.0.8 (rebased)
Comment 15 Christoph Moench-Tegeder freebsd_committer 2019-05-27 10:49:33 UTC
Testing that latest patch, I can still reproduce the problems reported in comment #9 - starting a VM (via GUI, via VBoxManage, headless or with GUI - doesn't matter, it's all the same) waits "forever" (I gave up after ~10min latest) without anything relevant happening (when starting the VM via GUI, a progress bar appears after some time (15s? 30s?) but stays stuck at 0%). That affects old VMs carried over from a 5.2 installation, but also newly created VMs.
Comment 16 Samy Mahmoudi 2019-05-27 11:49:06 UTC
(In reply to Christoph Moench-Tegeder from comment #15)
I only tested on 12.0-RELEASE.

Did you test on CURRENT ? If you did not and if Jung-uk Kim can not reproduce on CURRENT, then we kind of know what is going on.
Comment 17 Christoph Moench-Tegeder freebsd_committer 2019-05-27 12:39:01 UTC
(In reply to Samy Mahmoudi from comment #16)
This is 12.0-RELEASE-p4 - basically, the same setup/problem as you have (had?). It's not clear whether we have a solution for that (have we? did I miss it?).
Comment 18 Samy Mahmoudi 2019-05-27 21:38:02 UTC
(In reply to Christoph Moench-Tegeder from comment #17)
We may have something if Jung-uk Kim can not reproduce our freezes on CURRENT.

This would mean our problem is not only related to the port but also to the base system we both use. This would not be a solution though, only a starting point to investigate.
Comment 19 Samy Mahmoudi 2019-05-27 21:40:00 UTC
(In reply to Jung-uk Kim from comment #14)
Hi again,

Did you test launching a VM on FreeBSD-CURRENT ?
Comment 20 Jung-uk Kim freebsd_committer 2019-05-30 18:07:08 UTC
(In reply to Samy Mahmoudi from comment #19)
> Did you test launching a VM on FreeBSD-CURRENT ?

Yes, of course.  Does it only happen with Windows guests?  Did you turn on 2D/3D acceleration for the guests?
Comment 21 Jung-uk Kim freebsd_committer 2019-05-30 22:29:14 UTC
Created attachment 204727 [details]
Update to 6.0.8

Never mind.  Please try this.
Comment 22 Christoph Moench-Tegeder freebsd_committer 2019-05-31 10:14:08 UTC
(In reply to Jung-uk Kim from comment #21)

Yay! Progress! Thanks!
With aforementioned setup (and a Linux guest) the VM starts and seems to be ok.

Only one glitch: "VBoxManage startvm --type headless" fails with:
: cmt@elch:~$ VBoxManage startvm host1 --type headless  
: Waiting for VM "host1" to power on...
: VBoxManage: error: Unable to load R3 module /usr/local/lib/virtualbox/VBoxDD.so (VBoxDD): /usr/local/lib/virtualbox/VBoxDD.so: Undefined symbol "glXMakeCurrent" (VERR_FILE_NOT_FOUND)
: VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

This only happens with startvm in headless mode - other VBoxManage operations (like showinfo or controlvm) or even "start" without "--type headless" work just fine.
Comment 23 Jung-uk Kim freebsd_committer 2019-05-31 14:40:34 UTC
Created attachment 204742 [details]
Update to 6.0.8 (fixed OpenGL issue)

This patch should fix the OpenGL issue.  Please try this.
Comment 24 Christoph Moench-Tegeder freebsd_committer 2019-06-02 13:41:40 UTC
(In reply to Jung-uk Kim from comment #23)

This looks good - my VMs start (with and without GUI), new guest additions are working, shared folders ok... great!
Comment 25 Yuri Victorovich freebsd_committer 2019-06-12 05:55:11 UTC
Will the 6,0 update get committed any time soon?
Comment 26 eweiman 2019-08-08 15:32:05 UTC
Considering that this 3rd party add-on added support 
for vbox 6 with this commit a few months ago (April 2019)

https://github.com/pasha1st/phpvirtualbox-6/commit/bbdc56de41533e1ee420dafd620e96d0f8803ba9

Can we please move forwards on this and get virtual box updated?

I don't see the logic behind requiring the normal users of 
virtualbox that don't rely on a web interface from being able to
run the modern version of virtualbox without needing to venture 
in to manually compiling this.
Comment 27 BonHomme 2019-08-18 11:34:47 UTC
Hello,

There is absolutely no need to wait for phpvirtualbox. There is a (to my opinion) much better alternative, which already supports Virtualbox version 6 on freebsd since January this year.

So please update to Virtualbox v6 asap.

https://sourceforge.net/projects/remotebox/
http://remotebox.knobgoblin.org.uk/
https://wiki.archlinux.org/index.php/RemoteBox

I am working with it since beginning 2018 and it is working flawlessly, though installation was a bit complicated.
Comment 28 Cy Schubert freebsd_committer 2019-08-18 12:52:27 UTC
It would make sense that we rename virtualbox-ose and friends to virtualbox-ose5 and add this as virtualbox-ose6. There are many examples of this in the tree such as xpdf and many others.
Comment 29 VVD 2019-08-18 12:59:24 UTC
(In reply to Cy Schubert from comment #28)
Agree - make separate ports with 5 and 6.
VB 6 have stability problems on FreeBSD - already fixed?

RemoteBox isn't web application (but phpvirtualbox is) - it's stand-alone rich client on GTK.
Comment 30 BonHomme 2019-08-18 13:16:59 UTC
(In reply to VVD from comment #29)

Why should it be mandatory to be a web app? I can work very well with virtualbox on remotebox on my remote server. The only difference is that you must install remotebox on every computer that needs access to virtualbox.

I really don't see what is the problem? For me it is about the functionality and I prefer to be able to work with vbox 6 and install remotebox on more machines instead of waiting forever on phpvirtualbox
Comment 31 VVD 2019-08-18 14:18:31 UTC
(In reply to BonHomme from comment #30)
> Why should it be mandatory to be a web app?
Are you serious?

> The only difference is that you must install remotebox on every computer that needs access to virtualbox.
YES!

> I really don't see what is the problem?
You must install software on every computer, as you said before, and this is the problem!
How to use it on non-supported platforms, for example?

It's classical problem with all stand-alone rich clients compared to web applications.

> For me it is about the functionality and I prefer to be able to work with vbox 6 and install remotebox on more machines instead of waiting forever on phpvirtualbox
You can do it self now if you need - patch is here.
Are stability issues of VB 6 on FreeBSD fixed already?
Comment 32 BonHomme 2019-08-18 15:08:42 UTC
(In reply to VVD from comment #31)

Come on. Be a little bit practical please. 

How many people really need to reach Virtualbox from more than one or two machines? Beside that, once you installed Remotebox on the client and Freebsd, installing the next client is just a matter of a few minutes.

Using phpvirtualbox or remotebox is just a matter of choice and what is most important to you as the Virtualbox funtionality in both solutions is the same. Only the access method is different. And for people that work with an unsupported platform nothing changes. They have to wait for phpvirtualbox anyway.

So as remotebox is an excellent, very well working and very well maintained  alternative to phpvirtualbox (remotebox supports V6 already since January 6 2019) I really don't understand why everybody using virtualbox must wait (more than 8 months) for phpvirtualbox to be ready.

And as far as using an (untested?) and unsupported patch for Vbox 6: Are yóu serious?
Comment 33 VVD 2019-08-18 19:50:04 UTC
> How many people really need to reach Virtualbox from more than one or two machines?
At least 10 people in our company use it from different devices.
And we regularly use it from arbitrary computers in the office.

> Beside that, once you installed Remotebox on the client and Freebsd, installing the next client is just a matter of a few minutes.
Please stop this stupid dispute "rich client vs web application"! Web application is zero-cost support on client side and "true" cross-platform. Rich client isn't.

> And as far as using an (untested?) and unsupported patch for Vbox 6: Are yóu serious?
And you think that this patch will become tested after the maintainer updates the port? "Are yóu serious?"

Just make separate port for VB 6 and keep VB 5 as more stable version. And you can be happy to be beta-tester for this patch.
But better get this patch included in the upstream.
Comment 34 Christoph Moench-Tegeder freebsd_committer 2019-08-18 20:49:23 UTC
Can we keep this civil and on-topic? Thank you.

To summarize, the questions are:
- Are there any outstanding issues with VirtualBox 6? (It works for me, but sometimes I'm one of the lucky ones...)
- If there are any ports which cannot be updated to work with VirtualBox 6, is there anything preventing a repocopy and having both virtualbox 5 and 6 in the tree? (I don't mind the naming, let it be "virtualbox" and "virtualbox6" or "virtualbox5" and "virtualbox", or some variation thereof).

Is that the state of things right now?
Comment 35 Mikhail Teterin freebsd_committer 2019-08-27 14:45:54 UTC
I too would like the VirtualBox ports upgraded (the current latest from upstream is 6.0.10) -- at least, the ose-guest-additions, because that's all I use.

The one point, that all of the virtualbox ports have omitted so far is adding -DPAE to the compiler command lines building kernel modules. I'm trying to deal with this myself currently with things like this:

.if ${.CURDIR:M*/ports/*virtualbox-ose*}
CFLAGS+=        -DPAE
COPTFLAGS+=     -DPAE
CXXFLAGS+=      -DPAE
.endif

but I'm never certain, if they have the proper effect every time or if my vboxguest.ko is subtly miscompiled :(

This may be less important to the server port, as VM-hosting servers these days tend to be 64bit anyway, but it is perfectly normal for a guest VM to be 32-bit -- using PAE to have more than 4GB of total memory, while limiting each process to 4GB.

I'm not sure, if PAE should be a "flavor" or an option... Given that it only affects kernel-modules (both for the host- and the guest- ports), maybe, the vboxguest.ko needs a port of its own (like the already-existing virtualbox-ose-kmod).
Comment 36 Li-Wen Hsu freebsd_committer 2019-09-14 00:23:28 UTC
My WIP for 6.0.12 is here: https://github.com/lwhsu/freebsd-ports-virtualbox-ose
Comment 37 Christoph Moench-Tegeder freebsd_committer 2019-09-15 20:29:48 UTC
(In reply to Li-Wen Hsu from comment #36)

That 6.0.12 works fine for what I'm doing (FreeBSD host, guests are mostly Linux).
One small nitpick: when downloading the Guest Additions ISO image, right when the download is at 100%, an error message pops up: "The network operation failed with the following error: During network request: Unknown reason." (that's really neither specific nor helpful...). Downloading the image manually into the right place works fine.
Comment 38 Mikhail Teterin freebsd_committer 2019-09-20 16:55:11 UTC
Created attachment 207660 [details]
Kernel panic

When loading the vboxguest (built from 6.0.12) after booting a PAE guest (11.3-STABLE), I usually get the kernel panic attached. It takes multiple reboots to get the module to load, after which the machine seems usable.

Is there something we need to patch in the guest code?
Comment 39 Mario Lobo 2019-10-17 19:44:31 UTC
(In reply to Li-Wen Hsu from comment #36)

I've downloaded your port. ose-kmod compiles fine but the main app fails with:


ports/emulators/virtualbox-ose/work/VirtualBox-6.0.12/src/VBox/Runtime/r3/posix/process-creation-posix.cpp:368:49: error:
      invalid application of 'sizeof' to an incomplete type 'struct crypt_data'
        size_t const       cbCryptData = RT_MAX(sizeof(struct crypt_data) * 2, _256K);
                                                                          ^     ~~~~~~~~~~~~~~~~~~~

ports/emulators/virtualbox-ose/work/VirtualBox-6.0.12/src/VBox/Runtime/r3/posix/process-creation-posix.cpp:190:63: note:
      forward declaration of 'crypt_data'
typedef char *(*PFNCRYPTR)(const char *, const char *, struct crypt_data *);
Comment 40 Mario Lobo 2019-10-17 19:46:08 UTC
Sorry for not mentioning.

FreeBSD 11.3-STABLE
Comment 41 Jung-uk Kim freebsd_committer 2019-12-04 20:49:17 UTC
I decided to skip 6.0.  6.1 is imminent.
Comment 42 Li-Wen Hsu freebsd_committer 2019-12-04 21:01:23 UTC
(In reply to Jung-uk Kim from comment #41)
Not sure if this helps, I was working on cleaning the patches for 6.1:
https://github.com/lwhsu/freebsd-ports-virtualbox-ose/pull/1
Comment 43 Jung-uk Kim freebsd_committer 2019-12-04 21:10:45 UTC
(In reply to Li-Wen Hsu from comment #42)
Oh, I didn't know.  I already have a patch for 6.1.0 RC1.
Comment 44 VVD 2019-12-05 00:45:17 UTC
(In reply to Jung-uk Kim from comment #43)
As far as I remember, 6.1 drop support of i386 hosts...
Comment 45 Mario Lobo 2019-12-13 22:32:29 UTC
Created attachment 209925 [details]
VBOX 6.1.0 port
Comment 46 Mario Lobo 2019-12-13 22:38:12 UTC
The above is mu attempt to compile VBox 6.1.0 after tweaking the patches.

The VMs start and run OK.

Problems:

1) with 2 monitors, the 2nd monitor doesn't get the same max resolution as the 1rst.

2) Shutting down the VM freezes the host UI (in my case, kde). Had to alt+F1 to issue a ^C to kill kde.


uname: FreebSD 11.3-STABLE
Comment 47 Jung-uk Kim freebsd_committer 2019-12-13 22:50:12 UTC
Created attachment 209927 [details]
Update to 6.1.0

(In reply to Mario Lobo from comment #45)
Thanks but I already have 6.1 patches.  Please let me know if I missed anything.
Comment 48 Jung-uk Kim freebsd_committer 2019-12-13 22:53:18 UTC
Note the patches are NOT final and you need to update devel/kBuild first.
Comment 49 Mario Lobo 2019-12-13 23:38:30 UTC
(In reply to Jung-uk Kim from comment #48)

Could you provide a link for your patches?

To me, this is the version with the best performance I've seen! The VMs are really fast!.
Comment 50 Mario Lobo 2019-12-16 14:05:16 UTC
(In reply to Jung-uk Kim from comment #48)

Ok. Found the patches and applied them. I had to make little corrections on a few files but everything ended up compiling and running.

The problems I mentioned on the attempt on my patches remained with yours:

1) with 2 monitors, the 2nd monitor doesn't get the same max resolution as the 1rst. Only after I resize de 2nd monitor, it adjusts to full screen.

2) Shutting down the VM freezes the host UI (in my case, kde). Had to alt+F1 to issue a ^C to kill kde. If I leave the VM on a background workspace, I can terminate the VM without having the host UI frozen. The status on VBox never gets past "stopping", although the logs show that the VM has finished.

Other than that, the VMs run really fast and are fully operational while up.
Comment 51 Naram Qashat 2019-12-19 01:04:44 UTC
So, I had been trying these patches as they came about.

The 6.0.x line seemed to work perfectly fine (albeit that I've never been able to get audio to work in the guest, despite the host driver working on the host, but this was a problem for me in the 5.x line too and I don't know when that started happening).

But 6.1.0 seems to be trouble galore. I've had the following issues at one point or another:

* VMs won't start (I would get a pretty generic NS_ERROR_FAILURE 0x80004005 in component SessionMachine, and while others online say it was from starting from a snapshot, I was starting from an offline VM)

* With a dual-monitor Windows 10 VM and using mouse integration, I was getting an issue with the mouse cursor treating the first monitor as if it was both monitors combined (so as I moved right, the cursor position inside the VM itself was going farther right than it should've)

* When I tried to change the display type (which was originally VBoxVGA) to another option, I'd either start getting those generic errors from the first point or it would start fine, but the mouse issue would persist. At one point I switched back to VBoxVGA and ran into an issue where the guest display was some small 640x480 I think with an almost grayscale like 16-color-ish looking display.

* Every time a VM shuts down, it says it aborted instead of being powered off. I see the following in one of the logs:

00:00:05.595427 !!Assertion Failed!!
00:00:05.595427 Expression: <NULL>
00:00:05.595428 Location  : /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.0/src/VBox/VMM/VMMR3/MMHeap.cpp(667) void MMR3HeapFree(void *)
00:00:05.595433 Stack     :
00:00:05.595434 00000008014439a7
00:00:05.595434 
00:00:05.595453 Invalid heap header! pv=0000000818c3be20, size=0x2d6e492d

* Some of the above issues ended up with the processes of VBoxNetDHCP, VBoxSVC and VBoxXPCOMIPCD still persisting even though no VMs were running (and not even the manager GUI was running). I didn't attempt to stop them because I didn't want to possibly cause a kernel panic.

* After a forced reboot caused by a kernel panic (that wasn't caused by VirtualBox), my Windows 10 VM no longer seems to want to do mouse integration (regardless of if the Guest Additions were installed or not) and wouldn't start if I had my guest audio driver set to Intel HD, getting the following in the log:

00:00:28.109998 !!Assertion Failed!!
00:00:28.109998 Expression: RT_SUCCESS_NP(rc2)
00:00:28.109999 Location  : /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.0/src/VBox/Devices/Audio/DevHDA.cpp(1348) VBOXSTRICTRC hdaRegWriteSDCTL(PPDMDEVINS, PHDASTATE, uint32_t, uint32_t)
00:00:28.110020 Stack     :
00:00:28.110021 00000008014439a7
00:00:28.110022 
00:00:28.110052 VERR_NOT_SUPPORTED (-37) - Not supported.
Comment 52 Naram Qashat 2019-12-19 14:39:35 UTC
I just had another assertion pop up in the Windows 10 VM after it was idle for a bit over half a day:

13:54:39.917997 !!Assertion Failed!!
13:54:39.917998 Expression: pTimer->enmClock == TMCLOCK_VIRTUAL_SYNC ? enmState == TMTIMERSTATE_ACTIVE : enmState == TMTIMERSTATE_PENDING_SCHEDULE || enmState == TMTIMERSTATE_PENDING_STOP_SCHEDULE
13:54:39.917999 Location  : /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.0/src/VBox/VMM/include/TMInline.h(39) void tmTimerQueueUnlinkActive(PTMTIMERQUEUE, PTMTIMER)
13:54:39.918016 Stack     :
13:54:39.918016 00000008014439a7
Comment 53 Jung-uk Kim freebsd_committer 2019-12-26 06:57:45 UTC
Back to the group.  I do not have enough time to work on it.
Comment 54 VVD 2019-12-27 14:05:22 UTC
May be keep 3 different ports:
emulators/virtualbox-ose-52 - old stable
emulators/virtualbox-ose-60 - new, support CPUs without VT-x/AMD-V
emulators/virtualbox-ose-61 - new, support CPUs with VT-x/AMD-V only
Comment 55 Hadi 2020-02-25 13:49:03 UTC
So, will be 6.1 landed in port-tree ? or still it is not stable.
Comment 56 Mario Lobo 2020-03-06 20:54:56 UTC
(In reply to Hadi from comment #55)

6.1.0 is still unstable. The last stable version I compiled and I use is 6.0.8. The ports version is still 5.x, and VBox is already up to 6.1.4.

I managed to compile version 6.1.0. It runs fine and it is pretty fast, at least in short tests. The problem is that instead of shutting down the machine, it aborts them, no matter what way you used to shut them down. The same happened with Jkim's patch for it.

I wish I had the knowledge to "correct" the code but unfortunately I don't, so I guess I'll just have to wait.
Comment 57 Mario Lobo 2020-04-17 14:31:56 UTC
I managed to compile VBox 6.1.6 yesterday without errors.

The GUI comes up OK with everything working (settings, preferences, media manager, etc..).

When I start a VM, the initial console window shows up for about 10 secs but the "PRESS F12 .." never shows. The window closes and a box with a "NS_ERROR_FAILURE 0x80004005" shows. Bellow are the ending log lines in chronological time of file creation:

- VBoxSVC.log

00:00:01.980290 nspr-2   Loading settings file "/root/.VirtualBox/Machines/Windows/Win10/Win10.vbox" with version "1.17-freebsd"
00:00:01.981326 nspr-2   VirtualBox: object created
00:00:07.032477 main     VirtualBox: object deletion starts
00:00:07.033816 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Snow.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.035501 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Debian.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.036172 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Windows7Allen.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.036208 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Windows72Allen.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.036780 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Novell-5.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.037423 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win98-Novell.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.037943 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Praieira_Server.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.038466 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Praieira_Client.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.038992 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win8Allen.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.039022 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win82Allen.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.039690 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/OPNsense.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.040260 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/xuDBServer.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.081253 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Harbour.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.082321 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win764.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.082947 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win7.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.082978 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win72.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.083561 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Klinx.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.084079 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/Vmachines/Win10.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:07.086053 main     HostDnsMonitor: shutting down ...
00:00:07.086062 main     HostDnsMonitor: shut down
00:00:07.086328 main     {000000080546ca40} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_INVALID_HANDLE
00:00:07.087070 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:07.087746 main     VirtualBox: object deleted


- VBox.log (VM log)

00:00:04.417050 VD: VDInit finished with VINF_SUCCESS
00:00:04.417156 VD: Opening the disk took 175900 ns
00:00:04.417188 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 102400000
00:00:04.417459 DrvVD: Flushes will be ignored
00:00:04.417462 DrvVD: Async flushes will be passed to the disk
00:00:04.420181 VD: Opening the disk took 96492 ns
00:00:04.420206 AHCI: LUN#1: disk, PCHS=16383/16/63, total number of sectors 81920000
00:00:04.420653 AHCI#0: Reset the HBA
00:00:04.420657 VD#0: Cancelling all active requests
00:00:04.420661 VD#1: Cancelling all active requests


- selectorwindow.log

00:00:09.318041 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x0 x 1920x1080
00:00:09.328396 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 1920x0 x 1920x1080
00:00:09.347424 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:01:15.203925 ERROR [COM]: aRC=NS_ERROR_UNEXPECTED (0x8000ffff) aIID={c0447716-ff5a-4795-b57a-ecd5fffa18a4} aComponent={SessionWrap} aText={The session is not locked (session state: Unlocked)}, preserve=false aResultDetail=0
00:08:08.517376 ERROR [COM]: aRC=NS_ERROR_UNEXPECTED (0x8000ffff) aIID={c0447716-ff5a-4795-b57a-ecd5fffa18a4} aComponent={SessionWrap} aText={The session is not locked (session state: Unlocked)}, preserve=false aResultDetail=0
Comment 58 Mario Lobo 2020-04-17 14:53:44 UTC
Created attachment 213495 [details]
VBOX 6.1.6 port

My specs:

FreeBSD 11.3-STABLE #1 r350287M
qt 5.10.1
kde 4.14.3
xorg-7.7_3

I reverted back to VBox 6.0.8 which works perfectly.

Attached is the 6.1.6 port in case anyone wants to try it.
Comment 59 Darin Luckie 2020-04-24 18:48:17 UTC
I'm running 12.1-STABLE r359734

I need 6.1 for GNS3 as I am preparing for my CCIE labs and last I tried, VMware was a non-starter.

I took a look at the Makefile and and the PR for LLVM8 7>8 issues (PR#236616), so I got it working after removing the clang6 requirement and patches because they failed to apply.

The ONLY change I made waas simply to change llvm=60 to llvm=70 since I am trying to keep python2 out of all my systems :)

211c211
< VBOX_LLVM_VER?=       70
---
> VBOX_LLVM_VER?=       60

THANK YOU SO MUCH FOR THIS!!!

I will be on my way now.

Cheers,

-D
Comment 60 Mario Lobo 2020-04-26 17:14:57 UTC
(In reply to Darin Luckie from comment #59)

Did you use the port I attached (6.1.6) or made your own?
Comment 61 Darin Luckie 2020-04-26 19:44:10 UTC
I used your patch, and it loaded the modules, but once it booted the VM, DHCP went beserk and the VBoxNetDHCP process wouldn't die (had to SIGSTOP & HUP cuz it was eating one of my my cores at 100%)

I'll try again with 6.1.4 and maybe use GCC or a newer LLVM?
Comment 62 Mario Lobo 2020-04-26 23:25:08 UTC
(In reply to Darin Luckie from comment #61)

See comment #57 to see what happens in my case.

I recently switched to 12 STABLE so I'll give it a go in a few days to see what happens.
Comment 63 Mario Lobo 2020-04-28 13:44:45 UTC
System: FreeBSD 12.1-STABLE r360328 amd64

I just attempted to compile and run VBox 6.0.8 (which works perfectly on my 11.3 STABLE).

I compiles fine but it doesn't start the VMs. The GUI is fully operational but when you choose to start a VM (any type), a dialog shows saying:

"Starting process for VM "whatever" (1/2)"

And hangs there forever. The logs indicates that all processes are started but the VM's log shows this:

00:12:17.463217 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:12:17.473293 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:12:17.482427 Console: Machine state changed to 'PoweredOff'
00:12:17.483007 GUI: Request to close Runtime UI because VM is powered off already.
00:12:17.483135 GUI: Passing request to close Runtime UI from machine-logic to UI session.

Nothing is ever shown on screen or console.
Comment 64 Mario Lobo 2020-04-28 17:30:36 UTC
Tried all VBox 6.x.x that work ok on 11-STABLE.

Conclusion:
None of them work on 12-STABLE. Only the current port version (5.2.34) woks on it.
Comment 65 Mario Lobo 2020-05-05 23:31:05 UTC
Well ... I tried everything I could with VBox on 12.1-STABLE. Not a glimpse of success. Even the official 5.2.34 port is sluggish on it and it still has glitches.

Result: went back to 11.3-STABLE where a working 6.0.8 is very fast. 

Bhyve is promissing but still not practical yet.
Comment 66 Mario Lobo 2020-05-08 22:59:10 UTC
11.4-STABLE breaks VBox 6.x.x completely! 

So, I went back to 11.3-STABLE r359971 (last one from the .iso) and VBox 6.x.x came alive again.
Comment 67 VVD 2020-05-16 13:11:33 UTC
Released new versions May 14 2020:
5.2.42: https://www.virtualbox.org/wiki/Changelog-5.2#v42
May 15 2020:
6.0.22: https://www.virtualbox.org/wiki/Changelog-6.0#v22
6.1.8: https://www.virtualbox.org/wiki/Changelog-6.1#v8
Comment 68 Mario Lobo 2020-05-20 00:46:34 UTC
Created attachment 214671 [details]
Port of VitualBox 5.2.42
Comment 69 didier.castellacci 2020-05-20 18:20:52 UTC
(In reply to Mario Lobo from comment #68)
Hello,

I have tried untar (tar zxvf) Port of VitualBox 5.2.42 I have problem with an impossible link to decompress

Thank you
Didier
Comment 70 didier.castellacci 2020-05-20 18:37:31 UTC
This is what i get

 sudo tar zxvf vbox_port-5.2.42.tar.gz 
x virtualbox-ose
x virtualbox-ose/Makefile: Cannot extract through symlink virtualbox-ose/Makefile
x virtualbox-ose/distinfo: Cannot extract through symlink virtualbox-ose/distinfo
x virtualbox-ose/pkg-descr: Cannot extract through symlink virtualbox-ose/pkg-descr
x virtualbox-ose/files/: Cannot extract through symlink virtualbox-ose/files
src_VBox_Runtime_r3_freebsd_systemmem-freebsd.cpp
src_VBox_Frontends_VirtualBox_src_settings_global_UIGlobalSettingsNetworkDetailsHost.cpp: Cannot extract through symlink virtualbox-ose/files/extrapatch-src_VBox_Frontends_VirtualBox_src_settings_global_UIGlobalSettingsNetworkDetailsHost.cpp
x virtualbox-ose/pkg-message: Cannot extract through symlink virtualbox-ose/pkg-message
x virtualbox-ose/pkg-plist: Cannot extract through symlink virtualbox-ose/pkg-plist
x virtualbox-ose-kmod
x virtualbox-ose-kmod/distinfo: Cannot extract through symlink virtualbox-ose-kmod/distinfo
x virtualbox-ose-kmod/pkg-descr: Cannot extract through symlink virtualbox-ose-kmod/pkg-descr
x virtualbox-ose-kmod/files/: Cannot extract through symlink virtualbox-ose-kmod/files
x virtualbox-ose-kmod/files/vboxnet.in: Cannot extract through symlink virtualbox-ose-kmod/files/vboxnet.in
x virtualbox-ose-kmod/pkg-plist: Cannot extract through symlink virtualbox-ose-kmod/pkg-plist
x virtualbox-ose-kmod/Makefile: Cannot extract through symlink virtualbox-ose-kmod/Makefile
tar: Error exit delayed from previous errors.


Thank you
Didier
Comment 71 per 2020-05-20 19:38:28 UTC
(In reply to didier.castellacci from comment #70)
Extremely weird tarball, with 'tar ztvf vbox_port-5.2.42.tar.gz' you'll see

lrwxr-xr-x  0 root   wheel       0 May 11 19:16 virtualbox-ose -> /Vmachines/ports/emulators/virtualbox-ose.5234
-rw-r--r--  0 root   wheel   13499 May 20 02:06 virtualbox-ose/Makefile
-rw-r--r--  0 root   wheel     324 May 20 02:37 virtualbox-ose/distinfo
...

and similarly for the supposedly-directory virtualbox-ose-kmod. It seems to unpack properly with 'tar ztvfU vbox_port-5.2.42.tar.gz', although it sounds like a "side effect" of the -U/--unlink/--unlink-first option...
Comment 72 per 2020-05-20 19:50:38 UTC
(In reply to per from comment #71)

Sorry, should of course have been "...unpack properly with 'tar zxvfU vbox_port-5.2.42.tar.gz'..."
Comment 73 Mario Lobo 2020-05-21 03:00:41 UTC
Sorry! My mistake.

I have virtuabox-ose and virtualbox-ose-kmod symbolically linked to whatever port I'm working on. I.e:

virtualbox-ose.5242
virtualbox-ose-kmod.5242

And I packed the ports from the sym links instead of the real dir.

Forgive me.
Comment 74 didier.castellacci 2020-05-21 14:45:28 UTC
(In reply to Li-Wen Hsu from comment #36)

Hello

I installed Virtualbox 6.0.12 via https://github.com/lwhsu/freebsd-ports-virtualbox-ose

I was able to build without problem.

I start VirtualBox 6.0.12 interface OK when I try to start a vm it crashes


Here is the message

: Failed to open a session for the virtual machine Ubuntu 20.04 Office ip12.

The virtual machine 'Ubuntu 20.04 Office ip12' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Here is the log of the virtualbox 6.0.12



00:00:02.970096 VirtualBox VM 6.0.20 r137117 freebsd.amd64 (Apr 25 2020 07:49:46) release log
00:00:02.970098 Log opened 2020-05-20T17:45:40.700683000Z
00:00:02.970099 Build Type: release
00:00:02.970108 OS Product: FreeBSD
00:00:02.970110 OS Release: 12.1-RELEASE-p5
00:00:02.970113 OS Version: FreeBSD 12.1-RELEASE-p5 GENERIC
00:00:02.970133 Host RAM: 7893MB (7.7GB) total, 394MB available
00:00:02.970137 Executable: /usr/home/opt/local/lib/virtualbox/VirtualBoxVM
00:00:02.970138 Process ID: 1545
00:00:02.970139 Package type: BSD_64BITS_GENERIC (OSE)
00:00:02.972699 Installed Extension Packs:
00:00:02.972725   VNC (Version: 6.0.20 r137117; VRDE Module: VBoxVNC)
00:00:02.973528 Console: Machine state changed to 'Starting'
00:00:02.973759 Qt version: 5.13.2
00:00:02.973771 X11 Window Manager code: 0
00:00:02.976282 X Server details: vendor: The X.Org Foundation, release: 12008000, protocol version: 11.0, display string: :0
00:00:02.976309 Using XKB for keycode to scan code conversion
00:00:02.992671 SUP: Loaded VMMR0.r0 (/usr/home/opt/local/lib/virtualbox/VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:02.992726 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:02.995523 Guest OS type: 'Ubuntu_64'
00:00:02.998285 fHMForced=true - SMP
00:00:02.998310 fHMForced=true - 64-bit guest
00:00:03.009395 File system of '/home/bs/VirtualBox VMs/Ubuntu 20.04 Office ip12/Snapshots' (snapshots) is unknown
00:00:03.009413 File system of '/home/bs/VirtualBox VMs/Ubuntu 20.04 Office ip12/Ubuntu 20.04 Office.vmdk' is zfs
00:00:03.024877 Shared clipboard service loaded
00:00:03.024909 Shared clipboard mode: Bidirectional
00:00:03.026733 Drag and drop service loaded
00:00:03.026757 Drag and drop mode: Bidirectional
00:00:03.028695 ************************* CFGM dump *************************
00:00:03.028697 [/] (level 0)
00:00:03.042354   CSAMEnabled       <integer> = 0x0000000000000001 (1)
00:00:03.042387   CpuExecutionCap   <integer> = 0x0000000000000064 (100)
00:00:03.042389   EnablePAE         <integer> = 0x0000000000000000 (0)
00:00:03.042390   HMEnabled         <integer> = 0x0000000000000001 (1)
00:00:03.042391   MemBalloonSize    <integer> = 0x0000000000000000 (0)
00:00:03.042391   Name              <string>  = "Ubuntu 20.04 Office ip12" (cb=25)
00:00:03.042393   NumCPUs           <integer> = 0x0000000000000004 (4)
00:00:03.042394   PATMEnabled       <integer> = 0x0000000000000001 (1)
00:00:03.042395   PageFusionAllowed <integer> = 0x0000000000000000 (0)
00:00:03.042395   RamHoleSize       <integer> = 0x0000000020000000 (536 870 912, 512 MB)
00:00:03.042397   RamSize           <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
00:00:03.042399   RawR0Enabled      <integer> = 0x0000000000000001 (1)
00:00:03.042400   RawR3Enabled      <integer> = 0x0000000000000001 (1)
00:00:03.042400   TimerMillies      <integer> = 0x000000000000000a (10)
00:00:03.042401   UUID              <bytes>   = "66 b3 51 b4 29 d8 49 48 be c9 0c 28 3e 4c e1 9d" (cb=16)
00:00:03.042405 
00:00:03.042406 [/CPUM/] (level 1)
00:00:03.042407   GuestCpuName       <string>  = "host" (cb=5)
00:00:03.042408   NestedHWVirt       <integer> = 0x0000000000000000 (0)
00:00:03.042409   PortableCpuIdLevel <integer> = 0x0000000000000000 (0)
00:00:03.042410   SpecCtrl           <integer> = 0x0000000000000000 (0)
00:00:03.042411 
00:00:03.042411 [/CPUM/IsaExts/] (level 2)
00:00:03.042412 
00:00:03.042413 [/DBGC/] (level 1)
00:00:03.042414   GlobalInitScript <string>  = "/home/bs/.config/VirtualBox/dbgc-init" (cb=38)
00:00:03.042415   HistoryFile      <string>  = "/home/bs/.config/VirtualBox/dbgc-history" (cb=41)
00:00:03.042415   LocalInitScript  <string>  = "/home/bs/VirtualBox VMs/Ubuntu 20.04 Office ip12/dbgc-init" (cb=59)
00:00:03.042416 
00:00:03.042417 [/DBGF/] (level 1)
00:00:03.042418   Path <string>  = "/home/bs/VirtualBox VMs/Ubuntu 20.04 Office ip12/debug/;/home/bs/VirtualBox VMs/Ubuntu 20.04 Office ip12/;/home/bs/" (cb=116)
00:00:03.042419 
....
00:02:00.972727 /PROF/CPU3/EM/NEMExecuteCalled          0 times
00:02:00.972735 /PROF/CPU3/EM/RAWTotal                  0 times
00:02:00.972743 /PROF/CPU3/EM/REMTotal                  0 times
00:02:00.972752 /PROF/CPU3/EM/RecordedExits        230851 times
00:02:00.972760 /PROF/CPU3/EM/Total              412372382294 ticks/call (412372382294 ticks,       1 times, max 412372382294, min 412372382294)
00:02:00.972771 /PROF/CPU3/VM/Halt/Block          2345064 ns/call (103089032281 ticks,   43960 times, max 265116938, min       1)
00:02:00.972780 /PROF/CPU3/VM/Halt/BlockInsomnia  2413592 ns/call ( 77722504929 ticks,   32202 times, max 232904767, min       1)
00:02:00.972789 /PROF/CPU3/VM/Halt/BlockOnTime    2208746 ns/call (  3271153280 ticks,    1481 times, max  92121137, min    2126)
00:02:00.972798 /PROF/CPU3/VM/Halt/BlockOverslept   526209 ns/call (  5407859383 ticks,   10277 times, max   8825929, min   50108)
00:02:00.972808 /PROF/CPU3/VM/Halt/R0HaltBlock          0 ns/call (           0 ticks,       0 times, max         0, min      -1)
00:02:00.972818 /PROF/CPU3/VM/Halt/R0HaltBlockInsomnia        0 ns/call (           0 ticks,       0 times, max         0, min      -1)
00:02:00.972826 /PROF/CPU3/VM/Halt/R0HaltBlockOnTime        0 ns/call (           0 ticks,       0 times, max         0, min      -1)
00:02:00.972835 /PROF/CPU3/VM/Halt/R0HaltBlockOverslept        0 ns/call (           0 ticks,       0 times, max         0, min      -1)
00:02:00.972844 /PROF/CPU3/VM/Halt/R0HaltExec           0 times
00:02:00.972852 /PROF/CPU3/VM/Halt/R0HaltExec/FromBlock        0 times
00:02:00.972860 /PROF/CPU3/VM/Halt/R0HaltExec/FromSpin        0 times
00:02:00.972869 /PROF/CPU3/VM/Halt/R0HaltHistoryCounter    23193 times
00:02:00.972877 /PROF/CPU3/VM/Halt/R0HaltHistorySucceeded        0 times
00:02:00.972885 /PROF/CPU3/VM/Halt/R0HaltHistoryToRing3      156 times
00:02:00.972893 /PROF/CPU3/VM/Halt/Timers            3607 ns/call (   277866727 ticks,   77019 times, max   2286595, min       2)
00:02:00.972903 /PROF/CPU3/VM/Halt/Yield             1525 ns/call (      253194 ticks,     166 times, max      5095, min     688)
00:02:00.972912 /Public/Net/E1k0/BytesReceived          0 bytes
00:02:00.972920 /Public/Net/E1k0/BytesTransmitted    13128 bytes
00:02:00.972928 /REM/TbFlushCount                       0 times
00:02:00.972937 /REM/TbPhysInvldCount                   0 times
00:02:00.972945 /REM/TlbFlushCount                      1 times
00:02:00.972954 /SELM/LoadHidSel/GstReadErrors          0 times
00:02:00.972963 /SELM/LoadHidSel/NoGoodGuest            0 times
00:02:00.972973 /TM/CPU/00/cNsExecuting          12466236412 ns
00:02:00.972982 /TM/CPU/00/cNsHalted             102441383975 ns
00:02:00.972993 /TM/CPU/00/cNsOther              2848071704 ns
00:02:00.973003 /TM/CPU/00/cNsTotal              117755692091 ns
00:02:00.973011 /TM/CPU/00/cPeriodsExecuting      1358018 count
00:02:00.973019 /TM/CPU/00/cPeriodsHalted           33346 count
00:02:00.973028 /TM/CPU/00/pctExecuting                 9 %
00:02:00.973036 /TM/CPU/00/pctHalted                   89 %
00:02:00.973045 /TM/CPU/00/pctOther                     1 %
00:02:00.973053 /TM/CPU/01/cNsExecuting          11340450238 ns
00:02:00.973061 /TM/CPU/01/cNsHalted             104772908457 ns
00:02:00.973070 /TM/CPU/01/cNsOther              1708851925 ns
00:02:00.973079 /TM/CPU/01/cNsTotal              117822210620 ns
00:02:00.973087 /TM/CPU/01/cPeriodsExecuting       240840 count
00:02:00.973096 /TM/CPU/01/cPeriodsHalted           25686 count
00:02:00.973104 /TM/CPU/01/pctExecuting                 9 %
00:02:00.973113 /TM/CPU/01/pctHalted                   89 %
00:02:00.973121 /TM/CPU/01/pctOther                     1 %
00:02:00.973129 /TM/CPU/02/cNsExecuting          10056021804 ns
00:02:00.973138 /TM/CPU/02/cNsHalted             106243871772 ns
00:02:00.973146 /TM/CPU/02/cNsOther              1522289924 ns
00:02:00.973155 /TM/CPU/02/cNsTotal              117822183500 ns
00:02:00.973163 /TM/CPU/02/cPeriodsExecuting       232198 count
00:02:00.973172 /TM/CPU/02/cPeriodsHalted           21877 count
00:02:00.973180 /TM/CPU/02/pctExecuting                 8 %
00:02:00.973189 /TM/CPU/02/pctHalted                   90 %
00:02:00.973197 /TM/CPU/02/pctOther                     1 %
00:02:00.973205 /TM/CPU/03/cNsExecuting          12514785973 ns
00:02:00.973214 /TM/CPU/03/cNsHalted             103415052549 ns
00:02:00.973222 /TM/CPU/03/cNsOther              1892367054 ns
00:02:00.973231 /TM/CPU/03/cNsTotal              117822205576 ns
00:02:00.973240 /TM/CPU/03/cPeriodsExecuting       230851 count
00:02:00.973248 /TM/CPU/03/cPeriodsHalted           23242 count
00:02:00.973257 /TM/CPU/03/pctExecuting                11 %
00:02:00.973265 /TM/CPU/03/pctHalted                   87 %
00:02:00.973273 /TM/CPU/03/pctOther                     0 %
00:02:00.973281 /TM/CPU/pctExecuting                    9 %
00:02:00.973291 /TM/CPU/pctHalted                      89 %
00:02:00.973299 /TM/CPU/pctOther                        1 %
00:02:00.973308 /TM/MaxHzHint                           0 Hz
00:02:00.973316 /TM/R0/1nsSteps                       111 times
00:02:00.973325 /TM/R3/1nsSteps                      1191 times
00:02:00.973334 /TM/TSC/offCPU0                  18446744073698307537 ticks
00:02:00.973343 /TM/TSC/offCPU1                  18446744073698307537 ticks
00:02:00.973352 /TM/TSC/offCPU2                  18446744073698307537 ticks
00:02:00.973361 /TM/TSC/offCPU3                  18446744073698307537 ticks
00:02:00.973370 /TM/VirtualSync/CurrentOffset      151040 ns
00:02:00.973378 /VUSB/0/cUrbsInPool                     0 count
00:02:00.973388 ********************* End of statistics **********************
00:02:00.973702 VUSB: Detached 'HidMouse' from port 1 on RootHub#0
00:02:00.976054 NAT: Zone(nm:mbuf_cluster, used:0)
00:02:00.976079 NAT: Zone(nm:mbuf_packet, used:0)
00:02:00.976089 NAT: Zone(nm:mbuf, used:0)
00:02:00.976099 NAT: Zone(nm:mbuf_jumbo_pagesize, used:0)
00:02:00.976110 NAT: Zone(nm:mbuf_jumbo_9k, used:0)
00:02:00.976121 NAT: Zone(nm:mbuf_jumbo_16k, used:0)
00:02:00.976131 NAT: Zone(nm:mbuf_ext_refcnt, used:0)
00:02:00.976165 E1000#0: Interrupt attempts: 394
00:02:00.976174 E1000#0: Interrupts raised : 219
00:02:00.976183 E1000#0: Interrupts lowered: 0
00:02:00.976191 E1000#0: ICR outside ISR   : 0
00:02:00.976200 E1000#0: IMS raised ints   : 9
00:02:00.976208 E1000#0: Interrupts skipped: 158
00:02:00.976216 E1000#0: Masked interrupts : 17
00:02:00.976224 E1000#0: Early interrupts  : 0
00:02:00.976232 E1000#0: Late interrupts   : 8
00:02:00.976240 E1000#0: Lost interrupts   : 0
00:02:00.976249 E1000#0: Interrupts by RX  : 0
00:02:00.976257 E1000#0: Interrupts by TX  : 165
00:02:00.976265 E1000#0: Interrupts by ICS : 55
00:02:00.976273 E1000#0: Interrupts by RDTR: 0
00:02:00.976282 E1000#0: Interrupts by RDMT: 0
00:02:00.976290 E1000#0: Interrupts by TXQE: 0
00:02:00.976298 E1000#0: TX int delay asked: 0
00:02:00.976306 E1000#0: TX delayed:         0
00:02:00.976314 E1000#0: TX delay expired:   0
00:02:00.976322 E1000#0: TX no report asked: 44
00:02:00.976330 E1000#0: TX abs timer expd : 0
00:02:00.976339 E1000#0: TX int timer expd : 0
00:02:00.976347 E1000#0: RX abs timer expd : 0
00:02:00.976355 E1000#0: RX int timer expd : 0
00:02:00.976363 E1000#0: TX CTX descriptors: 44
00:02:00.976372 E1000#0: TX DAT descriptors: 44
00:02:00.976380 E1000#0: TX LEG descriptors: 121
00:02:00.976388 E1000#0: Received frames   : 0
00:02:00.976396 E1000#0: Transmitted frames: 165
00:02:00.976405 E1000#0: TX frames up to 1514: 165
00:02:00.976413 E1000#0: TX frames up to 2962: 0
00:02:00.976421 E1000#0: TX frames up to 4410: 0
00:02:00.976429 E1000#0: TX frames up to 5858: 0
00:02:00.976437 E1000#0: TX frames up to 7306: 0
00:02:00.976446 E1000#0: TX frames up to 8754: 0
00:02:00.976454 E1000#0: TX frames up to 16384: 0
00:02:00.976462 E1000#0: TX frames up to 32768: 0
00:02:00.976470 E1000#0: Larger TX frames    : 0
00:02:00.976479 E1000#0: Max TX Delay        : 0
00:02:00.977033 GIM: KVM: Resetting MSRs
00:02:00.981667 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:02:00.984794 Console: Machine state changed to 'PoweredOff'
00:02:00.984987 GUI: Request to close Runtime UI because VM is powered off already.
00:02:00.985018 GUI: Passing request to close Runtime UI from machine-logic to UI session.
Comment 75 Mario Lobo 2020-05-21 16:10:06 UTC
It's about the same error that happens with all 6.0.x and 6.1.x versions I tried.
Comment 76 didier.castellacci 2020-05-21 18:28:44 UTC
(In reply to Mario Lobo from comment #75)

Hello

I installed via Virtualbox 5.2.34 ports to build it went well.

Virtualbox 5.2.34 interface starts well

but starting a vm it crashes

Here is the error message

Kernel driver not accessible Abort

Failed to open a session for the virtual machine Ubuntu 20.04 Office ip12.

The virtual machine 'Ubuntu 20.04 Office ip12' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Thank you
Didier
Comment 77 Cy Schubert freebsd_committer 2020-05-21 18:36:46 UTC
(In reply to didier.castellacci from comment #76)

Did you load the drivers?
Comment 78 didier.castellacci 2020-05-21 18:45:22 UTC
(In reply to Cy Schubert from comment #77)



Did you load the drivers?
Yes


In

pwd
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/src


sudo make load

 ll *.ko
-r-xr-xr-x  1 root  vboxusers  uarch 460288 May 21 19:53 vboxdrv.ko*
-r-xr-xr-x  1 root  vboxusers  uarch  10016 May 21 19:53 vboxnetadp.ko*
-r-xr-xr-x  1 root  vboxusers  uarch  28008 May 21 19:53 vboxnetflt.ko*




kldstat
Id Refs Address                Size Name
 1   73 0xffffffff80200000  2448f20 kernel
 3    2 0xffffffff826d3000     a5b8 opensolaris.ko
 4    1 0xffffffff826de000   3a99a8 zfs.ko
 6    2 0xffffffff82c25000     9e30 netgraph.ko
 7    1 0xffffffff82c2f000     1710 ng_ether.ko
 9    1 0xffffffff82c35000   152fd0 radeonkms.ko
10    2 0xffffffff82d88000    76570 drm.ko
11    5 0xffffffff82dff000    10eb0 linuxkpi.ko
12    4 0xffffffff82e10000    12f30 linuxkpi_gplv2.ko
13    2 0xffffffff82e23000      6d0 debugfs.ko
14    1 0xffffffff82e24000     f181 ttm.ko
15    1 0xffffffff82e34000      a75 radeon_RS780_pfp_bin.ko
16    1 0xffffffff82e35000     5573 radeon_RS780_me_bin.ko
17    1 0xffffffff82e3b000      d73 radeon_R600_rlc_bin.ko
18    1 0xffffffff82e3c000    161b5 radeon_RS780_uvd_bin.ko
19    1 0xffffffff82e53000     2668 intpm.ko
20    1 0xffffffff82e56000      b50 smbus.ko
21    1 0xffffffff82e57000     18a0 uhid.ko
22    1 0xffffffff82e59000     2928 ums.ko
23    1 0xffffffff82e5c000     1aa0 wmt.ko
24    1 0xffffffff82e5e000    32830 pf.ko
25    1 0xffffffff82e91000     1aa0 fdescfs.ko
28    3 0xffffffff82e93000    52748 vboxdrv.ko
29    2 0xffffffff82c22000     2ce0 vboxnetflt.ko
30    1 0xffffffff82c31000     3f30 vboxnetadp.ko



on the other hand in the directory /boot/modules the rights are:


ll /boot/modules/vb*
-r-xr-xr-x  1 root  wheel  - 460288 May 21 20:37 /boot/modules/vboxdrv.ko*
-r-xr-xr-x  1 root  wheel  -  10016 May 21 20:37 /boot/modules/vboxnetadp.ko*
-r-xr-xr-x  1 root  wheel  -  28008 May 21 20:37 /boot/modules/vboxnetflt.ko*


Thank you
Didier
Comment 79 didier.castellacci 2020-05-21 19:00:09 UTC
(In reply to Cy Schubert from comment #77)

I don't have a VirtualBoxVM bin
This is normal the make command (sudo make DISABLE_VULNERABILITIES = yes) did not generate it for me

Thank You
Didier
Comment 80 Cy Schubert freebsd_committer 2020-05-21 19:26:34 UTC
(In reply to didier.castellacci from comment #79)

There is no VirtualBoxVM binary.
Comment 81 didier.castellacci 2020-05-22 10:36:35 UTC
(In reply to Cy Schubert from comment #80)


Hello

I installed via Virtualbox 5.2.34 ports

I set as compilation option

virtualbox-ose ports

sudo make config
sudo make build-depends-list
sudo make run-depends-list


sudo make package DISABLE_VULNERABILITIES = yes

Here is the error message


===> Staging rc.d startup script(s)
===>  Installing for virtualbox-ose-kmod-5.2.34
===>  Checking if virtualbox-ose-kmod is already installed
===>   Registering installation for virtualbox-ose-kmod-5.2.34 as automatic
Installing virtualbox-ose-kmod-5.2.34...
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/etc/rc.d/vboxnet - found
===>   Returning to build of virtualbox-ose-5.2.34_4
===>   virtualbox-ose-5.2.34_4 depends on executable: gtk-update-icon-cache - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/xcb.pc - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/x11.pc - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/xcursor.pc - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/xext.pc - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/xinerama.pc - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/xmu.pc - found
===>   virtualbox-ose-5.2.34_4 depends on file: /usr/local/libdata/pkgconfig/xt.pc - found
===>   Generating temporary packing list
===> Creating groups.
===> Creating users
cd /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/sdk/bindings/xpcom &&  /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE "idl samples" /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/share/virtualbox-ose
/bin/mkdir -p /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/include/virtualbox
cd /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include &&  /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE "*" /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/include/virtualbox
/bin/mkdir -p /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
cd /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin && /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE  "*.fd *.r0 *.rc *.so components" /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/src/VBox/Installer/freebsd/VBox.sh  /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxAutostart /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxBalloonCtrl /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxBugReport /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxHeadless /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxManage /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VirtualBox /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxSDL /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxExtPackHelperApp /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxNetAdpCtl /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxNetDHCP /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxNetNAT /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxSVC /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxXPCOMIPCD /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
install  -s -m 555 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/VBoxTestOGL /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxAutostart
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxBalloonCtrl
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxBugReport
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxHeadless
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxManage
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VirtualBox
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxSDL
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/VBoxVRDP
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/vboxautostart
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/vboxballoonctrl
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/vboxbugreport
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/vboxheadless

/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/vboxmanage
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/virtualbox
/bin/ln -fs ../lib/virtualbox/VBox.sh /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/bin/vboxsdl
cd /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/VirtualBox/qtnls &&  /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE "*.qm" /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/share/virtualbox-ose/nls
install  -m 0644  /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/src/VBox/Frontends/VirtualBox/images/OSE/VirtualBox_48px.png  /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/share/pixmaps/VBox.png
install  -m 0644  /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/src/VBox/Installer/freebsd/virtualbox.desktop  /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/share/applications/virtualbox.desktop
/bin/mkdir -p /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox/ExtensionPacks/VNC/freebsd.amd64
install  -m 0644 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/ExtensionPacks/VNC/ExtPack*  /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox/ExtensionPacks/VNC/
install  -s -m 0644 /usr/home/opt/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/bin/ExtensionPacks/VNC/freebsd.amd64/*  /usr/home/opt/ports/emulators/virtualbox-ose/work/stage/usr/local/lib/virtualbox/ExtensionPacks/VNC/freebsd.amd64/
====> Compressing man pages (compress-man)
===> Staging rc.d startup script(s)
===>  Building package for virtualbox-ose-5.2.34_4
pkg-static: Unable to access file /usr/home/opt/ports/emulators/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxHeadless.so:No such file or directory
pkg-static: Unable to access file /usr/home/opt/ports/emulators/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxNetDHCP.so:No such file or directory
pkg-static: Unable to access file /usr/home/opt/ports/emulators/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxNetNAT.so:No such file or directory
pkg-static: Unable to access file /usr/home/opt/ports/emulators/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxSDL.so:No such file or directory
pkg-static: Unable to access file /usr/home/opt/ports/emulators/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxVMMPreload.so:No such file or directory
pkg-static: Unable to access file /usr/home/opt/ports/emulators/virtualbox-ose/work/stageusr/local/lib/virtualbox/VirtualBox.so:No such file or directory
*** Error code 1

Stop.
make[1]: stopped in /usr/home/opt/ports/emulators/virtualbox-ose
*** Error code 1

Stop.
make: stopped in /usr/home/opt/ports/emulators/virtualbox-ose
[bs@MyFreeBSD]$ 




Thank you
Didier
Comment 82 didier.castellacci 2020-05-22 12:01:41 UTC
(In reply to Cy Schubert from comment #80)


Hello

I installed via Virtualbox 5.2.42 ports

I set as compilation option

virtualbox-ose ports

sudo make config
sudo make build-depends-list
sudo make run-depends-list


sudo make package DISABLE_VULNERABILITIES = yes


I have the same problem as with version 5.2.34




Here is the error message

===>  Building package for virtualbox-ose-5.2.42
pkg-static: Unable to access file /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxHeadless.so:No such file or directory
pkg-static: Unable to access file /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxNetDHCP.so:No such file or directory
pkg-static: Unable to access file /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxNetNAT.so:No such file or directory
pkg-static: Unable to access file /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxSDL.so:No such file or directory
pkg-static: Unable to access file /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose/work/stageusr/local/lib/virtualbox/VBoxVMMPreload.so:No such file or directory
pkg-static: Unable to access file /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose/work/stageusr/local/lib/virtualbox/VirtualBox.so:No such file or directory
*** Error code 1

Stop.
make[1]: stopped in /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose
*** Error code 1

Stop.
make: stopped in /usr/home/bs/Downloads/VirtualBox/freebsd-ports-virtualbox-ose-5.2.42/virtualbox-ose
[bs@MyFreeBSD]$ 




Thank you
Didier
Comment 83 didier.castellacci 2020-05-22 18:42:56 UTC
(In reply to Cy Schubert from comment #80)

Hello

I successfully installed Virtualbox 5.2.42 via ports

The vm opens I was able to install Ubuntu 20.04 and Installed Guest addition for 5.2.42

I have a problem running mp3 music and mp4 video.

When I connect with mozilla firefox on youtube and that I launch a music the music remains blocked from the beginning impossible to execute it.

Similar with mp3 players (mplayer, sox play) that I installed on ubuntu with codecs mpg123 etc ...

nothing works

Do you have an idea

Thank you
Didier
Comment 84 VVD 2020-05-23 08:01:22 UTC
(In reply to Mario Lobo from comment #73)
> And I packed the ports from the sym links instead of the real dir.
Can you, please, pack it without symlinks?
Comment 85 Mario Lobo 2020-05-23 13:11:08 UTC
There are only 3 things that need to be done on the official 5.2.34 port to move to 5.2.42:

1) Adjust both Makefiles (virtualbox-ose & virtualbox-ose-kmod)

change PORTVERSION=     5.2.34  to  PORTVERSION=        5.2.42
remove PORTREVISION=    4

2) remove patch-src_VBox_Devices_PC_vbox-cpuhotplug.dsl from
virtualbox-ose/files

3) recalculate distinfo, which becomes this:

SHA256 (VirtualBox-5.2.42.tar.bz2) =
e5bee2e34f349aac115ee93974febfe3213ad5e94045fa36b9f04b5f8caa3720
SIZE (VirtualBox-5.2.42.tar.bz2) = 124013981
SHA256 (VBoxGuestAdditions_5.2.42.iso) =
ff784417295e48e3cee80a596faf05e3b0976e1b94d3b88427939912b0c1fc45
SIZE (VBoxGuestAdditions_5.2.42.iso) = 49833984


Thatś it!

OBS - these alterations also work for virtualbox-guestadditions and the no-x11 ports.
Comment 86 VVD 2020-05-23 16:51:23 UTC
(In reply to Mario Lobo from comment #85)

It need a lot of fixes in patches.
For example:
-@@ -2538,6 +2534,10 @@ ifeq ($(KBUILD_HOST),win) ## @todo can drop this now, 
+@@ -2550,6 +2546,10 @@ ifeq ($(KBUILD_HOST),win) ## @todo can drop this now,
…
-@@ -4158,6 +4154,7 @@ ifdef VBOX_WITH_RAW_MODE
+@@ -4218,6 +4218,7 @@ ifdef VBOX_WITH_RAW_MODE
…
-@@ -4299,6 +4296,7 @@ ifeq ($(VBOX_LDR_FMT),elf)
+@@ -4359,6 +4360,7 @@ ifeq ($(VBOX_LDR_FMT),elf)

And there are warnings during make patch:
===>  Applying FreeBSD patches for virtualbox-ose-5.2.42 from /usr/ports/emulators/virtualbox-ose/files
No such line 731 in input file, ignoring
No such line 435 in input file, ignoring
Comment 87 VVD 2020-06-05 18:02:16 UTC
6.1.10 released: https://www.virtualbox.org/wiki/Changelog-6.1
Comment 88 Mikhail Teterin freebsd_committer 2020-06-22 02:23:28 UTC
I'd like to propose, we drop the attempts to keep the Virtual Box hosting side (ose and ose-kmod) at the same version as the Virtual Box guest side (the ose-additions).

There is no need for such synchronization -- even if people do use both (whom I'd estimate to be very few), the precise match of the hosting and guest software versions is not required.

Decoupling the two should make maintenance of both easier, and the upgrades -- more frequent.
Comment 89 Mario Lobo 2020-06-22 16:19:47 UTC
I agree with you completely, but we are lagging so far behind on the hosting side (ose and ose-kmod) that I think people that are trying to upgrade it aren't even thinking about the guest-additions port.
Comment 90 Mario Lobo 2020-06-22 21:09:59 UTC
For the record:

FreeBSD 13.0-CURRENT #1 r360882

Managed to compile cleanly virtualbox-ose-6.1.10 and virtualbox-ose-kmod-6.1.10.

Modules load OK:

kldstat | grep vbox
4    3 0xffffffff8122c000    8cba8 vboxdrv.ko
17    2 0xffffffff8334b000     4218 vboxnetflt.ko
20    1 0xffffffff8335f000     55e0 vboxnetadp.ko

vboxnet0: Ethernet address: 0a:00:27:00:00:00

GUI comes up fine but none of the VMs (no matter the guest OS) starts. 

Via GUI: The console never shows.

Via VBoxHeadless: 
VBoxHeadless --startvm Debian
Oracle VM VirtualBox Headless Interface 6.1.10
(C) 2008-2020 Oracle Corporation
All rights reserved.

Error: failed to start machine. Error message: Failed to construct device 'VMMDev' instance #0 (VERR_INTERNAL_ERROR_3)

and back to prompt.
Comment 91 Mario Lobo 2020-06-22 21:34:06 UTC
A small correction.

Starting the VM with VBoxHeadless or VBoxSDL, it just hangs open on the terminal, the process doesn't end with ^C, and even if the terminal is closed, the process still hangs in there and only a reboot is able to kill it.

1448  1- I     0:00.06 /usr/local/lib/virtualbox/VBoxHeadless --startvm Debian

The previous VBoxHeadless error message came out because I already had a hanging attempt from trying to run an Ubuntu VM.
Comment 92 Mikhail Teterin freebsd_committer 2020-06-23 16:54:30 UTC
(In reply to Mario Lobo from comment #89)
> we are lagging so far behind on the hosting side (ose and ose-kmod) that I think people that are trying to upgrade it aren't even thinking about the guest-additions port.

We are, obviously, lagging on _both_ sides -- and the "not thinking" is mutual. Most people interested in -- and capable of -- upgrading one side, aren't using the other, and must rely on others for testing their changes. This leads to delays...

Delays so high, people lose interest, and Oracle manages to make several releases in between -- obsoleting the original work. That the work is happening in little GitHub repos is not helping either :(

This ticket is old, and has 90+ comments and lots of attachments -- our problem is not lack of interest or expertise, it is organizational.

I'd like to expand my proposal (from comment #88) with this plan:

1. Leave the current virtualbox-* ports be (or upgrade them to the latest 5.x).
2. Repo-copy each virtualbox-foo to the ...foo6.
3. Disconnect the new virtualbox-ose-additions6 (guest) from the new virtualbox-ose6 (host) by:
   a) giving the guest its own files/ (for patches) and distinfo;
   b) moving the guest-only patches from the host's files/ into the guest's;
   c) enumerate the few -- if any -- patches necessary to both sides as EXTRAPATCHES in the guest -- or even just copy them over.
4. Assign the sides to different maintainers.

If no one objects to these steps in principle -- and no one volunteers to do it -- I'll perform the copying/moving myself. I can also take up maintainership of the new virtualbox-ose-additions6, if there is no better candidate (my own usage is limited to a FreeBSD-11.x/i386 PAE guest inside a Windows 10 desktop).

Based on one of the many attachments here, I can also upgrade the new hosting virtualbox-ose6 port (once), but I will not be able to test it beyond "it compiles".
Comment 93 Mario Lobo 2020-06-23 17:35:34 UTC
Would anyone know how to set up a debug build of the VBox port?
Comment 94 Li-Wen Hsu freebsd_committer 2020-06-23 18:16:04 UTC
(In reply to Mario Lobo from comment #93)
There is a "DEBUG" option. I just checked my very old log (2016), need to check if when this option enabled, it still correctly passes BUILD_TYPE=debug to LocalConfig.kmk file.
Comment 95 Mario Lobo 2020-06-23 21:12:14 UTC
Marking the Debug option does not produce debug symbols for any of the VBox executables.
Comment 96 Mario Lobo 2020-06-24 17:33:37 UTC
I finally managed to get VBox into gdb.

Starting program: /Vmachines/ports/emulators/virtualbox-ose.6110/work/VirtualBox-6.1.10/out/freebsd.amd64/debug/bin/VBoxHeadless --startvm Debian
Oracle VM VirtualBox Headless Interface 6.1.10
(C) 2008-2020 Oracle Corporation
All rights reserved.

Type Manifest File: /root/.VirtualBox/xpti.dat
[New LWP 101112 of process 13360]
[New LWP 101131 of process 13360]
[New LWP 101141 of process 13360]
nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)
^C
Thread 2 received signal SIGINT, Interrupt.
[Switching to LWP 101112 of process 13360]
_umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:40
40      RSYSCALL_ERR(_umtx_op)

=============================================================

Starting program: /Vmachines/ports/emulators/virtualbox-ose.6110/work/VirtualBox-6.1.10/out/freebsd.amd64/debug/bin/VBoxSDL --startvm Debian
Oracle VM VirtualBox SDL GUI version 6.1.10
(C) 2005-2020 Oracle Corporation
All rights reserved.

Type Manifest File: /root/.VirtualBox/xpti.dat
[New LWP 101168 of process 13409]
[New LWP 101169 of process 13409]
[New LWP 101173 of process 13409]
nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)
^C
Thread 2 received signal SIGINT, Interrupt.
[Switching to LWP 101168 of process 13409]
_umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:40
40      RSYSCALL_ERR(_umtx_op)

=============================================================

Starting program: /Vmachines/ports/emulators/virtualbox-ose.6110/work/VirtualBox-6.1.10/out/freebsd.amd64/debug/bin/VirtualBoxVM --startvm Debian
[New LWP 101200 of process 13489]
[New LWP 101201 of process 13489]
^C
Thread 1 received signal SIGINT, Interrupt.
_umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:40
40      RSYSCALL_ERR(_umtx_op)


They all get stuck on the same line.
Comment 97 Samy Mahmoudi 2020-06-24 18:05:18 UTC
(In reply to Mario Lobo from comment #96)
> I finally managed to get VBox into gdb.
How did you do so?
Comment 98 Mario Lobo 2020-06-24 18:55:44 UTC
By compiling with the Debug option, and running the binaries directly from the port's work directory.

I.E.

gdb --args /usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.10/out/freebsd.amd64/debug/bin/VBoxSDL --startvm Debian

Doing this way, gdb finds the debug symbols and sources.
Comment 99 Samy Mahmoudi 2020-06-24 22:43:20 UTC
(In reply to Mario Lobo from comment #98)
Thank you for the explanation Mario.
Comment 100 Mario Lobo 2020-06-29 13:58:50 UTC
A few things I did that I forgot to mention.

Here are the steps I've done to compile it:

1) cd /usr/ports/emulators/virtualbox-ose/ 

   make config and mark Debug option
   make patch

2) cd /usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.10/

   add VBOX_WITHOUT_HARDENING=1 to LocalConfig.kmk
   (this makes it easier to run a debug session.)

3) kmk build-debug-amd64
Comment 101 Mario Lobo 2020-06-29 14:21:20 UTC
Created attachment 216038 [details]
VBox 6.1.10 port files

Here are the virtualbox-ose 6.1.10 port files
Comment 102 Mario Lobo 2020-06-29 14:22:39 UTC
Created attachment 216039 [details]
VBox 6.1.10 kmod port files

Here are the VBox 6.1.10 kmod port files