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

[Kevin Oberman]

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
make the almost humorous claim that only Windows and MacOS are adequately
secure.

At this point I have no idea if the issue is with VirtualBx or FreeBSD,
but, after seeing more details of your problem, I doubt mine is related. I
really suspect it's VirtualBox, so I will drop out of this discussion as it
appears that I don't have an issue with it. After some more work on it,
I'll open a ticket with emulators@.

Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Fri, Mar 26, 2021 at 7:23 PM Graham Perrin 
wrote:

> On 26/03/2021 21:55, Kevin Oberman wrote:
> > On Fri, Mar 26, 2021 at 1:01 PM Graham Perrin  > > wrote:
> >
> >
> > If I'm not mistaken:
> >
> > …
> >
> > Had nothing but frequent guest lockups on 6.1.18 with my Win7 system.
> > That was right after 6.1.18 was put into ports. Fell back to legacy
> > (v5) and will try again shortly to see if it's any better.
>
> Windows 7 guest or host?
>
> For me, Windows 10 20H2 guest is rock solid.
>
> % pkg info -x virtualbox
> virtualbox-ose-6.1.18
> virtualbox-ose-kmod-6.1.18_1
> % freebsd-version -kru
> 14.0-CURRENT
> 14.0-CURRENT
> 14.0-CURRENT
> % uname -a
> FreeBSD mowa219-gjp4-8570p 14.0-CURRENT FreeBSD 14.0-CURRENT #90
> main-n245648-66f138563be: Thu Mar 25 08:00:54 GMT 2021
> root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
> amd64
> %
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox segmentation fault, FreeBSD-CURRENT r359068

[Kyle Evans]

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 requires yet another PR.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Don Lewis]

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

Thanks, that appears to be it.  I'm kind of wondering why I didn't run
into this before my last upgrade.  I was worried about this before my
previous upgrade, but didn't encounter any problems.  Since I hadn't
seen any discussion of this in a while, I thought the problem had been
resolved already ...

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Matthew D. Fuller]

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-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Don Lewis]

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 Desktop (82540EM). …
>> 
>> No panic here. 32-bit Windows 7 guest with the same virtual adapter.
>> 
>> $ date ; uname -v
>> Sat 20 Oct 2018 00:15:49 BST
>> FreeBSD 12.0-BETA1 r339438 GENERIC
>> $ pkg query '%o %v %R' virtualbox-ose virtualbox-ose-kmod
>> emulators/virtualbox-ose 5.2.20 poudriere
>> emulators/virtualbox-ose-kmod 5.2.20 poudriere
>> $
>> 
>> If you have not already done so, try building and installing from ports.
> 
> I'm using locally built packages and the poudriere jail is the exactly
> same source revision.

My camera isn't working at the moment, so here is a partial,
hand-transcribed DDB backtrace:

... looks like something nearby ng_ether_ifnet_arrival_cookie()
ng_ether_ifnet_arrival_cookie()
... looks like something nearby ng_ether_ifnet_arrival_cookie()
supdrvIOCtlInnerUnrestricted()
VBOXDrvFreeBSDIOCtl()
devfs_ioctl()

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Don Lewis]

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-bit Windows 7 guest with the same virtual adapter.
> 
> $ date ; uname -v
> Sat 20 Oct 2018 00:15:49 BST
> FreeBSD 12.0-BETA1 r339438 GENERIC
> $ pkg query '%o %v %R' virtualbox-ose virtualbox-ose-kmod
> emulators/virtualbox-ose 5.2.20 poudriere
> emulators/virtualbox-ose-kmod 5.2.20 poudriere
> $
> 
> If you have not already done so, try building and installing from ports.

I'm using locally built packages and the poudriere jail is the exactly
same source revision.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Graham Perrin]

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 adapter.

$ date ; uname -v
Sat 20 Oct 2018 00:15:49 BST
FreeBSD 12.0-BETA1 r339438 GENERIC
$ pkg query '%o %v %R' virtualbox-ose virtualbox-ose-kmod
emulators/virtualbox-ose 5.2.20 poudriere
emulators/virtualbox-ose-kmod 5.2.20 poudriere
$

If you have not already done so, try building and installing from ports.



Side note: if you can get beyond the panic, then you might encounter this bug:

232408 – emulators/virtualbox-ose VirtualBoxVM guest crash when attempting to 
download guest additions

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Virtualbox kernel module on 11-CURRENT

[Julian Elischer]

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 module
'vboxdrv', it says:
"KLD vboxdrv.ko: depends on kernel - not available or version mismatch.
linker_load_file: Unsupported file type"


The virtualbox module needs to be in full sync with the kernel. Most
probably the sources being used by the cluster for building packages on
head are a little different from yours, so the kernel module is not in
sync.

You will need to build the kernel module yourself to actually match your
kernel sources.

It's not really a problem or a bug, it's how it works. On head there is
no warranty about the KBI. This cannot happen on releases and stable
because the KBI is not going to change there.

--
Guido Falsi 


I don't think this is true. While shareable libraries have fixed ABIs, I
believe the KBI can change even in STABLE branches.  If a security fix
requires it, it might even change in a RELEASE. I my be wrong about this,
but I recall having to re-build the VB kmod port even withing a minor
version (i.e. STABLE).


We try hard NOT to change the KBI within a single stable branch.
we do things like add spare fields before we make a new stable branch 
to help with this.



In any case, I do strongly recommend the use of PORTS_MODULES in
/etc/src.conf to assure that the kernel modules always get re-built when
the kernel is re-built. so that the sources, the kernel, and the module are
in sync. The PORTS_MODULES are re-installed as a part of the "make
installkernel", so things are almost safe, but beware of "make
reinstallkernel" as it does not do the right thing. (See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201779)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Virtualbox kernel module on 11-CURRENT

[Guido Falsi]

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 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
> mismatch.
> > linker_load_file: Unsupported file type"
> >
> 
> The virtualbox module needs to be in full sync with the kernel. Most
> probably the sources being used by the cluster for building packages on
> head are a little different from yours, so the kernel module is not
> in sync.
> 
> You will need to build the kernel module yourself to actually match your
> kernel sources.
> 
> It's not really a problem or a bug, it's how it works. On head there is
> no warranty about the KBI. This cannot happen on releases and stable
> because the KBI is not going to change there.
> 
> --
> Guido Falsi >
> 
> 
> I don't think this is true. While shareable libraries have fixed ABIs, I
> believe the KBI can change even in STABLE branches.  If a security fix
> requires it, it might even change in a RELEASE. I my be wrong about
> this, but I recall having to re-build the VB kmod port even withing a
> minor version (i.e. STABLE).

I'm unable to find a final statement about KBI stability, but freezing
it is an essential step in the new major release schedule:

https://www.freebsd.org/releases/11.0R/schedule.html

(KBI freeze begins  24 June 2016)

If the promise has not been maintained in the past it's a sad event and
a mistake, but the promise is still valid in it's intent.

BTW at present the cluster building packages for 10.x is running on
10.1, so the kernel modules built by it are built on 10.1 and will work
on 10.3. This would be impossible without KBI being frozen.

Mistakes do happen unluckily.

> 
> In any case, I do strongly recommend the use of PORTS_MODULES in
> /etc/src.conf to assure that the kernel modules always get re-built when
> the kernel is re-built. so that the sources, the kernel, and the module
> are in sync. The PORTS_MODULES are re-installed as a part of the "make
> installkernel", so things are almost safe, but beware of "make
> reinstallkernel" as it does not do the right thing. (See
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201779)

Yes leveraging PORTS_MODULES is a good solution, although I don't like
mixing the system build process with the port one so I prefer manually
doing the modules part.

-- 
Guido Falsi 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Virtualbox kernel module on 11-CURRENT

[Kevin Oberman]

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:
> > "KLD vboxdrv.ko: depends on kernel - not available or version mismatch.
> > linker_load_file: Unsupported file type"
> >
>
> The virtualbox module needs to be in full sync with the kernel. Most
> probably the sources being used by the cluster for building packages on
> head are a little different from yours, so the kernel module is not in
> sync.
>
> You will need to build the kernel module yourself to actually match your
> kernel sources.
>
> It's not really a problem or a bug, it's how it works. On head there is
> no warranty about the KBI. This cannot happen on releases and stable
> because the KBI is not going to change there.
>
> --
> Guido Falsi 
>

I don't think this is true. While shareable libraries have fixed ABIs, I
believe the KBI can change even in STABLE branches.  If a security fix
requires it, it might even change in a RELEASE. I my be wrong about this,
but I recall having to re-build the VB kmod port even withing a minor
version (i.e. STABLE).

In any case, I do strongly recommend the use of PORTS_MODULES in
/etc/src.conf to assure that the kernel modules always get re-built when
the kernel is re-built. so that the sources, the kernel, and the module are
in sync. The PORTS_MODULES are re-installed as a part of the "make
installkernel", so things are almost safe, but beware of "make
reinstallkernel" as it does not do the right thing. (See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201779)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Virtualbox kernel module on 11-CURRENT

[Ngie Cooper]

> 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 vboxdrv.ko: depends on kernel - not available or version mismatch.
>> linker_load_file: Unsupported file type"
> 
> The virtualbox module needs to be in full sync with the kernel. Most
> probably the sources being used by the cluster for building packages on
> head are a little different from yours, so the kernel module is not in sync.
> 
> You will need to build the kernel module yourself to actually match your
> kernel sources.
> 
> It's not really a problem or a bug, it's how it works. On head there is
> no warranty about the KBI. This cannot happen on releases and stable
> because the KBI is not going to change there.

Look for "PORTS_MODULES" (case sensitive) in "man 5 src.conf". I think that was 
the variable name for building ports during buildkernel and installing via 
installkernel. It's been a while though and it's harder to search for it on my 
smartphone..

Cheers,
-Ngie

> -- 
> Guido Falsi 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Virtualbox kernel module on 11-CURRENT

