Bug 234878 - emulators/virtualbox-ose: Update to 6.0
Summary: emulators/virtualbox-ose: Update to 6.0
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: Jung-uk Kim
URL:
Keywords: needs-patch
Depends on:
Blocks:
 
Reported: 2019-01-11 18:26 UTC by kunda
Modified: 2019-07-03 07:50 UTC (History)
13 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

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?