[Bug 246330] emulators/virtualbox-ose-additions - shared clipboard does not work because VBoxClient is invoked from wrong location
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246330 Bug ID: 246330 Summary: emulators/virtualbox-ose-additions - shared clipboard does not work because VBoxClient is invoked from wrong location Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: v...@freebsd.org Reporter: bourne.ident...@hotmail.com Flags: maintainer-feedback?(v...@freebsd.org) Assignee: v...@freebsd.org Hi, I am running FreeBSD 11.3 in a VirtualBox guest with shared clipboard set to bidirectional. But the the shared clipboard did not work. I found the reason for this - the shell script /usr/local/bin/VBoxClient-all tries to invoke VBoxClient from /usr/bin (instead of /usr/local/bin) at line 38: Of course, there is no /usr/bin/VBoxClient Regards, Manish Jain -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
maintainer-feedback requested: [Bug 246330] emulators/virtualbox-ose-additions - shared clipboard does not work because VBoxClient is invoked from wrong location
Bugzilla Automation has asked v...@freebsd.org for maintainer-feedback: Bug 246330: emulators/virtualbox-ose-additions - shared clipboard does not work because VBoxClient is invoked from wrong location https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246330 --- Description --- Hi, I am running FreeBSD 11.3 in a VirtualBox guest with shared clipboard set to bidirectional. But the the shared clipboard did not work. I found the reason for this - the shell script /usr/local/bin/VBoxClient-all tries to invoke VBoxClient from /usr/bin (instead of /usr/local/bin) at line 38: Of course, there is no /usr/bin/VBoxClient Regards, Manish Jain ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Find specific changes between revisions
Hi;
I'm attempting to port VirtualBox 6.0.8 to FreeBSD. I managed do get it
working perfectly up to
11.3-STABLE-amd64-r359971.
After an svn up to 11.4-PRERELEASE-r360676M, VirtualBox 6.0.8 no longer
works. Bringing world+kernel back to 11.3-STABLE-amd64-r359971 makes it
work again, despite whatever ports I've got installed on my machines. This
was tested on 2 physical machines (desktop and laptop) and it is true for
both.
When starting a VM on 11.4-PRERELEASE-r360676M, the VM console window shows
up for 2 seconds and vanishes. Tha VM log shows this:
00:00:02.343339 AssertLogRel
/Vmachines/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.8/src/VBox/Main/src-client/VMMDevInterface.cpp(960)
int VMMDev::i_guestPropLoadAndConfigure(): timestampsOut.size() == cProps
00:00:02.343365 AssertLogRel
/Vmachines/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.8/src/VBox/Main/src-client/VMMDevInterface.cpp(1157)
static int VMMDev::drvConstruct(PPDMDRVINS, PCFGMNODE, uint32_t):
RT_SUCCESS_NP(rc)
00:00:02.343450 VERR_INTERNAL_ERROR_3 (-227) - Internal error no. 3.
00:00:02.345073 PDM: Failed to construct 'VMMDev'/0! VERR_INTERNAL_ERROR_3
(-227) - Internal error no. 3.
00:00:02.347293 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:00:02.531769 VMSetError:
/Vmachines/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.8/src/VBox/VMM/VMMR3/VM.cpp(328)
int VMR3Create(uint32_t, PCVMM2USERMETHODS, PFNVMATERROR, void *,
PFNCFGMCONSTRUCTOR, void *, PVM *, PUVM *); rc=VERR_INTERNAL_ERROR_3
00:00:02.531778 VMSetError: Internal error no. 3.
00:00:02.533693 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap}
aText={Internal error no. 3. (VERR_INTERNAL_ERROR_3)}, preserve=false
aResultDetail=-227
00:00:02.534000 Console: Machine state changed to 'PoweredOff'
This is the same error that shows when trying to run it on
12.1-STABLE-amd64-r359985 by the way.
I am no wiz. And on top of that, VBox is extremely complex but I don't
think that the problem lies on the kernel or on vbox kernel modules. They
all load correctly and without errors on both 11.4-PRERELEASE-r360676M and
12.1-STABLE-amd64-r359985.
What looks like (to my poor lame eyes) is that some revision change in
userland "broke" the connection between vbox and its modules/drivers.
So my quest is to try to pinpoint the changes between
11.3-STABLE-amd64-r359971 and 11.4-PRERELEASE-r360676M that made VirtualBox
6.0.8 stop working, and I was wondering if anyone here could give me some
direction on how to accomplish that.
Thanks for any advice.
--
Mario Lobo
FreeBSD since version 2.2.8 [not Pro-Audio YET!!]
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
[Bug 244962] emulators/virtualbox-ose-additions mount -t vboxsf Operation not supported by device
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244962 --- Comment #17 from groenv...@acm.org --- John-Mark Gurney's patch worked for me with FreeBSD 13.0-CURRENT #0 r360723: https://lists.freebsd.org/pipermail/freebsd-virtualization/2020-May/008448.html> John groenv...@acm.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Find specific changes between revisions
09.05.2020 23:41, Mario Lobo wrote:
> Hi;
>
> I'm attempting to port VirtualBox 6.0.8 to FreeBSD. I managed do get it
> working perfectly up to
>
> 11.3-STABLE-amd64-r359971.
>
> After an svn up to 11.4-PRERELEASE-r360676M, VirtualBox 6.0.8 no longer
> works. Bringing world+kernel back to 11.3-STABLE-amd64-r359971 makes it
> work again, despite whatever ports I've got installed on my machines. This
> was tested on 2 physical machines (desktop and laptop) and it is true for
> both.
>
> When starting a VM on 11.4-PRERELEASE-r360676M, the VM console window shows
> up for 2 seconds and vanishes. Tha VM log shows this:
>
>
> 00:00:02.343339 AssertLogRel
> /Vmachines/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.8/src/VBox/Main/src-client/VMMDevInterface.cpp(960)
> int VMMDev::i_guestPropLoadAndConfigure(): timestampsOut.size() == cProps
> 00:00:02.343365 AssertLogRel
> /Vmachines/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.8/src/VBox/Main/src-client/VMMDevInterface.cpp(1157)
> static int VMMDev::drvConstruct(PPDMDRVINS, PCFGMNODE, uint32_t):
> RT_SUCCESS_NP(rc)
> 00:00:02.343450 VERR_INTERNAL_ERROR_3 (-227) - Internal error no. 3.
> 00:00:02.345073 PDM: Failed to construct 'VMMDev'/0! VERR_INTERNAL_ERROR_3
> (-227) - Internal error no. 3.
> 00:00:02.347293 GIM: HyperV: Resetting MMIO2 regions and MSRs
> 00:00:02.531769 VMSetError:
> /Vmachines/ports/emulators/virtualbox-ose/work/VirtualBox-6.0.8/src/VBox/VMM/VMMR3/VM.cpp(328)
> int VMR3Create(uint32_t, PCVMM2USERMETHODS, PFNVMATERROR, void *,
> PFNCFGMCONSTRUCTOR, void *, PVM *, PUVM *); rc=VERR_INTERNAL_ERROR_3
> 00:00:02.531778 VMSetError: Internal error no. 3.
> 00:00:02.533693 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
> aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap}
> aText={Internal error no. 3. (VERR_INTERNAL_ERROR_3)}, preserve=false
> aResultDetail=-227
> 00:00:02.534000 Console: Machine state changed to 'PoweredOff'
>
>
> This is the same error that shows when trying to run it on
> 12.1-STABLE-amd64-r359985 by the way.
>
> I am no wiz. And on top of that, VBox is extremely complex but I don't
> think that the problem lies on the kernel or on vbox kernel modules. They
> all load correctly and without errors on both 11.4-PRERELEASE-r360676M and
> 12.1-STABLE-amd64-r359985.
>
> What looks like (to my poor lame eyes) is that some revision change in
> userland "broke" the connection between vbox and its modules/drivers.
>
> So my quest is to try to pinpoint the changes between
> 11.3-STABLE-amd64-r359971 and 11.4-PRERELEASE-r360676M that made VirtualBox
> 6.0.8 stop working, and I was wondering if anyone here could give me some
> direction on how to accomplish that.
>
> Thanks for any advice.
You did not mention if you rebuild VirtualBox and its kernel modules after
update of FreeBSD to 11.4-PRERELEASE.
If not, such behaviour is expected and first thing you need is rebuild
VirtualBox using sources of 11.4-PRERELEASE
installed in /usr/src.
If you already did that, you need to bisect revisions. Also, you may find
useful output of "svnlite help diff"
that documents a way to find differences betwheen revisions: cd
/usr/src/sys/some-subdir && svnlite diff -r NN:MM
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Find specific changes between revisions
On Sat, May 9, 2020 at 3:25 PM Yuri Pankov wrote: > Eugene Grosbein wrote: > > 09.05.2020 23:41, Mario Lobo wrote: > > > >> Hi; > >> > >> I'm attempting to port VirtualBox 6.0.8 to FreeBSD. I managed do get it > >> working perfectly up to > >> > >> 11.3-STABLE-amd64-r359971. > [snip..] >> Thanks for any advice. > > > > You did not mention if you rebuild VirtualBox and its kernel modules > after update of FreeBSD to 11.4-PRERELEASE. > > If not, such behaviour is expected and first thing you need is rebuild > VirtualBox using sources of 11.4-PRERELEASE > > installed in /usr/src. > > > > If you already did that, you need to bisect revisions. Also, you may > find useful output of "svnlite help diff" > > that documents a way to find differences betwheen revisions: cd > /usr/src/sys/some-subdir && svnlite diff -r NN:MM > > And if you are looking for the specific revision that broke it, look > into the 'git bisect' using github's git mirror; there's also > devel/p5-App-SVN-Bisect, but I have never used it. > > The command: svn diff https://svn.freebsd.org/base/stable/11@359971 https://svn.freebsd.org/base/stable/11@360676 yielded a 170 Mbytes file!! It will be like looking for a needle in a haystack, in the dark, with just a hunch of where the needle was dropped. Well ... at least I have the haystack. Thanks everyone for the tips! -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio YET!!] ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: patch to make vboxvfs work again
That will do the trick indeed. I don't know about that bcmp thingy, ideally it would be needed. I presume there is a sufficient header mess which makes this to be the easiest hack. On 5/9/20, John-Mark Gurney wrote: > Hello virtualbox maintainer(s), > > Attached is a patch to make VirtualBox vboxvfs work again. I've only > tested under -current. > > mjg, what is the correct way to make this patch work on past versions > of FreeBSD? would a simple #ifdef VFS_VOP_VECTOR_REGISTER wrapper > around the call work? > > Thanks. > > -- > John-Mark GurneyVoice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > -- Mateusz Guzik ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
patch to make vboxvfs work again
Hello virtualbox maintainer(s),
Attached is a patch to make VirtualBox vboxvfs work again. I've only
tested under -current.
mjg, what is the correct way to make this patch work on past versions
of FreeBSD? would a simple #ifdef VFS_VOP_VECTOR_REGISTER wrapper
around the call work?
Thanks.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Index: virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_Makefile.kmk
===
--- virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_Makefile.kmk (revision 534710)
+++ virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_Makefile.kmk (working copy)
@@ -1,8 +1,10 @@
src/VBox/Additions/freebsd/vboxvfs/Makefile.kmk.orig 2017-04-28 16:59:22.0 +0200
-+++ src/VBox/Additions/freebsd/vboxvfs/Makefile.kmk 2017-07-13 00:52:49.020669620 +0200
-@@ -33,32 +33,36 @@
+--- src/VBox/Additions/freebsd/vboxvfs/Makefile.kmk.orig 2019-10-10 18:06:51.0 +
src/VBox/Additions/freebsd/vboxvfs/Makefile.kmk 2020-05-09 06:51:51.411749000 +
+@@ -32,33 +32,38 @@
+ . \
$(vboxvfs_0_OUTDIR)
vboxvfs_SOURCES = \
++ bcmp.c \
vboxvfs_vfsops.c \
- vboxvfs_vnops.c
+ vboxvfs_vnops.c \
Index: virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_bcmp.c
===
--- virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_bcmp.c (nonexistent)
+++ virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_bcmp.c (working copy)
@@ -0,0 +1,12 @@
+--- src/VBox/Additions/freebsd/vboxvfs/bcmp.c.orig 2020-05-09 06:57:06.22914 +
src/VBox/Additions/freebsd/vboxvfs/bcmp.c 2020-05-09 06:54:55.886751000 +
+@@ -0,0 +1,9 @@
++#include
++
++int bcmp(const void *b1, const void *b2, size_t len);
++
++int
++bcmp(const void *b1, const void *b2, size_t len)
++{
++ return __builtin_memcmp((b1), (b2), (len));
++}
Property changes on: virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_bcmp.c
___
Added: fbsd:nokeywords
## -0,0 +1 ##
+yes
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property
Index: virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_vboxvfs__vnops.c
===
--- virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_vboxvfs__vnops.c (revision 534793)
+++ virtualbox-ose/files/patch-src_VBox_Additions_freebsd_vboxvfs_vboxvfs__vnops.c (working copy)
@@ -1,5 +1,5 @@
src/VBox/Additions/freebsd/vboxvfs/vboxvfs_vnops.c.orig 2019-10-10 18:06:51 UTC
-+++ src/VBox/Additions/freebsd/vboxvfs/vboxvfs_vnops.c
+--- src/VBox/Additions/freebsd/vboxvfs/vboxvfs_vnops.c.orig 2019-10-10 18:06:51.0 +
src/VBox/Additions/freebsd/vboxvfs/vboxvfs_vnops.c 2020-05-09 07:07:49.485808000 +
@@ -1,10 +1,6 @@
-/* $Id: vboxvfs_vnops.c $ */
-/** @file
@@ -12,7 +12,7 @@
*
* This file is part of VirtualBox Open Source Edition (OSE), as
* available from http://www.virtualbox.org. This file is free software;
-@@ -14,228 +10,1338 @@
+@@ -14,228 +10,1339 @@
* VirtualBox OSE distribution. VirtualBox OSE is distributed in the
* hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
*/
@@ -172,6 +172,7 @@
+ .vop_write = vboxfs_write,
+ .vop_bmap = VOP_EOPNOTSUPP
};
++VFS_VOP_VECTOR_REGISTER(vboxfs_vnodeops);
-static int vboxvfs_access(struct vop_access_args *ap)
+static uint64_t
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
[Bug 246339] fix SIGSEGV of linux java packaged with ADVA NMS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246339 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org Summary|[Patch] SIGSEGV of linux|fix SIGSEGV of linux java |java packaged with ADVA NMS |packaged with ADVA NMS Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
