Re: VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

Host is FreeBSD 13-STABLE.Guest is Win 7 which I depend on for Quicken. I also use it to access a bank account at a bank that refuses access from any OS other than Windows or MacOS. I managed to access it for about a year by having Firefox lie and claim to be Windows, but that stopped working. They

Re: VirtualBox segmentation fault, FreeBSD-CURRENT r359068

On Thu, Mar 19, 2020 at 12:11 PM Graham Perrin wrote: > > Is this maybe related to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 or should I > make a separate bug report? > Please throw a tentative "Me too" on that PR; I'm investigating it, then we'll see if they're related or requir

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19 Oct, Matthew D. Fuller wrote: > On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of > Don Lewis, and lo! it spake thus: >> >> The first is that when I attempt to start a Virtualbox VM, the >> system panics. > > Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460 Thank

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of Don Lewis, and lo! it spake thus: > > The first is that when I attempt to start a Virtualbox VM, the > system panics. Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460 -- Matthew Fuller (MF4839) | fulle...@over-

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19 Oct, Don Lewis wrote: > On 20 Oct, Graham Perrin wrote: >> On 19/10/2018 23:47, Don Lewis wrote: >> >>> … when I attempt to start a Virtualbox VM, the system panics. … (guest) >>> Windows 7 with >> networking configured as > NAT and the underlying adapter being Intel >> PRO/1000 >> MT Desk

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 20 Oct, Graham Perrin wrote: > On 19/10/2018 23:47, Don Lewis wrote: > >> … when I attempt to start a Virtualbox VM, the system panics. … (guest) >> Windows 7 with > networking configured as > NAT and the underlying adapter being Intel PRO/1000 > MT Desktop (82540EM). … > > No panic here. 32-

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19/10/2018 23:47, Don Lewis wrote: > … when I attempt to start a Virtualbox VM, the system panics. … (guest) > Windows 7 with networking configured as > NAT and the underlying adapter being Intel PRO/1000 MT Desktop (82540EM). … No panic here. 32-bit Windows 7 guest with the same virtual adap

Re: Virtualbox kernel module on 11-CURRENT

On 8/06/2016 5:13 AM, Kevin Oberman wrote: On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi wrote: On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: Hello, I tried installing virtualbox from packages, building it from sources, trying the GENERIC kernel but everytime I can't start the kernel modul

Re: Virtualbox kernel module on 11-CURRENT

On 06/07/16 23:13, Kevin Oberman wrote: > On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi > wrote: > > On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: > > Hello, > > > > I tried installing virtualbox from packages, building it from sources, > > trying t

Re: Virtualbox kernel module on 11-CURRENT

On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi wrote: > On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: > > Hello, > > > > I tried installing virtualbox from packages, building it from sources, > > trying the GENERIC kernel but everytime I can't start the kernel module > > 'vboxdrv', it says: > >

Re: Virtualbox kernel module on 11-CURRENT

> On Jun 7, 2016, at 01:04, Guido Falsi wrote: > >> On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: >> Hello, >> >> I tried installing virtualbox from packages, building it from sources, >> trying the GENERIC kernel but everytime I can't start the kernel module >> 'vboxdrv', it says: >> "KLD

Re: Virtualbox kernel module on 11-CURRENT

On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: > Hello, > > I tried installing virtualbox from packages, building it from sources, > trying the GENERIC kernel but everytime I can't start the kernel module > 'vboxdrv', it says: > "KLD vboxdrv.ko: depends on kernel - not available or version mism

Re: VirtualBox network connectivity broken on recent -CURRENT

On Sun, Jun 05, 2016 at 12:35:29PM -0700, Don Lewis wrote: > On 4 Jun, To: mm...@nextbsd.org wrote: > > On 4 Jun, Matthew Macy wrote: > >> > >> > >> > >> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund > >> wrote > >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:

Re: VirtualBox network connectivity broken on recent -CURRENT

On 4 Jun, To: mm...@nextbsd.org wrote: > On 4 Jun, Matthew Macy wrote: >> >> >> >> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund >> wrote >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >> > > It looks like something changed in -CURRENT to break network >>

Re: VirtualBox network connectivity broken on recent -CURRENT

On 5 Jun, Otacílio wrote: > Em 04/06/2016 23:04, Randy Westlund escreveu: >> On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known to work with >>> r299139 (May 6th) an

Re: VirtualBox network connectivity broken on recent -CURRENT