[Guido Falsi]

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 mismatch.
> linker_load_file: Unsupported file type"
> 

The virtualbox module needs to be in full sync with the kernel. Most
probably the sources being used by the cluster for building packages on
head are a little different from yours, so the kernel module is not in sync.

You will need to build the kernel module yourself to actually match your
kernel sources.

It's not really a problem or a bug, it's how it works. On head there is
no warranty about the KBI. This cannot happen on releases and stable
because the KBI is not going to change there.

-- 
Guido Falsi 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Konstantin Belousov]

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: 
> >>  > > 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 problems as well.  I can't
> >>  > get my VMs on the network recently, but I don't recall when it
> >>  > last worked. Everything looks right from the guest (the arp cache
> >>  > shows the VirtualBox NAT router), but tcpdump on the host shows no
> >>  > traffic.  I haven't had time to investigate further :/
> >>  > 
> >> 
> >> The odds of it being fixed will increase greatly if someone would do a
> >> bisect and test.
> > 
> > I started bisecting a bit earlier today.  So far all I know is r300184
> > is also broken.
> 
> The culprit turned out to be r300043.  There seems to be some
> sort of ABI compatiblity issue that was resolved when I rebuilt and
> reinstalled virtualbox-ose-kmod.  There should probably be note in
> src/UPDATING if so.  The .kmod files that I had been
> running were probably built with r299139.
Not ABI, bit KBI.  The revision changed layout of the struct thread,
which occurs semi-regularly on HEAD, but we maintain the layout for
struct proc and struct thread for existing fields on stable.

I also changes the layouts of struct proc and thread today, please see
r301456.

I am not sure about __FreeBSD_version bump for that changes, since they
do not add or remove any consumable interfaces.  The sole purpose of the
bump would be to delineate the modules build time.

> 
> I used to have PORTS_MODULES=emulators/virtualbox-ose-kmod in
> /etc/make.conf, but took it out because pkg would also try to
> intall/upgrade it from my local pkg repo.
> 
> What is strange is that the kmods would successfully load even on very
> recent kernels, but when I did a "pkg install -f virtualbox-ose-kmod"
> to fetch a recently rebuilt version (just a few days old), it would not
> load with a r300043 kernel.  Is there a check to prevent a module with a
> newer version from loading on an older kernel, but not the reverse?
Yes, the __FreeBSD_version from the headers pack used for module build
is embedded into module metadata, and module loader checks it against
the version of the kernel.  It makes sense on stable, but not much on
HEAD, where only exact match would ever reasonable.

Even on stable, we only guarantee partial KBI stability, mostly
to interfaces relevant for device drivers, and not for e.g. ABI emulators.
For such modules which are too tied to the kernel, I added the
DECLARE_MODULE_TIED() declarator.  Might be vbox kmods need to start
using that (if not using _TIED already).
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Don Lewis]

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 
>>  > > 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 problems as well.  I can't
>>  > get my VMs on the network recently, but I don't recall when it
>>  > last worked. Everything looks right from the guest (the arp cache
>>  > shows the VirtualBox NAT router), but tcpdump on the host shows no
>>  > traffic.  I haven't had time to investigate further :/
>>  > 
>> 
>> The odds of it being fixed will increase greatly if someone would do a
>> bisect and test.
> 
> I started bisecting a bit earlier today.  So far all I know is r300184
> is also broken.

The culprit turned out to be r300043.  There seems to be some
sort of ABI compatiblity issue that was resolved when I rebuilt and
reinstalled virtualbox-ose-kmod.  There should probably be note in
src/UPDATING if so.  The .kmod files that I had been
running were probably built with r299139.

I used to have PORTS_MODULES=emulators/virtualbox-ose-kmod in
/etc/make.conf, but took it out because pkg would also try to
intall/upgrade it from my local pkg repo.

What is strange is that the kmods would successfully load even on very
recent kernels, but when I did a "pkg install -f virtualbox-ose-kmod"
to fetch a recently rebuilt version (just a few days old), it would not
load with a r300043 kernel.  Is there a check to prevent a module with a
newer version from loading on an older kernel, but not the reverse?

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Don Lewis]

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) and is definitely broken with r301229.
>> I've been having VirtualBox networking problems as well.  I can't get my
>> VMs on the network recently, but I don't recall when it last worked.
>> Everything looks right from the guest (the arp cache shows the
>> VirtualBox NAT router), but tcpdump on the host shows no traffic.  I
>> haven't had time to investigate further :/
> 
> I'm running rev 301210 guest and here looks working.

It doesn't appear to be a guest problem.  Both recent FreeBSD
11.0-CURRENT and Debian on broken if the host is FreeBSD 11.0 HEAD >=
r300184.  The same FreeBSD guest works if the host is FreeBSD
10.3-STABLE r301231.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Don Lewis]

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 last known to work
>  > > with r299139 (May 6th) and is definitely broken with r301229.
>  >  
>  > I've been having VirtualBox networking problems as well.  I can't
>  > get my VMs on the network recently, but I don't recall when it
>  > last worked. Everything looks right from the guest (the arp cache
>  > shows the VirtualBox NAT router), but tcpdump on the host shows no
>  > traffic.  I haven't had time to investigate further :/
>  > 
> 
> The odds of it being fixed will increase greatly if someone would do a
> bisect and test.

I started bisecting a bit earlier today.  So far all I know is r300184
is also broken.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Otacílio]

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've been having VirtualBox networking problems as well.  I can't get my
VMs on the network recently, but I don't recall when it last worked.
Everything looks right from the guest (the arp cache shows the
VirtualBox NAT router), but tcpdump on the host shows no traffic.  I
haven't had time to investigate further :/


I'm running rev 301210 guest and here looks working.

[ota@nostromo /usr/home/ota]$ uname -a
FreeBSD nostromo 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #0 r301210: Fri Jun  3 
01:24:19 BRT 2016 ota@nostromo:/usr/obj/usr/src/sys/NOSTROMO  amd64

[ota@nostromo /usr/home/ota]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=91.683 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=67.433 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=52.106 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=153.091 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 52.106/91.078/153.091/38.483 ms
[ota@nostromo /usr/home/ota]$ wget
bash: wget: comando não encontrado
[ota@nostromo /usr/home/ota]$ telnet www.google.com 80
Trying 216.58.218.4...
Connected to www.google.com.
Escape character is '^]'.
GET index.html
HTTP/1.0 404 Not Found
Content-Type: text/html; charset=UTF-8
Content-Length: 1561
Date: Sun, 05 Jun 2016 03:01:55 GMT



  
  

  Error 404 (Not Found)!!1
  

Re: VirtualBox network connectivity broken on recent -CURRENT

[Matthew Macy]

  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) and is definitely broken with r301229. 
 >  
 > I've been having VirtualBox networking problems as well.  I can't get my 
 > VMs on the network recently, but I don't recall when it last worked. 
 > Everything looks right from the guest (the arp cache shows the 
 > VirtualBox NAT router), but tcpdump on the host shows no traffic.  I 
 > haven't had time to investigate further :/ 
 > 

The odds of it being fixed will increase greatly if someone would do a bisect 
and test.
-M

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Randy Westlund]

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 problems as well.  I can't get my
VMs on the network recently, but I don't recall when it last worked.
Everything looks right from the guest (the arp cache shows the
VirtualBox NAT router), but tcpdump on the host shows no traffic.  I
haven't had time to investigate further :/


signature.asc
Description: PGP signature

Re: VirtualBox network connectivity broken on recent -CURRENT

[Don Lewis]

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 with r301229.  The VirtualBox
>>> port revisions are:
>>>   virtualbox-ose-4.3.38_1
>>>   virtualbox-ose-kmod-4.3.38
>>> It looks like there was one change to the VirtualBox on May 9th, but it
>>> looks unlikely to be the cause of the problem.
>>>
>>> The network settings are:
>>>   Attached to: Bridged Adapter
>>>   Name: re0
>>>   Adapter Type: Paravirtualized Network (virtio-net)
>>>   Promiscuous Mode: Deny
>>>   MAC Address: [snip]
>>> Ifconfig says that the interface is up, but I am unable to ping either
>>> the host or anything else on the LAN from the guest.  It looks like the
>>> problem is with outbound traffic.  If I attempt to ping the guest, the
>>> source IP address and MAC address show up in the guest's arp table, but
>>> ping reports:
>>>   ping: sendto: Host is down
>>> That makes me think that the arp responses from the guest are not
>>> getting transmitted.  None of the machines involved are running
>>> firewalls.  If I ping from the guest, I don't see any arp requests on
>>> the wire and the arp command shows the table entry as incomplete.
>>>
>>> The problem shows up with both FreeBSD -CURRENT and Debian guests.
>>
>> I see the same behaviour if I set:
>> Attached to: NAT
>> or
>> Adapter Type: 82540EM
>>
> 
> Might be related to this routing bug:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831

Doesn't look like it.  The questionable commit there seems to be
r293159.  I didn't see breakage until after r299139.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Alan Somers]

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 revisions are:
>>   virtualbox-ose-4.3.38_1
>>   virtualbox-ose-kmod-4.3.38
>> It looks like there was one change to the VirtualBox on May 9th, but it
>> looks unlikely to be the cause of the problem.
>>
>> The network settings are:
>>   Attached to: Bridged Adapter
>>   Name: re0
>>   Adapter Type: Paravirtualized Network (virtio-net)
>>   Promiscuous Mode: Deny
>>   MAC Address: [snip]
>> Ifconfig says that the interface is up, but I am unable to ping either
>> the host or anything else on the LAN from the guest.  It looks like the
>> problem is with outbound traffic.  If I attempt to ping the guest, the
>> source IP address and MAC address show up in the guest's arp table, but
>> ping reports:
>>   ping: sendto: Host is down
>> That makes me think that the arp responses from the guest are not
>> getting transmitted.  None of the machines involved are running
>> firewalls.  If I ping from the guest, I don't see any arp requests on
>> the wire and the arp command shows the table entry as incomplete.
>>
>> The problem shows up with both FreeBSD -CURRENT and Debian guests.
>
> I see the same behaviour if I set:
> Attached to: NAT
> or
> Adapter Type: 82540EM
>

