On Sun, Aug 1, 2021 at 1:38 PM Guido Falsi wrote:
> On 01/08/21 14:49, Mario Lobo wrote:
> >
> > On Wed, Jul 21, 2021, 17:11 Guido Falsi via freebsd-emulation
> > mailto:freebsd-emulation@freebsd.org>>
> > wrote:
> >
> > Hi,
> >
> >
On Wed, Jul 21, 2021, 17:11 Guido Falsi via freebsd-emulation <
freebsd-emulation@freebsd.org> wrote:
> Hi,
>
> I've tested updating to latest virtualbox. It mostly works. But the
> audio subsystem has been overhauled. Our patches don't apply anymore,
> but they may not be necessary. Looks like th
don't know exactly what should be on a report and I'm not a committer but
in my humble opinion,
I think your text synthesizes the resulting port pretty well.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!]
_
6 working was on:
FreeBSD 11.3-STABLE #0 r353691
virtualbox-ose-6.0.8 General-purpose full virtualizer for x86
hardware
virtualbox-ose-kmod-6.0.8 VirtualBox kernel module for FreeBSD
This same port doesn't compile and/or runs on any FreeBSD above the above
version
--
Mario Lo
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 perf
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 m
ick
> --
> punkt.de GmbH Internet - Dienstleistungen - Beratung
> Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
> 76133 Karlsruhe i...@punkt.de http://punkt.de
> AG Mannheim 108285 Gf: Juergen Egeling
>
>
ectivity, If I
unplug the cable, lagg0 switches over wlan0 and the host never looses
connectivity, BUT the VMs do!
Even if boot with the cable unplugged, the host has perfect connectivity
but any started VM doesn' t.
I can't think of a reason why this is happening and go
ebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "freebsd-emulation-
> unsubscr...@freebsd.org"
>
Have you tried starting it with VBoxHeadless?
--
Mario Lobo
http://www.mallavoodoo.c
ed any further details.
>
>
> Regards,
>
> Dan
>
> --
> Dan Turner
> SkillsForge Ltd.
> The Catalyst,
> Baird Lane,
> Heslington,
> York,
> YO10 5GA
>
> EMAIL DISCLAIMER: http://www.york.ac.uk/docs/disclaimer/email.htm
> _______
> freebsd-emulation@f
peoples' port, it compiles and
runs fine.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing cle
scr...@freebsd.org"
Tell it to use base ssl by putting DEFAULT_VERSIONS+=ssl=base
in make.conf and see if it compiles.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that wo
Hi;
Just found out that jkim has much better port version for trying VBox.
Please get it from here.
https://people.freebsd.org/~jkim/vbox/vbox5020.tar.xz
Same warnings from my previous post apply.
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET
d the port here:
http://www.digiart.art.br/virtualbox-ose.5.0.20.tar.gz
Please report your findings.
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that would also stop y
d the port here:
http://www.digiart.art.br/virtualbox-ose.5.0.20.tar.gz
Please report your findings.
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that would also stop y
2016-04-13 15:20 GMT-03:00 Johannes Jost Meixner :
> Hi,
>
>
> On 04/13/16 04:39 PM, Mario Lobo wrote:
> > Hi there;
> >
> > A recent commit seems to make this is possible:
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206943
> >
>
, should it be:
OVERRIDE_LINUX_BASE_PORT=c6
OVERRIDE_LINUX_NONBASE_PORTS=c6
or
OVERRIDE_LINUX_BASE_PORT=c6_64
OVERRIDE_LINUX_NONBASE_PORTS=c6_64 ?
How about compat.linux.osrelease: 2.6.18? Still the same?
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio
On Sat, 5 Mar 2016 20:47:00 +0100
Bernhard Fröhlich wrote:
> Am 05.03.2016 3:56 nachm. schrieb "Mario Lobo" :
> >
> > On Sat, 5 Mar 2016 12:26:42 +0100
> > Bernhard Fröhlich wrote:
> >
> > > Am 05.03.2016 1:01 vorm. schrieb "Michael" :
&
66:11.24 /usr/local/lib/virtualbox/VBoxSVC
934 v0- I 3065:24.90 /usr/local/lib/virtualbox/VBoxHeadless
-startvm DBServer --vrde off 935 v0- I
13068:32.29 /usr/local/lib/virtualbox/VBoxHeadless -startvm WEBServer
--vrde off 936 v0- I
8552:00.08 /usr/local/lib/virtualbox/VBoxHeadless -
On Sat, 26 Sep 2015 13:44:33 +0200
Alexander Leidinger wrote:
> Quoting Mario Lobo (from Thu, 24 Sep 2015 19:54:43
> -0300):
>
> > I was trying to find out where a linux binary will look for the /dev
> > directory.
> >
> > I tried to link the device I n
Hi;
Using 11-CURRENT.
I was trying to find out where a linux binary will look for the /dev
directory.
I tried to link the device I need to /compat/linux/dev but that didn't
work.
How can a linux binary see the devices (serial ports, usb, etc) of the
system?
Thanks,
--
Mario Lobo
On Sun, 20 Sep 2015 17:49:38 +0200
Mateusz Guzik wrote:
> On Sun, Sep 20, 2015 at 12:40:35PM -0300, Mario Lobo wrote:
> > > > I'm trying to compile this epoll implementation into the kernel
> > > > following
> > > >
> > > > https://
On Sun, 20 Sep 2015 13:03:26 +0200
Gary Jennejohn wrote:
> On Sat, 19 Sep 2015 13:06:25 -0300
> Mario Lobo wrote:
>
> > Hi;
> >
> > I'm trying to compile this epoll implementation into the kernel
> > following
> >
> > https://wiki.freebsd.
in man kqueue:
int kqueue(void);
so I really ran out of options on finding out what this kqueue call
really is about.
Would anyone have any pointers on this?
Thanks.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you
On Thu, 10 Sep 2015 16:41:33 -0500
Vue Vang wrote:
> Any idea on when 5.0 will make it to ports?
>
> Thanks,
>
See here:
https://lists.freebsd.org/pipermail/freebsd-emulation/2015-September/012793.html
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-A
this mail.
I hope the list doesn't trim it.
Regards,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that would also stop you from
On Fri, 4 Sep 2015 06:20:31 -0600 (MDT)
Warren Block wrote:
> On Fri, 4 Sep 2015, Mario Lobo wrote:
>
> > Hi there.
> >
> >
> > I have never had a problem with any virtualbox version.
> >
> > I don't know what I did or installed or configured, but
se-kmod-4.3.30 VirtualBox kernel module for
FreeBSD Would anyone have any suggestion on this?
Thanks
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that would also stop yo
se-kmod-4.3.30 VirtualBox kernel module for
FreeBSD Would anyone have any suggestion on this?
Thanks
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
"UNIX was not designed to stop you from doing stupid things,
because that would also stop you from
he VM itself should make no
difference, right? Except noticing possible improvements on
responsiveness, speed, etc... Well, maybe there could incompatibilities
if the VM has guestadditions 4.3.28/30 installed and is running on a
5.0 environment, although I believe this shouldn't happen.
Other
> Zubair
>
> It is 4.3.30 - https://www.virtualbox.org/wiki/Changelog-4.3
>
> --
> Bernhard Fröhlich
>
How about VBox 5.0? Is there a time frame of when will it reach the
ports/pkg?
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Aud
the answer.
>
> No not right now. All work happens directly in the FreeBSD portstree
> now.
>
Any prediction for a port date of VBox 5, Bernhard?
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE)
"UNIX was not desi
_ problem.
>
> Regards,
> Christoph
>
Nope!
I have:
/usr/local/lib/virtualbox/VBoxRT.so:
(snip)
libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x8026a7000)
libcrypto.so.7 => /lib/libcrypto.so.7 (0x80431d000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x804
On Thu, 26 Mar 2015 15:24:29 -0600 (MDT)
Warren Block wrote:
> On Thu, 26 Mar 2015, Mario Lobo wrote:
>
> > On Thu, 26 Mar 2015 10:29:51 -0600 (MDT)
> > Warren Block wrote:
> >
> >> Anyone else having trouble with 4.3.26?
> >>
> >> Seems li
LE FreeBSD 10.1-STABLE #0 r278323M: Fri Feb 6
19:34:48 BRT 2015
and
pkg info | grep virtual
virtualbox-ose-4.3.26 General-purpose full virtualizer for x86
hardware virtualbox-ose-kmod-4.3.26 VirtualBox kernel module for
FreeBSD
and no problem whatsoever.
--
Mario Lobo
http://www
users list but have no got any response that could
solve this yet.
I've been googling for a fews days but so far no info
that I found gave me any hint on solving this.
Would anyone have any pointers?
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
users list but have no got any response that could
solve this yet.
I've been googling for a fews days but so far no info
that I found gave me any hint on solving this.
Would anyone have any pointers?
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET
your kernel could be out of sync with your /usr/src.
Try recompiling your kernel and reboot to check if the vbox module
loads.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE)
"UNIX was not designed to stop you from
x198) -> GP(0)
> 00:00:13.174017
> !!
> 00:00:13.174017 !!
> 00:00:13.174018 !! Guru Meditation 1155
> (VINF_EM_TRIPLE_FAULT)
> 00:00:13.17
FYI
Sorry! Forgot to reply to the list. My bad.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE)
"UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing clever things."
rc.d.
I said initially because I wasn't too akin to creating VMs from command
line, and opted for the vbox qt GUI to create them.
Regards,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE)
"UNIX was not designed to stop you fr
already so the number
> of ports patches for 4.3 has decreased a bit.
>
> This release would not have been possible without the awesome
> feedback and help on emulation@ and all people that did send patches:
> Mikhail Tsatsenko, Peter Jeremy, David Morgan, Mario Lobo, Jung-uk
> Kim, D
.amd64/release/obj/VirtualBox/VirtualBox.so]
Error 1
Dispite my attempt to remove -ldl (which applies to only to linux,
according to what i googled) from all occurences I could find, it
somehow keeps sneaking in again.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audi
utput. This would show the preprocessor file which is passed to yasm
> and would help to narrow it down.
>
> On Mon, Nov 11, 2013 at 2:33 PM, Mario Lobo wrote:
> > How about these? Any clues?
> > I've been trying to figure this out for days and I'm still stuck.
>
kmk: ***
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
Error 1
Thanks,
Mario Lobo
2013/11/9 Mike C.
>
>
> On 11/09/13 07:00, Bernhard Fröhlich wrote:
> >
> > Am 04.11.2013 16:35 schrieb &q
s/virtualbox-ose/work/VirtualBox-4.3.2/include/iprt/x86extra.mac:206:
warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136
kmk: ***
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
Error 1
System: FreeBSD Papi 8.3-STABLE F
mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "
> freebsd-emulation-unsubscr...@freebsd.org"
>
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FRE
*,
> STAMUNIT, const char*)
>
>
> Yuri
>
> ___
> freebsd-emulation@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to
> "freebsd-emulation-
On Sat, 29 Sep 2012 08:08:11 +0200
Bernhard Fröhlich wrote:
> On Fr., 28. Sep. 2012 23:25:42 CEST, Mario Lobo
> wrote:
>
> > On Fri, 28 Sep 2012 15:57:40 -0500
> > Rusty Nejdl wrote:
> >
> > > On 2012-09-28 15:43, Gour wrote:
> > > > On Fri,
On Fri, 28 Sep 2012 23:32:31 +0200
Gour wrote:
> On Fri, 28 Sep 2012 18:25:42 -0300
> Mario Lobo wrote:
>
> > Shared folders always worked perfectly for me with all versions of
> > VBox I used so far with FBSD as a host.
>
> What about USB support?
>
>
>
ere 3 patches specific
for FBSD, published by Ed Maste on VBox-dev list
that were committed by Alexander Eichner. They are:
[vbox-dev] [PATCH] Implement media state for host-only interface
[vbox-dev] [PATCH] Make FreeBSD build with SUPDRV_WITH_RELEASE_LOGGER
[vbox-dev] [PATCH] Correct com
p://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.0-20120920.tar.gz
>
> IRC: #freebsd-vbox on Freenode
>
>
> Bernhard on behalf of the new VirtualBox on FreeBSD Team!
>
Great news! It's official now !
I've been using it for about 3 weeks now. Confirm the stabil
On Thursday 28 June 2012 19:32:16 John Hein wrote:
> Mario Lobo wrote at 18:51 -0300 on Jun 28, 2012:
> > System: FreeBSD 8.3-STABLE
> >
> > Trying to compile from ports and get the following error
> >
> > /usr/ports/emulators/virtualbox-
> > ose/wo
> System: FreeBSD 8.3-STABLE
> Trying to compile from ports and get the following error
Updated ports tree and rebuilt libvncserver.
Sorry for the noise... :(
Thanks
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblow
-
ose/work/VirtualBox-4.1.18/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp:94:
error: 'struct _rfbScreenInfo' has no member named 'ipv6port'
It happened when trying with 4.1.16 too.
Any suggestions on how to solve this?
Thanks
--
Mario Lobo
http://www.mallavoodoo.com.b
-
ose/work/VirtualBox-4.1.18/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp:94:
error: 'struct _rfbScreenInfo' has no member named 'ipv6port'
It happened when trying with 4.1.16 too.
Any suggestions on how to solve this?
Thanks
--
Mario Lobo
http://www.mallavoodoo.com.b
ualbox-ose-kmod]>uname -a
FreeBSD Papi 8.2-STABLE FreeBSD 8.2-STABLE #0: Mon Jan 30 11:08:39 BRT 2012
root@Papi:/usr/src/sys/amd64/compile/LOBO amd64
Had 4.1.8 when I red your post, went on and just finished compiling 4.1.12.
Up and running as I write.
I am yet to have a pr
On Thursday 22 December 2011 03:11:02 Daichi GOTO wrote:
> And it's working well :)
>
> p.s.
> Anyone can use Windows 7 guest with Aero effect on vbox 4.1.8?
>
> On Thu, 22 Dec 2011 13:48:25 +0900
Yes!! Mine has been working since 4.1.6.
--
Mario Lobo
http://www.mal
d vbox
3.x, I am yet to see issues on VBox and FBSD amd64 host!
I am using the 4.0.5 devel port now and I'm running all sorts of guest OSes
inside of it, with the SAME .vdi files of my first VBox install!
Here is a list of my guests:
Win7 (32&64)
XP (2)
Win2003 (4)
Leopard OSx
retail
tal 3D drivers (installed in safe mode)
and my board is a 9800 GT.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winfoes FREE)
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mail
ions
> installed earlier on Windows 7 so the Windows Experience Index ran correctly
> but gave graphics a 1. I installed guest additions in safe mode with the
> experimental 3d support and then rebooted. Running the test this time
> closed the VM just as you saw.
>
> Rusty
>
Just found something.
On a win 7 guest. When I tried to refresh the "Windows Experience Index", the
VM was summarily closed midway through the process. No crash or abort warnings
of any kind. No host disturbance whatsoever however.
Without the 2d enebled, the refresh runs without proble
gt; >
> > Sean
>
> Just found the enable 2d acceleration checkbox. I only works for
> Windows clients that you have installed the 2d acceleration drivers.
> Using it for Diablo II has a noticeable improvement. No mouse
> stuttering that I have seen since then.
>
d VB when I moved the disk. Is
> now running 3.2.8.
>
Even in safe mode?
If it doesn't BSOD in safe mode, try deinstalling/reinstalling guest
additions.
hope this helps.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winfoes FREE)
___
obj/usr/src/sys/LOBO amd64
VBox rules ! My deepest thanks to all developers, porters, testers and users
that made this a reality.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winfoes FREE)
___
freebsd-e
used will be chosen based on the
file extension
So:
VBoxHeadless -s VM_NAME -n -m 5100
will start the VM "VM_NAME" with a VNC listener at port 5100
So any vnc viewer will connect to it.
Very simple and eas
virtualbox developers and this is obviously an
> known bug in the 3.2.0 additions. As a workaround you can use the 3.1.8
> additions and they said it will be fixed with 3.2.2.
>
> Thanks!
>
Actually, this problem doesn't happen up to
VBoxGuestAdditions_3.2.0_BETA1.iso.
VBoxGuestAd
the port Makefile could have --enable-vde added, on the next port
> > revision?
>
> beat@ has updated the devel ports and added VDE and VNC support. A few
> weeks ago there was also a VNC patch committed upstream so vbox will not
> need to be patched in the future to have v
ot; --with-g++="${CXX}" --enable-vde
This corrected the problem. Now the VDE Adapter appears in the "Attached to"
listBox.
Could the configure script be patched to set the condition to TRUE, or maybe
the port Makefile could have --enable-vde added, on the next
On Wednesday 21 April 2010 07:11:43 Bernhard Froehlich wrote:
> On Tue, 20 Apr 2010 17:42:01 +0000, Mario Lobo wrote:
> > On Tuesday 20 April 2010 19:27:15 Brandon Gooch wrote:
> >> On Tue, Apr 20, 2010 at 6:32 PM, Rusty Nejdl
> >
> > wrote:
> >> >&g
tyv0, and let it
> >> run for while? This is the only way I can get a clean crash dump and
> >> generate any data -- I've never been able to "cleanly" crash my system
> >> running Xorg (it usually freezes).
> >>
> >> FYI, I'm running multip
nd rebuild (finished yesterday)
AOD79GX/128M Mobo (latest bios)
Phenom II 955 Black CPU
8G ram
VirtualBox (Devel or 3.1.6 from ports)
3 500G sata barracudas
I tried my best but I reached the limit of my knowledge in trying to figure
this one out.
Ironically, Virtualbox is superbly tuned to Wi
system since always.
This started happening when moved from 3.1.51r27187 to 3.1.51r27657
virtualbox-ose 3.1.6 does not have this problem. Why don't I stick to it?
because my MacOSx doesn't run on it. Which brigsup one question:
Why the 3.1.5 devel version has the Mac OS option and 3.1
ng for the fsck to finish to see my
observation was correct. And it was! When fsck finished, the thingy went off
with it.
I know its not a big thing but, is it a bug?.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winfoes FREE)
__
74 matches
Mail list logo