On 4 Jun, Matthew Macy wrote: > > > > On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund > wrote > > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > > It looks like something changed in -CURRENT to break network > > > connectivity to VirtualBox guests. This was

Re: VirtualBox network connectivity broken on recent -CURRENT

Em 04/06/2016 23:04, Randy Westlund escreveu: On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: It looks like something changed in -CURRENT to break network connectivity to VirtualBox guests. This was last known to work with r299139 (May 6th) and is definitely broken with r301229. I'v

Re: VirtualBox network connectivity broken on recent -CURRENT

On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund wrote > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > It looks like something changed in -CURRENT to break network > > connectivity to VirtualBox guests. This was last known to work with > > r299139 (May 6th

Re: VirtualBox network connectivity broken on recent -CURRENT

On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > It looks like something changed in -CURRENT to break network > connectivity to VirtualBox guests. This was last known to work with > r299139 (May 6th) and is definitely broken with r301229. I've been having VirtualBox networking problem

Re: VirtualBox network connectivity broken on recent -CURRENT

On 4 Jun, Alan Somers wrote: > On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis wrote: >> On 3 Jun, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known to work with >>> r299139 (May 6th) and is definitely broken w

Re: VirtualBox network connectivity broken on recent -CURRENT

On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis wrote: > On 3 Jun, Don Lewis wrote: >> It looks like something changed in -CURRENT to break network >> connectivity to VirtualBox guests. This was last known to work with >> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox >> port

Re: VirtualBox network connectivity broken on recent -CURRENT

On 3 Jun, Don Lewis wrote: > It looks like something changed in -CURRENT to break network > connectivity to VirtualBox guests. This was last known to work with > r299139 (May 6th) and is definitely broken with r301229. The VirtualBox > port revisions are: > virtualbox-ose-4.3.38_1 >

Re: Virtualbox 4.3.20 crashes FreeBSD 11.0-CURRENT

Hi Hans, the bug is network related: in VirtualBox per VM Settings - Network - Attach to - changing from "NAT" to "Bridged Adapter" it works. Probably I will open a new PR for this bug. I am testing your patch and I will report the result in the above PR (id 194196). Maurizio 2014-11-29 17:49

Re: Virtualbox 4.3.20 crashes FreeBSD 11.0-CURRENT

On 11/29/14 16:00, Ranjan1018 . wrote: *Just upgrade emulators/virtualbox-ose-4.3.20 via pkg upgrade. Starting a VM, Windows XP or Ubuntu x86, after few seconds the laptop freezes.The system responds only to power off, pressing the power button for few seconds. The only things I can do is a phot

Re: Virtualbox "Settings" don't show any window (FreeBSD-10 current)

I run it on my 10-ALPHA1 without problem. There were many fix for clang/libc++ in ports recently. Try to update ports and rebuild all dependencies. Eric On Mon, Sep 16, 2013 at 7:14 AM, Mike C. wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Perhaps this is best placed in "curre

Re: Virtualbox addition in FreeBSD -current guest OS?

On Fri, May 03, 2013 at 12:13:58AM +0200, Bernhard Fröhlich wrote: > This should be fixed together with the update to 4.2.12 now. > Thank you. Glen pgplW_7fUjT3v.pgp Description: PGP signature

Re: Virtualbox addition in FreeBSD -current guest OS?

This should be fixed together with the update to 4.2.12 now. On Fri, Apr 26, 2013 at 7:43 PM, Mark Johnston wrote: > On Fri, Apr 26, 2013 at 11:07:35AM -0400, Glen Barber wrote: >> On Fri, Apr 26, 2013 at 11:02:10AM -0400, Mark Johnston wrote: >> > On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen B

Re: Virtualbox addition in FreeBSD -current guest OS?

On Fri, Apr 26, 2013 at 11:07:35AM -0400, Glen Barber wrote: > On Fri, Apr 26, 2013 at 11:02:10AM -0400, Mark Johnston wrote: > > On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen Barber wrote: > > > On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote: > > > > I was having problems compiling th

Re: Virtualbox addition in FreeBSD -current guest OS?

On Fri, Apr 26, 2013 at 11:02:10AM -0400, Mark Johnston wrote: > On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen Barber wrote: > > On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote: > > > I was having problems compiling the virtualbox guest additions on a FBSD > > > -current (Apr 23 20:30

Re: Virtualbox addition in FreeBSD -current guest OS?

On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen Barber wrote: > On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote: > > I was having problems compiling the virtualbox guest additions on a FBSD > > -current (Apr 23 20:30 EDT) system. I changed all the VM_OBJECT_LOCKs to > > VM_OBJECT_WLOCKs

Re: Virtualbox addition in FreeBSD -current guest OS?

On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote: > I was having problems compiling the virtualbox guest additions on a FBSD > -current (Apr 23 20:30 EDT) system. I changed all the VM_OBJECT_LOCKs to > VM_OBJECT_WLOCKs (and same for the UNLOCKS) and added rwlock.h to the > includes. Tha

Re: VirtualBox driver patch for -current post SVN r248084

On 03/09/13 21:58, Michael Butler wrote: > With the changing of the vm_object mutex to a rwlock, the VirtualBox > drivers (emulators/virtualbox-ose-kmod) need the attached patch to run, > > imb *** src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c~ Sat Mar 9 21:15:12 2013 --- src

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On 08/04/2012 17:56, Kevin Oberman wrote: > On Sat, Aug 4, 2012 at 2:30 PM, Doug Barton wrote: >> On 08/04/2012 14:26, Garrett Cooper wrote: >>> On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton wrote: >>> On 08/04/2012 00:40, O. Hartmann wrote: > No, also in my case. I build world and the VBo

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

Am 08/04/12 22:26, schrieb Doug Barton: > On 08/04/2012 00:40, O. Hartmann wrote: >> No, also in my case. I build world and the VBox software with each >> kernel - usually. > > You can ensure that by putting this in src.conf: > > PORTS_MODULES= emulators/virtualbox-ose-kmod > > You can place ot

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Sat, Aug 4, 2012 at 2:30 PM, Doug Barton wrote: > On 08/04/2012 14:26, Garrett Cooper wrote: >> On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton wrote: >> >>> On 08/04/2012 00:40, O. Hartmann wrote: No, also in my case. I build world and the VBox software with each kernel - usually. >>> >

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On 08/04/2012 14:26, Garrett Cooper wrote: > On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton wrote: > >> On 08/04/2012 00:40, O. Hartmann wrote: >>> No, also in my case. I build world and the VBox software with each >>> kernel - usually. >> >> You can ensure that by putting this in src.conf: >> >> POR

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 08/04/2012 00:40, O. Hartmann wrote: >> No, also in my case. I build world and the VBox software with each >> kernel - usually. > > You can ensure that by putting this in src.conf: > > POR

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/04/2012 00:40, O. Hartmann wrote: > No, also in my case. I build world and the VBox software with each > kernel - usually. You can ensure that by putting this in src.conf: PORTS_MODULES= emulators/virtualbox-ose-kmod You can place other mod

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

Am 08/04/12 00:36, schrieb Kevin Oberman: > On Fri, Aug 3, 2012 at 6:41 AM, Luigi Rizzo wrote: >> On Fri, Aug 03, 2012 at 07:44:27AM +0200, Bernhard Fr?hlich wrote: >>> On Fr.,?? 3. Aug. 2012 06:18:33 CEST, Kevin Oberman >>> wrote: >>> On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. wr

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Fri, Aug 3, 2012 at 6:41 AM, Luigi Rizzo wrote: > On Fri, Aug 03, 2012 at 07:44:27AM +0200, Bernhard Fr?hlich wrote: >> On Fr.,?? 3. Aug. 2012 06:18:33 CEST, Kevin Oberman >> wrote: >> >> > On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. >> > wrote: >> > > I discover that when running Windows

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Fri, Aug 03, 2012 at 07:44:27AM +0200, Bernhard Fr?hlich wrote: > On Fr.,?? 3. Aug. 2012 06:18:33 CEST, Kevin Oberman > wrote: > > > On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. > > wrote: > > > I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 > > > (r238968: Wed Aug 1

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Fr.,  3. Aug. 2012 06:18:33 CEST, Kevin Oberman wrote: > On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. > wrote: > > I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 > > (r238968: Wed Aug 1 14:26:40 CEST 2012), VBox is most recent from the > > ports, that the VirtualBox ea

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Thu, Aug 2, 2012 at 9:18 PM, Kevin Oberman wrote: > On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. > wrote: >> I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 >> (r238968: Wed Aug 1 14:26:40 CEST 2012), VBox is most recent from the >> ports, that the VirtualBox eats up 100%

Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O. wrote: > I discover that when running Windows 7 in a VirtualBox On FreeBSD 10 > (r238968: Wed Aug 1 14:26:40 CEST 2012), VBox is most recent from the > ports, that the VirtualBox eats up 100% CPU time and freezes Windows 7 > for more than a minute. For

Re: virtualbox r0 memory management update

on 06/12/2011 22:22 Andriy Gapon said the following: > > Could you please change that line as follows? > vm_page_t pPage = pPages +iPage; > Additionally the patch has another bug. Here is a patch on top of the previous patch: --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.ori

Re: virtualbox r0 memory management update [Was: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}]

on 06/12/2011 20:54 Bernhard Froehlich said the following: > On 06.12.2011 12:14, Andriy Gapon wrote: >> Meanwhile, here is the code that I came up with: >> http://people.freebsd.org/~avg/vbox/ >> For your convenience I have uploaded both the new file and its diff >> against svn >> head. I am test

Re: virtualbox r0 memory management update [Was: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}]

On 06.12.2011 12:14, Andriy Gapon wrote: Meanwhile, here is the code that I came up with: http://people.freebsd.org/~avg/vbox/ For your convenience I have uploaded both the new file and its diff against svn head. I am testing this on FreeBSD head (r228017), so far no breakage observed. I would

Re: VirtualBox causes kernel panic

On Mon, 22 Aug 2011 13:14:48 +0200, Bernhard Froehlich wrote: > On Sat, 20 Aug 2011 19:35:16 +0100, Alvaro Castillo wrote: >> VirtualBox Version: 4.0.12_OSE r72916 >> >> uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #1: Wed Aug >> 17 01:21:47 WEST 2011 >> net...@shuttle0.lan:/usr/obj/u

Re: VirtualBox causes kernel panic

On Sat, 20 Aug 2011 19:35:16 +0100, Alvaro Castillo wrote: > VirtualBox Version: 4.0.12_OSE r72916 > > uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #1: Wed Aug > 17 01:21:47 WEST 2011 > net...@shuttle0.lan:/usr/obj/usr/src/sys/GALILEO amd64 > > The kernel panic is occurred when I s

Re: virtualbox-ose 4.0.8 fails

On Tuesday 26 July 2011 08:00 am, Ben Ellis wrote: > > On Saturday 25 June 2011 10:28 am, Bernhard Froehlich wrote: > >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > >> > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: > >> >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim >>

Re: virtualbox-ose 4.0.8 fails

On Monday 27 June 2011 03:42 pm, Bernhard Froehlich wrote: > On Mon, 27 Jun 2011 11:40:31 -0400, Jung-uk Kim wrote: > > On Saturday 25 June 2011 10:28 am, Bernhard Froehlich wrote: > >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > >> > On Friday 24 June 2011 02:58 pm, George Kontostanos

Re: virtualbox-ose 4.0.8 fails

On Mon, 27 Jun 2011 11:40:31 -0400, Jung-uk Kim wrote: > On Saturday 25 June 2011 10:28 am, Bernhard Froehlich wrote: >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: >> > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim >> > >>

Re: virtualbox-ose 4.0.8 fails

On Saturday 25 June 2011 10:28 am, Bernhard Froehlich wrote: > On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: > >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim > > > > wrote: > >> >> Any ideas regarding the virtualbox itself ?

Re: virtualbox-ose 4.0.8 fails

On 06/27/11 02:49, Bernhard Froehlich wrote: On Mon, 27 Jun 2011 10:54:08 +0300, Sergey V. Dyatko wrote: On Sat, 25 Jun 2011 16:28:41 +0200 Bernhard Froehlich wrote: On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: On Fri, Jun

Re: virtualbox-ose 4.0.8 fails

On Mon, 27 Jun 2011 10:54:08 +0300, Sergey V. Dyatko wrote: > On Sat, 25 Jun 2011 16:28:41 +0200 > Bernhard Froehlich wrote: > >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: >> > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk K

Re: virtualbox-ose 4.0.8 fails

On Sat, 25 Jun 2011 16:28:41 +0200 Bernhard Froehlich wrote: > On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: > >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim > > wrote: > >> >> Any ideas regarding the virtualbox itself ? >

Re: virtualbox-ose 4.0.8 fails

On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim > wrote: >> >> Any ideas regarding the virtualbox itself ? >> > >> > I am rebuilding world/kernel now. �After that, I'll rebuild >> >

Re: virtualbox-ose 4.0.8 fails

On Fri, Jun 24, 2011 at 11:11 PM, Jung-uk Kim wrote: > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim > wrote: >> >> Any ideas regarding the virtualbox itself ? >> > >> > I am rebuilding world/kernel now.  After that, I'll rebuild >> > v

Re: virtualbox-ose 4.0.8 fails

On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: > On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim wrote: > >> Any ideas regarding the virtualbox itself ? > > > > I am rebuilding world/kernel now. �After that, I'll rebuild > > virtualbox-ose and try to fix it unless someone beat me to it.

Re: virtualbox-ose 4.0.8 fails

On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim wrote: > >> Any ideas regarding the virtualbox itself ? > > I am rebuilding world/kernel now.  After that, I'll rebuild > virtualbox-ose and try to fix it unless someone beat me to it. :-) > > Jung-uk Kim > Brilliant !!! -- George Kontostanos aisecu

Re: virtualbox-ose 4.0.8 fails

On Friday 24 June 2011 02:40 pm, George Kontostanos wrote: > > You should be able to build the kmod with this patch. > > > > http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-free > >bsd-mp-r0drv-freebsd.c > > > > Just drop this patch in ports/emulators/virtualbox-ose-kmod/files > > and

Re: virtualbox-ose 4.0.8 fails

> > You should be able to build the kmod with this patch. > > http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-mp-r0drv-freebsd.c > > Just drop this patch in ports/emulators/virtualbox-ose-kmod/files and > rebuild. > > Please note the revision wasn't set right for the obvious re

Re: virtualbox-ose 4.0.8 fails

On 06/24/11 10:52, Jung-uk Kim wrote: On Friday 24 June 2011 01:14 pm, Matt wrote: It fails a couple ways actually, first on an isDVD in a disk system request...commenting out the inq_(something, not in front of machine with recent svn) parts of that code yields virtualbox compiling, but failing

Re: virtualbox-ose 4.0.8 fails

On Friday 24 June 2011 01:14 pm, Matt wrote: > It fails a couple ways actually, first on an isDVD in a disk system > request...commenting out the inq_(something, not in front of > machine with recent svn) parts of that code yields virtualbox > compiling, but failing during kmod compile due to the r

Re: virtualbox-ose 4.0.8 fails

On 06/24/11 09:41, George Kontostanos wrote: Hi everyone, I am trying to compile virtualbox-ose 4.0.8 but it fails with /out/freebsd.amd64/debug -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" -DRTP

Re: VirtualBox guest panic in ACPI

On 26/03/2011, at 17:47, Daniel O'Connor wrote: > I tried running a -current (r219926) release in VirtualBox and got a panic. I found that modifying the VM with.. VBoxManage modifyvm Installer\ test --hpet on --ioapic on Makes it boot. > > acpi0: could not allocate interrupt > ACPI Exception:

Re: Virtualbox

Ian FREISLICH wrote: > > >Has anyone managed to make Virtualbox work on 9-Current? Since > > >installing 3.1.2-OSE VMs, all brand new, abort on startup. > > > > > >The last part of the log seems pertinent: > > > > > >00:00:15.481 !!Assertion Failed!! > > >00:00:15.481 Expression: paPages[i].Phys !

Re: Virtualbox

On Mon, 1 Mar 2010 18:09:34 +0300, KOT MATPOCKuH wrote: > 2010/2/24 Bernhard Froehlich >> >> >> 00:00:15.481 !!Assertion Failed!! >> 00:00:15.481 Expression: paPages[i].Phys != 0 && paPages[i].Phys != >> >>> NIL_RTHCPHYS && >!(paPages[i].Phys & PAGE_OFFSET_MASK) >> 00:00:15.481 L

Re: Virtualbox

2010/2/24 Bernhard Froehlich > > > 00:00:15.481 !!Assertion Failed!! > 00:00:15.481 Expression: paPages[i].Phys != 0 && paPages[i].Phys != > >>> NIL_RTHCPHYS && >!(paPages[i].Phys & PAGE_OFFSET_MASK) > 00:00:15.481 Location  : > >>> /usr/ports/emulators/virtualbox-ose/work/Virtual

Re: Virtualbox

On Wed, 24 Feb 2010 16:38:15 +0100, Bernhard Froehlich wrote: > beat@ has already commited it to our vbox testing repository so you > can get the virtualbox 3.1.4 port with the new patch included from: > > http://svn.bluelife.at/nightlies/virtualbox-port-r731.tar.gz Work fine here! 8.0-STABLE r204

Re: Virtualbox

On Wed, February 24, 2010 10:38, Bernhard Froehlich wrote: > I've got the new patch from Alexander Eichner now. It's currently untested > on newer kernels so could someone please test it on an affected kernel? > > http://pastebin.ca/1808177 > (linefeeds from the patch are dos so beware!) > > beat@

Re: Virtualbox

On Wed, 24 Feb 2010 16:04:33 +0100, Bernhard Froehlich wrote: > On Wed, 24 Feb 2010 15:02:30 +0100, Giovanni Trematerra > wrote: >> 2010/2/24 Bernhard Fröhlich : >>> Hi Has anyone managed to make Virtualbox work on 9-Current?  Since installing 3.1.2-OSE VMs, all brand new, abort

Re: Virtualbox

On Wed, 24 Feb 2010 15:02:30 +0100, Giovanni Trematerra wrote: > 2010/2/24 Bernhard Fröhlich : >> >>>Hi >>> >>>Has anyone managed to make Virtualbox work on 9-Current?  Since >>>installing 3.1.2-OSE VMs, all brand new, abort on startup. >>> >>>The last part of the log seems pertinent: >>> >>>00:00

Re: Virtualbox

=?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= wrote: > > >Hi > > > >Has anyone managed to make Virtualbox work on 9-Current? Since > >installing 3.1.2-OSE VMs, all brand new, abort on startup. > > > >The last part of the log seems pertinent: > > > >00:00:15.481 !!Assertion Failed!! > >00:00:15.481 Expressio

Re: Virtualbox

2010/2/24 Bernhard Fröhlich : > >>Hi >> >>Has anyone managed to make Virtualbox work on 9-Current?  Since >>installing 3.1.2-OSE VMs, all brand new, abort on startup. >> >>The last part of the log seems pertinent: >> >>00:00:15.481 !!Assertion Failed!! >>00:00:15.481 Expression: paPages[i].Phys !=

Re: Virtualbox

>Hi > >Has anyone managed to make Virtualbox work on 9-Current? Since >installing 3.1.2-OSE VMs, all brand new, abort on startup. > >The last part of the log seems pertinent: > >00:00:15.481 !!Assertion Failed!! >00:00:15.481 Expression: paPages[i].Phys != 0 && paPages[i].Phys != NIL_RTHCPHYS &&

Re: Virtualbox

On Wed, Feb 24, 2010 at 12:16 PM, Jacques Fourie wrote: > As a test you can apply the following mod to sys/i386/include/pmap.h > and re-compile vboxdrv.ko. It fixed the problem for me but I'm by no > means an expert on the i386 pmap stuff so use at your own risk. Also > revert the change to pmap.h

Re: Virtualbox

As a test you can apply the following mod to sys/i386/include/pmap.h and re-compile vboxdrv.ko. It fixed the problem for me but I'm by no means an expert on the i386 pmap stuff so use at your own risk. Also revert the change to pmap.h after re-compiling vboxdrv just so that you don't inadvertently

Re: Virtualbox

Hi, On what kind of CPU are you trying to get VirtualBox to work? In some cases VirtualBox requires VT-x/AMD-V support in the CPU to work - you might want to make sure your CPU supports that and it's actually on. Otherwise, I've see the same errors trying to get VirtualBox to work on Intel Atom N

Re: Virtualbox

On Tue, Feb 23, 2010 at 5:20 PM, Ian FREISLICH wrote: > Hi > > Has anyone managed to make Virtualbox work on 9-Current?  Since > installing 3.1.2-OSE VMs, all brand new, abort on startup. > > The last part of the log seems pertinent: > > 00:00:15.481 !!Assertion Failed!! > 00:00:15.481 Expression:

Re: Virtualbox

On Tue, Feb 23, 2010 at 06:20:22PM +0200, Ian FREISLICH wrote: > Hi > > Has anyone managed to make Virtualbox work on 9-Current? Since > installing 3.1.2-OSE VMs, all brand new, abort on startup. > > The last part of the log seems pertinent: > > 00:00:15.481 !!Assertion Failed!! > 00:00:15.481