Might be related to this routing bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: VirtualBox network connectivity broken on recent -CURRENT

[Don Lewis]

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
>   virtualbox-ose-kmod-4.3.38
> It looks like there was one change to the VirtualBox on May 9th, but it
> looks unlikely to be the cause of the problem.
> 
> The network settings are:
>   Attached to: Bridged Adapter
>   Name: re0
>   Adapter Type: Paravirtualized Network (virtio-net)
>   Promiscuous Mode: Deny
>   MAC Address: [snip]
> Ifconfig says that the interface is up, but I am unable to ping either
> the host or anything else on the LAN from the guest.  It looks like the
> problem is with outbound traffic.  If I attempt to ping the guest, the
> source IP address and MAC address show up in the guest's arp table, but
> ping reports:
>   ping: sendto: Host is down
> That makes me think that the arp responses from the guest are not
> getting transmitted.  None of the machines involved are running
> firewalls.  If I ping from the guest, I don't see any arp requests on
> the wire and the arp command shows the table entry as incomplete.
> 
> The problem shows up with both FreeBSD -CURRENT and Debian guests.

I see the same behaviour if I set:
Attached to: NAT
or
Adapter Type: 82540EM

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Virtualbox 4.3.20 crashes FreeBSD 11.0-CURRENT

[Ranjan1018 .]

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 GMT+01:00 Hans Petter Selasky h...@selasky.org:

 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 photo of the screen:
 https://plus.google.com/112995826906094353410/posts/6amoaitgP8e
 https://plus.google.com/112995826906094353410/posts/6amoaitgP8e*

 *Maurizio*


 Hi,

 Can you try to apply the patch in the following PR:

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196

 Not sure if it helps.

 --HPS


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox 4.3.20 crashes FreeBSD 11.0-CURRENT

[Hans Petter Selasky]

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 photo of the screen:
https://plus.google.com/112995826906094353410/posts/6amoaitgP8e
https://plus.google.com/112995826906094353410/posts/6amoaitgP8e*

*Maurizio*


Hi,

Can you try to apply the patch in the following PR:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196

Not sure if it helps.

--HPS

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Eric Camachat]

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. miguelmcl...@gmail.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1


 Perhaps this is best placed in current list!

 -  Original Message 
 Subject: Virtualbox Settings don't show any window (FreeBSD-10 current)
 Date: Sun, 15 Sep 2013 18:35:02 +
 From: Mike C. miguelmcl...@gmail.com
 To: freebsd-emulat...@freebsd.org


 I've successfully installed virtualbox in my Latptop running Freebsd-10
 current...

 Everything seems fine except for when I click the Settings button it
 doesn't show any window and the current windows stays locked (I can't
 click anything)...

 Running VirtualBox from the command-line I don't see any error...

 Has anyone tried VirtualBox in FreeBSD-10?

 Thanks!


 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.21 (FreeBSD)
 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

 iQIcBAEBAgAGBQJSNxItAAoJEGKyFhaKt9g3utAP/34rlyrLGntXCIDa9LHv3Qly
 nmRRcIWgkT//MEDFG2OZMdWo+50DQ12k9L0qAAoUkezhDqfZXTo+U5DOn2mr0MEf
 2KOXT5yMkqNBtab54a/nCDxp0bCAiaMSJjsKqXjF6mq6fqoj6aVEFJY6rgzG+Qb1
 cAjHlBfbOBcOFtWd4xt0+w1m5VodnJ8dsd5CTVfkazTRRfk32qlLMraRUmQT1x+C
 STi2Dt4xDJzbx6MThDcwjOfudPQeQiQ1SnFn65aNRCxSj//pNcZW0DeU3efKq730
 1RA2yPjpoqzrPklkkW4wF0Kv/50rGGytS1WYcA01uwBq8noBdVmW9J7GfeqmVuF8
 vATRX8eDYNVtkJLZmBqgUgXPT0BocHpoW7qPpTmRHG2OJ8TQTIytGT+nx08rG/T3
 EEWssgY/kOKDfYgB9DYcgLyGIPcLt0JuwCWL/sm5wzX1bogNyVhrn5hmJTTiFAng
 O4cbyXDPaEHdZhQ9SibqiJ2H1FfUa4keD0d2JW2ZhR5cSFD3oW1s8WprNf/ujBWn
 Bc7Z78qy4z0feqrYUabFKMxhmJJtwVfW7Y7Kmuzuvk08CHYjsAikQjumkKNm4Onz
 iYFFDfYXbEF73KJslr7tY+kWIY1iRuFc4xnjjaucEIbG/Bp7SvgMhTsNgQ7d//z5
 ZVwvJTV0HsyqF+VPz1Ei
 =kQa4
 -END PGP SIGNATURE-
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox addition in FreeBSD -current guest OS?

[Bernhard Fröhlich]

This should be fixed together with the update to 4.2.12 now.

On Fri, Apr 26, 2013 at 7:43 PM, Mark Johnston mark...@gmail.com 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 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 (and same for the UNLOCKS) and added rwlock.h to the
includes. That enabled it to compile but I'm having problems getting X
started (it just hangs) using those vbox modules for xorg. Log msg (see
attached) says failed to initialize VirtualBox device (rc=-102)
   
Anyone having recently compiled the vbox ose-additions on a -current 
system
and had it work? I'm just trying to figure out if this is a
-current-related issue or a vbox related one.
   
  
   This was fixed months ago, I think.  Is your ports tree updated?
 
  As far as the compilation issue goes, the virtualbox-ose-kmod port is
  indeed fixed but virtualbox-ose-additions is still broken on current
  with the latest ports tree.

 *sigh*...  Is this broken again or broken still ?

 Looks like the latter based on the port's revision history. It was just
 never fixed when the lock changed to a rwlock.
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org



-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox addition in FreeBSD -current guest OS?

[Glen Barber]

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?

[Glen Barber]

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. That enabled it to compile but I'm having problems getting X
 started (it just hangs) using those vbox modules for xorg. Log msg (see
 attached) says failed to initialize VirtualBox device (rc=-102)
 
 Anyone having recently compiled the vbox ose-additions on a -current system
 and had it work? I'm just trying to figure out if this is a
 -current-related issue or a vbox related one.
 

This was fixed months ago, I think.  Is your ports tree updated?

Glen

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox addition in FreeBSD -current guest OS?

[Mark Johnston]

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 (and same for the UNLOCKS) and added rwlock.h to the
  includes. That enabled it to compile but I'm having problems getting X
  started (it just hangs) using those vbox modules for xorg. Log msg (see
  attached) says failed to initialize VirtualBox device (rc=-102)
  
  Anyone having recently compiled the vbox ose-additions on a -current system
  and had it work? I'm just trying to figure out if this is a
  -current-related issue or a vbox related one.
  
 
 This was fixed months ago, I think.  Is your ports tree updated?

As far as the compilation issue goes, the virtualbox-ose-kmod port is
indeed fixed but virtualbox-ose-additions is still broken on current
with the latest ports tree.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox addition in FreeBSD -current guest OS?

[Glen Barber]

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 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. That enabled it to compile but I'm having problems getting X
   started (it just hangs) using those vbox modules for xorg. Log msg (see
   attached) says failed to initialize VirtualBox device (rc=-102)
   
   Anyone having recently compiled the vbox ose-additions on a -current 
   system
   and had it work? I'm just trying to figure out if this is a
   -current-related issue or a vbox related one.
   
  
  This was fixed months ago, I think.  Is your ports tree updated?
 
 As far as the compilation issue goes, the virtualbox-ose-kmod port is
 indeed fixed but virtualbox-ose-additions is still broken on current
 with the latest ports tree.

*sigh*...  Is this broken again or broken still ?

Glen



pgpM70iOwAuRF.pgp
Description: PGP signature

Re: Virtualbox addition in FreeBSD -current guest OS?

[Mark Johnston]

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 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. That enabled it to compile but I'm having problems getting X
started (it just hangs) using those vbox modules for xorg. Log msg (see
attached) says failed to initialize VirtualBox device (rc=-102)

Anyone having recently compiled the vbox ose-additions on a -current 
system
and had it work? I'm just trying to figure out if this is a
-current-related issue or a vbox related one.

   
   This was fixed months ago, I think.  Is your ports tree updated?
  
  As far as the compilation issue goes, the virtualbox-ose-kmod port is
  indeed fixed but virtualbox-ose-additions is still broken on current
  with the latest ports tree.
 
 *sigh*...  Is this broken again or broken still ?

Looks like the latter based on the port's revision history. It was just
never fixed when the lock changed to a rwlock.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: VirtualBox driver patch for -current post SVN r248084

[Michael Butler]

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/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c   Sat Mar
 9 21:21:20 2013
***
*** 162,168 
  case RTR0MEMOBJTYPE_PHYS:
  case RTR0MEMOBJTYPE_PHYS_NC:
  {
! VM_OBJECT_LOCK(pMemFreeBSD-pObject);
  vm_page_t pPage = vm_page_find_least(pMemFreeBSD-pObject, 0);
  #if __FreeBSD_version  90
  /* See
http://lists.freebsd.org/pipermail/freebsd-current/2012-November/037963.html
*/
--- 162,168 
  case RTR0MEMOBJTYPE_PHYS:
  case RTR0MEMOBJTYPE_PHYS_NC:
  {
! VM_OBJECT_WLOCK(pMemFreeBSD-pObject);
  vm_page_t pPage = vm_page_find_least(pMemFreeBSD-pObject, 0);
  #if __FreeBSD_version  90
  /* See
http://lists.freebsd.org/pipermail/freebsd-current/2012-November/037963.html
*/
***
*** 177,183 
  #if __FreeBSD_version  90
  vm_page_unlock_queues();
  #endif
! VM_OBJECT_UNLOCK(pMemFreeBSD-pObject);
  vm_object_deallocate(pMemFreeBSD-pObject);
  break;
  }
--- 177,183 
  #if __FreeBSD_version  90
  vm_page_unlock_queues();
  #endif
! VM_OBJECT_WUNLOCK(pMemFreeBSD-pObject);
  vm_object_deallocate(pMemFreeBSD-pObject);
  break;
  }
