Re: Call for Testers: VirtualBox 4.0.6
On Mon, 09 May 2011 07:30:41 -0700 Kevin Oberman ober...@es.net wrote: 4.0.6 is still not as robust for me as 3.2.12, but it's now close and the added features still make it a win for me. I have not had an actual crash with 4.0.6, but I have had VMs simply deadlock. Does 4.0.x bring support for USB devices? I hope I might get my scanner working with VueScan which is not possible via Linux-emulation. Will there be a 4.0.x port for 9.0 soon? Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature
Re: Call for Testers: VirtualBox 4.0.6
On Fri, 20 May 2011 09:58:35 +0200, Gour-Gadadhara Dasa wrote: On Mon, 09 May 2011 07:30:41 -0700 Kevin Oberman ober...@es.net wrote: 4.0.6 is still not as robust for me as 3.2.12, but it's now close and the added features still make it a win for me. I have not had an actual crash with 4.0.6, but I have had VMs simply deadlock. Does 4.0.x bring support for USB devices? Yes, but from the reports that we got I assume it only works with Windows XP guests right now. There are some bugs to fix. I hope I might get my scanner working with VueScan which is not possible via Linux-emulation. Will there be a 4.0.x port for 9.0 soon? Yes, hopefully pretty soon. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
http://www.virtualbox.org/wiki/Changelog 4.0.8 just released -- View this message in context: http://freebsd.1045724.n5.nabble.com/Call-for-Testers-VirtualBox-4-0-6-tp4332763p4402785.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
Cool =) Thanks! 2011/5/17 Bernhard Froehlich de...@bluelife.at: On Mon, 16 May 2011 23:45:08 -0700 (PDT), timp wrote: http://www.virtualbox.org/wiki/Changelog 4.0.8 just released Don't you think we know that? http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1316 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Mon, 16 May 2011 23:45:08 -0700 (PDT), timp wrote: http://www.virtualbox.org/wiki/Changelog 4.0.8 just released Don't you think we know that? http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1316 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Tue, May 17, 2011 at 10:34:44AM +0200, Bernhard Froehlich wrote: On Mon, 16 May 2011 23:45:08 -0700 (PDT), timp wrote: http://www.virtualbox.org/wiki/Changelog 4.0.8 just released Don't you think we know that? http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1316 Will this enter the ports tree soon? -- Denny Lin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Tue, 17 May 2011 22:31:56 +0800, Denny Lin wrote: On Tue, May 17, 2011 at 10:34:44AM +0200, Bernhard Froehlich wrote: On Mon, 16 May 2011 23:45:08 -0700 (PDT), timp wrote: http://www.virtualbox.org/wiki/Changelog 4.0.8 just released Don't you think we know that? http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1316 Will this enter the ports tree soon? Yes, that's the plan. We're currently waiting for a repocopy to finish which will take at least a few more days and hope that 4.0.8 is not regressing too much. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156843 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
I think 4.0.6 is quite stable now. Is it really less stable than the current version in ports 3.2.12? Why don't you at least put them into ports/emulators repository with -devel suffix like many other ports do? So that there is no need to go through the third party repository. Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Mon, 09 May 2011 05:57:05 -0700, Yuri wrote: I think 4.0.6 is quite stable now. Is it really less stable than the current version in ports 3.2.12? There are a few regressions also in 4.0.6 but it's already a lot better than 4.0.4. We have already decided last week to update the ports to 4.0.6 soon (currently waiting for a repocopy). Why don't you at least put them into ports/emulators repository with -devel suffix like many other ports do? So that there is no need to go through the third party repository. Throwing another -devel port in the won't solve anything! In fact it would even make the situation much worse because it trains people to use beta software which we strongly discourage and causes even more error reports and debugging headaches for another version that we would have to maintain. We have that 3rd party repository because it is our working repository. You should not use it at all if you don't want to be a beta tester and work with us to solve specific problems. If you use them for regular systems you are clearly doing something wrong except you have done a _lot_ of testing. We know that the situation is not perfect and we have already taken a few actions to improve it but if that is still not enough to you we need more people and a bigger team to test earlier, more and faster. Read here: http://lists.freebsd.org/pipermail/freebsd-emulation/2011-April/008633.html -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
Date: Mon, 09 May 2011 05:57:05 -0700 From: Yuri y...@rawbw.com Sender: owner-freebsd-emulat...@freebsd.org I think 4.0.6 is quite stable now. Is it really less stable than the current version in ports 3.2.12? Why don't you at least put them into ports/emulators repository with -devel suffix like many other ports do? So that there is no need to go through the third party repository. 4.0.6 is still not as robust for me as 3.2.12, but it's now close and the added features still make it a win for me. I have not had an actual crash with 4.0.6, but I have had VMs simply deadlock. The problems I have seen are all upstream, not FreeBSD specific. I see the same issues when I use my Ubuntu VM running on Windows7. 4.0.6 is MUCH more stable than 4.0.4. I think it's reasonable to update the port. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Wed, Apr 27, 2011 at 3:28 PM, Ryan Stone ryst...@gmail.com wrote: (Sorry for the noise earlier about the PBIs not working under PC-BSD; I'm not sure how I missed that had been already reported). I tried the new amd64 PBI and I am able to successfully start VMs now. I had one VM(running some relatively recent version of amd64 HEAD) boot up fine, but a second one (also running amd64 HEAD, but maybe a different svn revision) gets a Guru Meditation during startup. I'm not sure what is causing the crash. In their original configurations the working VM booted off of an emulated IDE disk while the broken VM booted of an emulated SATA disk, however I just tried changing the SATA disk to instead be an IDE disk and it doesn't seems to have resolved the problem. I'm not getting a corefile for the crash(or I'm unable to find it). I do have kern.sugid_coredump=1 and I'm running the PBI. Is this expected for a Guru Meditation, or should it be putting a core somewhere? I've put the VBox.log for the most recent crash here: http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log This seems to be easy to reproduce so let me know if there's any more information that I can gather. Also, the working VM was emulating uniprocessor machine. I tried adding a second CPU and that VM started crashing, too. I tried changing the broken VM to have only one core but it still crashes. I'm not sure if it's related to the first crash or not. To follow up, I tried playing around with the working VM configuration. I can only make it fail if I emulate a machine with multiple processors and I leave SMP enabled in the kernel. If I either emulate a uniprocessor machine or disable SMP via tunable, the VM is able to boot without crashing. To summarize, I believe that I am running into two separate issues with VirtualBox 4.0.6: - Booting off of an emulated SATA drive leads to crashes during boot: http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log (Guru Meditation -4001 (VERR_VMX_INVALID_VMCS_PTR) ) - Booting a VM with multiple virtual processors on a kernel with SMP enabled crashes during boot: http://people.freebsd.org/~rstone/vbox-4.0.6/VBox-SMP.log (Guru Meditation -4002 (VERR_VMX_INVALID_VMXON_PTR)) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On 22/04/2011 13: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. Last time I asked for some help and Baptiste Daroussin (bapt@) made the classic mistake to respond. So all please welcome bapt to the FreeBSD Vbox Team! This is also the first time that we provide FreeBSD binary packages. They are build for FreeBSD 7.4 and 8.2 on i386 and amd64 platform and have the DEBUG option enabled. If you use a STABLE kernel you can use the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary package but have to compile the kernel module port for your kernel yourself. (emulators/virtualbox-ose-kmod) PBIs for PC-BSD are currently worked on and will hopefully be available in a few days. What has happened since the last cft: - VirtualBox update to 4.0.6 - phpvirtualbox updated to 4.0-5 - VIMAGE support added - vboxheadless startscript added - vboxwebsrv rc startscript fixes - Build fixed with LOCALBASE != PREFIX - Documentation of USB configuration (see pkg-message or Wiki) Thanks to all people that have contributed to that release and also reported problems for the last cft. We really appreciate that! Changes in the port: http://svn.bluelife.at/index.cgi/blueports/log/emulators Changelog for 4.0.6: http://www.virtualbox.org/wiki/Changelog FreeBSD specific configuration: http://wiki.freebsd.org/VirtualBox Todo List: http://wiki.freebsd.org/VirtualBox/ToDo Ports: http://home.bluelife.at/ports/virtualbox-cft-20110421.tar.gz FreeBSD 8.2/amd64 packages: virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz FreeBSD 8.2/i386 packages: virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz FreeBSD 7.4/amd64 packages: virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz FreeBSD 7.4/i386 packages: virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz Checksums: SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-amd64.tbz) = d7bdad02d2a04dd9dc3f12cc3ee002ce3bfc196b SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-i386.tbz) = e3023f5117fd15e918cba749d1ace2b7366bdc88 SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-amd64.tbz) = bd2785ac54e8363d217e35433d942ccae8bb7ffd SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-i386.tbz) = f6c437febf60828218cb42d7bfab8b536ecb7301 SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz) = 31bbe5ff1e8d9b14dbd64c5d1f964fb702efda9e SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz) = 019955d07293f25421a0ca49d67975c165ee3e85 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz) = e56736714e01dbe693515ed89e239337c7df77d3 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz) = 8f59294036b2f1ef407849f874139a80b6aabbcb SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz) = cc7e72fdcf0e2cd0bcd21bb152ffa8b1b1adcaae SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz) = be14e942cd2b426007b2d9a395cc65843340970d SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz) = d5be908e99f9dfc4f7a1efe1570b67ad2d6b8d27 SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz) = 2627acdb5ea9008bfa6ac6c2f452d6b883cfa40e SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz) = e846f4a94bf14d0a50d3deab0ae325da25e79448 SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz) = 68144054e11bebe21fcb2b19e99cb33cead6f25b SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz) = 7f08351028f18a3d76ed8c57aba525b11b47ee9a SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz) = 6e9bbfe0a2b19985b556e739f02f02a86ef873dd Mirrors: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/ (master) http://files.etoilebsd.net/vbox/4.0.6/ Thanks and good luck, Bernhard, on behalf of the FreeBSD Vbox Team It works like a charm, please import it as emulators/virtualbox-ose update! Cheers, -- David Demelier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Friday 22 April 2011 07:01 am, 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.
Last time I asked for some help and Baptiste Daroussin (bapt@) made
the classic mistake to respond. So all please welcome bapt to the
FreeBSD Vbox Team!
This is also the first time that we provide FreeBSD binary
packages. They are build for FreeBSD 7.4 and 8.2 on i386 and amd64
platform and have the DEBUG option enabled. If you use a STABLE
kernel you can use the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary
package but have to compile the kernel module port for your kernel
yourself.
(emulators/virtualbox-ose-kmod)
For very long time, I had a serious performance/timer issues with
VirtualBox where TSC is not constant and timecounter hardware is not
TSC. Today, I finally found a workaround (please see the attached
patch). With this patch, TSC frequency is quite reasonable now.
Basically, we were using nano(up)time(9) and they were too expensive
for VirtualBox timekeeping. I believe it is okay to use
getnano(up)time(9) here because a) VirtualBox already assumes these
calls do not return accurate time (unless high-res timer is
available, i.e., Linux) and b) we already report timer granularity is
equal to kern.hz via RTTimerGetSystemGranularity(). Any thoughts?
Thanks for your hard work!
Jung-uk Kim
--- src/VBox/Runtime/r0drv/freebsd/time-r0drv-freebsd.c.orig2011-04-21
06:31:45.0 -0400
+++ src/VBox/Runtime/r0drv/freebsd/time-r0drv-freebsd.c 2011-04-29
18:57:26.0 -0400
@@ -41,7 +41,7 @@
RTDECL(uint64_t) RTTimeNanoTS(void)
{
struct timespec tsp;
-nanouptime(tsp);
+getnanouptime(tsp);
return tsp.tv_sec * UINT64_C(10)
+ tsp.tv_nsec;
}
@@ -68,6 +68,6 @@ RTDECL(uint64_t) RTTimeSystemMilliTS(voi
RTDECL(PRTTIMESPEC) RTTimeNow(PRTTIMESPEC pTime)
{
struct timespec tsp;
-nanotime(tsp);
+getnanotime(tsp);
return RTTimeSpecSetTimespec(pTime, tsp);
}
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
(Sorry for the noise earlier about the PBIs not working under PC-BSD; I'm not sure how I missed that had been already reported). I tried the new amd64 PBI and I am able to successfully start VMs now. I had one VM(running some relatively recent version of amd64 HEAD) boot up fine, but a second one (also running amd64 HEAD, but maybe a different svn revision) gets a Guru Meditation during startup. I'm not sure what is causing the crash. In their original configurations the working VM booted off of an emulated IDE disk while the broken VM booted of an emulated SATA disk, however I just tried changing the SATA disk to instead be an IDE disk and it doesn't seems to have resolved the problem. I'm not getting a corefile for the crash(or I'm unable to find it). I do have kern.sugid_coredump=1 and I'm running the PBI. Is this expected for a Guru Meditation, or should it be putting a core somewhere? I've put the VBox.log for the most recent crash here: http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log This seems to be easy to reproduce so let me know if there's any more information that I can gather. Also, the working VM was emulating uniprocessor machine. I tried adding a second CPU and that VM started crashing, too. I tried changing the broken VM to have only one core but it still crashes. I'm not sure if it's related to the first crash or not. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Wed, 27 Apr 2011 15:28:11 -0400, Ryan Stone wrote:
(Sorry for the noise earlier about the PBIs not working under PC-BSD;
I'm not sure how I missed that had been already reported).
I tried the new amd64 PBI and I am able to successfully start VMs now.
I had one VM(running some relatively recent version of amd64 HEAD)
boot up fine, but a second one (also running amd64 HEAD, but maybe a
different svn revision) gets a Guru Meditation during startup. I'm
not sure what is causing the crash. In their original configurations
the working VM booted off of an emulated IDE disk while the broken VM
booted of an emulated SATA disk, however I just tried changing the
SATA disk to instead be an IDE disk and it doesn't seems to have
resolved the problem.
I'm not getting a corefile for the crash(or I'm unable to find it). I
do have kern.sugid_coredump=1 and I'm running the PBI. Is this
expected for a Guru Meditation, or should it be putting a core
somewhere? I've put the VBox.log for the most recent crash here:
No, that looks fine.
http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log
This seems to be easy to reproduce so let me know if there's any more
information that I can gather.
I've added it to the Todo list for 4.0.6 and will report it to the vbox
developers tomorrow. Sorry, don't have a clue what is going wrong there
- but i'm sure they know.
http://wiki.freebsd.org/VirtualBox/ToDo
Also, the working VM was emulating uniprocessor machine. I tried
adding a second CPU and that VM started crashing, too. I tried
changing the broken VM to have only one core but it still crashes.
I'm not sure if it's related to the first crash or not.
Look at the relevant parts of VBox.log and see if they look about the
same.
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current pointer
vs 84362000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current VMCS version e
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Entered Cpu 3
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current Cpu 2
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current pointer
vs 84365000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current VMCS version 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Entered Cpu 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current Cpu 0
00:00:08.374
!!
00:00:08.374 !!
00:00:08.374 !! Guru Meditation -4001
(VERR_VMX_INVALID_VMCS_PTR)
00:00:08.374 !!
00:00:08.374 !!
00:00:08.374 !! {mappings, NULL}
00:00:08.374 !!
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Fri, Apr 22, 2011 at 6:01 AM, Bernhard Froehlich de...@freebsd.orgwrote: 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. Probably not a FreeBSD specific issue, but my legacy XP VM had an issue. When viewing the Settings screen, a warning came up saying invalid VM name. Checking that field revealed a blank name. Reentering the correct one allowed me to proceed with settings changes, but after closing and reopening the main Vbox GUI, then Settings tab again the VM name was again blank. I then created a new XP VM with an identical name which took. At first this seemed odd, but I see Virtualbox changed it's configuration directory location to perhaps a more Windows friendly. I ended up deleting the old configuration and it seems to be working correctly with the new one. Thanks for the work, -- Adam Vande More ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Sun, 24 Apr 2011 12:29:43 -0300, Sergio de Almeida Lenzi wrote: For me it is working... running windows XP dnd linux over an old(4.0.2) image it is ok... very stable... Only a problem remains (that is not still fixed): it is the problem with the vnc in VBoxHeadless the cursor is not in sync (the vnc cursor) is not in sync with the XP cursor.. although the sync is better (compared with 4.0.2 but is still out of sync)... How to reproduce: VBoxHeadless --vnc --vncport 5901 --startvm XPimg then goto another machine and execute: vncviewer x.x.x.x:5901, the system opens works but the mouse cursor is not in sync... Question: Will there be a fix??? Don't know if that is a bug or a problem of the implementation. I would recommend waiting for the VNC extpack. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Tue, 26 Apr 2011 15:42:29 -0400, Ryan Stone wrote:
On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich
de...@freebsd.org wrote:
On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
PBIs for PC-BSD are currently worked on and will hopefully be available
in a few days.
Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
to provide the PBIs!
PC-BSD 8.x 32bit:
http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi
ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi
PC-BSD 8.x 64bit:
http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi
ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
Feedback (positive and negative) from PC-BSD users is very welcome!
I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable
to start any virtual machines(both pre-existing VMs or a new VM that I
tried to create). I get the following error dialog:
Failed to open a session for the virtual machine RELENG_8_amd64.
Failed to load VMMR0.r0
(VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
Unknown error creating VM
(VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
Details:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
Yeah, thanks we already know. They added some strict hardening checks
in virtualbox 4.0 that fail on PC-BSD. Kris Moore is currently
rebuilding the PBIs with some modifications.
That's exactly why we have call for testers so find such weird problems
that nobody could think of.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
On Sun, 24 Apr 2011 16:37:15 -0400, Jason Andresen wrote: On Fri, 22 Apr 2011 13:01:40 +0200 Bernhard Froehlich de...@freebsd.org 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. Last time I asked for some help and Baptiste Daroussin (bapt@) made the classic mistake to respond. So all please welcome bapt to the FreeBSD Vbox Team! Good news and bad news. The good news is that it appears to be stable with my WinXP Pro VM. Bad news is that enabling 3D acceleration still causes the VM to immediately crash when I try to start it. Please try to get a coredump and stacktrace. You need to have the DEBUG option enabled or use the binary packages and set sysctl kern.sugid_coredump=1 first to also get coredumps for suid binaries like VirtualBox is. Once you have a core file please run gdb /usr/local/lib/virtualbox/VirtualBox your_corefile.core and send me the output of bt full. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote: PBIs for PC-BSD are currently worked on and will hopefully be available in a few days. Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts to provide the PBIs! PC-BSD 8.x 32bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi PC-BSD 8.x 64bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi Feedback (positive and negative) from PC-BSD users is very welcome! -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Call for Testers: VirtualBox 4.0.6
For me it is working... running windows XP dnd linux over an old(4.0.2) image it is ok... very stable... Only a problem remains (that is not still fixed): it is the problem with the vnc in VBoxHeadless the cursor is not in sync (the vnc cursor) is not in sync with the XP cursor.. although the sync is better (compared with 4.0.2 but is still out of sync)... How to reproduce: VBoxHeadless --vnc --vncport 5901 --startvm XPimg then goto another machine and execute: vncviewer x.x.x.x:5901, the system opens works but the mouse cursor is not in sync... Question: Will there be a fix??? Thanks for your attention Happy Easter for all ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Call for Testers: VirtualBox 4.0.6
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. Last time I asked for some help and Baptiste Daroussin (bapt@) made the classic mistake to respond. So all please welcome bapt to the FreeBSD Vbox Team! This is also the first time that we provide FreeBSD binary packages. They are build for FreeBSD 7.4 and 8.2 on i386 and amd64 platform and have the DEBUG option enabled. If you use a STABLE kernel you can use the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary package but have to compile the kernel module port for your kernel yourself. (emulators/virtualbox-ose-kmod) PBIs for PC-BSD are currently worked on and will hopefully be available in a few days. What has happened since the last cft: - VirtualBox update to 4.0.6 - phpvirtualbox updated to 4.0-5 - VIMAGE support added - vboxheadless startscript added - vboxwebsrv rc startscript fixes - Build fixed with LOCALBASE != PREFIX - Documentation of USB configuration (see pkg-message or Wiki) Thanks to all people that have contributed to that release and also reported problems for the last cft. We really appreciate that! Changes in the port: http://svn.bluelife.at/index.cgi/blueports/log/emulators Changelog for 4.0.6: http://www.virtualbox.org/wiki/Changelog FreeBSD specific configuration: http://wiki.freebsd.org/VirtualBox Todo List: http://wiki.freebsd.org/VirtualBox/ToDo Ports: http://home.bluelife.at/ports/virtualbox-cft-20110421.tar.gz FreeBSD 8.2/amd64 packages: virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz FreeBSD 8.2/i386 packages: virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz FreeBSD 7.4/amd64 packages: virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz FreeBSD 7.4/i386 packages: virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz Checksums: SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-amd64.tbz) = d7bdad02d2a04dd9dc3f12cc3ee002ce3bfc196b SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-i386.tbz) = e3023f5117fd15e918cba749d1ace2b7366bdc88 SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-amd64.tbz) = bd2785ac54e8363d217e35433d942ccae8bb7ffd SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-i386.tbz) = f6c437febf60828218cb42d7bfab8b536ecb7301 SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz) = 31bbe5ff1e8d9b14dbd64c5d1f964fb702efda9e SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz) = 019955d07293f25421a0ca49d67975c165ee3e85 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz) = e56736714e01dbe693515ed89e239337c7df77d3 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz) = 8f59294036b2f1ef407849f874139a80b6aabbcb SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz) = cc7e72fdcf0e2cd0bcd21bb152ffa8b1b1adcaae SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz) = be14e942cd2b426007b2d9a395cc65843340970d SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz) = d5be908e99f9dfc4f7a1efe1570b67ad2d6b8d27 SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz) = 2627acdb5ea9008bfa6ac6c2f452d6b883cfa40e SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz) = e846f4a94bf14d0a50d3deab0ae325da25e79448 SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz) = 68144054e11bebe21fcb2b19e99cb33cead6f25b SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz) = 7f08351028f18a3d76ed8c57aba525b11b47ee9a SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz) = 6e9bbfe0a2b19985b556e739f02f02a86ef873dd Mirrors: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/ (master) http://files.etoilebsd.net/vbox/4.0.6/ Thanks and good luck, Bernhard, on behalf of the FreeBSD Vbox Team -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
