On Mon, May 18, 2009 at 04:56:13PM +0100, Tim Bishop wrote: > On Mon, May 18, 2009 at 08:38:18AM -0500, Doug Poland wrote: > > On Sun, May 17, 2009 19:25, Greg Byshenk wrote: > > > On Sun, May 17, 2009 at 08:09:20PM +0200, Martin Wilke wrote: > > >> > > >> We rolled a new tarball with the patch from Juergen Lock [1] > > >> with a posible fix for AMD64 users, tested on 3 machines > > >> which now works without problems. Many Thanks to him for > > >> his nice work! > > >> > > >> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz > > > > Working for me with a fresh cvsup of 7.2-STABLE (17 May 09). > > Installing a 7.2-RELEASE amd64 guest as I write this. > > Works for me, but I've not been able to get a 64 bit guest to work. I > get the following error when booting the installer: > > CPU doesn't support long mode > > I think I've got all the right options set. Maybe my CPU doesn't support > the necessary VM stuff to let a 64 bit guest work? I'm getting good at answering my own questions :D Yes, it's my CPU. Found a different machine and confirmed it has the VMX extension, and all is fine. > I'm also still seeing the following on loading vboxdrv: > > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > kldload: unexpected relocation type 10 > vboxdrv: fAsync=0 offMin=0x41f offMax=0x53b > > Are others still seeing that on amd64? Not that I thought it'd make any difference, but I can confirm those still happen even with the VMX extension. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984Received on Mon May 18 2009 - 14:49:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:47 UTC