***
*** 205,214 

  while (cTries = 1)
  {
! VM_OBJECT_LOCK(pObject);
  pPages = vm_page_alloc_contig(pObject, iPIndex, fFlags, cPages, 0,
VmPhysAddrHigh, uAlignment, 0,
VM_MEMATTR_DEFAULT);
! VM_OBJECT_UNLOCK(pObject);
  if (pPages)
  break;
  vm_pageout_grow_cache(cTries, 0, VmPhysAddrHigh);
--- 205,214 

  while (cTries = 1)
  {
! VM_OBJECT_WLOCK(pObject);
  pPages = vm_page_alloc_contig(pObject, iPIndex, fFlags, cPages, 0,
VmPhysAddrHigh, uAlignment, 0,
VM_MEMATTR_DEFAULT);
! VM_OBJECT_WUNLOCK(pObject);
  if (pPages)
  break;
  vm_pageout_grow_cache(cTries, 0, VmPhysAddrHigh);
***
*** 228,234 

  if (!pPages)
  return pPages;
! VM_OBJECT_LOCK(pObject);
  for (vm_pindex_t iPage = 0; iPage  cPages; iPage++)
  {
  vm_page_t pPage = pPages + iPage;
--- 228,234 

  if (!pPages)
  return pPages;
! VM_OBJECT_WLOCK(pObject);
  for (vm_pindex_t iPage = 0; iPage  cPages; iPage++)
  {
  vm_page_t pPage = pPages + iPage;
***
*** 240,246 
  atomic_add_int(cnt.v_wire_count, 1);
  }
  }
! VM_OBJECT_UNLOCK(pObject);
  return pPages;
  #endif
  }
--- 240,246 
  atomic_add_int(cnt.v_wire_count, 1);
  }
  }
! VM_OBJECT_WUNLOCK(pObject);
  return pPages;
  #endif
  }
***
*** 264,270 
  if (!pPage)
  {
  /* Free all allocated pages */
! VM_OBJECT_LOCK(pObject);
  while (iPage--  0)
  {
  pPage = vm_page_lookup(pObject, iPage);
--- 264,270 
  if (!pPage)
  {
  /* Free all allocated pages */
! VM_OBJECT_WLOCK(pObject);
  while (iPage--  0)
  {
  pPage = vm_page_lookup(pObject, iPage);
***
*** 278,284 
  vm_page_unlock_queues();
  #endif
  }
! VM_OBJECT_UNLOCK(pObject);
  return rcNoMem;
  }
  }
--- 278,284 
  vm_page_unlock_queues();
  #endif
  }
! VM_OBJECT_WUNLOCK(pObject);
  return rcNoMem;
  }
  }
***
*** 411,419 
  if (fContiguous)
  {
  Assert(enmType == RTR0MEMOBJTYPE_PHYS);
! VM_OBJECT_LOCK(pMemFreeBSD-pObject);
  pMemFreeBSD-Core.u.Phys.PhysBase =
VM_PAGE_TO_PHYS(vm_page_find_least(pMemFreeBSD-pObject, 0));
! VM_OBJECT_UNLOCK(pMemFreeBSD-pObject);
  pMemFreeBSD-Core.u.Phys.fAllocated = true;
  }

--- 411,419 
  if (fContiguous)
  {
  Assert(enmType == RTR0MEMOBJTYPE_PHYS);
! VM_OBJECT_WLOCK(pMemFreeBSD-pObject);
  pMemFreeBSD-Core.u.Phys.PhysBase =
VM_PAGE_TO_PHYS(vm_page_find_least(pMemFreeBSD-pObject, 0));
! VM_OBJECT_WUNLOCK(pMemFreeBSD-pObject);
  pMemFreeBSD-Core.u.Phys.fAllocated = true;
  }

***
*** 823,831 
  case RTR0MEMOBJTYPE_PHYS_NC:
  {
  RTHCPHYS addr;
! 

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

[Doug Barton]

On 08/04/2012 17:56, Kevin Oberman wrote:
 On Sat, Aug 4, 2012 at 2:30 PM, Doug Barton do...@freebsd.org wrote:
 On 08/04/2012 14:26, Garrett Cooper wrote:
 On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton do...@freebsd.org 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:

 PORTS_MODULES=  emulators/virtualbox-ose-kmod

 You can place other modules in that list as well. I use vbox so you can
 be pretty confident that this is going to keep working. :)

 That doesn't work

 I assure you that it does. I have put a non-zero amount of work into
 fixing it, I use this method, and the resulting kernel module works just
 fine.

 If you actually try it and find something is not as it should be, then
 yes; please do file a PR and feel free to cc me.

 Doug
 
 I am only aware of this because of your posts. No reference to it at
 all in src.conf(5). It would be nice to see it there.

It's in make.conf(5) for historical reasons, along with a lot of other
options that should be moved.

 It is mentioned in build(7), but only as a MAKE option and a lot of
 people are not going to realize it can be placed in src.conf.

It can also go in make.conf, so that's not a total loss I suppose.

 Also,
 for those not fairly conversant in make, it is not clear whether
 multiple ports should be space, comma, colon, or otherwise delimited
 
 This is a very nice option as it is very easy to overlook rebuilding
 kernel modules in ports when building the kernel. Thanks or working on
 it.

My pleasure ... it was one of those things on the list and I finally
got around to it.

Doug

-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[O. Hartmann]

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 other modules in that list as well. I use vbox so you can
 be pretty confident that this is going to keep working. :)
 
 Doug
 

Hello Doug.

This is exactly how I build the kernel modules for nvidia and VBox ;-)
So I guess this makes it unlikely - in my case - that the problems occur
due to unsynchronized kernel/modules.

Oliver



signature.asc
Description: OpenPGP digital signature

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

[O. Hartmann]

Am 08/04/12 00:36, schrieb Kevin Oberman:
 On Fri, Aug 3, 2012 at 6:41 AM, Luigi Rizzo ri...@iet.unipi.it 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 kob6...@gmail.com 
 wrote:

 On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O.
 ohart...@zedat.fu-berlin.de 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 a minute or so, I can work, then, the
 freeze occurs again.

 I can't see this behaviour with a Ubuntu Guest on the same box. Is
 there Windows 7 specifica to be aware of?

 I am seeing the same thing. Also Win7 guest with Windows showing idle
 process at 99%, but my system is showing VB at 100%. The VM is only
 running a single CPU, so FreeBSD is still running OK, but the Win7
 system seems to freeze up periodically.

 9.1-PRERELEASE on amd64 updated yesterday (though it has been this way
 since VB was updated to 4.1.18. Guest additions for 4.1.18
 installed.All ports current. I'm thinking of backing off to 4.1.16.

 Can someone confirm that this is a regression in 4.1.18? Then I could talk 
 to upstream and see if I can get that adressed.

 Could it be a case of kernel and virtualbox modules out of sync ?
 I do see occasional crashes with virtualbox in both the host and guest,
 but a reinstall of in-sync kernel and modules usually fixes them.
 
 Nope. To be really, really sure I just re-built the module and
 rebooted. VB still eats 100% CPU (out of 400%) continually.
 
 Thanks for the suggestion, though.
 

No, also in my case. I build world and the VBox software with each
kernel - usually.

Regards,
Oliver



signature.asc
Description: OpenPGP digital signature

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

[Doug Barton]

-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 modules in that list as well. I use vbox so you can
be pretty confident that this is going to keep working. :)

Doug

- -- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBCAAGBQJQHYWJAAoJEFzGhvEaGryEyLUIALgi1n65I8oBaFYJEcIkDB6P
W3f5PMZa72DN4r2lI3A3XXdPUJsNRmNy/X0HYyrrIwvfD3Z3m8bReYCd7DHAKOX4
pBsLA/73cwns9c3+zsUe4i9TZOsJM8fNVsRp/BSvdtBgv61ZZUurvt43H+Ek0E0B
h5ttGaIanxLqrkwP2FC/q30t0pmauJYu3jDTGiugOh98o/3oNT+25etyJBNgvg4c
VxBs/5aCSc5VHAcLXRN6Y0BGGbeimpPqEFlq3FEFGLkC7LGjqoSBUaJVz1cgDP+t
RIK9g0V+XIfyirgZ2VMeK3tfQ0Q17zfyl0+Iyzl2IxZptU67OBV/9LMqyhRaBOc=
=KbES
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Garrett Cooper]

On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton do...@freebsd.org 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:

 PORTS_MODULES=  emulators/virtualbox-ose-kmod

 You can place other modules in that list as well. I use vbox so you can
 be pretty confident that this is going to keep working. :)

That doesn't work because what variables are defined in the kernel
compile that get passed through to the port's autoconf. I've seen it
for a while but I need to figure out what to pass through exactly to
make things work. That or I'll just file a PR and get back to it
later.
Thanks,
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Doug Barton]

On 08/04/2012 14:26, Garrett Cooper wrote:
 On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton do...@freebsd.org 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:

 PORTS_MODULES=  emulators/virtualbox-ose-kmod

 You can place other modules in that list as well. I use vbox so you can
 be pretty confident that this is going to keep working. :)
 
 That doesn't work

I assure you that it does. I have put a non-zero amount of work into
fixing it, I use this method, and the resulting kernel module works just
fine.

If you actually try it and find something is not as it should be, then
yes; please do file a PR and feel free to cc me.

