Re: VirtualBox 3.2.0-beta-1 fails to compile on -current
On 05/26/10 15:38, Brandon Gooch wrote:
On Wed, May 26, 2010 at 1:45 AM, Beat Gaetzi b...@freebsd.org wrote:
On 05/26/10 08:27, Brandon Gooch wrote:
On Fri, Apr 30, 2010 at 1:05 PM, Jung-uk Kim j...@freebsd.org wrote:
On Thursday 29 April 2010 09:02 pm, Michael Butler wrote:
On 04/29/10 19:23, Jung-uk Kim wrote:
I read the source again and I found it is not patched by the
emulator itself. It's done from usual _CRS method. Please try
the attached patch instead.
Now I get ..
kBuild: iasl DevicesR3 -
/usr/home/imb/svn/virtualbox-ose/work/VirtualBox-3.2.0_OSE/src/VBox
/Devices/PC/vbox-cpuhotplug.dsl
/usr/home/imb/svn/virtualbox-ose/work/VirtualBox-3.2.0_OSE/out/free
bsd.x86/release/obj/DevicesR3/vboxssdt-cpuhotplug.hex.pre 14:
Device (SCK0) { Name (_HID, ACPI0004) Name (_UID, SCKCPU0)
Processor (CPU0, 0x00, 0x0, 0x0 ) { Name (_HID, ACPI0007) Name
(_UID, SCK0-CPU0) Name (_PXM, 0x00) Method(_MAT, 0) { IF
(CPCK(0x00)) { Name (APIC, Buffer (8) {0x00, 0x08, 0x00, 0x00,
0x01}) Return(APIC) } Else { Return (0x00) } } Method(_STA) { IF
(CPCK(0x00)) { Return (0xF) } Else { Return (0x0) } } Method(_EJ0,
1) { Store(0x00, \_SB.CPUL) Return } } }
Error4080 -
Invalid object type for reserved
name ^ (found INTEGER, requires Buffer)
.. where the Return(0x00) as the alternate result to
Result(APIC) is causing an issue,
Sigh... A new file, a new bug. :-(
Try the attached patch.
It seems this patch has been committed to the 'virtualbox-ose-devel'
port, but your previous patch (attached to an earlier message in this
thread) did not. Will you submit the original patch to the
freebsd-vbox crew as well?
I forgot to commit this patch to the virtualbox-ose-devel port as our
main focus is on the 3.2.0 port at the moment with already includes this
patch. I will commit the patch in a few minutes to the -devel port.
I see... Well, as it stands, both of my laptops, one running CURRENT,
the other running 8.1-PRERELEASE, panic when loading the vboxdrv
module right now (on 3.2.1 at least), so I'm looking to rollback to
3.1.8 -- or test 3.2.0 :)
We received a few reports from users that 3.2.0 panics the host when
loading the kernel module. This is the reason why we haven't announced a
CFT for 3.2.0 yet.
Will you announce to the list when we VirtualBox users should begin
testing 3.2.0? Or did I already miss that?
Yes, our plan is to announce a CFT for 3.2.0 once we think the port is
in a good shape.
Beat
___
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: CFT: VirtualBox 3.2.0
Bernhard Froehlich wrote: - Ursprüngliche Mitteilung - On Sat, 29 May 2010 15:22:44 +0200 Beat Gaetzi b...@freebsd.org wrote: The vbox@ team is happy to announce a call for tester for VirtualBox 3.2.0. I installed the -devel versions first. Loading vboxdrv.ko resulted in a kernel panic caused by a NULL pointer dereference. I have a crash dump, but it's not very useful because kgdb complains that it can't access address 0. The non-devel version works just fine, however. Our focus was on the 3.2.0 port thats why this patch was missing in the -devel port. Yes, this is the bug that alexander and i worked on since friday. Beat if you have time then please commit the last change also to the devel kmod. Otherwise i will do this tomorrow. I've committed the patch to the -devel port a few minutes ago. Thanks for testing! Beat ___ 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: CFT: VirtualBox 3.2.0
Brandon Gooch wrote: On Mon, May 31, 2010 at 2:06 PM, Mario Lobo l...@bsd.com.br wrote: On Monday 31 May 2010 15:14:01 Bernhard Froehlich wrote: On Mon, 31 May 2010 09:05:47 -0400, Michael Butler i...@protected-networks.net wrote: On 05/31/10 04:55, Anton Berezin wrote: On Mon, May 31, 2010 at 11:01:04AM +0900, Daichi GOTO wrote: Memory leaks there I have noticed. Look at follow message of top(1): I also experience memory leaks. WinXP guest, amd64-CURRENT (from 2010-05-10) host. 100% CPU load when the guest is doing nothing, and memory usage keeps growing at a rather alarming pace. Just an observation - this appears to be related to using the additions from 3.2.0. Using VBox 3.2.0 with the 3.1.8 additions doesn't appear to display the leak - no idea what triggers this behaviour, I've just talked to the virtualbox developers and this is obviously an known bug in the 3.2.0 additions. As a workaround you can use the 3.1.8 additions and they said it will be fixed with 3.2.2. Thanks! Actually, this problem doesn't happen up to VBoxGuestAdditions_3.2.0_BETA1.iso. VBoxGuestAdditions_3.2.0_BETA2.iso and newer do have it. I can confirm this. For the record. I've updated the port in our repository to 3.2.2 which should fix the memory leak. Could you please check if the problem is solved now. Thanks, Beat ___ 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: Serial ports under VirtualBox
Ted Mittelstaedt wrote: A month or so ago I posted the following, I was wondering if anyone has taken a look at the disconnect then cannot reconnect problem in the port. There is an update to the bug I referenced here that will help the situation, but it won't do any good if the FreeBSD port still has the disconnect then cannot reconnect problem with the serial ports. According to the information from the ticket this problem should be fixed in VirtualBox 3.2.2. Could you please try the virtualbox-ose-kmod and virtualbox-ose port from our development repository and check if the problem is fixed for you: https://svn.bluelife.at/nightlies/virtualbox-port.tar.gz Beat ___ 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: why vbox is marked broken for head?
On 06/24/10 09:39, Andriy Gapon wrote: Why vbox is marked broken for head? I keep using it with TRYBROKEN and see zero problems. Where are the bug reports? Perhaps there are specific problems that can be investigated, fixed or worked around (via configuration)? There are several known panics with CURRENT older than revision 209048. The port also do not build on current newer than revision 208751. This is fixed in our development repository and we will remove the BROKEN with the update to 3.2.6. Beat ___ 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: why vbox is marked broken for head?
On 06/24/10 10:00, Andriy Gapon wrote: on 24/06/2010 10:46 Beat Gaetzi said the following: On 06/24/10 09:39, Andriy Gapon wrote: Why vbox is marked broken for head? I keep using it with TRYBROKEN and see zero problems. Where are the bug reports? Perhaps there are specific problems that can be investigated, fixed or worked around (via configuration)? There are several known panics with CURRENT older than revision 209048. I see. The port also do not build on current newer than revision 208751. This is fixed in our development repository and we will remove the BROKEN with the update to 3.2.6. The memchr issue? Yes. When 3.2.6 is planned? If it's soon I'd just wait, otherwise it seems to be trivial to unbreak the port for post-r209048 head. I don't know the release date but 3.2.6_BETA2 was released two days ago so I think 3.2.6 will be released soon. Beat ___ 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
