From owner-freebsd-virtualization@FreeBSD.ORG Thu Dec 17 04:11:36 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22988106566C for ; Thu, 17 Dec 2009 04:11:36 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id A69FF8FC15 for ; Thu, 17 Dec 2009 04:11:35 +0000 (UTC) Received: by ewy26 with SMTP id 26so819554ewy.3 for ; Wed, 16 Dec 2009 20:11:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=eIWOR+hbvQthAZyqXPprHGw+w/5KcxWbmUsQcFt3L1Y=; b=uss6cefHkcBOOvkZD+r7qsC7eY1hKJUiK401aH7m244AywJeU+rMkAurKhrVRHJsXd f4vs6BDLMO7n1XICfiriPyiGDIf0vzQSmtH60MnHppcfgWnQPklPi6i5a6wcPhZpzASY MM+3aNf7Xewh5hb1KBuyFlne4jT4Muvjh+KcQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=s1lTVhodSxjP9mPbeXQhNJQuS28ogrT6DLrkBk3hamqcMug6SX1sXlfqIBkePWgMZs i+qOlt+j+5DMex9BcVZ/NM4ZtFx1/mFbzQfD4POFuMR/LlrhoQmcqPBkDYIGaSt9SjsE Mtab6zozRoeGxxNBqF2L/embOAt3rpuhajdpw= Received: by 10.213.24.9 with SMTP id t9mr7732400ebb.92.1261021654323; Wed, 16 Dec 2009 19:47:34 -0800 (PST) Received: from sevans-mac-pro.local (newbie.thingamajig-systems.co.uk [93.97.185.103]) by mx.google.com with ESMTPS id 28sm8890633eye.9.2009.12.16.19.47.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 16 Dec 2009 19:47:33 -0800 (PST) Message-ID: <4B29A933.70701@gmail.com> Date: Thu, 17 Dec 2009 03:44:51 +0000 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: FreeBSD virtualization mailing list Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: kernel with vimage enabled panics after loading rum(4) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 04:11:36 -0000 Hi Guys, I've raised a PR for this issue, anybody have any ideas on what needs to be done to fix the issue?? http://www.freebsd.org/cgi/query-pr.cgi?pr=141696 Sevan / Venture37 From owner-freebsd-virtualization@FreeBSD.ORG Thu Dec 17 18:51:35 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 980641065672 for ; Thu, 17 Dec 2009 18:51:35 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outK.internet-mail-service.net (outk.internet-mail-service.net [216.240.47.234]) by mx1.freebsd.org (Postfix) with ESMTP id 7F2E98FC20 for ; Thu, 17 Dec 2009 18:51:35 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id DE4C2D1547; Thu, 17 Dec 2009 10:51:42 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id C826D2D6021; Thu, 17 Dec 2009 10:51:34 -0800 (PST) Message-ID: <4B2A7DC3.8000504@elischer.org> Date: Thu, 17 Dec 2009 10:51:47 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Venture37 References: <200912171530.nBHFUDBO087113@freefall.freebsd.org> In-Reply-To: <200912171530.nBHFUDBO087113@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marko Zec , FreeBSD virtualization mailing list Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 18:51:35 -0000 Venture37 wrote: > The following reply was made to PR kern/141696; it has been noted by GNATS. > > From: Venture37 > To: bug-followup@FreeBSD.org, venture37@geeklan.co.uk > Cc: > Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic > Date: Thu, 17 Dec 2009 15:25:28 +0000 > > Photo of the trace output > http://img64.imageshack.us/i/img1517.jpg/ Marko, et al. looking at this, the crash is in ifindex_alloc_locked() from: if_alloc() rum_attach() device_attach() device_probe_and_attach() usb_probe_and_attach_sub() usb_probe_and_attach() uhub_explore() usb_bus_explore() usb_process() the question is "where should we load the current vnet? is it up to the driver (if_rum) or should device_attach assume that the resulting device MIGHT be a network device. Julian > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 18 09:45:07 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FF44106566C; Fri, 18 Dec 2009 09:45:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id 0CA608FC12; Fri, 18 Dec 2009 09:45:07 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 6DEE041C7B7; Fri, 18 Dec 2009 10:45:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id d-eU5j1Wp-AQ; Fri, 18 Dec 2009 10:45:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id A1F7141C6A1; Fri, 18 Dec 2009 10:45:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7F3EC4448EC; Fri, 18 Dec 2009 09:44:17 +0000 (UTC) Date: Fri, 18 Dec 2009 09:44:17 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Julian Elischer In-Reply-To: <4B2A7DC3.8000504@elischer.org> Message-ID: <20091218094256.J86040@maildrop.int.zabbadoz.net> References: <200912171530.nBHFUDBO087113@freefall.freebsd.org> <4B2A7DC3.8000504@elischer.org> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Marko Zec , FreeBSD virtualization mailing list Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 09:45:07 -0000 On Thu, 17 Dec 2009, Julian Elischer wrote: Hi Julian, > Venture37 wrote: >> The following reply was made to PR kern/141696; it has been noted by GNATS. >> >> From: Venture37 >> To: bug-followup@FreeBSD.org, venture37@geeklan.co.uk >> Cc: Subject: Re: kern/141696: [rum] [panic] rum(4)+ vimage = kernel panic >> Date: Thu, 17 Dec 2009 15:25:28 +0000 >> >> Photo of the trace output >> http://img64.imageshack.us/i/img1517.jpg/ > > Marko, et al. > > looking at this, the crash is in > > ifindex_alloc_locked() > from: > if_alloc() > rum_attach() > device_attach() > device_probe_and_attach() > usb_probe_and_attach_sub() > usb_probe_and_attach() > uhub_explore() > usb_bus_explore() > usb_process() > > the question is "where should we load the current vnet? > > is it up to the driver (if_rum) or should device_attach assume that the > resulting device MIGHT be a network device. Different question - why is it a problem for rum/usb whne it's not a problem for all the other physical interfaces like bge, bce, em, .... or have we just not noticed what happens if we have them as module and attach at run-time? /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 18 17:25:13 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD69F106568D for ; Fri, 18 Dec 2009 17:25:13 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 8FDBF8FC0A for ; Fri, 18 Dec 2009 17:25:13 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.3/8.14.3) with ESMTP id nBIH4rwV002322 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 18 Dec 2009 11:04:53 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <4B2BB633.8080302@tundraware.com> Date: Fri, 18 Dec 2009 11:04:51 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (ozzie.tundraware.com [75.145.138.73]); Fri, 18 Dec 2009 11:04:54 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: nBIH4rwV002322 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: FBSD 8.0 And VirtualBox 3.1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 17:25:13 -0000 I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1. The hardware happily boots the Ubuntu amd64 CDROM natively and FreeBSD 8.0 also boots fine - well ... up to the point where it has to ID the hard drive, but that's another story. IOW, the hardware is 64-bit capable (It is an Intel mobo w/a Pentium-D 940 w/EMT64 option). HOWEVER, when I run VirtualBox and try to install the 64 bit version of FreeBSD in a VM, it get a "CPU doesn't support long mode" error during the FreeBSD virtual booting process. FreeBSD 8.0 i386 works fine. 'Anyone run across this before and/or have a fix? TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-virtualization@FreeBSD.ORG Sat Dec 19 02:42:52 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CE681065670 for ; Sat, 19 Dec 2009 02:42:52 +0000 (UTC) (envelope-from fbsdq@peterk.org) Received: from poshta.pknet.net (sokol.pknet.net [216.241.167.214]) by mx1.freebsd.org (Postfix) with ESMTP id 317388FC13 for ; Sat, 19 Dec 2009 02:42:51 +0000 (UTC) Received: (qmail 42720 invoked by uid 89); 19 Dec 2009 02:16:08 -0000 Received: from sokol.pknet.net (HELO pop2.pknet.net) (216.241.167.214) by poshta.pknet.net with SMTP; 19 Dec 2009 02:16:08 -0000 Received: from 216.241.167.212 (SquirrelMail authenticated user fbsdq@peterk.org) by pop2.pknet.net with HTTP; Fri, 18 Dec 2009 19:16:08 -0700 Message-ID: <71884493a925c9959242935b6db83e80.squirrel@pop2.pknet.net> In-Reply-To: <4B2BB633.8080302@tundraware.com> References: <4B2BB633.8080302@tundraware.com> Date: Fri, 18 Dec 2009 19:16:08 -0700 From: "Peter" To: "Tim Daneliuk" User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-virtualization@freebsd.org Subject: Re: FBSD 8.0 And VirtualBox 3.1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 02:42:52 -0000 > I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1. > > The hardware happily boots the Ubuntu amd64 CDROM natively and FreeBSD 8.0 > also boots fine - well ... up to the point where it has to ID the hard > drive, but that's another story. > > IOW, the hardware is 64-bit capable (It is an Intel mobo w/a Pentium-D > 940 w/EMT64 option). > > HOWEVER, when I run VirtualBox and try to install the 64 bit version > of FreeBSD in a VM, it get a "CPU doesn't support long mode" error > during the FreeBSD virtual booting process. FreeBSD 8.0 i386 works > fine. > > 'Anyone run across this before and/or have a fix? > > TIA, Do you have VT-x/AMD-v enabled? [in the BIOS and VBox for this VM] ]Peter[ From owner-freebsd-virtualization@FreeBSD.ORG Sat Dec 19 03:48:50 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0322106566C for ; Sat, 19 Dec 2009 03:48:50 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 806788FC12 for ; Sat, 19 Dec 2009 03:48:50 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.3/8.14.3) with ESMTP id nBJ3mjHK015830 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 18 Dec 2009 21:48:45 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <4B2C4D1C.8000707@tundraware.com> Date: Fri, 18 Dec 2009 21:48:44 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org References: <4B2BB633.8080302@tundraware.com> <71884493a925c9959242935b6db83e80.squirrel@pop2.pknet.net> In-Reply-To: <71884493a925c9959242935b6db83e80.squirrel@pop2.pknet.net> X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (ozzie.tundraware.com [75.145.138.73]); Fri, 18 Dec 2009 21:48:45 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: nBJ3mjHK015830 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: FBSD 8.0 And VirtualBox 3.1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 03:48:50 -0000 On 12/18/2009 8:16 PM, Peter wrote: >> I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1. >> >> The hardware happily boots the Ubuntu amd64 CDROM natively and FreeBSD 8.0 >> also boots fine - well ... up to the point where it has to ID the hard >> drive, but that's another story. >> >> IOW, the hardware is 64-bit capable (It is an Intel mobo w/a Pentium-D >> 940 w/EMT64 option). >> >> HOWEVER, when I run VirtualBox and try to install the 64 bit version >> of FreeBSD in a VM, it get a "CPU doesn't support long mode" error >> during the FreeBSD virtual booting process. FreeBSD 8.0 i386 works >> fine. >> >> 'Anyone run across this before and/or have a fix? >> >> TIA, > > > Do you have VT-x/AMD-v enabled? [in the BIOS and VBox for this VM] > > > > ]Peter[ > > Yup, but I wonder ... I'm running XP as the host which is 32-bit even though the hardware is 64-bit capabale. Could this be limiting what VirtualBox can deliver? -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-virtualization@FreeBSD.ORG Sat Dec 19 11:25:56 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C49241065676 for ; Sat, 19 Dec 2009 11:25:56 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 669D88FC14 for ; Sat, 19 Dec 2009 11:25:56 +0000 (UTC) Received: by ewy3 with SMTP id 3so4539531ewy.13 for ; Sat, 19 Dec 2009 03:25:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.88.206 with SMTP id a56mr1810115wef.64.1261220500163; Sat, 19 Dec 2009 03:01:40 -0800 (PST) In-Reply-To: <4B2C4D1C.8000707@tundraware.com> References: <4B2BB633.8080302@tundraware.com> <71884493a925c9959242935b6db83e80.squirrel@pop2.pknet.net> <4B2C4D1C.8000707@tundraware.com> From: =?ISO-8859-1?Q?Marius_N=FCnnerich?= Date: Sat, 19 Dec 2009 12:01:20 +0100 Message-ID: To: Tim Daneliuk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-virtualization@freebsd.org Subject: Re: FBSD 8.0 And VirtualBox 3.1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 11:25:56 -0000 On Sat, Dec 19, 2009 at 04:48, Tim Daneliuk wrote: > On 12/18/2009 8:16 PM, Peter wrote: >>> I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1. >>> >>> The hardware happily boots the Ubuntu amd64 CDROM natively and FreeBSD = 8.0 >>> also boots fine - well ... up to the point where it has to ID the hard >>> drive, but that's another story. >>> >>> IOW, the hardware is 64-bit capable (It is an Intel mobo w/a Pentium-D >>> 940 w/EMT64 option). >>> >>> HOWEVER, when I run VirtualBox and try to install the 64 bit version >>> of FreeBSD in a VM, it get a "CPU doesn't support long mode" error >>> during the FreeBSD virtual booting process. =A0FreeBSD 8.0 i386 works >>> fine. >>> >>> 'Anyone run across this before and/or have a fix? >>> >>> TIA, >> >> >> Do you have VT-x/AMD-v enabled? [in the BIOS and VBox for this VM] >> >> >> >> ]Peter[ >> >> > > Yup, but I wonder ... I'm running XP as the host which is 32-bit even tho= ugh > the hardware is 64-bit capabale. =A0Could this be limiting what VirtualBo= x > can deliver? Exactly. For 64bit guests the host has to be 64bit too afaik.