Doug

-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Kevin Oberman]

On Sat, Aug 4, 2012 at 2:30 PM, Doug Barton do...@freebsd.org wrote:
 On 08/04/2012 14:26, Garrett Cooper wrote:
 On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton do...@freebsd.org 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:

 PORTS_MODULES=  emulators/virtualbox-ose-kmod

 You can place other modules in that list as well. I use vbox so you can
 be pretty confident that this is going to keep working. :)

 That doesn't work

 I assure you that it does. I have put a non-zero amount of work into
 fixing it, I use this method, and the resulting kernel module works just
 fine.

 If you actually try it and find something is not as it should be, then
 yes; please do file a PR and feel free to cc me.

 Doug

I am only aware of this because of your posts. No reference to it at
all in src.conf(5). It would be nice to see it there.

It is mentioned in build(7), but only as a MAKE option and a lot of
people are not going to realize it can be placed in src.conf. Also,
for those not fairly conversant in make, it is not clear whether
multiple ports should be space, comma, colon, or otherwise delimited

This is a very nice option as it is very easy to overlook rebuilding
kernel modules in ports when building the kernel. Thanks or working on
it.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Bernhard Fröhlich]

On Fr.,   3. Aug. 2012 06:18:33 CEST, Kevin Oberman kob6...@gmail.com wrote:

 On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O.
 ohart...@zedat.fu-berlin.de 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 a minute or so, I can work, then, the
  freeze occurs again.
  
  I can't see this behaviour with a Ubuntu Guest on the same box. Is
  there Windows 7 specifica to be aware of?
 
 I am seeing the same thing. Also Win7 guest with Windows showing idle
 process at 99%, but my system is showing VB at 100%. The VM is only
 running a single CPU, so FreeBSD is still running OK, but the Win7
 system seems to freeze up periodically.
 
 9.1-PRERELEASE on amd64 updated yesterday (though it has been this way
 since VB was updated to 4.1.18. Guest additions for 4.1.18
 installed.All ports current. I'm thinking of backing off to 4.1.16.

Can someone confirm that this is a regression in 4.1.18? Then I could talk to 
upstream and see if I can get that adressed.

-- 
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Luigi Rizzo]

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 kob6...@gmail.com 
 wrote:
 
  On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O.
  ohart...@zedat.fu-berlin.de 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 a minute or so, I can work, then, the
   freeze occurs again.
   
   I can't see this behaviour with a Ubuntu Guest on the same box. Is
   there Windows 7 specifica to be aware of?
  
  I am seeing the same thing. Also Win7 guest with Windows showing idle
  process at 99%, but my system is showing VB at 100%. The VM is only
  running a single CPU, so FreeBSD is still running OK, but the Win7
  system seems to freeze up periodically.
  
  9.1-PRERELEASE on amd64 updated yesterday (though it has been this way
  since VB was updated to 4.1.18. Guest additions for 4.1.18
  installed.All ports current. I'm thinking of backing off to 4.1.16.
 
 Can someone confirm that this is a regression in 4.1.18? Then I could talk to 
 upstream and see if I can get that adressed.

Could it be a case of kernel and virtualbox modules out of sync ?
I do see occasional crashes with virtualbox in both the host and guest,
but a reinstall of in-sync kernel and modules usually fixes them.

cheers
luigi
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Kevin Oberman]

On Fri, Aug 3, 2012 at 6:41 AM, Luigi Rizzo ri...@iet.unipi.it 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 kob6...@gmail.com 
 wrote:

  On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O.
  ohart...@zedat.fu-berlin.de 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 a minute or so, I can work, then, the
   freeze occurs again.
  
   I can't see this behaviour with a Ubuntu Guest on the same box. Is
   there Windows 7 specifica to be aware of?
 
  I am seeing the same thing. Also Win7 guest with Windows showing idle
  process at 99%, but my system is showing VB at 100%. The VM is only
  running a single CPU, so FreeBSD is still running OK, but the Win7
  system seems to freeze up periodically.
 
  9.1-PRERELEASE on amd64 updated yesterday (though it has been this way
  since VB was updated to 4.1.18. Guest additions for 4.1.18
  installed.All ports current. I'm thinking of backing off to 4.1.16.

 Can someone confirm that this is a regression in 4.1.18? Then I could talk 
 to upstream and see if I can get that adressed.

 Could it be a case of kernel and virtualbox modules out of sync ?
 I do see occasional crashes with virtualbox in both the host and guest,
 but a reinstall of in-sync kernel and modules usually fixes them.

Nope. To be really, really sure I just re-built the module and
rebooted. VB still eats 100% CPU (out of 400%) continually.

Thanks for the suggestion, though.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Kevin Oberman]

On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O.
ohart...@zedat.fu-berlin.de 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 a minute or so, I can work, then, the freeze
 occurs again.

 I can't see this behaviour with a Ubuntu Guest on the same box. Is there
 Windows 7 specifica to be aware of?

I am seeing the same thing. Also Win7 guest with Windows showing idle
process at 99%, but my system is showing VB at 100%. The VM is only
running a single CPU, so FreeBSD is still running OK, but the Win7
system seems to freeze up periodically.

9.1-PRERELEASE on amd64 updated yesterday (though it has been this way
since VB was updated to 4.1.18. Guest additions for 4.1.18
installed.All ports current. I'm thinking of backing off to 4.1.16.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Garrett Cooper]

On Thu, Aug 2, 2012 at 9:18 PM, Kevin Oberman kob6...@gmail.com wrote:
 On Thu, Aug 2, 2012 at 12:54 AM, Hartmann, O.
 ohart...@zedat.fu-berlin.de 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 a minute or so, I can work, then, the freeze
 occurs again.

 I can't see this behaviour with a Ubuntu Guest on the same box. Is there
 Windows 7 specifica to be aware of?

 I am seeing the same thing. Also Win7 guest with Windows showing idle
 process at 99%, but my system is showing VB at 100%. The VM is only
 running a single CPU, so FreeBSD is still running OK, but the Win7
 system seems to freeze up periodically.

 9.1-PRERELEASE on amd64 updated yesterday (though it has been this way
 since VB was updated to 4.1.18. Guest additions for 4.1.18
 installed.All ports current. I'm thinking of backing off to 4.1.16.

I've been seeing consistent hangs with VBox 4.1.18, but mostly
with shared folders and the like under Windows 7 with certain paths
using Cygwin (probably an application issue, but I haven't dug into
why things are that way). I'm not sure what the exact revision is for
9.1-BETA1, but there are a handful of threading and amd64-specific
signal, etc related changes that may or may not affect things.
Thanks!
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox r0 memory management update

[Andriy Gapon]

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.orig2 2011-12-07
18:15:48.695189924 +0200
+++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c   2011-12-07
18:17:35.359192030 +0200
@@ -251,7 +251,7 @@ static int FreeBSDPhysAllocHelper(vm_obj
 vm_page_free(pPage);
 vm_page_unlock_queues();
 }
-VM_OBJECT_LOCK(pObject);
+VM_OBJECT_UNLOCK(pObject);
 return VERR_NO_MEMORY;
 }
 }

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Bernhard Froehlich]

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 appreciate reviews and testing of this code.  Especially 
testing with

earlier FreeBSD releases.


VirtualBox 4.1.6 on FreeBSD 9.0-RC2/amd64 gave me:

cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX 
-DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS 
-DRT_ARCH_AMD64 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE 
-nostdinc  -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq 
-finline-limit=8000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-common  -fno-omit-frame-pointer  
-mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float  
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector 
-std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option -c 
/usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c
/usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: 
In function 'FreeBSDContigPhysAllocHelper':
/usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:212: 
error: incompatible types in initialization

*** Error code 1

Stop in 
/usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv.

*** Error code 1

--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

[Andriy Gapon]

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 testing this on FreeBSD head (r228017), so far no
 breakage observed.

 I would appreciate reviews and testing of this code.  Especially testing with
 earlier FreeBSD releases.
 
 VirtualBox 4.1.6 on FreeBSD 9.0-RC2/amd64 gave me:
 
 cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX
 -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS
 -DRT_ARCH_AMD64 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc 
 -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param
 inline-unit-growth=100 --param large-function-growth=1000 -fno-common 
 -fno-omit-frame-pointer  -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx
 -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs
 -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
 -Wcast-qual 
 -Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option -c
 /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c
 
 /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:
 In function 'FreeBSDContigPhysAllocHelper':
 /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:212:
 error: incompatible types in initialization
 *** Error code 1
 
 Stop in
 /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv.
 
 *** Error code 1
 

Could you please change that line as follows?
vm_page_t pPage = pPages +iPage;

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: VirtualBox causes kernel panic

[Bernhard Froehlich]

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 start a virtual machine with boot
 from CD/DVD burner/reader device.
 
 With or without passthrough.
 
 Kernel panic  http://pastie.org/private/0nxanttdmtc9zvtllg0rw
 
 atapicam is loaded and hald is working.

I've added the bugreport and stacktrace to our list of known problems
and will inform you once there is something new about it.

http://wiki.freebsd.org/VirtualBox/ToDo

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: VirtualBox causes kernel panic

[Bernhard Froehlich]

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/usr/src/sys/GALILEO  amd64

 The kernel panic is occurred when I start a virtual machine with boot
 from CD/DVD burner/reader device.

 With or without passthrough.

 Kernel panic  http://pastie.org/private/0nxanttdmtc9zvtllg0rw

 atapicam is loaded and hald is working.
 
 I've added the bugreport and stacktrace to our list of known problems
 and will inform you once there is something new about it.
 
 http://wiki.freebsd.org/VirtualBox/ToDo

