Date: Tue, 02 Mar 2010 20:39:51 -0500 From: Adam K Kirchhoff <adamk@voicenet.com> To: freebsd-emulation@freebsd.org, alexeichi@yahoo.de Subject: Re: Patch to fix VirtualBox with recent kernel versions Message-ID: <4B8DBDE7.9060401@voicenet.com> In-Reply-To: <4B8CFD31.2080805@voicenet.com> References: <215745.35399.qm@web27602.mail.ukl.yahoo.com> <4B8B19DF.2040101@voicenet.com> <1267522633.3221.2.camel@Prometheus> <4B8CFD31.2080805@voicenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/02/10 06:57, Adam K Kirchhoff wrote: > On 03/02/10 04:37, Alexander Eichner wrote: >> Adam K Kirchhoff wrote: >>> >>> I'm sorry to say, but I'm getting the exact same Assertion Failed error >>> as before with this new patch. The only difference this time is that >>> i=0x7 instead of i=0x4. >>> >>> Adam >>> >>> _______________________________________________ >>> freebsd-emulation@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation >>> To unsubscribe, send any mail to >>> "freebsd-emulation-unsubscribe@freebsd.org" >> That's not good. Everything works just fine here now on a 32bit FreeBSD >> 8.0 host. Can you give some information of your host (RAM, CPU, ...) and >> the guest configuration please? Do you have any special kernel options >> set? > > I've been testing on two 32-bit installations. I was using a custom > kernel on both, but I just tried with GENERIC on one of them and the > crash of VirtualBox still happens. Both machines have 2 gigs of RAM, > one with 3 gigs of swap and one with 2 gigs of swap. Both are running > -CURRENT from 6 days ago. > > One machine: > > CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3191.87-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0xe43d<SSE3,DTES64,MON,DS_CPL,VMX,CNXT-ID,CX16,xTPR,PDCM> > AMD Features=0x20100000<NX,LM> > AMD Features2=0x1<LAHF> > TSC: P-state invariant > real memory = 2147483648 (2048 MB) > avail memory = 2084831232 (1988 MB) > > And the other: > > CPU: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz (2327.49-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x10677 Stepping = 7 > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > Features2=0x8e39d<SSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1> > > AMD Features=0x20100000<NX,LM> > AMD Features2=0x1<LAHF> > TSC: P-state invariant > real memory = 2147483648 (2048 MB) > avail memory = 2085683200 (1989 MB) > > The Xeon supports AMD-V, but it doesn't matter if I enable that in the > acceleration configuration of the VM or not. > > On both machines I have tested the same Windows XP guest. Base memory > is 512 MB, 1 CPU. The video memory is set at 64 megs. On one of the > machines I have also tried Ubuntu. 128 megs of RAM, 1 CPU, 12 megs of > video memory. 3D acceleration is disabled on both machines. > > The XML config file for the guest is here: http://pastebin.com/Qaqx7gTi > > I'm actually installing -CURRENT amd64 to a spare USB drive I have on > the Xeon and can test to confirm that it works there since you believe > this to be a problem only with 32-bit FreeBSD. > > Adam Alexander*, *OK, so I can only assume that we are, in fact, talking about the same problem as it is, indeed, working just fine here on the AMD64 system I installed today. Same machine, -CURRENT from today (instead of last week) and the same VirtualBox configuration, and it works just fine. Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B8DBDE7.9060401>