Re: Virtualbox headless, X11=off, VNC not working
On 21.11.18 19:22, Ole wrote: Hi, I'm trying to run a VM in Headless mode with VNC-Server activated. The VM runns, the VNC Server is up and I can connect but the screen stays black. Mouse and Keyboard is transmitted (I can see the cursor moving on phphvirtualbox VM-preview) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232528 Come join the club. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
virtualbox-ose 5.2.20 - vnc doesn't work for me
Hello. After upgrading to latest VB and connecting to any host via VNC I see only a default 640x480 black screen with no output. No errors shown. Anyone else seeing this? Thanks in advance. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
r318716 effectively kills virtualbox on STABLE-11
Hello. After updating today I see this: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x5a fault code = supervisor read data, page not present instruction pointer = 0x20:0x805e59c0 stack pointer = 0x28:0xfe046c81d570 frame pointer = 0x28:0xfe046c81d5e0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 37300 (VBoxHeadless) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x803ab4e7 at kdb_backtrace+0x67 #1 0x8036add6 at vpanic+0x186 #2 0x8036ac43 at panic+0x43 #3 0x806113a2 at trap_fatal+0x322 #4 0x806113f9 at trap_pfault+0x49 #5 0x80610c36 at trap+0x286 #6 0x805f7371 at calltrap+0x8 #7 0x818924e4 at rtR0MemObjFreeBSDPhysAllocHelper+0x94 #8 0x81891bf2 at rtR0MemObjFreeBSDAllocPhysPages+0x72 #9 0x81891b6b at rtR0MemObjNativeAllocPhys+0x2b #10 0x81935981 at nrefs+0x7da1 #11 0x819549d4 at nrefs+0x26df4 #12 0x81957902 at nrefs+0x29d22 #13 0x8186d38c at supdrvIOCtlInnerUnrestricted+0x114c #14 0x8187ab13 at VBoxDrvFreeBSDIOCtl+0x1a3 #15 0x802eff98 at devfs_ioctl_f+0x128 #16 0x803c6965 at kern_ioctl+0x255 #17 0x803c668e at sys_ioctl+0x16e Rebuilding virtualbox-ose* doesn't help. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: core dump in vboxdrv memory management on 11-STABLE
Volodymyr Kostyrko wrote: Hi all. Is anyone else seeing this or that's me breaking something? Unread portion of the kernel message buffer: panic: page 0xf80404001980 is PG_FICTITIOUS or PG_MARKER cpuid = 1 Just in case someone would step into it: my kernel was based off MINIMAL which has full debugging enabled. Turning all debugging off in the kernel cleared the problem. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
core dump in vboxdrv memory management on 11-STABLE
Hi all. Is anyone else seeing this or that's me breaking something? Unread portion of the kernel message buffer: panic: page 0xf80404001980 is PG_FICTITIOUS or PG_MARKER cpuid = 1 KDB: stack backtrace: #0 0x803a6c07 at kdb_backtrace+0x67 #1 0x80368aa6 at vpanic+0x186 #2 0x80368916 at kassert_panic+0x126 #3 0x805c9db6 at vm_page_scan_contig+0xc6 #4 0x805d2385 at vm_phys_scan_contig+0xf5 #5 0x805ca3e7 at vm_page_reclaim_contig+0x127 #6 0x81ab222a at rtR0MemObjFreeBSDPhysAllocHelper+0xda #7 0x81ab18bc at rtR0MemObjFreeBSDAllocPhysPages+0x7c #8 0x81ab182b at rtR0MemObjNativeAllocPhys+0x2b #9 0x81b55867 at nrefs+0x7a5f #10 0x81b72d24 at nrefs+0x24f1c #11 0x81b75f1a at nrefs+0x28112 #12 0x81a8c627 at supdrvIOCtlInnerUnrestricted+0x407 #13 0x81a9ac96 at VBoxDrvFreeBSDIOCtl+0x1b6 #14 0x802f0916 at devfs_ioctl_f+0x156 #15 0x803c7de0 at kern_ioctl+0x2b0 #16 0x803c7a8c at sys_ioctl+0x13c #17 0x805fbd69 at amd64_syscall+0x2f9 (kgdb) #0 doadump (textdump=) at pcpu.h:222 #1 0x80368520 in kern_reboot (howto=) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0x80368ae0 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0x80368916 in kassert_panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:649 #4 0x805c9db6 in vm_page_scan_contig (npages=512, m_start=, m_end=0xf80408dec100, alignment=, boundary=0, options=) at /usr/src/sys/vm/vm_page.c:2191 #5 0x805d2385 in vm_phys_scan_contig (npages=512, low=, high=, alignment=, boundary=, options=1) at /usr/src/sys/vm/vm_phys.c:1215 #6 0x805ca3e7 in vm_page_reclaim_contig (req=, npages=512, low=0, high=18446744073709551615, alignment=, boundary=) at /usr/src/sys/vm/vm_page.c:2693 #7 0x81ab222a in rtR0MemObjFreeBSDPhysAllocHelper () from /boot/modules/vboxdrv.ko #8 0x81ab18bc in rtR0MemObjFreeBSDAllocPhysPages () from /boot/modules/vboxdrv.ko #9 0x81ab182b in rtR0MemObjNativeAllocPhys () from /boot/modules/vboxdrv.ko #10 0x81b55867 in ?? () #11 0xfe031b372010 in ?? () #12 0x in ?? () VirtualBox 5.1.14, 11-STABLE daily updated... -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: bhyve: zvols for guest disk - yes or no?
Jan Bramkamp wrote: An other thing I learned the hard way is that ZVOL are set in stone at the ZVOL creation. You have to (cam)dd everything to change the block size. The default ZVOL block size is 8K which isn't wrong but your guests need to align their file systems (and swap) correctly or you'll suffer from write amplification. And ZFS RAID-Z really sucks for such small block sizes. Use mirrored VDEVs in your pools or you will suffer from massive metadata overhead and disappointing IOPS. This pole has two ends though. When you are working with file system default 8k block size is too small. Setting it up to 64k will save a lot writes for host. This is due to most current filesystems do work correctly with extents/big blocks: * Linux: ext4, xfs - full support; * BSD: ufs - disabled, need to be enabled on format, zfs - full support; * NTFS: no support, but you can use 64k blocks with Win XP - Win 10 (though Win XP can't boot off such partition). Setting block size bigger makes fragmentation less common (check your `zpool list`) and saves writes. When guest writes one 64k chunk ZFS writes 8 separate 8k blocks (+ metadata and stuff) and this is not good for the speed. On the opposite when you have some database inside VM you need to prepare disk for it accordingly. Guides for using PostgreSQL and MySQL apply to VM's too. MSSQL on the other hand uses 64k extents to work with database internally so raising block size to 64k would be good for it. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
what's current aio status for upcoming 11?
Hi all. FreeBSD limbo.b1t.name 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #5 r304082: Sun Aug 14 19:03:18 EEST 2016 arc...@limbo.b1t.name:/usr/obj/usr/src/sys/MIN amd64 VBoxHeadless dumps core at signal 11: (gdb) bt full #0 0x000801d8200c in RTFileAioReqPrepareWrite (hReq=0x805e1b3c0, hFile=0x14, off=9701297152, pvBuf=0x84f573000, cbWrite=4096, pvUser=0x805e5aea0) at /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/VBox/Runtime/r3/freebsd/fileaio-freebsd.cpp:227 No locals. #1 0x0008053dcc96 in pdmacFileAioMgrNormalReqCompleteRc (pAioMgr=0x80a84e3a0, hReq=0x805e1b3c0, rcReq=0, cbTransfered=optimized out>) at /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:1503 offStart = cbToTransfer = pEndpoint = 0x806257aa0 pTasksWaiting = pTask = #2 0x0008053dca8e in pdmacFileAioMgrNormalReqsEnqueue () at /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:615 rcReq = 2 pAioMgr = Cannot access memory at address 0x0 Current language: auto; currently c++ I see aio is in MINIMAL kernel now yet I haven't requested it... Is it mandatory now? What I should do with VBox dumping core randomly? Thanks in advance. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Is FreeBSD ready for VirtualBox 5.0?
Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/02/2015 17:46, Jung-uk Kim wrote: On 04/02/2015 00:35, Korto Ivork wrote: Good day! There is a announce of VirtualBox 5.0 Beta, is FreeBSD VBOX-Team ready to bring that product in ports? ... I took a look at it yesterday. Unfortunately, it seems it may take a while. I have done some work today. If you feel adventurous, you can download the first rough cut from here. https://people.freebsd.org/~jkim/vbox/vbox5.tar.xz I'll try to revive this thread a little. 5.0.24: 1. Building fails when openssl is installed from port. 2. Can't get any sound: > VBoxManage modifyvm 7_1 --audio oss VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available) VBoxManage: error: Context: "COMSETTER(AudioDriver)(AudioDriverType_OSS)" at line 2261 of file VBoxManageModifyVM.cpp -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox development repository
On 28.04.2015 01:01, Jung-uk Kim wrote: FYI, preliminary port for 5.0.0-BETA2 is available from here: https://people.freebsd.org/~jkim/vbox/vbox5.tar.xz Works on STABLE-10, no problems with executable bit after installation. Guests checked: Fedora, Debian, Windows 10. OS X is not working but that's since 4.3.8. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: FreeBSD Port: emulators/virtualbox-ose exited on signal 11 random crashes on screen update using VNC
On 23.07.2014 11:02, Ron Thomas wrote: Have an intermittent crash that I haven't been able to figure out the trigger for perhaps a race condition? Happens frequently, usually when lots of stuff is happening on screen. Core dump shows that it always fails at the same line of code. You are not alone. FreeBSD spathi.maxima.local 10.1-RELEASE-p1 FreeBSD 10.1-RELEASE-p1 #0 r275833M: Tue Dec 16 22:48:44 EET 2014 arcade@spathi.maxima.local:/usr/obj/usr/src/sys/MINIMAL amd64 (gdb) frame #0 0x000808e20bc0 in rfbSetClientColourMaps () from /usr/local/lib/libvncserver.so.0 (gdb) bt full #0 0x000808e20bc0 in rfbSetClientColourMaps () from /usr/local/lib/libvncserver.so.0 No symbol table info available. #1 0x000808e3249a in rfbSendRectEncodingZRLE () from /usr/local/lib/libvncserver.so.0 No symbol table info available. #2 0x000808e16143 in rfbSendFramebufferUpdate () from /usr/local/lib/libvncserver.so.0 No symbol table info available. #3 0x000808e10e0c in rfbRunEventLoop () from /usr/local/lib/libvncserver.so.0 No symbol table info available. #4 0x00080082c585 in pthread_create () from /lib/libthr.so.3 No symbol table info available. #5 0x in ?? () No symbol table info available. I'm running virtualbox-ose-4.3.6, virtualbox-ose-4.3.20_1 is the latest version but all versions above 4.3.6 has some weird problems with Mac guests. You can try updating vbox though. There was a change about VRDP at 4.3.16. The other hont is: disable DEBUG for VBox, it can become unstable. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Virtualbox fails in poudriere 3.1
On 05.12.2014 21:42, Kenta S. wrote: Hi. Virtualbox is failing to build for me and I would appreciate any help. Sorry for huge log, i compressed so its smaller. This is the ending: 8 warnings and 8 errors generated. kmk: *** [/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/obj/VBoxSDL/VBoxSDL.o] Error 1 The failing command: @clang++ -c -O2 -fPIC -g -pipe -pedantic -Wshadow -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter -Wno-long-long -Wno-long-long -Wno-delete-non-virtual-dtor -Wno-variadic-macros -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fexceptions -frtti -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -m64 -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/obj/VBoxSDL -I/usr/local/include -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include -I/tmp/usr/ports/emulators/virtualbox-o se/work/VirtualBox-4.3.20/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/bin/sdk/bi ndings/xpcom/include/string -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/ipcd -I/usr/local/include/SDL -I/usr/local/include -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/include -I/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/lo cal/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\ " -DPIC -DIN_RING3 -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DNDEBUG -DTRIMMED -DVBOXSDL_WITH_X11 -Wp,-MD,/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/obj/VBoxSDL/VBoxSDL.o.dep -Wp,-MT,/tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/obj/VBoxSDL/VBoxSDL.o -Wp,-MP -o /tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/out/freebsd.amd64/release/obj/VBoxSDL/VBoxSDL.o /tmp/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.20/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp *** [do-build] Error code 2 Stop in /usr/ports/emulators/virtualbox-ose. >> Cleaning up wrkdir ===> Cleaning for virtualbox-ose-4.3.20_1 build of emulators/virtualbox-ose ended at Fri Dec 5 09:37:28 CET 2014 build time: 00:29:43 !!! build failure encountered !!! So what was the error? -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: www/linux-c6-flashplugin11 broken after latest update
On 04.12.2014 18:46, Beeblebrox wrote: Hi Volodymyr. Been there, done that. I had issues with video and sound making flashplugin appear more stable. That was on Current I assume? I might still give it a try if that experience was on 10*. Nope, I'm living on -STABLE. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: www/linux-c6-flashplugin11 broken after latest update
On 04.12.2014 12:26, Beeblebrox wrote: Have you tried nspluginwrapper -r and reinstall them with -v -a -u? Yes, same result. I saw that thread as well (http://freebsd.1045724.n5.nabble.com/Does-linux-c6-flashplugin-11-2r202-406-work-under-stable-10-td5959857.html) I think I'm going to switch to emulators/pipelight - uses flash ver 14 supposedly. Been there, done that. I had issues with video and sound making flashplugin appear more stable. Looking forward for freshplugin... -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ZFS zvol support improved - VirtualBox gets unstable with it
On 13.08.2014 22:16, Adam Vande More wrote: Looking at your error msg's closer, it appear AIO might be enabled. FreeBSD, ZVOL's, and AIO have a reported incompatability: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298 Yes, that was AIO. Everything works fine without it (except for Mac OS X that still prefers VBox 4.3.6 :). -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
ZFS zvol support improved - VirtualBox gets unstable with it
Hi all.
There was a long time ago when I started to use pure zvol's as
VirtualBox disks. This way virtual machines were working faster due to
default smaller cluster size and I also can snapshot them and mount
right from the OS. Too bad this also required setting 'use host i/o
cache' at storage controller properties. Without that most guest OS
would just break or hang.
Recently 10-STABLE was shown some improvements:
1. zfs set volmode=dev
Now you can mark zvol as a dev node preventing system from touching it.
Also this makes working with zvol simpler.
2. r269429 (MFC r269123): Implement separate I/O dispatch method for
ZVOLs in "dev" mode.
After this one if you have zvol's marked as volmode=dev you can turn off
useHostIOCache for your virtual machines. And they would also work much
faster! But alas after that VirtualBox becomes unstable and your
machines can also fail on heavy IO.
Aug 13 14:00:17 limbo kernel: pid 50275 (VirtualBox), uid 1001: exited
on signal 11 (core dumped)
00:01:06.704138 NAT: DHCP offered IP address 10.0.2.15
00:01:13.352513 NAT: IPv6 not supported
00:05:10.647121 UIMediumEnumerator: Machine (or snapshot) event
received, ID = 127e4da5-ca27-41f0-bda7-23a3b76fd447
00:05:10.647313 UIMediumEnumerator: Old usage:
d85e4ed7-2c67-4947-ad91-3d37c410e047
00:05:10.649943 UIMediumEnumerator: New usage:
d85e4ed7-2c67-4947-ad91-3d37c410e047
00:05:10.650007 UIMediumEnumerator: Machine (or snapshot) event
processed, ID = 127e4da5-ca27-41f0-bda7-23a3b76fd447
^^^ No errors.
#0 0x0008020e1dad in RTLogLoggerEx (pLogger=0x811462e40, fFlags=8,
iGroup=293652128, pszFormat=0x81180c6a0 "$") at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/Runtime/common/log/logellipsis.cpp:80
80 {
#0 0x0008020e1dad in RTLogLoggerEx (pLogger=0x811462e40, fFlags=8,
iGroup=293652128, pszFormat=0x81180c6a0 "$") at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/Runtime/common/log/logellipsis.cpp:80
args = {{gp_offset = 4, fp_offset = 0, overflow_arg_area = 0x0,
reg_save_area = 0x100}}
#1 0x0008073632ef in pdmacFileAioMgrNormalReqCompleteRc
(pAioMgr=0x8141e5620, hReq=0x81180c6a0, rcReq=0, cbTransfered=0)
at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:1348
rc = 0
pEndpoint = 0x101000817ea93c0
pTask = 0x811462e40
pTasksWaiting = 0x7e9a21f0
#2 0x000807365f1c in pdmacFileAioMgrNormalReqsEnqueue
(pAioMgr=0x8141e5620, pEndpoint=0x8142000a0, pahReqs=0x7e9a2380,
cReqs=1)
at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:613
rcReq = 0
i = 0
rc = -250
#3 0x000807363f6d in pdmacFileAioMgrNormalReqCompleteRc
(pAioMgr=0x8141e5620, hReq=0x81180c6a0, rcReq=0, cbTransfered=0)
at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:1504
offStart = 9376530432
cbToTransfer = 16384
pbBuf = (uint8_t *) 0x85c2fe000 "\001"
rc = 0
pEndpoint = 0x8142000a0
pTask = 0x811462e40
pTasksWaiting = 0x7e9a2390
#4 0x000807365f1c in pdmacFileAioMgrNormalReqsEnqueue
(pAioMgr=0x8141e5620, pEndpoint=0x8142000a0, pahReqs=0x7e9a2520,
cReqs=1)
at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:613
rcReq = 0
i = 0
rc = -250
#5 0x000807363f6d in pdmacFileAioMgrNormalReqCompleteRc
(pAioMgr=0x8141e5620, hReq=0x81180c6a0, rcReq=0, cbTransfered=0)
at
/tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:1504
offStart = 9376530432
cbToTransfer = 16384
pbBuf = (uint8_t *) 0x85c2fe000 "\001"
rc = 0
pEndpoint = 0x8142000a0
pTask = 0x811462e40
pTasksWaiting = 0x7e9a2530
If anyone want's to see whole log I can grab it somewhere, it's too long.
--
Sphinx of black quartz judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: virtualbox-4.3.8 just hit ports and me with a new Guru meditation for MacOS X guests
04.03.2014 19:43, Mario Lobo wrote: Maybe this applies to your problem. https://www.virtualbox.org/pipermail/vbox-dev/2014-March/012133.html This will take time, patches are for 4.2.8 actually so they fail to apply cleanly. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
virtualbox-4.3.8 just hit ports and me with a new Guru meditation for MacOS X guests
Hi all. After updating to 4.3.8 all of my guest with MacOS X refuse to work, the major difference in logs was: 4.3.6: 00:00:03.653484 End of CPUID dump ** 00:00:03.657130 VM: Halt method global1 (5) 00:00:03.657145 HaltedGlobal1 config: cNsSpinBlockThresholdCfg=5 00:00:03.657157 Changing the VM state from 'CREATING' to 'CREATED'. 00:00:03.657613 Changing the VM state from 'CREATED' to 'LOADING'. 00:00:03.658284 SSM: File header: Format 2.0, VirtualBox Version 4.3.6 r91406, 64-bit host, cbGCPhys=8, cbGCPtr=8 00:00:03.659594 VUSB: detached 'HidKeyboard' from port 1 00:00:03.659640 VUSB: detached 'HidMouse' from port 2 00:00:03.659667 SSM: Saved state info: 00:00:03.659677 SSM: Build Type: release 00:00:03.659686 SSM: Host OS: freebsd.amd64 00:00:03.659695 SSM: OSE: true 00:00:03.659870 PCI: vga/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.659883 PCI: vga/0: 8-bit field INTERRUPT_LINE: a -> 12 00:00:03.659928 PCI: vga/0: 16-bit field COMMAND: 3 -> 7 00:00:03.660202 PCI:e1000/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660213 PCI:e1000/0: 8-bit field INTERRUPT_LINE: 9 -> 13 00:00:03.660222 PCI:e1000/0: 16-bit field COMMAND: 3 -> 16 00:00:03.660245 PCI: VMMDev/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660255 PCI: VMMDev/0: 8-bit field INTERRUPT_LINE: 5 -> 14 00:00:03.660265 PCI: VMMDev/0: 16-bit field COMMAND: 3 -> 7 00:00:03.660301 PCI: acpi/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660320 PCI: acpi/0: 16-bit field COMMAND: 1 -> 7 00:00:03.660331 PCI: ich9pcibridge/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660341 PCI: ich9pcibridge/0: 32-bit field BASE_ADDRESS_2: 100 -> 40010100 00:00:03.660351 PCI: ich9pcibridge/0: 16-bit field COMMAND: 0 -> 7 00:00:03.660361 PCI: ich9pcibridge/1: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660371 PCI: ich9pcibridge/1: 32-bit field BASE_ADDRESS_2: 10200 -> 40020200 00:00:03.660381 PCI: ich9pcibridge/1: 16-bit field COMMAND: 0 -> 7 00:00:03.660398 PCI: lpc/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660409 PCI: lpc/0: register ad: 00 -> ef 00:00:03.660418 PCI: lpc/0: register de: 00 -> be 00:00:03.660428 PCI: piix3ide/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660449 PCI: piix3ide/0: register 40: 00 -> 07 00:00:03.660459 PCI: piix3ide/0: register 41: 80 -> e3 00:00:03.660468 PCI: piix3ide/0: register 43: 80 -> c0 00:00:03.660477 PCI: piix3ide/0: register 48: 00 -> 01 00:00:03.660493 PCI: piix3ide/0: register 4a: 00 -> 01 00:00:03.660502 PCI: piix3ide/0: register 55: 04 -> 14 00:00:03.660511 PCI: ahci/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660521 PCI: ahci/0: 8-bit field INTERRUPT_LINE: 9 -> 17 00:00:03.660530 PCI: ahci/0: 16-bit field COMMAND: 3 -> 7 00:00:03.660561 PCI: ahci/0: register 86: 00 -> e0 00:00:03.660571 PCI: ahci/0: register 87: 00 -> fe 00:00:03.660580 PCI: ahci/0: register 88: 00 -> 90 00:00:03.660589 PCI: ahci/0: register 89: 00 -> 40 00:00:03.660606 PCI: usb-ohci/0: 8-bit field LATENCY_TIMER: 0 -> 40 00:00:03.660616 PCI: usb-ohci/0: 8-bit field INTERRUPT_LINE: 9 -> 17 00:00:03.660625 PCI: usb-ohci/0: 16-bit field COMMAND: 2 -> 6 00:00:03.660643 PCI: usb-ohci/0: register 86: 00 -> e0 00:00:03.660653 PCI: usb-ohci/0: register 87: 00 -> fe 00:00:03.660662 PCI: usb-ohci/0: register 88: 00 -> 91 00:00:03.660671 PCI: usb-ohci/0: register 89: 00 -> 40 00:01:09.839497 TM: cTSCTicksPerSecond=0xcab6a1c8 (3 400 966 600) fTSCVirtualized=true fTSCUseRealTSC=false (state load) 00:01:09.839737 PIT: mode=2 count=0x1 (65536) - 18.20 Hz (ch=0) (restore) 00:01:09.839755 RTC: stopped the periodic timer (restore) 00:01:09.839818 HGCM: restoring [VBoxSharedFolders] 00:01:09.839872 HGCM: restoring [VBoxGuestControlSvc] 00:01:09.839883 HGCM: restoring [VBoxGuestPropSvc] 00:01:09.839893 HGCM: restoring [VBoxSharedCrOpenGL] 00:01:09.839902 HGCM: restoring [VBoxSharedClipboard] 00:01:09.841310 Releasing keys... 00:01:09.844228 Changing the VM state from 'LOADING' to 'SUSPENDED'. 00:01:09.844380 Changing the VM state from 'SUSPENDED' to 'RESUMING'. 00:01:09.844530 Changing the VM state from 'RESUMING' to 'RUNNING'. 00:01:09.970782 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00081bdc7000 w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:10.075431 2D video acceleration is disabled. 00:01:10.220775 VUSB: attached 'HidKeyboard' to port 1 00:01:10.220872 VUSB: attached 'HidMouse' to port 2 ... 4.3.8: 00:00:01.876847 End of CPUID dump ** 00:00:01.880572 VM: Halt method global1 (5) 00:00:01.880586 HaltedGlobal1 config: cNsSpinBlockThresholdCfg=5 00:00:01.880613 Changing the VM state from 'CREATING' to 'CREATED'. 00:00:01.881064 Changing the VM state from 'CREATED' to 'POWERING_ON'. 00:00:01.881249 Changing the VM state from 'POWERING_ON' to 'RUNNING'. 00:00:01.885703 Guest Log: BIOS: VirtualBox 4.3.8 00:00:01.885836 PIT: mode=2
Re: skype 4.2.0.11 port
11.11.2013 15:45, Artyom Mirgorodskiy wrote: Please test Works for me. www/nspluginwrapper and x11/nvidia-driver fails to work due to absent /compat/linux/etc/fedora-release file. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose
03.11.2013 16:00, Konstantin Belousov wrote: On Sun, Nov 03, 2013 at 10:10:01AM +, Peter Jeremy wrote: The following reply was made to PR ports/182468; it has been noted by GNATS. From: Peter Jeremy To: Volodymyr Kostyrko Cc: bug-follo...@freebsd.org Subject: Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose Date: Sun, 3 Nov 2013 21:09:07 +1100 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2013-Nov-01 15:19:32 +0200, Volodymyr Kostyrko wrote: >Isn't it easier to map libstdc++.so.6 to gcc46/libstdc++.so.6 in=20 >/etc/libmap.conf? The libstdc++.so ABI is supposed to be backward-compatible, so, in theory, libstdc++ from gcc 4.6 should be a drop-in replacement for the libstdc++ from our base. I'll second this. When i tried this for the first time I expected a weird outcome with heavy breakage but alas everything was working as before. Nothing failed in base or in ports. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.3.0
02.11.2013 22:11, Mike C. wrote: Weird. VirtualBox is working for me on 10-STABLE (BETA2 right now I suppose). `VBoxManage list ostypes` yields a lengthy list of systems. Maybe this is something about build options? I'm building it only with DBUS GUESTADDITIONS NLS QT4 X11. Can you share your list of build options? I used the same options to compile and it and the include change, I was able to compile and install, but I still get the same problem with 4.2... I need to run "VirtualBox" with root or sudo -u myuser... Have you added your user to vboxusers group? What kind of errors you see? Is kernel module loaded? -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose
The following reply was made to PR ports/182468; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, pe...@rulingia.com Cc: Subject: Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose Date: Fri, 01 Nov 2013 15:19:32 +0200 Isn't it easier to map libstdc++.so.6 to gcc46/libstdc++.so.6 in /etc/libmap.conf? -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.3.0
20.10.2013 19:25, Bernhard Fröhlich wrote: Hi virtualbox users! Just one more thing that freaks me out a lot. I'm using host-only networking with host machine been a gateway and a firewall for all the guests. But: # rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep '\(named\|dhcp\|vboxnet\)' /etc/rc.d/named /usr/local/etc/rc.d/isc-dhcpd /usr/local/etc/rc.d/isc-dhcpd6 /usr/local/etc/rc.d/vboxnet If everything starts automatically named and dhcpd will ignore all vboxnet0 interfaces as they are actually created after they are searched. Moving NETWORKING from REQUIRE to BEFORE fixes this and doesn't have any side effects on vboxnet startup. FILESYSTEMS and ldconfig are correct, as we need to launch VBoxManage to create interfaces and bring them up. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.3.0
31.10.2013 21:06, Гуляев Гоша wrote: Thanks! Adding #include solve problem with building. But VBoxManage "any action" gets error (Exact same error with VirtualBox from ports on 10-STABLE, PR: 183085 ): VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start. uname -a: FreeBSD BSD-VBOX 10.0-BETA2 FreeBSD 10.0-BETA2 #0: Thu Oct 31 23:11:53 MSK 2013 mike@BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV amd64 I have a headless machine. My user is in vboxusers group, and vboxdrv, vboxnetadp and vboxflt loaded and dbus started. Volodymyr, can you tell please, are your VirtualBox instance works on 10-STABLE? And how it working (For example is VBoxManage list ostypes - working?). Maybe you say that it works only with existed machines and not works on any other actions? Weird. VirtualBox is working for me on 10-STABLE (BETA2 right now I suppose). `VBoxManage list ostypes` yields a lengthy list of systems. Maybe this is something about build options? I'm building it only with DBUS GUESTADDITIONS NLS QT4 X11. Can you share your list of build options? -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.3.0
31.10.2013 17:17, Гуляев Гоша wrote: /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:404:14: error: 'free' was not declared in this scope kmk: *** [/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/NetIf-freebsd.o] Error 1 Missing "#include "? ^^^ Installed fine here, Snow Leo and WinXP seems working... Yet WinXP is giving BSOD, maybe some HW changes... Tested this 10-STABLE and it works for me like a charm. The only change is that I'm building virtualbox-ose with USE_GCC=yes (picking lang/gcc from the ports). On 9-STABLE this also requires overloading libstdc++.so.6 with gcc46/libstdc++.so.6 in /etc/libmap.conf. Friends! I don't fully understand from your mails is it possible to build and use VirtualBox on FreeBSD-STABLE? I get ports from first [CFT] message, add USE_GCC=yes in /etc/make.conf (and also change USE_GCC=any to USE_GCC=yes in Makefile on emulators/virtualbox-ose), and when try to build I get errors exactly as above Is it any way to use virtualbox on -STABLE? uname -a: FreeBSD BSD-VBOX 10.0-BETA1 FreeBSD 10.0-BETA1 #0: Thu Oct 17 22:04:29 MSK 2013 mike@BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV amd64 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/VBox/com/defs.h:313:0: warning: "TRUE" redefined [enabled by default] /usr/include/rpc/types.h:61:0: note: this is the location of the previous definition kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/USBDeviceFilterImpl.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/USBProxyService.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/HostUSBDeviceImpl.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/PerformanceImpl.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/Performance.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/generic/NetIf-generic.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp: In function 'int getDVDInfoFromCAM(DriveInfoList*, bool*)': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp:254:122: warning: invalid conversion from 'int' to 'periph_pattern_flags' [-fpermissive] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp: At global scope: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp:337:12: warning: unused parameter 'isDVD' [-Wunused-parameter] kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/USBProxyServiceFreeBSD.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:40:5: warning: unused parameter 'user' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:40:5: warning: unused parameter 'kernel' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:40:5: warning: unused parameter 'idle' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:102:5: warning: unused parameter 'process' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:102:5: warning: unused parameter 'user' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:102:5: warning: unused parameter 'kernel' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:107:5: warning: unused parameter 'process' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/PerformanceFreeBSD.cpp:107:5: warning: unused parameter 'used' [-Wunused-parameter] /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-se
Re: [Call for Testers] VirtualBox 4.3.0
20.10.2013 19:25, Bernhard Fröhlich wrote:
Hi virtualbox users!
This is again a call for testers to get some feedback before we commit
VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will
still
be available as emulators/virtualbox-ose-legacy.
I optionized pulse (e.g ripped relevant part from old version):
.if ${PORT_OPTIONS:MPULSEAUDIO}
PULSEAUDIO_LIB_DEPENDS= libpulse.so:${PORTSDIR}/audio/pulseaudio
PULSEAUDIO_CONFIGURE_ENABLE= pulse
.else
CONFIGURE_ARGS+=--disable-pulse
.endif
Compilation seems to go on until:
kBuild: Compiling VBoxSVC -
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
In function 'int getDefaultIfaceIndex(short unsigned int*, int)':
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:94:39:
error: 'malloc' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:98:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:133:30:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:139:14:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
In function 'int NetIfList(std::list >&)':
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:205:39:
error: 'malloc' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:209:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:217:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:291:16:
warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:303:14:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
In function 'int NetIfGetConfigByName(PNETIFINFO)':
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:328:39:
error: 'malloc' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:332:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:340:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:404:14:
error: 'free' was not declared in this scope
kmk: ***
[/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/NetIf-freebsd.o]
Error 1
Missing "#include "?
Installed fine here, Snow Leo and WinXP seems working... Yet WinXP is
giving BSOD, maybe some HW changes...
Tested this 10-STABLE and it works for me like a charm. The only change
is that I'm building virtualbox-ose with USE_GCC=yes (picking lang/gcc
from the ports). On 9-STABLE this also requires overloading
libstdc++.so.6 with gcc46/libstdc++.so.6 in /etc/libmap.conf.
--
Sphinx of black quartz, judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.3.0
20.10.2013 19:25, Bernhard Fröhlich wrote:
Hi virtualbox users!
This is again a call for testers to get some feedback before we commit
VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will still
be available as emulators/virtualbox-ose-legacy.
I optionized pulse (e.g ripped relevant part from old version):
.if ${PORT_OPTIONS:MPULSEAUDIO}
PULSEAUDIO_LIB_DEPENDS= libpulse.so:${PORTSDIR}/audio/pulseaudio
PULSEAUDIO_CONFIGURE_ENABLE= pulse
.else
CONFIGURE_ARGS+=--disable-pulse
.endif
Compilation seems to go on until:
kBuild: Compiling VBoxSVC -
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
In function 'int getDefaultIfaceIndex(short unsigned int*, int)':
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:94:39:
error: 'malloc' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:98:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:133:30:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:139:14:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
In function 'int NetIfList(std::list >&)':
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:205:39:
error: 'malloc' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:209:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:217:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:291:16:
warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:303:14:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
In function 'int NetIfGetConfigByName(PNETIFINFO)':
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:328:39:
error: 'malloc' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:332:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:340:18:
error: 'free' was not declared in this scope
/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:404:14:
error: 'free' was not declared in this scope
kmk: ***
[/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/NetIf-freebsd.o]
Error 1
Missing "#include "?
Installed fine here, Snow Leo and WinXP seems working... Yet WinXP is
giving BSOD, maybe some HW changes...
--
Sphinx of black quartz, judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
emulators/virtualbox-ose can't work when switching to gcc46
Hello.
Just a tiny background. I'm just experimenting with getting rid of
in-base gcc and using compiler from ports whenever possible. And gcc46
produces much better code then our gcc42.
When I change USE_GCC to yes everything compiles and install perfectly.
But when I try to run VirtualBox I get this:
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed:
/usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by
/usr/local/lib/virtualbox/VBoxRT.so not found
VirtualBox: Tip! It may help to reinstall VirtualBox.
Substituting /usr/lib/libstdc++.so.6 with
/usr/local/lib/gcc46/libstdc++.so.6 fixes that and VirtualBox is fully
functional, but this looks like wrong library resolution order or what?
Can this be fixed somewhere in the port or should I brag the guys that
stay behind adopting clang? Or is this rather a problem with gcc port?
--
Sphinx of black quartz, judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
one more glitch with vboxnet: wrong rcorder
Hi all. Can we also add "BEFORE: DAEMON" to /usr/local/etc/rc.d/vboxnet? I'm working with isc-dhcpd and isc-dhcpd seem to prefer starting earlier then vboxnet omitting vboxnet0 from processing: rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /etc/rc.d/rtadvd /etc/rc.d/rwho /etc/rc.d/timed /etc/rc.d/ugidfw /etc/rc.d/yppasswdd /usr/local/etc/rc.d/isc-dhcpd /usr/local/etc/rc.d/isc-dhcpd6 /usr/local/etc/rc.d/samba /usr/local/etc/rc.d/svnserve /etc/rc.d/LOGIN /usr/local/etc/rc.d/wiki /usr/local/etc/rc.d/viewvc /usr/local/etc/rc.d/vboxnet /usr/local/etc/rc.d/vboxheadless /usr/local/etc/rc.d/dbus -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: rc.d/vboxnet fails to fully configure interface
21.01.2013 14:53, Volodymyr Kostyrko:
Hi all.
After patching rc.d/vboxnet to run VBoxManage correctly I found that it
doesn't create interface at all, as all interface specification is bound
to user running machines.
Moreover, when I checked logs written by VBoxManage from this rc script
I found:
00:00:00.152123 nspr-2 Loading settings file
"/root/.VirtualBox/VirtualBox.xml" with version "1.12-freebsd"
00:00:03.974933 nspr-2 VDInit finished
00:00:09.190551 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005)
aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox}
aText={The object is not ready}, preserve=false
Anyway I found how I can make interface working during the boot.
Duplicating interface configuration in /etc/rc.conf gives system hints
on how to complete interface initialization. Everything (named, inetd,
other daemons listening on virtual interface) now works correctly for me.
--
Sphinx of black quartz, judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
rc.d/vboxnet fails to fully configure interface
Hi all. After patching rc.d/vboxnet to run VBoxManage correctly I found that it doesn't create interface at all, as all interface specification is bound to user running machines. I had created a sample config file for VirtualBox: http://www.innotek.de/VirtualBox-settings"; version="1.12-freebsd"> name="HostOnly/vboxnet0/IPAddress" value="192.168.56.1"/> name="HostOnly/vboxnet0/IPNetMask" value="255.255.255.0"/> name="HostOnly/vboxnet0/IPV6NetMask" value="64"/> But this only results in interface been created but not configured: vboxnet0: flags=8802 metric 0 mtu 1500 ether 0a:00:27:00:00:00 nd6 options=21 media: Ethernet autoselect status: active This is very bad from a production perspective. Imagine that I want to run a number of machines on one host-only interfaces making parent host the firewall for all of them. Then no system service can start and bind to this interface prior to making it fully active. This covers at least named and isc-dhcpd as I prefer to use full fledged dhcpd server to be able to provide routing info, local dns servers and machine registration in dns. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: vboxnet fails to start fully: VBoxRT.so misses libiconv.so
19.01.2013 06:50, Craig Wiesen: On my host vboxnet says when booting: Shared object "libiconv.so.3" not found, required by "VBoxRT.so" This is possibly is because of trying to bring up host-only interfaces with VBoxManage. Maybe this is beacause we try bring them up before network, and network takes place before ldconfig? I ran into this too. Here is a patch I came up with for /usr/ports/emulators/virtualbox-ose-kmod/files/vboxnet.in It moves the /usr/local/etc/rc.d/vboxnet script execution to after networking and ldconfig paths have been set up. (as you thought) Index: vboxnet.in === --- vboxnet.in (revision 310569) +++ vboxnet.in (working copy) @@ -4,8 +4,7 @@ # # PROVIDE: vboxnet -# REQUIRE: FILESYSTEMS -# BEFORE: netif +# REQUIRE: FILESYSTEMS NETWORKING ldconfig # KEYWORD: nojail # Looks good, this also shoud fix named and isc-dhcpd startup on vboxnet\d interfaces. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
vboxnet fails to start fully: VBoxRT.so misses libiconv.so
Hi all. On my host vboxnet says when booting: Shared object "libiconv.so.3" not found, required by "VBoxRT.so" This is possibly is because of trying to bring up host-only interfaces with VBoxManage. Maybe this is beacause we try bring them up before network, and network takes place before ldconfig? -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.2.0
20.09.2012 09:02, Bernhard Fröhlich wrote: I am very glad to be able to send out a VirtualBox 4.2.0 call for testers. We've done a good job pushing many patches upstream before the release this time so our port is much smaller and easier to handle. The stability of 4.2.0 seems to be better than the past .0 releases so our plan is to commit 4.2 to the portstree as soon as FreeBSD 9.1 is out the door. Feedback from this CFT will tell us where we really are so please also report positive feedback. I found two lesser bugs with it: 1. Giving Mac OS X more then one processor can result in a core dump. 2. DMG format support doesn't work, Mac says that such image cannot be read. But when I download this image to the virtual machine or open it from them network everything works. -- Sphinx of black quartz, judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: flashplugin 11.2r202.238
01.10.2012 21:33, Jerry wrote: I just finished installing "linux-f10-flashplugin-11.2r202.238". For some inexplicable reason, it is no longer working. I followed the directions in "UPDATING" but without success. I even cleared out the entries in the "~/.mozilla/plugins" directory and reran the command without results. In fact, now nothing is listed in the directory and flash still doesn't work. Every time I reach a page that requires flash, I am greeted with a message telling me I need to download and install it. Could you please rerun nspluginwrapper -v -a -i? Is there anything in the system log? -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable
The following reply was made to PR ports/166485; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, turut...@scphys.kyoto-u.ac.jp Cc: Subject: Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable Date: Mon, 09 Apr 2012 22:19:53 +0300 Geez, I missed one thing that possibly explains this situation: Apr 8 21:43:24 limbo kernel: pid 6571 (npviewer.bin), uid 1001: exited on signal 4 (core dumped) My machine is not SSE2 capable. CPU: AMD Athlon(tm) (1750.59-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Family = 6 Model = a Stepping = 0 Features=0x383fbff AMD Features=0xc0400800 Windows version on the same machine works. It seems I should bug Adobe about that... -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable
The following reply was made to PR ports/166485; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, turut...@scphys.kyoto-u.ac.jp Cc: Subject: Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable Date: Mon, 09 Apr 2012 13:37:39 +0300 On my other desktop everything works fine. FreeBSD green.tandem.local 9.0-STABLE FreeBSD 9.0-STABLE #1 r234052: Mon Apr 9 11:22:31 EEST 2012 arcade@green.tandem.local:/usr/obj/usr/src/sys/MINIMAL amd64 -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable
The following reply was made to PR ports/166485; it has been noted by GNATS. From: Volodymyr Kostyrko To: Tsurutani Naoki Cc: bug-follo...@freebsd.org Subject: Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable Date: Mon, 09 Apr 2012 07:30:29 +0300 Tsurutani Naoki wrote: > I cannot reproduce this trouble on my host with chromium and firefox. > > h120 % uname -a > FreeBSD h120.65.226.10.32118.vlan.kuins.net 8.2-PRERELEASE FreeBSD > 8.2-PRERELEASE #25: Mon > Jan 24 10:37:18 JST 2011 > turut...@h120.65.226.10.32118.vlan.kuins.net:usr/obj/usr/src/sys/POLYMER > i386 > > Does running "nspluginwrapper -a -v -i" help it ? No, nothing changes. Installing previous version fixes things. I'll try to recheck and rebuild everything close to nspluginwrapper. However I have already checked that there are no unresolved symbols in libraries under /usr/local. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable
The following reply was made to PR ports/166485; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, turut...@scphys.kyoto-u.ac.jp Cc: Subject: Re: ports/166485: www/linux-f10-flashplugin11 is vulnerable Date: Sun, 08 Apr 2012 23:20:57 +0300 Hi all. This patch results in unusable plugin on my machine. When running flash it quickly drops with: *** NSPlugin Wrapper *** ERROR: NPP_New() wait for reply: Connection closed *** NSPlugin Wrapper *** WARNING:(/tmp/ports/usr/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2150):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection)) FreeBSD limbo.lan 9.0-STABLE FreeBSD 9.0-STABLE #0 r233753: Sun Apr 1 19:06:58 EEST 2012 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMALx32 i386 World was built with clang. Previous version worked like a charm with chromium and seamonkey, this one fails for both. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: emulators/virtualbox-ose fails to build after recent update (maybe devel/dev86 lockup)
Volodymyr Kostyrko wrote: Maybe not directly related to recent update though... # uname -a FreeBSD limbo.lan 9.0-STABLE FreeBSD 9.0-STABLE #0 r232716: Fri Mar 9 22:38:03 EET 2012 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMALx32 i386 World and ports built with clang. When building port everything stop after: kBuild: Compiling PcBiosBin - /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/obj/PcBiosBin/rombios1.s That's surely dev86 lockup. as86 hangs on i386 if compiled with clang and works if compiled with gcc46 / stock gcc. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
emulators/virtualbox-ose fails to build after recent update (maybe devel/dev86 lockup)
Maybe not directly related to recent update though... # uname -a FreeBSD limbo.lan 9.0-STABLE FreeBSD 9.0-STABLE #0 r232716: Fri Mar 9 22:38:03 EET 2012 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMALx32 i386 World and ports built with clang. When building port everything stop after: kBuild: Compiling PcBiosBin - /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/obj/PcBiosBin/rombios1.s load: 2.91 cmd: as86 21213 [runnable] 17.18r 16.10u 0.02s 53% 2136k load: 3.86 cmd: as86 21213 [runnable] 143.14r 132.38u 0.09s 91% 8980k load: 3.86 cmd: as86 21213 [runnable] 143.37r 132.60u 0.09s 91% 8980k load: 3.86 cmd: as86 21213 [runnable] 143.55r 132.77u 0.09s 91% 8980k load: 3.86 cmd: as86 21213 [runnable] 143.72r 132.93u 0.09s 91% 8980k load: 3.86 cmd: as86 21213 [runnable] 143.89r 133.09u 0.09s 91% 8980k load: 3.86 cmd: as86 21213 [runnable] 144.05r 133.24u 0.09s 91% 8980k load: 3.87 cmd: as86 21213 [runnable] 144.17r 133.35u 0.09s 91% 8980k load: 3.87 cmd: as86 21213 [runnable] 144.29r 133.46u 0.09s 91% 8980k load: 3.96 cmd: as86 21213 [runnable] 227.38r 212.50u 0.14s 93% 8980k It can sit for hours. I rebuild devel/dev86 from scratch and replaced /usr/local/bin/as86 with unstripped version. Using gcore I catched some cores of running process: (gdb) bt full #0 build_number (num=1, width=3, where=0x80587a0 "") at genlist.c:122 No locals. #1 0x0804d20a in entermac (symptr=Variable "symptr" is not available. ) at macro.c:37 param1 = Unhandled dwarf expression opcode 0x0 Current language: auto; currently minimal (gdb) bt full #0 build_number (num=1, width=3, where=0x80587a0 "") at genlist.c:122 No locals. #1 0x0804d20a in entermac (symptr=Variable "symptr" is not available. ) at macro.c:37 param1 = Unhandled dwarf expression opcode 0x0 Current language: auto; currently minimal (gdb) bt full #0 build_number (num=1, width=3, where=0x80587a0 "") at genlist.c:122 No locals. #1 0x0804d20a in entermac (symptr=Variable "symptr" is not available. ) at macro.c:37 param1 = Unhandled dwarf expression opcode 0x0 Current language: auto; currently minimal diff states that captured cores differ. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Andrey Chernov wrote:
Just in case it may help somebody: the cause (but not the root) of the
problem is found and workaround too.
The cause of the problem is
::1 localhost localhost.my.domain
line from our _standard_ /usr/src/etc/hosts which comes first before
127.0.0.1 localhost localhost.my.domain
line.
Linux takes the first match on localhost, i.e. ::1, then tries
8605 npviewer.bin STRU struct sockaddr { AF_INET6, [::1]:6010 }
it was last command from npviewer.bin, then it immeditelly terminates:
8605 npviewer.bin RET linux_socketcall -1 errno 4 Interrupted system
call
8605 npviewer.bin PSIG SIGTERM SIG_DFL code=0x10001
The workaround is to switch lines order in /etc/hosts, i.e.
127.0.0.1 localhost
::1 localhost
to make IPv4 one comes first. Flash works afterwards.
The bug affects IPv6-enabled machines with IPv4 over IPv6 preferred or
maybe IPv4 too I don't know, but since we don't have such reports in mass,
I think IPv4-only setup is fine.
Can you clarify this a bit? I have at least one machine with vanilla
/etc/hosts connected to IPv4/IPv6 network (i.e. some internal hosts
resolve to IPv6) and flash works fine there.
The DEPEND list on www/nspluginwrapper lists ftp/curl as a dependence.
And this port can be built without IPv6. Can you check your ports
configuration about enabling IPv6 support?
--
Sphinx of black quartz judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports/165215: www/linux-f10-flashplugin11 is vulnerable
ed...@freebsd.org wrote: Synopsis: www/linux-f10-flashplugin11 is vulnerable Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Thu Feb 16 23:00:34 UTC 2012 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=165215 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" Could someone take care to commit this? I already filed http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/165199 yesterday and still no move... And we have a 0-day here. http://watchguardsecuritycenter.com/2012/02/16/adobe-flash-update-plugs-zero-day-xss-hole-and-others/ -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Robert Huff wrote: > On my system, portversion did not catch the jump from Flash 9 > to Flash 11. Was this just me, or should there be an entry in > UPDATING? They are different ports. You need to switch to other one. Given the number of people who have/had trouble getting Flash to work, telling the average user that this is not covered by a common port version checking tool would be prudent. Traditionally FreeBSD ports contain more than one flash version. I don't know where this came from, maybe the previous version was left intact until Adobe/Macromedia fully moves to the next one resolving incompatibility issues or something... -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Robert Huff wrote: Am running flash successfully on 9-stable (daily rebuild). Works for me under chromium/seamonkey. Just filed a patch for the latest flash version... Works for me also. On my system, portversion did not catch the jump from Flash 9 to Flash 11. Was this just me, or should there be an entry in UPDATING? They are different ports. You need to switch to other one. You can do so with portmaster: portmaster -o www/linux-f10-flashplugin11 www/linux-flashplugin9 -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Andrey Chernov wrote:
Having 9-stable and ports from Feb 14, all builded from sources, I get
this commonly looking error attempting to view flash in FF 10.0.1:
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC
client connection
NOTE: child process received `Goodbye', closing down
Looking into ktrace I found error reason:
82037 plugin-container CALL connect(0x16,0x2c04f9d4,0x42)
82037 plugin-container STRU struct sockaddr { AF_LOCAL, invalid }
82037 plugin-container NAMI
"/tmp/_org_wrapper_NSPlugins_libflashplayer.so_82037-2_1804289383"
82037 plugin-container RET connect -1 errno 2 No such file or directory
(repeated several times).
This "invalid" in sockaddr looks familiar as for some time ago added
sockaddr length checks our kernel, but as bz@ says this should be
already fixed.
Does anybody runs flash successfly on 9-stable? If yes, where else the
problem can be?
Am running flash successfully on 9-stable (daily rebuild). Works for me
under chromium/seamonkey.
Just filed a patch for the latest flash version... Works for me also.
--
Sphinx of black quartz judge my vow.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: FreeBSD 9.0 on VirtualBox 4.1.8
Robert Simmons wrote: I encountered a problem installing FreeBSD 9.0-RELEASE on VirtualBox 4.1.8, and I wanted to share my fix for it, so it can be added to the FreeBSD wiki and Handbook if appropriate. The following checkbox needs to be checked in settings to be able to boot FreeBSD: Settings> System> Motherboard> Enable IO APIC You will not be able to boot any amd64 system without enabling IO APIC. That's said in VirtualBox manual. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox blueports repository moved to redports.org
20.12.2011 14:42, Bernhard Froehlich wrote: Hi VirtualBox Testers! Why vboxnet0 interface is created only when some virtual machine is started? This way isc-dhcpd fails to pickup interface at machine boot. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: emulators/virtualbox-ose 4.1.2
09.09.2011 01:19, Kevin Oberman wrote: Just to be sure, did you re-build VirtualBox and, more importantly virtualbox-ose-kmod on 9.0? Any kernel modules installed from ports must be re-built after a major kernel change and might need to be re-built after any new kernel is installed. The nvidia-driver is especially sensitive. Yes. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
emulators/virtualbox-ose 4.1.2
Hi all. For a start I want to apologize for been too late for test start, I was moving to 9.0 and having fun fixing things. When I was on 8-STABLE VirtualBox just hanged my machine completely. Right now starting that machine on BETA2 results in: > VBoxSDL -s 7 Oracle VM VirtualBox SDL GUI version 4.1.2_OSE (C) 2005-2011 Oracle Corporation All rights reserved. Type Manifest File: /home/arcade/.VirtualBox/xpti.dat nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) ###!!! ASSERTION: failed to deserialize/set exception: 'NS_SUCCEEDED(rv)', file /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.2_OSE/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2709 Break: at file /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.2_OSE/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2709 ###!!! ASSERTION: failed to deserialize/set exception: 'NS_SUCCEEDED(rv)', file /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.2_OSE/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2709 Break: at file /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.2_OSE/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2709 ###!!! ASSERTION: failed to deserialize/set exception: 'NS_SUCCEEDED(rv)', file /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.2_OSE/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2709 Break: at file /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.2_OSE/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2709 And it stucks until killed with ^C. FreeBSD limbo.lan 9.0-BETA2 FreeBSD 9.0-BETA2 #0: Wed Sep 7 14:59:59 EEST 2011 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMAL i386 -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
virtualbox: vboxnet0 not found
Hi again. I've tried to use vboxnet0 (Host only networking) and I really like it. I like it better then bridged because it's much more configurable. Too bad vboxnet0 interface is not created at start. I can't bind isc-dhcpd to it or make a bridged configuration. I need to run machine and only then I can manage that interface. Can this be done in any other way? -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [ports-i...@freebsd.org: linux-f10-flashplugin-10.3r181.34 failed on i386 9]
11.08.2011 22:20, Martin Simmons wrote: On Wed, 10 Aug 2011 23:20:04 +0300, Volodymyr Kostyrko said: PS: As far as I understand the main problem is about mirroring correct player versions. Anyone (even me) can apply for a redistribution rights and make those files available for download the way we want (the way each version will have unique url). Wouldn't that be dangerous, because it would allow easy use of old versions that contain critical vulnerabilities? This applies to any vulnerable package like apache or png. We already have means of dealing with this like ports updating and vuxml. I'm talking about stability here. Adobe silently shipped another version and our port become unbuildable because distfile wasn't available anymore. Making up mirror with archive versions saves us the time when port wasn't updated yet but we have no directions of retrieving old verified distfile. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [ports-i...@freebsd.org: linux-f10-flashplugin-10.3r181.34 failed on i386 9]
10.08.2011 09:08, Erwin Lansing wrote: FYI; can you please investigate and/or report to the developers? If you are already aware of this problem but do not yet have a fix, please mark the port BROKEN in the appropriate case, so that users do not unexpectedly encounter it. See http://pointyhat.freebsd.org for the full log. Thanks, -erwin The distfile on the adobe server was updated to the more recent version. The local distfile mirror misses correct file version. The port should be updated with newer file size/hashsum. PS: As far as I understand the main problem is about mirroring correct player versions. Anyone (even me) can apply for a redistribution rights and make those files available for download the way we want (the way each version will have unique url). https://www.adobe.com/cfusion/mmform/index.cfm?name=distribution_form&pv=fp -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: firefox and chrome both fail to play certain flash clips
09.08.2011 02:31, Yuri написав(ла): Here is an example: http://www.stansberryresearch.com/pro/1011PSIENDVD/WPSIM800/PR Place where flash should be blinks and turns white after this in both browsers. linux-f10-flashplugin-10.3r181.34 nspluginwrapper-1.4.4 Current Ubuntu has no problem with this clip. Works for me, RELENG_8 i386, 10.3.185 -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
07.08.2011 15:18, Bernhard Froehlich написав(ла): Another VirtualBox major release is available since a few weeks and we are proud to provide you a call for testers now. We had very good results during the beta phase so we hope that it will be ready to be committed quite soon. But it all depends on the feedback we get. This VirtualBox release only supports FreeBSD>= 8.0 as host system. If you think you really need FreeBSD 7.x support please get in contact with us. We also want to point out that GNS3 support has been added in VirtualBox 4.1.0 and should be working with our emulators/gns3 port but needs the UDPTUNNEL option to be enabled. I've been hit bu Guru Meditation. The log leftover is at http://limbo.xim.bz/guru.meditation.4.1.0.txt I'm puzzled with this one, switching from bridged to nat shows the same GM. Nothing with accelerate3d or usb too. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
virtualbox one more crash
Hi all. I just like all that crashes... > VBoxHeadless -s 7_0 -n -m 18083 Oracle VM VirtualBox Headless Interface 4.0.12_OSE (C) 2008-2011 Oracle Corporation All rights reserved. Type Manifest File: /home/arcade/.VirtualBox/xpti.dat nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) 19/07/2011 12:54:37 Listening for VNC connections on TCP port 18083 Set framebuffer: buffer=803c04000 w=800 h=600 bpp=32 !!Assertion Failed!! Expression: Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/CFGM.cpp(133) int CFGMR3Init(VM*, int (*)(VM*, void*), void*) Constructor failed with rc=VERR_NOT_FOUND pfnCFGMConstructor=000802cfd6f0 Trace/BPT trap Machine log contains this: 00:00:00.158 VMSetError: /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/src-client/ConsoleImpl2.cpp(2099) int Console::configConstructorInner(VM*, util::AutoWriteLock*); rc=VERR_NOT_FOUND 00:00:00.158 VMSetError: Implementation of the USB 2.0 controller not found! 00:00:00.158 Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings 00:00:00.160 00:00:00.160 !!Assertion Failed!! 00:00:00.160 Expression: 00:00:00.160 Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/CFGM.cpp(133) int CFGMR3Init(VM*, int (*)(VM*, void*), void*) 00:00:00.160 Constructor failed with rc=VERR_NOT_FOUND pfnCFGMConstructor=000802cfd6f0 If I disable --usbehci everything seem to work fine. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
another virtualbox crash
Hi all. I was little unprepaired... This one crashed just after another machine was taken off the same way. > VBoxManage controlvm xp_1 savestate Type Manifest File: /home/arcade/.VirtualBox/xpti.dat nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) !!Assertion Failed!! Expression: aI Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/Main/glue/ErrorInfo.cpp(193) void com::ErrorInfo::init(nsISupports*, const nsID&, bool) Trace/BPT trap(записано core) The machine logs ends up with: 141:26:50.250 NAT: DHCP offered IP address 10.0.2.15 141:27:53.190 NAT: DHCP offered IP address 10.0.2.15 141:29:11.296 NAT: DHCP offered IP address 10.0.2.15 144:45:38.511 Guest Additions capability report: (0x5) seamless: yes, hostWindowMapping: no, graphics: yes 144:45:38.566 Guest Additions capability report: (0x5) seamless: yes, hostWindowMapping: no, graphics: yes 144:54:46.990 NAT: DHCP offered IP address 10.0.2.15 146:21:28.685 Changing the VM state from 'RUNNING' to 'SUSPENDING'. 146:21:29.041 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'. 146:21:29.059 146:21:29.059 !!Assertion Failed!! 146:21:29.059 Expression: pVM->tm.s.cVirtualTicking 146:21:29.059 Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/VMM/VMMAl/TMAllVirtual.cpp(609) uint64_t tmVirtualSyncGetEx(VM*, bool, uint64_t*) I can give full logs, but testing or dumping core will be no more - the machine is already updated to 4.0.12. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports: emulators/virtualbox-ose --pagefusion
13.07.2011 13:07, Bernhard Froehlich wrote: !!Assertion Failed!! Expression: RT_SUCCESS_NP(rc) Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/VMM/VMMR3/PGMSharedPage.cpp(207) VBOXSTRICTRC pgmR3SharedModuleRegRendezvous(VM*, VMCPU*, void*) VERR_PGM_PHYS_INVALID_PAGE_ID (-1637) - Trying to free a page with an invalid Page ID. Trace/BPT trap I just talked to the vbox developers and they told me this is a known problem that you should also see with other hosts but it's hard to reproduce. Do you have multiple VMs running with page fusion enabled when the error occurs? Yep, 4. 1. XPx32 PageFusion OFF. 2. XPx32 PageFusion ON. 3. 2003x32 PageFusion OFF. 4. 2003x32 PageFusion ON. Those with PageFusion OFF are old production machines with pre-vbox4 settings. Other two are test machines intended for replacement of legacy ones. Please send the VBox.log (should be in $HOME/VirtualBox VMs//logs/VBox.log) of your failed session for further debugging. There's almost nothing there. I have published this one and a debug log at http://limbo.xim.bz/pagefusion/ If you need a `bt full` you're welcome, I just haven't enabled dumping core for those session but it's quite reproducible for me. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
ports: emulation/virtualbox-ose
Hi all. > VBoxHeadless -s xp_0 -n -m 18084 Oracle VM VirtualBox Headless Interface 4.0.10_OSE (C) 2008-2011 Oracle Corporation All rights reserved. Type Manifest File: /home/arcade/.VirtualBox/xpti.dat nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) 13/07/2011 11:06:47 Listening for VNC connections on TCP port 18084 Set framebuffer: buffer=803c04000 w=800 h=600 bpp=32 Set framebuffer: buffer=80ce47000 w=720 h=400 bpp=32 13/07/2011 11:06:50 Got connection from client 10.5.100.44 13/07/2011 11:06:50 other clients: 13/07/2011 11:06:50 Client Protocol Version 3.8 13/07/2011 11:06:50 Protocol version sent 3.8, using 3.8 13/07/2011 11:06:50 rfbProcessClientSecurityType: executing handler for type 1 13/07/2011 11:06:50 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 13/07/2011 11:06:50 Pixel format for client 10.5.100.44: 13/07/2011 11:06:50 8 bpp, depth 8 13/07/2011 11:06:50 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 13/07/2011 11:06:50 rfbProcessClientNormalMessage: ignoring unsupported encoding type ultraZip 13/07/2011 11:06:50 Using compression level 9 for client 10.5.100.44 13/07/2011 11:06:50 Using image quality level 0 for client 10.5.100.44 13/07/2011 11:06:50 Enabling KeyboardLedState protocol extension for client 10.5.100.44 13/07/2011 11:06:50 Enabling NewFBSize protocol extension for client 10.5.100.44 13/07/2011 11:06:50 Enabling LastRect protocol extension for client 10.5.100.44 13/07/2011 11:06:50 Enabling SupportedMessages protocol extension for client 10.5.100.44 13/07/2011 11:06:50 Enabling SupportedEncodings protocol extension for client 10.5.100.44 13/07/2011 11:06:50 Enabling ServerIdentity protocol extension for client 10.5.100.44 13/07/2011 11:06:50 Using tight encoding for client 10.5.100.44 Set framebuffer: buffer=80da04000 w=640 h=480 bpp=32 13/07/2011 11:06:51 Sending rfbEncodingNewFBSize for resize to (640x480) Set framebuffer: buffer=80ce47000 w=720 h=400 bpp=32 13/07/2011 11:07:04 Sending rfbEncodingNewFBSize for resize to (720x400) Set framebuffer: buffer=80dc04000 w=640 h=480 bpp=32 13/07/2011 11:07:04 Sending rfbEncodingNewFBSize for resize to (640x480) !!Assertion Failed!! Expression: i < 0 Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/Devices/USB/DevOHCI.cpp(1695) bool ohci_in_done_queue_check(OHCI*, uint32_t) TD 0x02210080 (i=1) Trace/BPT trap The machine has only: Pointing Device: USB Tablet Keyboard Device: USB Keyboard I personally think USB support is not mature enough for stable use. -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
ports: emulators/virtualbox-ose --pagefusion
Hi all. > VBoxHeadless -s xp_0 -n -m 18084 Oracle VM VirtualBox Headless Interface 4.0.10_OSE (C) 2008-2011 Oracle Corporation All rights reserved. Type Manifest File: /home/arcade/.VirtualBox/xpti.dat nsNativeComponentLoader: autoregistering begins. nsNativeComponentLoader: autoregistering succeeded nNCL: registering deferred (0) 13/07/2011 11:18:27 Listening for VNC connections on TCP port 18084 Set framebuffer: buffer=803c04000 w=800 h=600 bpp=32 Set framebuffer: buffer=80d20f000 w=720 h=400 bpp=32 Set framebuffer: buffer=80da04000 w=640 h=480 bpp=32 13/07/2011 11:18:31 Got connection from client 10.5.100.44 13/07/2011 11:18:31 other clients: 13/07/2011 11:18:31 Client Protocol Version 3.8 13/07/2011 11:18:31 Protocol version sent 3.8, using 3.8 13/07/2011 11:18:31 rfbProcessClientSecurityType: executing handler for type 1 13/07/2011 11:18:31 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 13/07/2011 11:18:31 Pixel format for client 10.5.100.44: 13/07/2011 11:18:31 8 bpp, depth 8 13/07/2011 11:18:31 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 13/07/2011 11:18:31 rfbProcessClientNormalMessage: ignoring unsupported encoding type ultraZip 13/07/2011 11:18:31 Using compression level 9 for client 10.5.100.44 13/07/2011 11:18:31 Using image quality level 0 for client 10.5.100.44 13/07/2011 11:18:31 Enabling KeyboardLedState protocol extension for client 10.5.100.44 13/07/2011 11:18:31 Enabling NewFBSize protocol extension for client 10.5.100.44 13/07/2011 11:18:31 Enabling LastRect protocol extension for client 10.5.100.44 13/07/2011 11:18:31 Enabling SupportedMessages protocol extension for client 10.5.100.44 13/07/2011 11:18:31 Enabling SupportedEncodings protocol extension for client 10.5.100.44 13/07/2011 11:18:31 Enabling ServerIdentity protocol extension for client 10.5.100.44 13/07/2011 11:18:31 Using tight encoding for client 10.5.100.44 Set framebuffer: buffer=80d20f000 w=720 h=400 bpp=32 13/07/2011 11:18:43 Sending rfbEncodingNewFBSize for resize to (720x400) Set framebuffer: buffer=80dc04000 w=640 h=480 bpp=32 13/07/2011 11:18:43 Sending rfbEncodingNewFBSize for resize to (640x480) Set framebuffer: buffer=807c0 w=1024 h=768 bpp=32 13/07/2011 11:19:23 Sending rfbEncodingNewFBSize for resize to (1024x768) !!Assertion Failed!! Expression: RT_SUCCESS_NP(rc) Location : /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/VMM/VMMR3/PGMSharedPage.cpp(207) VBOXSTRICTRC pgmR3SharedModuleRegRendezvous(VM*, VMCPU*, void*) VERR_PGM_PHYS_INVALID_PAGE_ID (-1637) - Trying to free a page with an invalid Page ID. Trace/BPT trap -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
22.04.2011 14:01, Bernhard Froehlich wrote: It's about two months since the last call for testers and a lot of bugfixing has happened since then. Not all of the reported problems were FreeBSD related which is a good indication that we're not too far behind the stability of the other hosts. So let's get it one once again. Some more questions. 1. Should any problems with guest systems be reported? Something like "DragonflyBSD doesn't correctly detect CD-ROM"? 2. When I have stuck process (using 0% cpu / using 100% cpu) what is a correct way to report it? ktrace(1)? gcore(1)? 3. I see that my working machines after correct guest shutdown ends up throwing 'Segmantation fault'. Should I report that too? -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
28.04.2011 13:35, Bernhard Froehlich wrote: Thanks i've added it to our list and will report back when I have some news. http://wiki.freebsd.org/VirtualBox/ToDo from Alexander Eichner: The problem is that the syscall to queue aio requests fails but no request has an error code. It could be possible that aio and zfs has some bug. As a workaround you can enable the host I/O cache of the storage controller for the VM or unload the aio kernel module on the host. Thanks, --hostiocache on works and machine proceeds further. Next try: !!Assertion Failed!! Expression: pDev->enmState == VUSB_DEVICE_STATE_RESET Location : /tmp/ports/home/arcade/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.6_OSE/src/VBox/Devices/USB/VUSBDevice.cpp(1229) void vusbDevResetDone(VUSBDEV*, int, void (*)(VUSBIDEVICE*, int, void*), void*) Trace/BPT trap (core dumped) Same machine as in part one, Windows 7 Beta x64 (this matters! - x32 works). Steps to produce: Some time after reboot and installation of VB guest tools machine gets 100% CPU. VBoxManage controlvm test reset Machine tries to boot, but waits forever on the flashing flag logo. VBoxManage controlvm test reset And we have a coredump. http://limbo.xim.bz/core3.bt.full.xz -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
22.04.2011 14:01, Bernhard Froehlich wrote: As I understand reporting bugs is good? uname -a FreeBSD flashk0.3501.lan 8.2-STABLE FreeBSD 8.2-STABLE #2: Mon Apr 25 21:50:44 UTC 2011 arc...@flashk0.3501.lan:/usr/obj/usr/src/sys/MINIMAL amd64 Session transcript: VBoxManage createvm --name test --register VBoxManage modifyvm test --ostype Windows7_64 --memory 512 --pagefusion on --vram 32 --acpi on --ioapic on --pae on --hpet on --hwvirtex on --hwvirtexexcl on --nestedpaging on --largepages on --accelerate3d on --accelerate2dvideo on --chipset ich9 --nic1 nat --nictype1 Am79C970A --mouse usbtablet --keyboard usb --audio oss --audiocontroller hda --usb on --usbehci on VBoxManage storagectl test --add sata --name SATA VBoxManage storageattach test --storagectl SATA --port 1 --device 0 --type dvddrive --medium win7_7100_x64.iso # zfs create -s -o compression=on -V 20G flashk0/vbox_test VBoxManage internalcommands createrawvmdk -filename VirtualBox\ VMs/test/test.vmdk -rawdisk /dev/zvol/flashk0/vbox_test VBoxManage storageattach test --storagectl SATA --port 0 --device 0 --type hdd --medium VirtualBox\ VMs/test/test.vmdk VBoxHeadless -s test -n -m 18083 And it dumps core on signal 11. Full bt available at http://limbo.xim.bz/core.bt.full.xz What am I missing here? -- Sphinx of black quartz judge my vow. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
