From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 5 11:06:52 2010 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 978E61065711 for ; Mon, 5 Jul 2010 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 85B6D8FC0A for ; Mon, 5 Jul 2010 11:06:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o65B6qUQ079166 for ; Mon, 5 Jul 2010 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o65B6p29079164 for freebsd-emulation@FreeBSD.org; Mon, 5 Jul 2010 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Jul 2010 11:06:51 GMT Message-Id: <201007051106.o65B6p29079164@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-emulation@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 11:06:52 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/148097 emulation [patch] suggested addition to linux_base-* packages to o kern/147793 emulation [vmware] cdrom handling, panic, possible race conditio o kern/146726 emulation [linux] Linux InstallJammer fails to execute on 8-STAB o kern/146237 emulation [linux] Linux binaries not reading directories mounted o kern/145024 emulation [linux] [panic] kernel crash by linux.ko module with n f kern/144763 emulation [linux] [panic] Kernel panic when start linux binaries o kern/144194 emulation [linux] [patch] linuxulator: 2 exec bug fixes o ports/142837 emulation [patch] emulators/linux_base-* packages fails to insta o kern/142082 emulation [patch] [panic] linuxulator: getppid: use after free o kern/141439 emulation [linux] [patch] linux_exit_group kills group leader o kern/140156 emulation [linux] cdparanoia fails to read drive data o kern/139423 emulation [parallels] Networking does not work on amd64 guest on o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest f ports/137332 emulation add caution messages to some adobe products s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] emulators/linux_base-f10: certain linux apps l o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 28 problems total. From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 5 21:43:34 2010 Return-Path: Delivered-To: freebsd-emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA35C1065672; Mon, 5 Jul 2010 21:43:34 +0000 (UTC) (envelope-from dchagin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1BE58FC14; Mon, 5 Jul 2010 21:43:34 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o65LhYII015673; Mon, 5 Jul 2010 21:43:34 GMT (envelope-from dchagin@freefall.freebsd.org) Received: (from dchagin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o65LhYQX015669; Mon, 5 Jul 2010 21:43:34 GMT (envelope-from dchagin) Date: Mon, 5 Jul 2010 21:43:34 GMT Message-Id: <201007052143.o65LhYQX015669@freefall.freebsd.org> To: dchagin@FreeBSD.org, freebsd-emulation@FreeBSD.org, dchagin@FreeBSD.org From: dchagin@FreeBSD.org Cc: Subject: Re: kern/142082: [patch] [panic] linuxulator: getppid: use after free X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 21:43:34 -0000 Synopsis: [patch] [panic] linuxulator: getppid: use after free Responsible-Changed-From-To: freebsd-emulation->dchagin Responsible-Changed-By: dchagin Responsible-Changed-When: Mon Jul 5 21:43:12 UTC 2010 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=142082 From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 5 21:44:11 2010 Return-Path: Delivered-To: freebsd-emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C33BA1065740; Mon, 5 Jul 2010 21:44:11 +0000 (UTC) (envelope-from dchagin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9ABF88FC12; Mon, 5 Jul 2010 21:44:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o65LiBGb015734; Mon, 5 Jul 2010 21:44:11 GMT (envelope-from dchagin@freefall.freebsd.org) Received: (from dchagin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o65LiBuC015730; Mon, 5 Jul 2010 21:44:11 GMT (envelope-from dchagin) Date: Mon, 5 Jul 2010 21:44:11 GMT Message-Id: <201007052144.o65LiBuC015730@freefall.freebsd.org> To: dchagin@FreeBSD.org, freebsd-emulation@FreeBSD.org, dchagin@FreeBSD.org From: dchagin@FreeBSD.org Cc: Subject: Re: kern/144194: [linux] [patch] linuxulator: 2 exec bug fixes X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 21:44:11 -0000 Synopsis: [linux] [patch] linuxulator: 2 exec bug fixes Responsible-Changed-From-To: freebsd-emulation->dchagin Responsible-Changed-By: dchagin Responsible-Changed-When: Mon Jul 5 21:43:55 UTC 2010 Responsible-Changed-Why: Grab http://www.freebsd.org/cgi/query-pr.cgi?pr=144194 From owner-freebsd-emulation@FreeBSD.ORG Mon Jul 5 21:44:56 2010 Return-Path: Delivered-To: freebsd-emulation@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF8F8106564A; Mon, 5 Jul 2010 21:44:56 +0000 (UTC) (envelope-from dchagin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C76558FC14; Mon, 5 Jul 2010 21:44:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o65LiuZw015782; Mon, 5 Jul 2010 21:44:56 GMT (envelope-from dchagin@freefall.freebsd.org) Received: (from dchagin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o65Liuik015778; Mon, 5 Jul 2010 21:44:56 GMT (envelope-from dchagin) Date: Mon, 5 Jul 2010 21:44:56 GMT Message-Id: <201007052144.o65Liuik015778@freefall.freebsd.org> To: dchagin@FreeBSD.org, freebsd-emulation@FreeBSD.org, dchagin@FreeBSD.org From: dchagin@FreeBSD.org Cc: Subject: Re: kern/141439: [linux] [patch] linux_exit_group kills group leader X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 21:44:57 -0000 Synopsis: [linux] [patch] linux_exit_group kills group leader Responsible-Changed-From-To: freebsd-emulation->dchagin Responsible-Changed-By: dchagin Responsible-Changed-When: Mon Jul 5 21:44:38 UTC 2010 Responsible-Changed-Why: Grab http://www.freebsd.org/cgi/query-pr.cgi?pr=141439 From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 02:59:00 2010 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E32B106564A for ; Tue, 6 Jul 2010 02:59:00 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A8FCF8FC1E for ; Tue, 6 Jul 2010 02:58:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o662wwYG009272 for ; Mon, 5 Jul 2010 20:58:58 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o662wwUc009269 for ; Mon, 5 Jul 2010 20:58:58 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 5 Jul 2010 20:58:58 -0600 (MDT) From: Warren Block To: emulation@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (wonkity.com [127.0.0.1]); Mon, 05 Jul 2010 20:58:58 -0600 (MDT) Cc: Subject: Mounting VirtualBox vdi files X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 02:59:00 -0000 Is there any hope of a utility like mdconfig that would allow mounting a vdi file directly? There's a tantalizingly-named ImageMounter/VBoxFUSE, which is probably not what that implies. It would be great to be able to access vdi files without having to waste time and space converting them to raw image files. From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 03:21:04 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 115B21065670 for ; Tue, 6 Jul 2010 03:21:04 +0000 (UTC) (envelope-from wilkinsa@dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6958A8FC14 for ; Tue, 6 Jul 2010 03:21:02 +0000 (UTC) Received: from ednmsw520.dsto.defence.gov.au (ednmsw520.dsto.defence.gov.au [131.185.68.60]) by digger1.defence.gov.au (DSTO/DSTO) with ESMTP id o663FpLb028962; Tue, 6 Jul 2010 12:45:51 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw520.dsto.defence.gov.au (Clearswift SMTPRS 5.3.2) with ESMTP id ; Tue, 6 Jul 2010 12:51:01 +0930 Received: from stlex511.dsto.defence.gov.au ([203.6.60.49]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 Jul 2010 12:50:58 +0930 Received: from stlux550.dsto.defence.gov.au ([203.6.60.61]) by stlex511.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.4675); Tue, 6 Jul 2010 11:20:57 +0800 Received: from stlux550.dsto.defence.gov.au (localhost [127.0.0.1]) by stlux550.dsto.defence.gov.au (8.14.3/8.14.3) with ESMTP id o663KvJ5016078; Tue, 6 Jul 2010 11:20:57 +0800 (WST) (envelope-from wilkinsa@stlux550.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by stlux550.dsto.defence.gov.au (8.14.3/8.14.3/Submit) id o663KvBN016077; Tue, 6 Jul 2010 11:20:57 +0800 (WST) (envelope-from wilkinsa) Date: Tue, 6 Jul 2010 11:20:57 +0800 From: "Wilkinson, Alex" To: freebsd-emulation@freebsd.org, emulation@freebsd.org Message-ID: <20100706032057.GA15827@stlux503.dsto.defence.gov.au> Mail-Followup-To: freebsd-emulation@freebsd.org, emulation@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: Organisation: Defence Science Technology Organisation X-Message-Flag: "Please Restore Line Breaks If Necessary" User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginalArrivalTime: 06 Jul 2010 03:20:57.0728 (UTC) FILETIME=[403AC800:01CB1CBA] X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.000.1038-17488.003 X-TM-AS-Result: No--4.024500-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Content-Transfer-Encoding: 7bit Cc: Subject: Re: Mounting VirtualBox vdi files [SEC=UNCLASSIFIED] X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 03:21:04 -0000 0n Mon, Jul 05, 2010 at 08:58:58PM -0600, Warren Block wrote: >Is there any hope of a utility like mdconfig that would allow mounting a >vdi file directly? > >There's a tantalizingly-named ImageMounter/VBoxFUSE, which is probably >not what that implies. > >It would be great to be able to access vdi files without having to >waste time and space converting them to raw image files. Try: http://libguestfs.org/ -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 03:35:08 2010 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FD26106564A for ; Tue, 6 Jul 2010 03:35:08 +0000 (UTC) (envelope-from wilkinsa@dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id E917E8FC18 for ; Tue, 6 Jul 2010 03:35:07 +0000 (UTC) Received: from ednmsw520.dsto.defence.gov.au (ednmsw520.dsto.defence.gov.au [131.185.68.60]) by digger1.defence.gov.au (DSTO/DSTO) with ESMTP id o663FpLb028962; Tue, 6 Jul 2010 12:45:51 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw520.dsto.defence.gov.au (Clearswift SMTPRS 5.3.2) with ESMTP id ; Tue, 6 Jul 2010 12:51:01 +0930 Received: from stlex511.dsto.defence.gov.au ([203.6.60.49]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 Jul 2010 12:50:58 +0930 Received: from stlux550.dsto.defence.gov.au ([203.6.60.61]) by stlex511.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.4675); Tue, 6 Jul 2010 11:20:57 +0800 Received: from stlux550.dsto.defence.gov.au (localhost [127.0.0.1]) by stlux550.dsto.defence.gov.au (8.14.3/8.14.3) with ESMTP id o663KvJ5016078; Tue, 6 Jul 2010 11:20:57 +0800 (WST) (envelope-from wilkinsa@stlux550.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by stlux550.dsto.defence.gov.au (8.14.3/8.14.3/Submit) id o663KvBN016077; Tue, 6 Jul 2010 11:20:57 +0800 (WST) (envelope-from wilkinsa) Date: Tue, 6 Jul 2010 11:20:57 +0800 From: "Wilkinson, Alex" To: freebsd-emulation@freebsd.org, emulation@freebsd.org Message-ID: <20100706032057.GA15827@stlux503.dsto.defence.gov.au> Mail-Followup-To: freebsd-emulation@freebsd.org, emulation@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: Organisation: Defence Science Technology Organisation X-Message-Flag: "Please Restore Line Breaks If Necessary" User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginalArrivalTime: 06 Jul 2010 03:20:57.0728 (UTC) FILETIME=[403AC800:01CB1CBA] X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.000.1038-17488.003 X-TM-AS-Result: No--4.024500-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Content-Transfer-Encoding: 7bit Cc: Subject: Re: Mounting VirtualBox vdi files [SEC=UNCLASSIFIED] X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 03:35:08 -0000 0n Mon, Jul 05, 2010 at 08:58:58PM -0600, Warren Block wrote: >Is there any hope of a utility like mdconfig that would allow mounting a >vdi file directly? > >There's a tantalizingly-named ImageMounter/VBoxFUSE, which is probably >not what that implies. > >It would be great to be able to access vdi files without having to >waste time and space converting them to raw image files. Try: http://libguestfs.org/ -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 03:46:30 2010 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BF9C1065670 for ; Tue, 6 Jul 2010 03:46:30 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id DA6528FC15 for ; Tue, 6 Jul 2010 03:46:29 +0000 (UTC) Received: by vws6 with SMTP id 6so7131082vws.13 for ; Mon, 05 Jul 2010 20:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=jl9W2phA1Eg9vIoNxjFCxrsRx35YZoG/iy5U2E5W+x4=; b=aLWGUxUKyZ+GWcZndKNwelgcucHDafDDWqrQNKQxZjI6LIo8PAs/xYvYTkjeeFmY08 uo/CU8Cbfhb7ZMZN6dZ/dvGiCiluD/lT12CoXlQaFE49tvKG7hMhr8rKjWjVEGXaN3qj 9GXKELDhs+T9p7Gb+knaXX90QAvVJeKRmfZGU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QnemoJjC4LJ4GHrz+XU9W8/fUqiK8Kebb2Oawqupc40bAyUS+ruoA/pwO3ox2s3fy6 ZxKufpqTWW374KMYQZD/HcBIP8qagEmIH2NITw75qmKG91aoz5QmnZz7Wkb1WdRmzQGH wKfYc7LkVEmsm4Fst7KMrwCCWSJlI8Lhf2Si0= MIME-Version: 1.0 Received: by 10.229.236.76 with SMTP id kj12mr2077491qcb.226.1278386423273; Mon, 05 Jul 2010 20:20:23 -0700 (PDT) Received: by 10.229.86.12 with HTTP; Mon, 5 Jul 2010 20:20:23 -0700 (PDT) In-Reply-To: References: Date: Mon, 5 Jul 2010 22:20:23 -0500 Message-ID: From: Adam Vande More To: Warren Block Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: emulation@freebsd.org Subject: Re: Mounting VirtualBox vdi files X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 03:46:30 -0000 On Mon, Jul 5, 2010 at 9:58 PM, Warren Block wrote: > Is there any hope of a utility like mdconfig that would allow mounting a > vdi file directly? > > There's a tantalizingly-named ImageMounter/VBoxFUSE, which is probably not > what that implies. > > It would be great to be able to access vdi files without having to waste > time and space converting them to raw image files. > Not that I'm aware of, all tools that do so depend on having a fixed size image. You could use a sparse file for the raw format :P I use some other methods for getting data from VM's to host and other machines. One place I do work for is a linux shop with a couple Win 2k8 VM's. All disk's are mapped to LVM's including 2k8's "dedicated" backup drive. The backup drive(lvm) is then mapped via kpartx and mounted read-only in the host system so tarsnap archives can be generated against it. I actually don't know how you'd do this under FreeBSD since I'm not aware of any equivalent functionality to kpartx under FBSD. -- Adam Vande More From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 03:50:08 2010 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CCB7106566B for ; Tue, 6 Jul 2010 03:50:08 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id AF0DE8FC19 for ; Tue, 6 Jul 2010 03:50:07 +0000 (UTC) Received: by vws6 with SMTP id 6so7135119vws.13 for ; Mon, 05 Jul 2010 20:50:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=sYwWgAfhDeloeR9mBJDI0sLJQkjenISu/8yLfJTokxg=; b=aK0s9f0XkxQxXAkJtJnEr1uG8IqKls7Ojfj8LKvAOhbXG7BqpqjpbXGv7w/yIwqVtc ZLwbEYaQWZUmNN4pNKZ2ZoBi2329VIpQ/A6zTfkDWoaqUS7JrTxR6SsqZ8DaLbb70YKp uCU1PvdFL3r01GZmZ45slfEYFkjI42ico9RXg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VaEahh6LuHt+DhbkoEsu6QxlU3JZfs89+5fhovdECqw38Y0TyVmQ6V/6i2yN48U+FU 7aHhGoA/vy2XMiYhDcMzdUT9Je+nYlLvBVtDTuO9jKbdJe8pfbFm+V6dPdAjk+Gtxt// NPCrtOZfU5rUUCERTnm99fKaG2lCVs0PM6Lko= MIME-Version: 1.0 Received: by 10.229.185.141 with SMTP id co13mr2118121qcb.253.1278386508358; Mon, 05 Jul 2010 20:21:48 -0700 (PDT) Received: by 10.229.86.12 with HTTP; Mon, 5 Jul 2010 20:21:48 -0700 (PDT) In-Reply-To: References: Date: Mon, 5 Jul 2010 22:21:48 -0500 Message-ID: From: Adam Vande More To: Warren Block Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: emulation@freebsd.org Subject: Re: Mounting VirtualBox vdi files X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 03:50:08 -0000 On Mon, Jul 5, 2010 at 10:20 PM, Adam Vande More wrote: > On Mon, Jul 5, 2010 at 9:58 PM, Warren Block wrote: > >> Is there any hope of a utility like mdconfig that would allow mounting a >> vdi file directly? >> >> There's a tantalizingly-named ImageMounter/VBoxFUSE, which is probably not >> what that implies. >> >> It would be great to be able to access vdi files without having to waste >> time and space converting them to raw image files. >> > > Not that I'm aware of, all tools that do so depend on having a fixed size > image. > > You could use a sparse file for the raw format :P I use some other methods > for getting data from VM's to host and other machines. One place I do work > for is a linux shop with a couple Win 2k8 VM's. All disk's are mapped to > LVM's including 2k8's "dedicated" backup drive. The backup drive(lvm) is > then mapped via kpartx and mounted read-only in the host system so tarsnap > archives can be generated against it. I actually don't know how you'd do > this under FreeBSD since I'm not aware of any equivalent functionality to > kpartx under FBSD. > Actually just had another idea if you're using ZFS. Just put the raw image on it's on FS, and set it compressed. Problem solved ;) -- Adam Vande More From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 07:45:00 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 585561065678; Tue, 6 Jul 2010 07:45:00 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 507648FC16; Tue, 6 Jul 2010 07:44:59 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA14153; Tue, 06 Jul 2010 10:44:57 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OW2pt-000N2C-EZ; Tue, 06 Jul 2010 10:44:57 +0300 Message-ID: <4C32DEF6.1020409@freebsd.org> Date: Tue, 06 Jul 2010 10:44:54 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: vbox@freebsd.org, freebsd-emulation@freebsd.org References: <4C0DF92C.9020204@icyb.net.ua> In-Reply-To: <4C0DF92C.9020204@icyb.net.ua> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: emulators/virtualbox-ose vs non-base gcc X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 07:45:00 -0000 on 08/06/2010 11:02 Andriy Gapon said the following: > I am trying to compile my ports with gcc44 instead of a base gcc. > It seems that currently VirtualBox build system assumes that FreeBSD means base > GCC only. For example, it unconditionally uses -fno-format-extensions and > -fformat-extensions options. Those are extensions available in base GCC, but > not in ports GCCs (at least for time being). > I am not proficient in KBuild, so I don't have a patch, but I can make a > suggestion that for these options CC and CXX should be tested in addition to > KBUILD_TARGET. > > Additionally, two files seem to miss some include directives because of GCC > changes outlined here: > http://gcc.gnu.org/gcc-4.3/porting_to.html I would like to remind that the reported issues are still there with VirtualBox 3.2.6 and something like the following patch is still required. --- src/VBox/Main/freebsd/NetIf-freebsd.cpp.orig 2010-07-06 10:31:07.328680775 +0300 +++ src/VBox/Main/freebsd/NetIf-freebsd.cpp 2010-07-06 10:31:28.000532682 +0300 @@ -44,6 +44,7 @@ #include #include +#include #include #include --- src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp.orig 2010-07-06 10:29:23.130414466 +0300 +++ src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp 2010-07-06 10:32:59.702484321 +0300 @@ -40,6 +40,7 @@ # include # include # include +# include # include # include # include And probably the following should just work too. --- Config.kmk.orig 2010-06-25 17:23:52.000000000 +0300 +++ Config.kmk 2010-07-05 20:59:21.772469818 +0300 @@ -2612,7 +2613,7 @@ $(VBOX_GCC_WARN) -Wpointer-arith -Winline $(VBOX_GCC_Wno-pointer-sign) \ -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs \ -Wimplicit-function-declaration -Werror-implicit-function-declaration \ - -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 \ + -O2 -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 \ $(VBOX_GCC_fno-stack-protector) $(VBOX_GCC_R0_OPT) $(VBOX_GCC_R0_FP) \ -nostdinc -std=c99 TEMPLATE_VBOXR0DRV_CFLAGS.x86 = -m32 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 @@ -2621,7 +2622,7 @@ -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -Wundef TEMPLATE_VBOXR0DRV_CXXFLAGS = -fno-exceptions -fno-rtti \ $(VBOX_GCC_WARN) -Wpointer-arith -Winline \ - -O2 -fno-format-extensions -fno-strict-aliasing -fno-common -finline-limit=8000 \ + -O2 -fno-strict-aliasing -fno-common -finline-limit=8000 \ $(VBOX_GCC_fno-stack-protector) $(VBOX_GCC_R0_OPT) $(VBOX_GCC_R0_FP) \ -nostdinc TEMPLATE_VBOXR0DRV_CXXFLAGS.x86 = $(TEMPLATE_VBOXR0DRV_CFLAGS.x86) -- Andriy Gapon From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 08:00:37 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8338F1065670; Tue, 6 Jul 2010 08:00:37 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from mail.itac.at (mail.itac.at [91.205.172.9]) by mx1.freebsd.org (Postfix) with ESMTP id DE6EB8FC1D; Tue, 6 Jul 2010 08:00:36 +0000 (UTC) Received: from [91.205.172.21] (helo=webmail.bluelife.at) by mail.itac.at with esmtpa (Exim 4.63) (envelope-from ) id 1OW351-00047c-5b; Tue, 06 Jul 2010 10:00:35 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 06 Jul 2010 10:00:35 +0200 From: Bernhard Froehlich To: Andriy Gapon In-Reply-To: <4C32DEF6.1020409@freebsd.org> References: <4C0DF92C.9020204@icyb.net.ua> <4C32DEF6.1020409@freebsd.org> Message-ID: <84bf85053cb54d393398f37c0861d1fb@bluelife.at> X-Sender: decke@FreeBSD.org User-Agent: RoundCube Webmail/0.4-beta X-Spam-Score: -0.6 (/) X-Spam-Report: Spam detection software, running on the system "mail.itac.at", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Tue, 06 Jul 2010 10:44:54 +0300, Andriy Gapon wrote: > on 08/06/2010 11:02 Andriy Gapon said the following: >> I am trying to compile my ports with gcc44 instead of a base gcc. >> It seems that currently VirtualBox build system assumes that FreeBSD >> means base >> GCC only. For example, it unconditionally uses -fno-format-extensions >> and >> -fformat-extensions options. Those are extensions available in base >> GCC, but >> not in ports GCCs (at least for time being). >> I am not proficient in KBuild, so I don't have a patch, but I can make a >> suggestion that for these options CC and CXX should be tested in >> addition to >> KBUILD_TARGET. >> >> Additionally, two files seem to miss some include directives because of >> GCC >> changes outlined here: >> http://gcc.gnu.org/gcc-4.3/porting_to.html > > I would like to remind that the reported issues are still there with > VirtualBox > 3.2.6 and something like the following patch is still required. > > --- src/VBox/Main/freebsd/NetIf-freebsd.cpp.orig 2010-07-06 > 10:31:07.328680775 +0300 > +++ src/VBox/Main/freebsd/NetIf-freebsd.cpp 2010-07-06 10:31:28.000532682 > +0300 > @@ -44, 6 +44, 7 @@ > #include > > #include > +#include > #include > #include > > --- src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp.orig 2010-07-06 > 10:29:23.130414466 +0300 > +++ src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp 2010-07-06 > 10:32:59.702484321 > +0300 > @@ -40, 6 +40, 7 @@ > # include > # include > # include > +# include > # include > # include > # include > > > And probably the following should just work too. > > --- Config.kmk.orig 2010-06-25 17:23:52.000000000 +0300 > +++ Config.kmk 2010-07-05 20:59:21.772469818 +0300 > @@ -2612, 7 +2613, 7 @@ > $(VBOX_GCC_WARN) -Wpointer-arith -Winline $(VBOX_GCC_Wno-pointer-sign) \ > -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes > -Wnested-externs \ > [...] Content analysis details: (-0.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.9 AWL AWL: From: address is in the auto white-list Cc: freebsd-emulation@freebsd.org, vbox@freebsd.org Subject: Re: emulators/virtualbox-ose vs non-base gcc X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 08:00:37 -0000 On Tue, 06 Jul 2010 10:44:54 +0300, Andriy Gapon wrote: > on 08/06/2010 11:02 Andriy Gapon said the following: >> I am trying to compile my ports with gcc44 instead of a base gcc. >> It seems that currently VirtualBox build system assumes that FreeBSD >> means base >> GCC only. For example, it unconditionally uses -fno-format-extensions >> and >> -fformat-extensions options. Those are extensions available in base >> GCC, but >> not in ports GCCs (at least for time being). >> I am not proficient in KBuild, so I don't have a patch, but I can make a >> suggestion that for these options CC and CXX should be tested in >> addition to >> KBUILD_TARGET. >> >> Additionally, two files seem to miss some include directives because of >> GCC >> changes outlined here: >> http://gcc.gnu.org/gcc-4.3/porting_to.html > > I would like to remind that the reported issues are still there with > VirtualBox > 3.2.6 and something like the following patch is still required. > > --- src/VBox/Main/freebsd/NetIf-freebsd.cpp.orig 2010-07-06 > 10:31:07.328680775 +0300 > +++ src/VBox/Main/freebsd/NetIf-freebsd.cpp 2010-07-06 10:31:28.000532682 > +0300 > @@ -44,6 +44,7 @@ > #include > > #include > +#include > #include > #include > > --- src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp.orig 2010-07-06 > 10:29:23.130414466 +0300 > +++ src/VBox/Main/freebsd/HostHardwareFreeBSD.cpp 2010-07-06 > 10:32:59.702484321 > +0300 > @@ -40,6 +40,7 @@ > # include > # include > # include > +# include > # include > # include > # include > > > And probably the following should just work too. > > --- Config.kmk.orig 2010-06-25 17:23:52.000000000 +0300 > +++ Config.kmk 2010-07-05 20:59:21.772469818 +0300 > @@ -2612,7 +2613,7 @@ > $(VBOX_GCC_WARN) -Wpointer-arith -Winline $(VBOX_GCC_Wno-pointer-sign) \ > -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes > -Wnested-externs \ > -Wimplicit-function-declaration -Werror-implicit-function-declaration \ > - -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common > -finline-limit=8000 \ > + -O2 -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 \ > $(VBOX_GCC_fno-stack-protector) $(VBOX_GCC_R0_OPT) $(VBOX_GCC_R0_FP) \ > -nostdinc -std=c99 > TEMPLATE_VBOXR0DRV_CFLAGS.x86 = -m32 -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > @@ -2621,7 +2622,7 @@ > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -Wundef > TEMPLATE_VBOXR0DRV_CXXFLAGS = -fno-exceptions -fno-rtti \ > $(VBOX_GCC_WARN) -Wpointer-arith -Winline \ > - -O2 -fno-format-extensions -fno-strict-aliasing -fno-common > -finline-limit=8000 \ > + -O2 -fno-strict-aliasing -fno-common -finline-limit=8000 \ > $(VBOX_GCC_fno-stack-protector) $(VBOX_GCC_R0_OPT) $(VBOX_GCC_R0_FP) \ > -nostdinc > TEMPLATE_VBOXR0DRV_CXXFLAGS.x86 = $(TEMPLATE_VBOXR0DRV_CFLAGS.x86) Thanks for the patch. We are aware of it and I already have it on my todo so it will just take some time. -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 10:38:20 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E10CF106564A; Tue, 6 Jul 2010 10:38:20 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A663B8FC1E; Tue, 6 Jul 2010 10:38:19 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA18252; Tue, 06 Jul 2010 13:38:18 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OW5Xd-000NAT-R8; Tue, 06 Jul 2010 13:38:17 +0300 Message-ID: <4C330798.5090606@freebsd.org> Date: Tue, 06 Jul 2010 13:38:16 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Bernhard Froehlich References: <4C0DF92C.9020204@icyb.net.ua> <4C32DEF6.1020409@freebsd.org> <84bf85053cb54d393398f37c0861d1fb@bluelife.at> In-Reply-To: <84bf85053cb54d393398f37c0861d1fb@bluelife.at> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-emulation@freebsd.org, vbox@freebsd.org Subject: Re: emulators/virtualbox-ose vs non-base gcc X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 10:38:21 -0000 on 06/07/2010 11:00 Bernhard Froehlich said the following: > Thanks for the patch. We are aware of it and I already have it on my todo > so it will just take some time. Thank you for the update. BTW, there is another issue with building VirtualBox using gcc44. $ VirtualBox VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/local/lib/virtualbox/VirtualBox.so",) failed: /usr/local/lib/virtualbox/VBoxREM.so: Undefined symbol "atan2l" zsh: exit 1 VirtualBox The problem is that base libstdc++ defines atan2l wrapper, but gcc44's libstdc++ doesn't do that, which I believe to be correct, because atan2l is defined in libm: $ objdump -T /usr/local/lib/virtualbox/VBoxREM.so | fgrep atan2l 0000000000000000 DF *UND* 0000000000000000 GLIBCXX_3.4 atan2l $ objdump -T /usr/lib/libstdc++.so | fgrep atan2l 00000000000519d0 g DF .text 0000000000000048 GLIBCXX_3.4 atan2l $ objdump -T /usr/lib/libm.so | fgrep atan2l 0000000000012230 g DF .text 000000000000035a FBSD_1.1 atan2l $ objdump -T /usr/local/lib/gcc44/libstdc++.so | fgrep atan2l $ Dependency on atan2l@GLIBCXX_3.4 is recorded because at link time linker uses /usr/lib/libstdc++.so. In turn, this happens because /usr/lib is explicitly specified in link search path (-L) and thus has higher precedence than built-in path (which includes /usr/local/lib/gcc44 for gcc44). I think that there is no reason to [explicitly] have /usr/lib (and also /usr/X11R6/lib) in virtualbox's library search path. Thus I propose the following patch: --- Config.kmk.orig 2010-06-25 17:23:52.000000000 +0300 +++ Config.kmk 2010-07-06 13:19:42.295639150 +0300 @@ -2794,8 +2795,6 @@ /usr/X11R6/include \ /usr/local/include TEMPLATE_VBOXR3EXE_LIBPATH += \ - /usr/lib \ - /usr/X11R6/lib \ /usr/local/lib else ifeq ($(KBUILD_TARGET),solaris) TEMPLATE_VBOXR3EXE_TOOL = GXX3PLAIN @@ -3236,8 +3235,6 @@ /usr/X11R6/include \ /usr/local/include TEMPLATE_VBOXMAINEXE_LIBPATH += \ - /usr/lib \ - /usr/X11R6/lib \ /usr/local/lib else ifeq ($(KBUILD_TARGET),solaris) TEMPLATE_VBOXMAINEXE_TOOL = GXX3PLAIN @@ -3564,8 +3561,6 @@ /usr/X11R6/include \ /usr/local/include TEMPLATE_VBOXQT4GUIEXE_LIBPATH += \ - /usr/lib \ - /usr/X11R6/lib \ /usr/local/lib endif ifeq ($(KBUILD_TARGET),solaris) @@ -3747,8 +3742,6 @@ /usr/X11R6/include \ /usr/local/include TEMPLATE_VBOXBLDPROG_LIBPATH += \ - /usr/lib \ - /usr/X11R6/lib \ /usr/local/lib else ifeq ($(KBUILD_HOST),solaris) TEMPLATE_VBOXBLDPROG_TOOL = GXX3PLAIN The patch is tested and works. Perhaps, there is a better way to achieve the same effect for FreeBSD. -- Andriy Gapon From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 6 15:58:32 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC280106566C for ; Tue, 6 Jul 2010 15:58:32 +0000 (UTC) (envelope-from mirya@zoc.com.ua) Received: from ex.volia.net (ex.volia.net [82.144.192.10]) by mx1.freebsd.org (Postfix) with ESMTP id 782DD8FC12 for ; Tue, 6 Jul 2010 15:58:32 +0000 (UTC) Received: from em.volia.net ([82.144.192.9]) by ex.volia.net with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1OW9ek-000C7t-Df for freebsd-emulation@freebsd.org; Tue, 06 Jul 2010 18:01:54 +0300 Received: from revelationless-overpass.volia.net ([77.122.14.168] helo=[192.168.0.28]) by em.volia.net with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1OW9ek-00054l-CN for freebsd-emulation@freebsd.org; Tue, 06 Jul 2010 18:01:54 +0300 From: Kyryll A Mirnenko aka Mirya Organization: ZOC To: freebsd-emulation@freebsd.org Date: Tue, 6 Jul 2010 18:01:51 +0300 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201007061801.52752.mirya@zoc.com.ua> X-Volia-Original-IP: 77.122.14.168 Subject: Re: Mounting VirtualBox vdi files X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 15:58:32 -0000 If you're creating the VM from scratch, you may use raw file-backed disk image along with VMDK format wrapper. You may create a sparse file # truncate -s 2G img or a preallocated one # dd if=/dev/zero of=img bs=1m count=2048 , then create a character device for it # mdconfig -a -t vnode -f img -u 4 , and wrap it with a vmdk container # VBoxManage internalcommands createrawvmdk -filename Img.vmdk -rawdisk /dev/md4 After that you may use Img.vmdk as any other disk image in VirtualBox, and mount /dev/md4* from the host machine. Just remember you'll need to run mdconfig after reboot, the md* devices are not preserved magically, and umount /dev/md4* before starting VBox. That's how i work with -current FreeBSD snapshots - they're cross-compiled and cross-installed in the host system (which is faster), then run in the VBox. -- Regards, Mirya ICQ #313898202 From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 10 05:26:26 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FCC2106564A; Sat, 10 Jul 2010 05:26:26 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 2339D8FC15; Sat, 10 Jul 2010 05:26:25 +0000 (UTC) Received: from lawrence1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 39D5C7E84A; Sat, 10 Jul 2010 15:26:23 +1000 (EST) Message-ID: <4C38047E.9010506@freebsd.org> Date: Sat, 10 Jul 2010 15:26:22 +1000 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-AU; rv:1.9.1.10) Gecko/20100704 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , John Baldwin Subject: vbox + gpxe + pxeboot = fail X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 05:26:26 -0000 Hi All, I had some frustration trying to get FreeBSD to pxeboot inside a vbox VM a while back. The thread is available here: http://lists.freebsd.org/pipermail/freebsd-emulation/2010-April/007681.html I left things for a while and came back to them yesterday with some fresh resolve to nut the problem out. I have some new insights I wanted to share. I'm using gpxe 1.0.1 from http://kernel.org/pub/software/utils/boot/gpxe/ and doing the builds on a Debian VM. To create a rom for the vbox AMD adapter types, I'm following the details at: http://www.etherboot.org/wiki/romburning/vbox I turned the instructions to pad the rom into a python script you can grab from here: http://people.freebsd.org/~lstewart/misc/vbox/rompad.py Here's what I've figured out so far: - The problem stems from the pxe boot rom environment provided by gpxe. It sends and receives packets correctly, but somehow the IP addresses get mangled (I think this happens inside gpxe) so it thinks the replies it is waiting for should be coming in on one IP address when they actually arrive on the real valid IP address. - Using the binary only vbox on Win XP which uses the Intel pxe boot rom has no problems and works perfectly i.e. further evidence this is isolated to gpxe - By changing the line "if (udpread_p->status > 0) {" to "if (udpread_p->status > 1) {" in sys/boot/i386/libi386/pxe.c, our pxeboot is able to work around the problem and I can pxeboot FreeBSD just fine. gpxe therefore is correctly reading the packets off the wire and passing them to our pxeboot code. gpxe just sets the failure status code because it thinks the packet is not the one we were waiting for because of the IP address being mismatched. The file in the gpxe distribution that I've been adding debug printf's to is: src/arch/i386/interface/pxe/pxe_udp.c By doing a "%s/DBG/dbg_printf/g" in that file, you get debugging output that shows you the failures and the IP address it thinks the pkt should be coming in on. In my case, it correctly sends UDP packets to 172.16.7.21, and then waits for the reply on 172.16.7.50 (but sees that the reply actually comes in on 172.16.7.43 which is the IP of the VM). Because .43 != .50, gpxe returns status failure (i.e. 1) but does still correctly read the pkt and pass it to our pxeboot hence why my hack of ignoring the status actually allows things to work. I've put an unmodified copy of pxe_udp.c at: http://people.freebsd.org/~lstewart/misc/vbox/pxe_udp.c If anyone is able to see any obvious problems in that file I'd love to hear about it. I suspect the problem is embedded somewhere a bit deeper in the gpxe code though so I'll ping the gpxe folks and see what they have to say. Cheers, Lawrence From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 10 07:04:37 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0079106566B; Sat, 10 Jul 2010 07:04:37 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 4DE628FC16; Sat, 10 Jul 2010 07:04:37 +0000 (UTC) Received: from lawrence1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 16BE37E84A; Sat, 10 Jul 2010 17:04:35 +1000 (EST) Message-ID: <4C381B82.40305@freebsd.org> Date: Sat, 10 Jul 2010 17:04:34 +1000 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-AU; rv:1.9.1.10) Gecko/20100704 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org References: <4C38047E.9010506@freebsd.org> In-Reply-To: <4C38047E.9010506@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , John Baldwin Subject: Re: vbox + gpxe + pxeboot = fail X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 07:04:37 -0000 On 07/10/10 15:26, Lawrence Stewart wrote: > Hi All, > > I had some frustration trying to get FreeBSD to pxeboot inside a vbox VM > a while back. The thread is available here: > > http://lists.freebsd.org/pipermail/freebsd-emulation/2010-April/007681.html > > I left things for a while and came back to them yesterday with some > fresh resolve to nut the problem out. I have some new insights I wanted > to share. > > I'm using gpxe 1.0.1 from > http://kernel.org/pub/software/utils/boot/gpxe/ and doing the builds on > a Debian VM. To create a rom for the vbox AMD adapter types, I'm > following the details at: > > http://www.etherboot.org/wiki/romburning/vbox > > I turned the instructions to pad the rom into a python script you can > grab from here: > > http://people.freebsd.org/~lstewart/misc/vbox/rompad.py > > > > Here's what I've figured out so far: > > - The problem stems from the pxe boot rom environment provided by gpxe. > It sends and receives packets correctly, but somehow the IP addresses > get mangled (I think this happens inside gpxe) so it thinks the replies > it is waiting for should be coming in on one IP address when they > actually arrive on the real valid IP address. > > - Using the binary only vbox on Win XP which uses the Intel pxe boot rom > has no problems and works perfectly i.e. further evidence this is > isolated to gpxe > > - By changing the line > "if (udpread_p->status > 0) {" > to > "if (udpread_p->status > 1) {" > in sys/boot/i386/libi386/pxe.c, our pxeboot is able to work around the > problem and I can pxeboot FreeBSD just fine. gpxe therefore is correctly > reading the packets off the wire and passing them to our pxeboot code. > gpxe just sets the failure status code because it thinks the packet is > not the one we were waiting for because of the IP address being mismatched. > > > > The file in the gpxe distribution that I've been adding debug printf's > to is: src/arch/i386/interface/pxe/pxe_udp.c > By doing a "%s/DBG/dbg_printf/g" in that file, you get debugging output > that shows you the failures and the IP address it thinks the pkt should > be coming in on. In my case, it correctly sends UDP packets to > 172.16.7.21, and then waits for the reply on 172.16.7.50 (but sees that > the reply actually comes in on 172.16.7.43 which is the IP of the VM). > Because .43 != .50, gpxe returns status failure (i.e. 1) but does still > correctly read the pkt and pass it to our pxeboot hence why my hack of > ignoring the status actually allows things to work. Some more useful info... gpxe has the correct IP address at the beginning when printed from "pxenv_udp_open()". Then in FreeBSD's pxe_open() in sys/boot/i386/libi386/pxe.c, the "if (rootip.s_addr == 0) {" statement evaluates true so we do another DHCP exchange by doing "bootp(pxe_sock, BOOTP_PXE);" in order to try and get our own copy of the various DHCP variables required to NFS boot. I think it's this second DHCP exchange that is somehow wiping gpxe's concept of the local IP as gpxe printfs done after the FreeBSD pxe_open() call return the bogus local IP. Sure enough, if I comment out the bootp() call and hardwire the rootip and rootpath, everything works as expected. The reason "rootip.s_addr == 0" appears to be because the "pxe_call(PXENV_GET_CACHED_INFO);" in our pxeboot's pxe_init() fails to pull cached values from gpxe. I tried upping PXE_BUFFER_SIZE in case we weren't supplying a large enough buffer to receive all the cached data but that didn't make any difference. So it appears there are two separate issues in our pxeboot's interaction with gpxe... first is we don't successfully manage to extract cached DHCP data from gpxe which causes us to do our own DHCP exchange in pxe_open() to get the info. Secondly, by doing the extra DHCP exchange, we're somehow trampling gpxe's concept of what the local IP is. Cheers, Lawrence From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 10 08:03:02 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86541106566C; Sat, 10 Jul 2010 08:03:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 3884A8FC08; Sat, 10 Jul 2010 08:03:02 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1OXV1Y-0005oN-Ni; Sat, 10 Jul 2010 11:03:00 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Lawrence Stewart In-reply-to: <4C38047E.9010506@freebsd.org> References: <4C38047E.9010506@freebsd.org> Comments: In-reply-to Lawrence Stewart message dated "Sat, 10 Jul 2010 15:26:22 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Jul 2010 11:03:00 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-emulation@freebsd.org, Pawel Jakub Dawidek , John Baldwin Subject: Re: vbox + gpxe + pxeboot = fail X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 08:03:02 -0000 Hi Lawrence, > Hi All, > > I had some frustration trying to get FreeBSD to pxeboot inside a vbox VM > a while back. The thread is available here: > > http://lists.freebsd.org/pipermail/freebsd-emulation/2010-April/007681.html > > I left things for a while and came back to them yesterday with some > fresh resolve to nut the problem out. I have some new insights I wanted > to share. > > I'm using gpxe 1.0.1 from > http://kernel.org/pub/software/utils/boot/gpxe/ and doing the builds on > a Debian VM. To create a rom for the vbox AMD adapter types, I'm > following the details at: > > http://www.etherboot.org/wiki/romburning/vbox > > I turned the instructions to pad the rom into a python script you can > grab from here: > > http://people.freebsd.org/~lstewart/misc/vbox/rompad.py > > > > Here's what I've figured out so far: > > - The problem stems from the pxe boot rom environment provided by gpxe. > It sends and receives packets correctly, but somehow the IP addresses > get mangled (I think this happens inside gpxe) so it thinks the replies > it is waiting for should be coming in on one IP address when they > actually arrive on the real valid IP address. > > - Using the binary only vbox on Win XP which uses the Intel pxe boot rom > has no problems and works perfectly i.e. further evidence this is > isolated to gpxe > > - By changing the line > "if (udpread_p->status > 0) {" > to > "if (udpread_p->status > 1) {" > in sys/boot/i386/libi386/pxe.c, our pxeboot is able to work around the > problem and I can pxeboot FreeBSD just fine. gpxe therefore is correctly > reading the packets off the wire and passing them to our pxeboot code. > gpxe just sets the failure status code because it thinks the packet is > not the one we were waiting for because of the IP address being mismatched. > > > > The file in the gpxe distribution that I've been adding debug printf's > to is: src/arch/i386/interface/pxe/pxe_udp.c > By doing a "%s/DBG/dbg_printf/g" in that file, you get debugging output > that shows you the failures and the IP address it thinks the pkt should > be coming in on. In my case, it correctly sends UDP packets to > 172.16.7.21, and then waits for the reply on 172.16.7.50 (but sees that > the reply actually comes in on 172.16.7.43 which is the IP of the VM). > Because .43 != .50, gpxe returns status failure (i.e. 1) but does still > correctly read the pkt and pass it to our pxeboot hence why my hack of > ignoring the status actually allows things to work. > > I've put an unmodified copy of pxe_udp.c at: > > http://people.freebsd.org/~lstewart/misc/vbox/pxe_udp.c > > If anyone is able to see any obvious problems in that file I'd love to > hear about it. I suspect the problem is embedded somewhere a bit deeper > in the gpxe code though so I'll ping the gpxe folks and see what they > have to say. > > Cheers, > Lawrence as far as i remember, the gpxe rom only worked with direct connected, no bridge nor nat, so I guess you figured out why :-) danny From owner-freebsd-emulation@FreeBSD.ORG Sat Jul 10 08:53:39 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07BF7106566B; Sat, 10 Jul 2010 08:53:39 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 77D728FC12; Sat, 10 Jul 2010 08:53:38 +0000 (UTC) Received: from lawrence1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id B7D247E84A; Sat, 10 Jul 2010 18:53:36 +1000 (EST) Message-ID: <4C383510.5040307@freebsd.org> Date: Sat, 10 Jul 2010 18:53:36 +1000 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-AU; rv:1.9.1.10) Gecko/20100704 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org References: <4C38047E.9010506@freebsd.org> <4C381B82.40305@freebsd.org> In-Reply-To: <4C381B82.40305@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , John Baldwin Subject: Re: vbox + gpxe + pxeboot = fail [SOLVED] X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2010 08:53:39 -0000 On 07/10/10 17:04, Lawrence Stewart wrote: > On 07/10/10 15:26, Lawrence Stewart wrote: >> Hi All, >> >> I had some frustration trying to get FreeBSD to pxeboot inside a vbox VM >> a while back. The thread is available here: >> >> http://lists.freebsd.org/pipermail/freebsd-emulation/2010-April/007681.html >> >> I left things for a while and came back to them yesterday with some >> fresh resolve to nut the problem out. I have some new insights I wanted >> to share. >> >> I'm using gpxe 1.0.1 from >> http://kernel.org/pub/software/utils/boot/gpxe/ and doing the builds on >> a Debian VM. To create a rom for the vbox AMD adapter types, I'm >> following the details at: >> >> http://www.etherboot.org/wiki/romburning/vbox >> >> I turned the instructions to pad the rom into a python script you can >> grab from here: >> >> http://people.freebsd.org/~lstewart/misc/vbox/rompad.py >> >> >> >> Here's what I've figured out so far: >> >> - The problem stems from the pxe boot rom environment provided by gpxe. >> It sends and receives packets correctly, but somehow the IP addresses >> get mangled (I think this happens inside gpxe) so it thinks the replies >> it is waiting for should be coming in on one IP address when they >> actually arrive on the real valid IP address. >> >> - Using the binary only vbox on Win XP which uses the Intel pxe boot rom >> has no problems and works perfectly i.e. further evidence this is >> isolated to gpxe >> >> - By changing the line >> "if (udpread_p->status > 0) {" >> to >> "if (udpread_p->status > 1) {" >> in sys/boot/i386/libi386/pxe.c, our pxeboot is able to work around the >> problem and I can pxeboot FreeBSD just fine. gpxe therefore is correctly >> reading the packets off the wire and passing them to our pxeboot code. >> gpxe just sets the failure status code because it thinks the packet is >> not the one we were waiting for because of the IP address being mismatched. >> >> >> >> The file in the gpxe distribution that I've been adding debug printf's >> to is: src/arch/i386/interface/pxe/pxe_udp.c >> By doing a "%s/DBG/dbg_printf/g" in that file, you get debugging output >> that shows you the failures and the IP address it thinks the pkt should >> be coming in on. In my case, it correctly sends UDP packets to >> 172.16.7.21, and then waits for the reply on 172.16.7.50 (but sees that >> the reply actually comes in on 172.16.7.43 which is the IP of the VM). >> Because .43 != .50, gpxe returns status failure (i.e. 1) but does still >> correctly read the pkt and pass it to our pxeboot hence why my hack of >> ignoring the status actually allows things to work. > > Some more useful info... > > gpxe has the correct IP address at the beginning when printed from > "pxenv_udp_open()". Then in FreeBSD's pxe_open() in > sys/boot/i386/libi386/pxe.c, the "if (rootip.s_addr == 0) {" statement > evaluates true so we do another DHCP exchange by doing "bootp(pxe_sock, > BOOTP_PXE);" in order to try and get our own copy of the various DHCP > variables required to NFS boot. > > I think it's this second DHCP exchange that is somehow wiping gpxe's > concept of the local IP as gpxe printfs done after the FreeBSD > pxe_open() call return the bogus local IP. Sure enough, if I comment out > the bootp() call and hardwire the rootip and rootpath, everything works > as expected. > > The reason "rootip.s_addr == 0" appears to be because the > "pxe_call(PXENV_GET_CACHED_INFO);" in our pxeboot's pxe_init() fails to > pull cached values from gpxe. I tried upping PXE_BUFFER_SIZE in case we > weren't supplying a large enough buffer to receive all the cached data > but that didn't make any difference. > > So it appears there are two separate issues in our pxeboot's interaction > with gpxe... first is we don't successfully manage to extract cached > DHCP data from gpxe which causes us to do our own DHCP exchange in > pxe_open() to get the info. Secondly, by doing the extra DHCP exchange, > we're somehow trampling gpxe's concept of what the local IP is. Please forgive the barrage of emails, but I've been in way over my head and hoping for some enlightenment. After persisting a bit longer and chatting with the helpful Doug White on IRC, I think I've got it all nutted out. Here goes... I did some more debugging and the "pxe_call(PXENV_GET_CACHED_INFO);" in our pxeboot's pxe_init() doesn't fail like I previously speculated, and in fact seems to work just fine and we end up with a copy of gpxe's cached DHCP data in the "bootplayer" variable, which is of type BOOTPLAYER defined as a struct in . We then fall through into our pxe_open() and check "if (rootip.s_addr == 0) {", and because rootip is always == 0, we fall into the "if". Why is "rootip" always == 0 I hear you ask? Excellent question! Because we never actually populate it (or any other necessary variables) with the cached data we stashed in "bootplayer" back in pxe_init(). This is true even in the case of the working Intel pxe boot rom. So here's the tricky bit. In the gpxe case, the rom's DHCP request includes a uid string of some bytes and my ISC DHCP server returns the 172.16.7.43 IP address to it. Then in the FreeBSD pxeboot binary we do the unneeded bootp() call in pxe_open(), but we don't include the uid value used by gpxe, so the DHCP server thinks this is a different client and hands back a different IP address (you guessed it, 172.16.7.50). So gpxe had IP .43, FreeBSD's boot loader updates it to .50 and everything falls in a heap because gpxe thinks the packets inbound to .43 are bogus. In the Intel pxe rom case, the rom doesn't include a uid in it's DHCP request, so when FreeBSD's pxeboot code does the unneeded DHCP request, it gets the same IP back and everything keeps working. *phew* Ok so what needs fixing... 1. FreeBSD's pxeboot code should try and use the cached data it gets from the pxe boot rom up front. I think this means patching our pxe_open() to fill in values from the "bootplayer" cache variable and then only doing the bootp() call if the cached values are insufficient. 2. If in pxeboot we realise the cached data doesn't have all the options we need to continue and we do have to do our own bootp() call to force a new DHCP exchange, we should use the same uid (which I'm hoping is stashed in the bootplayer variable - haven't confirmed yet) so that we get the same IP back from the DHCP server that was assigned to the pxe boot rom. 3. There is still the question of why packets are inbound to .43 at all after our bootp() call gets the new IP address of .50. I'm unsure if this is gpxe still sending packets using .43 but listening for packets on .50 or if the FreeBSD pxeboot binary has cached the old IP and continues to tell gpxe to use it. This needs to be tracked down. Step 2 may be unnecessary if we resolve this problem as things should be able to happily switch over to the new IP address and keep working. Cheers, Lawrence