I've just seen that the stacktrace does not belong to the panic. So
could you please generate a stacktrace for that panic?

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Jung-uk Kim]

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 jkim at
   freebsd.org
  
   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 !!!
  
   Please try this patch:
  
   http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server
  -fr eebsd-HostHardwareFreeBSD.cpp
  
   Just drop this in ports/emulators/virtualbox-ose/files and
   rebuild.
 
  Thanks a lot, they look good. Do you agree that those two
  patches are licensed under MIT License so that i can push them
  upstream?
 
  Yes, of course.  Please feel free.

 Hi guys,

 I am still having this issue building virtualbox on
 freebsd-current.

 I initially had some errors with some lib32 files (crt*) but
 thought I had over-come these issues.
 The HostHardwareFreeBSD.cpp patch described above appears to have
 been applied already, so I am at a loss as to what do next.

 It's a fairly vanilla build, the main difference is that I used the
 text installer to get a GUI-less build (for my headless machine).
 For this reason, I have also excluded qt in the virtualbox-ose
 config.

 As this is my first post on here, please allow me to overshare my
 setup, as well as the actual error below:

 Cheers


 # uname -a
 FreeBSD jupiter 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Thu May 12
 15:34:46 UTC 2011
 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

[SNIP]

Your world/kernel is too old.  Rebuild and install world/kernel or 
install 9.0-BETA1 when it is ready.

Jung-uk Kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Sergey V. Dyatko]

On Sat, 25 Jun 2011 16:28:41 +0200
Bernhard Froehlich de...@freebsd.org 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 j...@freebsd.org
  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 !!!
  
  Please try this patch:
  
  http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp
  
  Just drop this in ports/emulators/virtualbox-ose/files and rebuild.
 
 Thanks a lot, they look good. Do you agree that those two patches are
 licensed under MIT License so that i can push them upstream?
 
Hi, 

Works good for me (head, amd64).
Pushing patches into upstream is a good idea. What prevents
to put them in ports tree now?


-- 
wbr, tiger

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Bernhard Froehlich]

On Mon, 27 Jun 2011 10:54:08 +0300, Sergey V. Dyatko wrote:
 On Sat, 25 Jun 2011 16:28:41 +0200
 Bernhard Froehlich de...@freebsd.org 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 j...@freebsd.org
  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 !!!
 
  Please try this patch:
 
  http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp
 
  Just drop this in ports/emulators/virtualbox-ose/files and rebuild.

 Thanks a lot, they look good. Do you agree that those two patches are
 licensed under MIT License so that i can push them upstream?

 Hi, 
 
 Works good for me (head, amd64).
 Pushing patches into upstream is a good idea. What prevents
 to put them in ports tree now?

I just waited for some feedback as I could not test it myself right
now.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Matt]

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 Froehlichde...@freebsd.org  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 Kimj...@freebsd.org

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 !!!

Please try this patch:

http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp

Just drop this in ports/emulators/virtualbox-ose/files and rebuild.

Thanks a lot, they look good. Do you agree that those two patches are
licensed under MIT License so that i can push them upstream?


Hi,

Works good for me (head, amd64).
Pushing patches into upstream is a good idea. What prevents
to put them in ports tree now?

I just waited for some feedback as I could not test it myself right
now.



Worked on my machines running a VM with two procs, also was able to 
complete two different OS installs. No issues for what it's worth.


Thanks again,
Matt

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Jung-uk Kim]

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 j...@freebsd.org
 
  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 !!!
 
  Please try this patch:
 
  http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-fr
 eebsd-HostHardwareFreeBSD.cpp
 
  Just drop this in ports/emulators/virtualbox-ose/files and
  rebuild.

 Thanks a lot, they look good. Do you agree that those two patches
 are licensed under MIT License so that i can push them upstream?

Yes, of course.  Please feel free.

Jung-uk Kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Bernhard Froehlich]

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 j...@freebsd.org
 
  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 !!!
 
  Please try this patch:
 
  http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-fr
 eebsd-HostHardwareFreeBSD.cpp
 
  Just drop this in ports/emulators/virtualbox-ose/files and
  rebuild.

 Thanks a lot, they look good. Do you agree that those two patches
 are licensed under MIT License so that i can push them upstream?
 
 Yes, of course.  Please feel free.

Shouldn't the changes only be done for __FreeBSD_version = 900038 ?
It's also not fully correct because the version wasn't bumped for the
CAM changes but it's the best we can get.

The same is true for the cpuset_t change but the version wasn't bumped
either.

http://svnweb.freebsd.org/base?view=revisionrevision=223081
http://svnweb.freebsd.org/base?view=revisionrevision=222813

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Jung-uk Kim]

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 wrote:
   On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim
   j...@freebsd.org
  
   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 !!!
  
   Please try this patch:
  
   http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server
  -fr eebsd-HostHardwareFreeBSD.cpp
  
   Just drop this in ports/emulators/virtualbox-ose/files and
   rebuild.
 
  Thanks a lot, they look good. Do you agree that those two
  patches are licensed under MIT License so that i can push them
  upstream?
 
  Yes, of course.  Please feel free.

 Shouldn't the changes only be done for __FreeBSD_version = 900038
 ? It's also not fully correct because the version wasn't bumped for
 the CAM changes but it's the best we can get.

 The same is true for the cpuset_t change but the version wasn't
 bumped either.

 http://svnweb.freebsd.org/base?view=revisionrevision=223081
 http://svnweb.freebsd.org/base?view=revisionrevision=222813

To be absolutely correct, yes, we need to bump __FreeBSD_version 
first.  However, it is very close to feature freeze and I don't think 
anybody wants to do that ATM.  For -CURRENT, I don't think it really 
matters as I said earlier:

http://docs.freebsd.org/cgi/mid.cgi?201106241352.14262.jkim

Now, are you going to fix __FreeBSD_version = 70 in these 
files, too? ;-)

Jung-uk Kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Bernhard Froehlich]

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 j...@freebsd.org
 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 !!!
 
 Please try this patch:
 
 http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp
 
 Just drop this in ports/emulators/virtualbox-ose/files and rebuild.

Thanks a lot, they look good. Do you agree that those two patches are
licensed under MIT License so that i can push them upstream?

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Matt]

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\
-DRTPATH_APP_PRIVATE_ARCH=\/usr/local/lib/virtualbox\
-DRTPATH_SHARED_LIBS=\/usr/local/lib/virtualbox\
-DRTPATH_APP_DOCS=\/usr/local/share/doc/virtualbox-ose\
-DRT_LOCK_STRICT -DRT_LOCK_STRICT_ORDER -DDEBUG -DDEBUG_gkontos
-DDEBUG_USERNAME=gkontos -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64
-D__AMD64__ -DIN_RING3 -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM
-DVBOX_MAIN_SETTINGS_ADDONS -DIN_VMM_STATIC
-DVBOX_WITH_SYS_V_IPC_SESSION_WATCHER -DVBOX_WITH_RAW_MODE
-DVBOX_WITH_NETFLT -DVBOX_WITH_CROGL -DVBOX_WITH_GUEST_PROPS
-DVBOX_WITH_GUEST_CONTROL -DVBOX_WITH_HOSTNETIF_API -DVBOX_WITH_VDE
-DVBOX_WITH_NEW_SYS_V_KEYGEN -DVBOX_WITH_VBOXSDL -DVBOX_WITH_HEADLESS
-DVBOX_WITH_QTGUI -DVBOX_WITH_HGCM -DVBOX_WITH_ALSA -DVBOX_WITH_E1000
-DVBOX_WITH_VIRTIO -DVBOX_WITH_AHCI -DVBOX_WITH_LSILOGIC
-DVBOX_WITH_RESOURCE_USAGE_API -DVBOX_WITH_PDM_ASYNC_COMPLETION
-DVBOX_WITH_EXTPACK -DVBOX_WITH_VUSB -DVBOX_WITH_S3 -DVBOX_WITH_USB
-DVBOX_WITH_NEW_USB_CODE_ON_DARWIN -DVBOX_WITH_HOSTNETIF_API
-DVBOX_USE_LIBHAL
-Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o.dep
-Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o
-Wp,-MP -o 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp
kmk: *** Waiting for unfinished jobs
kmk: *** Exiting with status 2
*** Error code 2

Stop in /usr/ports/emulators/virtualbox-ose.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose.

I have even try to build with debug symbols but I don't see anything
different. The system is running GENERIC kernel with debug options
disabled.

options COMPAT_FREEBSD32

Is included in the kernel as I saw that this has caused similar
problems in the past.

Any help would be appreciated
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 recent change (without revision 
bump) from cpumask_t to cpuset_t.


It seems like recent CAM changes and CPU change are going to require 
some changes to virtualbox in HostHardwareFreeBSD.c and mp-r0drv.c at 
least. Even though OS revision was not bumped, perhaps Makefile can 
switch on presence of cpuset userland utility?


Luckily I only csup'd a machine I don't really need Vbox on, so I'm 
holding back all other machines until Vbox maintainers sort out the issue.


Matt

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Jung-uk Kim]

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 recent change
 (without revision bump) from cpumask_t to cpuset_t.

 It seems like recent CAM changes and CPU change are going to
 require some changes to virtualbox in HostHardwareFreeBSD.c and
 mp-r0drv.c at least. Even though OS revision was not bumped,
 perhaps Makefile can switch on presence of cpuset userland utility?

 Luckily I only csup'd a machine I don't really need Vbox on, so I'm
 holding back all other machines until Vbox maintainers sort out the
 issue.

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 reason, 
though.  Do we really need revision bump, BTW?  Current means no 
seat belt anyway. ;-)

Cheers,

Jung-uk Kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Matt]

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 during kmod compile due to the recent change
(without revision bump) from cpumask_t to cpuset_t.

It seems like recent CAM changes and CPU change are going to
require some changes to virtualbox in HostHardwareFreeBSD.c and
mp-r0drv.c at least. Even though OS revision was not bumped,
perhaps Makefile can switch on presence of cpuset userland utility?

Luckily I only csup'd a machine I don't really need Vbox on, so I'm
holding back all other machines until Vbox maintainers sort out the
issue.

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 reason,
though.  Do we really need revision bump, BTW?  Current means no
seat belt anyway. ;-)

