Re: Virtualbox
On Wed, 24 Feb 2010 15:02:30 +0100, Giovanni Trematerra wrote: > 2010/2/24 Bernhard Fröhlich : >> >>>Hi >>> >>>Has anyone managed to make Virtualbox work on 9-Current? Since >>>installing 3.1.2-OSE VMs, all brand new, abort on startup. >>> >>>The last part of the log seems pertinent: >>> >>>00:00: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
On Wed, 24 Feb 2010 16:04:33 +0100, Bernhard Froehlich wrote: > On Wed, 24 Feb 2010 15:02:30 +0100, Giovanni Trematerra > wrote: >> 2010/2/24 Bernhard Fröhlich : >>> >>>>Hi >>>> >>>>Has anyone managed to make Virtualbox work on 9-Current? Since >>>>installing 3.1.2-OSE VMs, all brand new, abort 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
On Mon, 1 Mar 2010 18:09:34 +0300, KOT MATPOCKuH wrote: > 2010/2/24 Bernhard Froehlich >> >> >>>> >> >>>>00:00:15.481 !!Assertion Failed!! >> >>>>00:00:15.481 Expression: paPages[i].Phys != 0 && paPages[i].Phys != >> >>> NIL_RTHCPHYS && >!(paPages[i].Phys & PAGE_OFFSET_MASK) >> >>>>00:00:15.481 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: Call for tester: VirtualBox 3.1.2 for FreeBSD (take 2)
On Sun, 07 Mar 2010 19:47:37 +0300, "Azim" wrote: > I am using FreeBSD 9.0 CURRENT (201002) as the host OS and I am trying > to run XP64-SP2 as Guest on VirtualBOX version 3.1.2_OSE r56127 > > I have vboxnet_enable="YES" in /etc/rc.conf and vboxdrv_load="YES" in > /boot/loader.conf for Networking support. > > VirtualBox allows me to add an existing vhd but when I click Start the > Guest Windows appears and gets cloded and the status below the Guest OS > name is seen as "Aborted". > > Below are the few end lines of the log file > XP64-SP2-2010-03-07-21-48-52.log : > > LOG FILE > 00:00:01.278 > 00:00:01.278 * End of CFGM dump > ** > 00:00:01.278 MM: cbHyperHeap=0x14 (1310720) > 00:00:01.284 > 00:00:01.284 !!Assertion Failed!! > 00:00:01.284 Expression: paPages[i].Phys != 0 && paPages[i].Phys != > NIL_RTHCPHYS && !(paPages[i].Phys & PAGE_OFFSET_MASK) > 00:00:01.284 Location : > /work/a/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:01.284 i=0x0 Phys= Heap > LOG FILE > > Is this a known error ? Yes and it is already investigated. It only happens with current and stable after beginning of February. A testing patch was send to freebsd-emulators@ last week. -- 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"
gcc segfault: Cannot build virtualbox-ose on 8-STABLE amd64
On Thu, 20 May 2010 23:05:53 -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I recently reinstalled my FreeBSD 8-STABLE box to move from > i386 to amd64. The hardware hasn't changed (except for an increase > from 4GB to 8GB ram). > > There have been some hiccups and I am still trying to tidy > up things together. > > One of the problems I am having is building virtualbox-ose > which previously built nicely on i386. > > I am running a vanilla 8-STABLE world (no special COPTFLAGS) from May > 17th. > > $ uname -a > FreeBSD exxodus.fedaykin.here 8.0-STABLE FreeBSD 8.0-STABLE #2: Mon May 17 > 19:53:30 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > > I have a clean and up to date ports tree from today. > All ports upgraded using portupgrade. > > I am trying to build the virtualbox-ose port with vanilla cflags. > > $ make -V CFLAGS > -O2 -pipe -fno-strict-aliasing > > The relevant message follows: > > - > > kBuild: Installing VBoxControl => > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/bin/additions/VBoxControl > kmk[2]: *** > [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h] > Segmentation fault: 11 (core dumped) > kmk[2]: *** Deleting file > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h' > kmk[2]: Leaving directory > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE' > kmk[1]: *** [pass_binaries_this] Error 2 > kmk[1]: Leaving directory > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE' > kmk: *** [pass_binaries_order] Error 2 > *** Error code 2 > > - > > The complete build log can be found at > > http://people.freebsd.org/~lioux/virtualbox-ose_3.1.8_build.log.bz2 > > My virtualbox-ose work directory can be found at > (you need archivers/xz to extract it) > > http://people.freebsd.org/~lioux/virtualbox-ose__work.tar.xz > > Let me know if there is anything I can do to help. > > Regards, > > ps: virtualbox-ose-kmod builds without a problem as well as my other > 1482 ports. :) Segmentation fault: 11 comes from gcc so this is likely to be a compiler bug and i'm not sure if we can help in this case so I cc'd curr...@. Could you try to get a backtrace from the core file that it has dumped? -- 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: emulators/vitrualbox-ose fails on 9.0-PRERELEASE
On 25.11.2011 08:02, Aryeh Friedman wrote:
With the following installed and all the prerequest ports for vbox
when I
attempt to boot a default machine setup for freebsd guest OS install
it
fails immediately with:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
flosoft# uname -a
FreeBSD flosoft.no-ip.biz 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #4:
Thu Nov
24 22:45:48 EST 2011
r...@flosoft.no-ip.biz:/usr/obj/usr/src/sys/GENERIC
i386
flosoft# kldstat
Id Refs AddressSize Name
1 27 0xc040 e59bd8 kernel
21 0xc125a000 97a4 linprocfs.ko
33 0xc1264000 2fcf4linux.ko
41 0xc1294000 ad87d0 nvidia.ko
53 0xc7f12000 2d000vboxdrv.ko
61 0xc7f4b000 2000 vboxnetadp.ko
71 0xc7f4d000 5000 vboxnetflt.ko
82 0xc7f52000 b000 netgraph.ko
91 0xc7f89000 4000 ng_ether.ko
Sorry, but this information is not enough to have a clue what is going
wrong. Please look at ~/Virtualbox VMs//logs/VBox.log (or kind
of) and send the logfile. If that doesn't help please recompile the
ports with the DEBUG option enabled.
--
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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 01.12.2011 00:07, Jung-uk Kim wrote: On Wednesday 30 November 2011 05:32 pm, Andriy Gapon wrote: on 26/11/2011 18:33 Gleb Kurtsou said the following: > Using new vm_page_alloc_contig() may be a better option here. > Can't help with patch, stuck with pre Nov 15 CURRENT myself. on 27/11/2011 19:09 Alan Cox said the following: > vm_page_alloc_contig() should be used instead. My take on the patch: http://people.freebsd.org/~avg/vbox-10.patch This is for head only, no check for FreeBSD version. Actually, I did the same thing last night: http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c This is a drop-in replacement for the patch. The only practical difference I see from yours is I used VM_ALLOC_INTERRUPT instead of VM_ALLOC_NORMAL. I believe this function may be used in interrupt context. FYI, I tried FreeBSD 9 and Fedora 10 without problem. Thanks a lot for both patches! Could you please as usual reply and tell me if it is okay to send this patch upstream under MIT license? Once there is some positive feedback I will commit both patches to the ports tree. -- 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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 01.12.2011 09:37, Bernhard Froehlich wrote: On 01.12.2011 00:07, Jung-uk Kim wrote: On Wednesday 30 November 2011 05:32 pm, Andriy Gapon wrote: on 26/11/2011 18:33 Gleb Kurtsou said the following: > Using new vm_page_alloc_contig() may be a better option here. > Can't help with patch, stuck with pre Nov 15 CURRENT myself. on 27/11/2011 19:09 Alan Cox said the following: > vm_page_alloc_contig() should be used instead. My take on the patch: http://people.freebsd.org/~avg/vbox-10.patch This is for head only, no check for FreeBSD version. Actually, I did the same thing last night: http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c This is a drop-in replacement for the patch. The only practical difference I see from yours is I used VM_ALLOC_INTERRUPT instead of VM_ALLOC_NORMAL. I believe this function may be used in interrupt context. FYI, I tried FreeBSD 9 and Fedora 10 without problem. Thanks a lot for both patches! Could you please as usual reply and tell me if it is okay to send this patch upstream under MIT license? Once there is some positive feedback I will commit both patches to the ports tree. Patch has been send upstream: https://www.virtualbox.org/pipermail/vbox-dev/2011-December/004842.html -- 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: emulators/vitrualbox-ose fails on 9.0-PRERELEASE
On 26.11.2011 07:29, Aryeh Friedman wrote:
On Fri, Nov 25, 2011 at 3:39 AM, Bernhard Froehlich wrote:
On 25.11.2011 08:02, Aryeh Friedman wrote:
With the following installed and all the prerequest ports for vbox
when I
attempt to boot a default machine setup for freebsd guest OS
install it
fails immediately with:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
flosoft# uname -a
FreeBSD flosoft.no-ip.biz [1] 9.0-PRERELEASE FreeBSD
9.0-PRERELEASE #4: Thu Nov
24 22:45:48 EST 2011
r...@flosoft.no-ip.biz:/usr/obj/usr/src/sys/GENERIC
i386
flosoft# kldstat
Id Refs Address Size Name
1 27 0xc040 e59bd8 kernel
2 1 0xc125a000 97a4 linprocfs.ko
3 3 0xc1264000 2fcf4 linux.ko
4 1 0xc1294000 ad87d0 nvidia.ko
5 3 0xc7f12000 2d000 vboxdrv.ko
6 1 0xc7f4b000 2000 vboxnetadp.ko
7 1 0xc7f4d000 5000 vboxnetflt.ko
8 2 0xc7f52000 b000 netgraph.ko
9 1 0xc7f89000 4000 ng_ether.ko
Sorry, but this information is not enough to have a clue what is
going wrong. Please look at ~/Virtualbox VMs//logs/VBox.log (or kind
of) and send the logfile. If that doesnt help please recompile the
ports with the DEBUG option enabled.
Thanks for the logfile and sorry that it took me so long to get back to
you. I've found the following:
00:00:00.410 rtldrNativeLoad:
dlopen('/usr/local/lib/virtualbox/VBoxREM32.so', RTLD_NOW | RTLD_LOCAL)
failed: /usr/local/lib/virtualbox/VBoxREM32.so: Undefined symbol
"atan2l"
This tells that we have an undefined symbol in one of the shared
objects
but you are the first one to report this and 4.0.12 is used quite a lot
so
I guess that there is something strange going on in your system. Could
you please try recompiling the virtualbox-ose port and see if this
fixes it?
--
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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 02.12.2011 12:55, Bernhard Froehlich wrote: On 01.12.2011 09:37, Bernhard Froehlich wrote: On 01.12.2011 00:07, Jung-uk Kim wrote: On Wednesday 30 November 2011 05:32 pm, Andriy Gapon wrote: on 26/11/2011 18:33 Gleb Kurtsou said the following: > Using new vm_page_alloc_contig() may be a better option here. > Can't help with patch, stuck with pre Nov 15 CURRENT myself. on 27/11/2011 19:09 Alan Cox said the following: > vm_page_alloc_contig() should be used instead. My take on the patch: http://people.freebsd.org/~avg/vbox-10.patch This is for head only, no check for FreeBSD version. Actually, I did the same thing last night: http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c This is a drop-in replacement for the patch. The only practical difference I see from yours is I used VM_ALLOC_INTERRUPT instead of VM_ALLOC_NORMAL. I believe this function may be used in interrupt context. FYI, I tried FreeBSD 9 and Fedora 10 without problem. Thanks a lot for both patches! Could you please as usual reply and tell me if it is okay to send this patch upstream under MIT license? Once there is some positive feedback I will commit both patches to the ports tree. Patch has been send upstream: https://www.virtualbox.org/pipermail/vbox-dev/2011-December/004842.html Patches have been committed upstream. Thanks a lot guys! https://www.virtualbox.org/changeset/39521 -- 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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 05.12.2011 14:06, Andriy Gapon wrote: on 05/12/2011 14:57 Bernhard Froehlich said the following: On 02.12.2011 12:55, Bernhard Froehlich wrote: Patch has been send upstream: https://www.virtualbox.org/pipermail/vbox-dev/2011-December/004842.html Patches have been committed upstream. Thanks a lot guys! https://www.virtualbox.org/changeset/39521 BTW, I think that we additionally need VM_ALLOC_NOBUSY in flags that we pass to vm_phys_alloc_contig. What's the difference of this? BTW you reported about the GCC 4.5 header stuff and it was also already fixed: http://lists.freebsd.org/pipermail/freebsd-emulation/2011-December/009312.html -- 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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 06.12.2011 10:08, Andriy Gapon wrote: on 06/12/2011 02:08 Alan Cox said the following: The right thing to do is to MFC vm_page_alloc_contig(). It shouldn't be that hard to merge it. Ah, but we want to be able to run virtualbox on the past releases too. Which releases are we talking about here? VirtualBox was always deprecating older FreeBSD releases much faster than our Security EOL so if we focus on latest 8.x and >= 9.0 I think it should be okay. We have already deprecated 7.x because of some other problems with the userland bits so we can forget about 7.x completely. What is left is 8.1 and 8.2 and both are EOL until mid 2012. So if is possible to get it merged in time for 8.3 and 9.1 (if needed) we should be fine. -- 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: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 06.12.2011 12:00, Andriy Gapon wrote: on 06/12/2011 11:40 Bernhard Froehlich said the following: On 06.12.2011 10:08, Andriy Gapon wrote: on 06/12/2011 02:08 Alan Cox said the following: The right thing to do is to MFC vm_page_alloc_contig(). It shouldn't be that hard to merge it. Ah, but we want to be able to run virtualbox on the past releases too. Which releases are we talking about here? VirtualBox was always deprecating older FreeBSD releases much faster than our Security EOL so if we focus on latest 8.x and >= 9.0 I think it should be okay. We have already deprecated 7.x because of some other problems with the userland bits so we can forget about 7.x completely. What is left is 8.1 and 8.2 and both are EOL until mid 2012. So if is possible to get it merged in time for 8.3 and 9.1 (if needed) we should be fine. So we would just say "screw you" to people who stick to e.g. 8.2 at the moment? :) No. We currently have the last 2 virtualbox major versions in the ports tree so if we decide to do such an incompatible change we always have the older version around for 8.2 users for about the next year. -- 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}]
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: Processes getting stuck in state tmpfs
On 01.03.2012 23:25, Florian Smeets wrote: On 01.03.12 20:31, Gleb Kurtsou wrote: Could you test the patch attached. It's also available here as seperate commits: https://github.com/glk/freebsd-head/commits/tmpfs-rename The test that used to hang within a minute has now been running successfully for almost 2 hours. Looks good to me. I have also re-enabled tmpfs on redports.org main tinderbox with this patch applied and it runs smooth so far! Very good work. Thanks a lot! FreeBSD tb3.bluelife.at 10.0-CURRENT FreeBSD 10.0-CURRENT #3: Wed Mar 7 23:47:56 CET 2012 r...@tb3.bluelife.at:/usr/obj/usr/src/sys/GENERIC amd64 -- 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
On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim > wrote: >> >> Any ideas regarding the virtualbox itself ? >> > >> > I am rebuilding world/kernel now. �After that, I'll rebuild >> > 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
On Mon, 27 Jun 2011 10:54:08 +0300, Sergey V. Dyatko wrote: > On Sat, 25 Jun 2011 16:28:41 +0200 > Bernhard Froehlich wrote: > >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: >> > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim >> > wrote: >> >> >> Any ideas regarding the virtualbox itself ? >> >> > >> >> > I am rebuilding world/kernel now. �After that, I'll rebuild >> >> > virtualbox-ose and try to fix it unless someone beat me to it. >> >> > :-) >> >> > >> >> > Jung-uk Kim >> >> >> >> Brilliant !!! >> > >> > 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
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 >> > >> > 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=revision&revision=223081 http://svnweb.freebsd.org/base?view=revision&revision=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: em problem in virtualbox since the weekend
On Wed, 20 Jul 2011 07:41:26 -0400, John Baldwin wrote: > On Tuesday, July 19, 2011 10:35:42 pm Steve Wills wrote: >> Hi, >> >> While testing some other things, I found -CURRENT from yesterday doesn't >> work with the em0 in my VirtualBox 4.0.8 (a little out of date >> admittedly). It worked Friday or Saturday I think. Anyone else seen this >> or should I open a PR? Has the code changed or am I perhaps >> misremembering dates? The error reported is: >> >> em0: Unable to allocate bus resource: memory >> em0: Allocation of PCI resources failed > > This is due to a bug in VirtualBox's BIOS implementation. Someone > should file > a bug report with VirtualBox to ask them to fix their BIOS. The problem is > that they claim that the Host-PCI bridge in their system only decodes > addresses 0xa-0xb (i.e. the VGA window) via the "Producer" resources > in the _CRS method of the Host-PCI bridge device. This tells the OS > that all > the existing PCI devices are using invalid memory address ranges but that > there is also no available address space to allocate for PCI devices such as > em0. > > You can workaround this by setting "debug.acpi.disabled=hostres" until > VirtualBox fixes their code. I'm happy to provide further > clarification to an > existing VirtaulBox bug report if needed. Thanks a lot for the analysis! I've talked to one of the virtualbox developers about that but they are not aware of such problems with Linux or Windows guests yet. So they are currently unsure if it's a VirtualBox or FreeBSD fault and if it's their fault why it works fine with other guests. I'm also unsure because I haven't heard of that problem before and now multiple people complain. That looks more like a FreeBSD related problem on current or stable. I think it would be good if someone could try to reproduce that with emulators/virtualbox-ose-legacy which is 3.2.12 to get some vbox dev look into the problem again. -- 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
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
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"