Cheers,

Jung-uk Kim

Thanks for the patch. I had read a comment somewhere complaining about 
detecting cpuset_t or cpumask_t regarding osrevision. Not really an 
issue, because it can be tested for without a bump.


Who needs seatbelts anyway... :). CURRENT  a cold beer is good enough 
for my home systems. Certainly prevents boredom anyway.


The Virtualbox error (not kmod error) looked like it was using an 
undefined struct to determine drive types, which I assume has been removed.


If you  the make output into a file and search for isDVD, you'll find 
that particular error, if still present. I just commented out the parts 
of the struct we don't have anymore, and it did compile...definitely 
could be dangerous, I haven't actually launched virtualbox with that 
fix...it could make for subtle or major problems. Your mileage  
seatbelt may vary :)


Matt

Matt


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[George Kontostanos]

 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 reason,
 though.  Do we really need revision bump, BTW?  Current means no
 seat belt anyway. ;-)

 Cheers,

 Jung-uk Kim


Yes the module build fine with this. Any ideas regarding the virtualbox itself ?

Cheers

-- 
George Kontostanos
aisecure.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Jung-uk Kim]

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 rebuild.
 
  Please note the revision wasn't set right for the obvious reason,
  though. �Do we really need revision bump, BTW? �Current means
  no seat belt anyway. ;-)
 
  Cheers,
 
  Jung-uk Kim

 Yes the module build fine with this.

Good.

 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
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[George Kontostanos]

On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim j...@freebsd.org 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
aisecure.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[Jung-uk Kim]

On Friday 24 June 2011 02:58 pm, George Kontostanos wrote:
 On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim j...@freebsd.org 
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 !!!

Please try this patch:

http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp

Just drop this in ports/emulators/virtualbox-ose/files and rebuild.

Cheers,

Jung-uk Kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: virtualbox-ose 4.0.8 fails

[George Kontostanos]

On Fri, Jun 24, 2011 at 11:11 PM, Jung-uk Kim j...@freebsd.org wrote:
 On Friday 24 June 2011 02:58 pm, George Kontostanos wrote:
 On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim j...@freebsd.org
 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 !!!

 Please try this patch:

 http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp

 Just drop this in ports/emulators/virtualbox-ose/files and rebuild.

 Cheers,

 Jung-uk Kim


Excellent work!

Best Regards,

-- 
George Kontostanos
aisecure.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: VirtualBox guest panic in ACPI

[Daniel O'Connor]

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: AE_ALREADY_EXISTS, Unable to install System Control Interrupt 
 handler (20110316/evevent-137)
 acpi: Could not enable ACPI: AE_ALREADY_EXISTS
 device_attach: acpi0 attach returned 6
 
 http://www.gsoft.com.au/~doconnor/Screen%20shot%202011-03-26%20at%2017.40.12%20.png
 
 Backtrace:
 http://www.gsoft.com.au/~doconnor/Screen%20shot%202011-03-26%20at%2017.37.38%20.png
 
 If I boot after setting hint.acpi.0.disabled=1 it then panics with No 
 usable event timer (there are errors about being unable to allocate an IRQ 
 prior to the panic)
 
 --
 Daniel O'Connor software and network engineer
 for Genesis Software - http://www.gsoft.com.au
 The nice thing about standards is that there
 are so many of them to choose from.
  -- Andrew Tanenbaum
 GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
 
 
 
 
 
 
 

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C






___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Ian FREISLICH]

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 !=3D 0  paPages[i].Phys !=3D
  NIL_RTHCPHYS  !(paPages[i].Phys  PAGE_OFFSET_MASK)
  00:00:15.481 Location  :
  /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox
  /VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t,
  const SUPPAGE*,=20
  const char*, RTGCPTR64*)
  00:00:15.482 i=3D0x0 Phys=3D Heap

Just wanted to report that -CURRENT compiled yesterday and Virtuabox
compiled last night work.

Ian

--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[KOT MATPOCKuH]

2010/2/24 Bernhard Froehlich de...@bluelife.at

 
 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/VirtualBox-3.1.2_OSE/src/VBox
 /VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR,
  size_t,
  const SUPPAGE*,
 const char*, RTGCPTR64*)
 00:00:15.482 i=0x0 Phys= Heap

 http://svn.bluelife.at/nightlies/virtualbox-port-r731.tar.gz
I also had this problem and with this port problem resolved.
Please commit to ports tree :)

--
MATPOCKuH
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Bernhard Froehlich]

On Mon, 1 Mar 2010 18:09:34 +0300, KOT MATPOCKuH matpoc...@gmail.com
wrote:
 2010/2/24 Bernhard Froehlich de...@bluelife.at

 
 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/VirtualBox-3.1.2_OSE/src/VBox
 /VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR,
  size_t,
  const SUPPAGE*,
 const char*, RTGCPTR64*)
 00:00:15.482 i=0x0 Phys= Heap

 http://svn.bluelife.at/nightlies/virtualbox-port-r731.tar.gz
 I also had this problem and with this port problem resolved.
 Please commit to ports tree :)

This problem is currently investigated and as soon as there is a final
patch that works for everyone we will commit it for sure.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Giovanni Trematerra]

On Tue, Feb 23, 2010 at 5:20 PM, Ian FREISLICH i...@clue.co.za 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: 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/VirtualBox-3.1.2_OSE/src/VBox/VMM/MMHyper.cpp(610)
  int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t, const SUPPAGE*, const 
 char*, RTGCPTR64*)
 00:00:15.482 i=0x0 Phys= Heap

 Does anyone have any ideas?


Hi Ian,
Are your arch i386?
There should be a bug in virtualbox-ose-kmod driver (vboxdrv to be precise).
vboxdrv passes to vtophys kernel macro, user virtual addresses instead
of kernel ones.
Without debug compilation you should experience freeze or reboot of
the host machine.

--
Gianni
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Shteryana Shopova]

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 N270 with CURRENT.

cheers,
Shteryana

On Tue, Feb 23, 2010 at 6:20 PM, Ian FREISLICH i...@clue.co.za 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: 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/VirtualBox-3.1.2_OSE/src/VBox/VMM/MMHyper.cpp(610)
  int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t, const SUPPAGE*, const 
 char*, RTGCPTR64*)
 00:00:15.482 i=0x0 Phys= Heap

 Does anyone have any ideas?

 Ian


 --
 Ian Freislich
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Jacques Fourie]

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 break something else.

Index: pmap.h
===
--- pmap.h  (revision 204194)
+++ pmap.h  (working copy)
@@ -296,7 +296,10 @@
 * however, safe to use the old PDE because the page table
 * page is preserved by the promotion.
 */
-   pa = KPTmap[i386_btop(va)];
+   if (va = KERNBASE)
+   pa = KPTmap[i386_btop(va)];
+   else
+   pa = *vtopte(va);
pa = (pa  PG_FRAME) | (va  PAGE_MASK);
}
return (pa);
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Giovanni Trematerra]

On Wed, Feb 24, 2010 at 12:16 PM, Jacques Fourie
jacques.fou...@gmail.com 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 after re-compiling vboxdrv just so that
 you don't inadvertently break something else.

 Index: pmap.h
 ===
 --- pmap.h      (revision 204194)
 +++ pmap.h      (working copy)
 @@ -296,7 +296,10 @@
                 * however, safe to use the old PDE because the page table
                 * page is preserved by the promotion.
                 */
 -               pa = KPTmap[i386_btop(va)];
 +               if (va = KERNBASE)
 +                       pa = KPTmap[i386_btop(va)];
 +               else
 +                       pa = *vtopte(va);
                pa = (pa  PG_FRAME) | (va  PAGE_MASK);
        }
        return (pa);

pmap_kextract is intend to be used with kernel virtual addresses and
not user virtual addresses.
The problem lies in the driver not in the kernel.

The vboxdrv call vtophys macro passing user virtual addresses through
rtR0MemObjNativeGetPagePhysAddr and this is wrong.

If you want a way to get virtualbox works try to revert this commit (r202894):
http://www.mail-archive.com/svn-src-...@freebsd.org/msg19081.html

If you don't use ZFS with superpages enable you have a good chance to
get a work system until a patch to vboxdrv will be around.

--
Gianni
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[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 != 0  paPages[i].Phys !=
NIL_RTHCPHYS  !(paPages[i].Phys  PAGE_OFFSET_MASK)
00:00:15.481 Location  :
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox
/VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t,
const SUPPAGE*, 
const char*, RTGCPTR64*)
00:00:15.482 i=0x0 Phys= Heap

Does anyone have any ideas?


Thanks for the report. I've talked to Alexander Eichner and he gave me a
patch that could
fix that problem. Could you please try to build the virtualbox-ose-kmod port
with that patch?
If it works we will include it in the port update coming quite soon.

http://pastebin.ca/1808090

If that does not help please create a backtrace from the vbox coredump and
send the vbox.log.

Thanks!

--
Bernhard Fröhlich
http://www.bluelife.at/
-- 
View this message in context: 
http://old.nabble.com/Virtualbox-tp27705983p27714203.html
Sent from the freebsd-current mailing list archive at Nabble.com.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Giovanni Trematerra]

2010/2/24 Bernhard Fröhlich de...@bluelife.at:

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  !(paPages[i].Phys  PAGE_OFFSET_MASK)
00:00:15.481 Location  :
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox
/VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t,
 const SUPPAGE*,
const char*, RTGCPTR64*)
00:00:15.482 i=0x0 Phys= Heap

Does anyone have any ideas?


 Thanks for the report. I've talked to Alexander Eichner and he gave me a
 patch that could
 fix that problem. Could you please try to build the virtualbox-ose-kmod port
 with that patch?
 If it works we will include it in the port update coming quite soon.

 http://pastebin.ca/1808090

 If that does not help please create a backtrace from the vbox coredump and
 send the vbox.log.

There are other point in src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c
where vtophys is misused as in rtR0MemObjNativeGetPagePhysAddr.
Using pmap_extract might be insufficient, what if the page will be swapped out?


 Thanks!

 --
 Bernhard Fröhlich
 http://www.bluelife.at/
 --
 View this message in context: 
 http://old.nabble.com/Virtualbox-tp27705983p27714203.html
 Sent from the freebsd-current mailing list archive at Nabble.com.

 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Ian FREISLICH]

=?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 Expression: paPages[i].Phys !=3D 0  paPages[i].Phys !=3D
 NIL_RTHCPHYS  !(paPages[i].Phys  PAGE_OFFSET_MASK)
 00:00:15.481 Location  :
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox
 /VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t,
 const SUPPAGE*,=20
 const char*, RTGCPTR64*)
 00:00:15.482 i=3D0x0 Phys=3D Heap
 
 Does anyone have any ideas?
 
 
 Thanks for the report. I've talked to Alexander Eichner and he gave me a
 patch that could
 fix that problem. Could you please try to build the virtualbox-ose-kmod por=
 t
 with that patch?
 If it works we will include it in the port update coming quite soon.
 
 http://pastebin.ca/1808090
 
 If that does not help please create a backtrace from the vbox coredump and
 send the vbox.log.

There is no coredump.

Answers to other questions:
The system is an intel atom N270.
Even though the processor does not support VT-x/AMD-V, nor was VB
compiled with that support, the virtual machine claims this is
enabled and there's no way to turn it off.

Log attached.

Ian

--
Ian Freislich

00:00:04.350 VirtualBox 3.1.2_OSE r56127 freebsd.x86 (Feb 23 2010 17:24:31) 
release log
00:00:04.350 Log opened 2010-02-24T14:09:20.811771000Z
00:00:04.351 OS Product: FreeBSD
00:00:04.351 OS Release: 9.0-CURRENT
00:00:04.351 OS Version: FreeBSD 9.0-CURRENT #16: Sun Feb  7 07:39:42 SAST 2010 
i...@mini.clue.co.za:/usr/obj/usr/src/sys/APPLE
00:00:04.351 Host RAM: 2031MB RAM, available: 1370MB
00:00:04.351 Executable: /usr/local/lib/virtualbox/VirtualBox
00:00:04.351 Process ID: 38681
00:00:04.351 Package type: BSD_32BITS_GENERIC (OSE)
00:00:04.365 Your keyboard type does not appear to be known to VirtualBox. If
00:00:04.365 you would like to help us improve the product, please submit a bug
00:00:04.365 report, attach this logfile and provide information about what type
00:00:04.365 of keyboard you have and whether you are using a remote X server or
00:00:04.365 something similar.
00:00:04.365 
00:00:04.365 The tables for your keyboard are:
00:00:04.365 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1, 0x2, 0x3, 0x4, 
0x5, 0x6, 0x7, 
00:00:04.365 0x8, 0x9, 0xa, 0xb, 0xc, 0xd, 0xe, 0xf, 0x10, 0x11, 0x12, 0x13, 
0x14, 0x15, 0x16, 0x17, 
00:00:04.365 0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f, 0x20, 0x21, 0x22, 
0x23, 0x24, 0x25, 0x26, 0x27, 
00:00:04.366 0x28, 0x29, 0x2a, 0x2b, 0x2c, 0x2d, 0x2e, 0x2f, 0x30, 0x31, 0x32, 
0x33, 0x34, 0x35, 0x36, 0x37, 
00:00:04.366 0x38, 0x39, 0x1d, 0x3b, 0x3c, 0x3d, 0x3e, 0x3f, 0x40, 0x41, 0x42, 
0x43, 0x44, 0x145, 0x46, 0x47, 
00:00:04.366 0x48, 0x49, 0x4a, 0x4b, 0x4c, 0x4d, 0x4e, 0x4f, 0x50, 0x51, 0x52, 
0x53, 0x0, 0x138, 0x56, 0x57, 
00:00:04.367 0x58, 0x147, 0x148, 0x149, 0x14b, 0x0, 0x14d, 0x14f, 0x150, 0x151, 
0x152, 0x153, 0x11c, 0x11d, 0x45, 0x137, 
00:00:04.367 0x135, 0x138, 0x0, 0x15b, 0x15c, 0x15d, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x138, 0x0, 0x0, 0x0, 
00:00:04.368 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.368 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.368 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.369 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.369 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.370 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.370 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 
00:00:04.370 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0
00:00:04.371 and
00:00:04.371 NULL, 0x25, 0x32, 0x0, 0x17, 0x9, 0x24, 0x62, 0x68,
00:00:04.371 0x64, 0x66, 0x43, 0x44, 0x45, 0x46, 0x47, 0x48, 0x49, 0x4a
00:00:04.433 SUP: Loaded VMMR0.r0 (/usr/local/lib/virtualbox/VMMR0.r0) at 
0xcb80f060 - ModuleInit at cb8233d0 and ModuleTerm at cb823390
00:00:04.433 SUP: VMMR0EntryEx located at cb823260, VMMR0EntryFast at 
cb823450 and VMMR0EntryInt at cb8224c0
00:00:04.684 VBoxSharedClipboard mode: Bidirectional
00:00:04.700 * CFGM dump *
00:00:04.700 [/] (level 0)
00:00:04.700   CSAMEnabled integer = 0x0001 (1)
00:00:04.700   EnablePAE   integer = 0x (0)
00:00:04.700   HwVirtExtForced integer = 0x (0)
00:00:04.700   Namestring  = windows1 (cb=9)
00:00:04.700   NumCPUs integer = 0x0001 (1)
00:00:04.700   PATMEnabled integer = 0x0001 (1)
00:00:04.700   RamHoleSize integer = 0x2000 

Re: Virtualbox

[Bernhard Froehlich]

On Wed, 24 Feb 2010 15:02:30 +0100, Giovanni Trematerra
giovanni.tremate...@gmail.com wrote:
 2010/2/24 Bernhard Fröhlich de...@bluelife.at:

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  !(paPages[i].Phys  PAGE_OFFSET_MASK)
00:00:15.481 Location  :
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox
/VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR,
size_t,
 const SUPPAGE*,
const char*, RTGCPTR64*)
00:00:15.482 i=0x0 Phys= Heap

Does anyone have any ideas?


 Thanks for the report. I've talked to Alexander Eichner and he gave me
a
 patch that could
 fix that problem. Could you please try to build the virtualbox-ose-kmod
 port
 with that patch?
 If it works we will include it in the port update coming quite soon.

 http://pastebin.ca/1808090

 If that does not help please create a backtrace from the vbox coredump
 and
 send the vbox.log.
 
 There are other point in
 src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c
 where vtophys is misused as in rtR0MemObjNativeGetPagePhysAddr.
 Using pmap_extract might be insufficient, what if the page will be
swapped
 out?

According to aeichner that should not happen as all memory allocated there
is locked. He's at the moment having a look at the other vtophys calls.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Bernhard Froehlich]

On Wed, 24 Feb 2010 16:04:33 +0100, Bernhard Froehlich de...@bluelife.at
wrote:
 On Wed, 24 Feb 2010 15:02:30 +0100, Giovanni Trematerra
 giovanni.tremate...@gmail.com wrote:
 2010/2/24 Bernhard Fröhlich de...@bluelife.at:

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  !(paPages[i].Phys  PAGE_OFFSET_MASK)
00:00:15.481 Location  :
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/src/VBox
/VMM/MMHyper.cpp(610) int MMR3HyperMapPages(VM*, void*, RTR0PTR,
 size_t,
 const SUPPAGE*,
const char*, RTGCPTR64*)
00:00:15.482 i=0x0 Phys= Heap

Does anyone have any ideas?


 Thanks for the report. I've talked to Alexander Eichner and he gave me
 a
 patch that could
 fix that problem. Could you please try to build the
virtualbox-ose-kmod
 port
 with that patch?
 If it works we will include it in the port update coming quite soon.

 http://pastebin.ca/1808090

 If that does not help please create a backtrace from the vbox coredump
 and
 send the vbox.log.
 
 There are other point in
 src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c
 where vtophys is misused as in rtR0MemObjNativeGetPagePhysAddr.
 Using pmap_extract might be insufficient, what if the page will be
 swapped
 out?
 
 According to aeichner that should not happen as all memory allocated
there
 is locked. He's at the moment having a look at the other vtophys calls.

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@ 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

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Michael Butler]

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@ 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:

I grabbed it from SVN and it works just fine here - thanks!

imb


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Douglas Berry]

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 r204216 i386 small memory machine.
Thanks to the virtualbox porters!

cheers,
doug

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Virtualbox

[Alexey Shuvaev]

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 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/VirtualBox-3.1.2_OSE/src/VBox/VMM/MMHyper.cpp(610)
  int MMR3HyperMapPages(VM*, void*, RTR0PTR, size_t, const SUPPAGE*, const 
 char*, RTGCPTR64*)
 00:00:15.482 i=0x0 Phys= Heap
 
 Does anyone have any ideas?
 
Me not.
Just FYI:

~ VBoxManage startvm WinXP --type sdl
VirtualBox Command Line Management Interface Version 3.1.2_OSE
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

Waiting for the remote session to open...
Remote session has been successfully opened.

~ uname -a
FreeBSD wep4035 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r202285: Thu Jan 14 19:04:21 
CET 2010 r...@wep4035:/usr/obj/usr/src/sys/GENERIC  amd64

~ sysctl vm.pmap.pg_ps_enabled
vm.pmap.pg_ps_enabled: 1

~ cat /boot/loader.conf
loader_logo=beastie
ichsmb_load=YES
snd_hda_load=YES
speaker_load=YES
i915_load=YES
linux_load=YES
vboxdrv_load=YES

The virtial machine was newly created and installed already on this CURRENT.

0.02$,
Alexey.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org