From owner-freebsd-virtualization@freebsd.org Sun Jan 8 17:22:12 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20976CA5C9F for ; Sun, 8 Jan 2017 17:22:12 +0000 (UTC) (envelope-from internationils@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75FAF12D9 for ; Sun, 8 Jan 2017 17:22:10 +0000 (UTC) (envelope-from internationils@gmx.net) Received: from [10.0.2.15] ([87.174.152.48]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LxMgg-1cWM0r2yfi-016zFd for ; Sun, 08 Jan 2017 18:21:59 +0100 Subject: Re: Help getting vbox .vdi imares to run under Freenas To: freebsd-virtualization@freebsd.org References: <9bcff734-5ed5-a228-df5e-5ff35cf9e3ff@gmx.net> <4b65f427-07dc-8b0c-1ac9-59c3c1533336@freebsd.org> From: Nils Message-ID: <201dbbc3-53de-ba98-6a88-16dd06444bc5@gmx.net> Date: Sun, 8 Jan 2017 18:21:58 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.5.1 MIME-Version: 1.0 In-Reply-To: <4b65f427-07dc-8b0c-1ac9-59c3c1533336@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:06Qo9ua3KV68RFEV0gCYAV20A2OiKSbYWqEKKa1fvxzVxE2vOFp QJdzIj2E8uF3iuWrLuywSUQtXSzgOQhj3+eUoHBjMlx7XITtWqIQnxpzc2XoaNqIoUkdMEl IdNng/i7mrBJ96Wt2usJK9S+UR2Wa255lPfDemCctV7geW5Y4a01VJxXZpMVQnoNAiwfeQ6 EZznX1hdYjTt/xWIy0CSQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:btVhgAP5Xcg=:RF1Xn2oQ5lQIZbBhCCv9SE 4xofApGjdzvqesLSwV0UksiofPvpSlZByv/qzaxZh7uToMDbfTG9EAO4ruf/nu/PkY/e8H8LJ mg5FcK2rMhcYsVcyceFSGshesuLyujb8TGfBxU0kDhQunHDiQxwowBuqfi2AGEOXlJ8J+FM16 Ck3/8w/tqSXs4LbmqJJGY1eTUy2QYlwHpVvePE996Uy/19VN0EfSYfGgpEfnWQyiazqRr2NoQ 9pxwBn2ENNx3XEbak6+xWZBjbIz9G9VeBgmKOF4VU7tfXdq+RPxZ+PTjpf6X0rBS2SFetZ/84 R1fFRqSImVbrzTfe6SAhQSmxgCGobxtEDZRVPN7h9We/3nYIiezVCSnZJjsnBwkp2ExYnHGY/ 1EyY7YygQzRd5afVu4ih/l3avk7tTdmCz6UMH5lWkj0BHQTMuohkBhb1UeYr9zWz8X9Z09pjE eZDXmhXrPn8BTnmJshIEymIGNQ+iJZcd0ynoFeoom4nx1PeUEibI1W/gcWkuzU88Z72Y7qdv3 yR0vf7ZTAhkZfvwaT3cKNtiIIFsTTmXULBozYNjkA3dK7aupi4BFohzcC51g+yzOhVQGywDID hewr0a4dh8n9s7isEC1uailqY7ILv5NuAQ47UVYqrg0wbGYmVWeopwVPnskgOabiQVRXibjcy +5IGOltY0atnfAFlrAMv4QrJnqfL5PYWFWLDZauU0A4RMpqOAb3ilhJXuGFLfJlt1TvHc/h0b /DlSalxM9mfM7KnNjAY3/R1c30pSlYFgeYiXSbH5whmISxgZcmkvfq1qBL4ROPC6E7/M6ZKY1 ZwJhvoC0ZkTxKhCv8nh7LRC8Z+xVJQPgefY5Yk2hM4EyD00LroV8DiH2QkN0STU9yHO0DD8IO uBcmG5j2AdKJq3oAfPZb2Hl0FSPgySR4gY1AbmRr8kxnUi4QcoF+++U7Kr2wDzFgtbV6N1pyn 8afj0x/U/Yz6oJswBF8Do9o9Dw3C3Dr8fJZpzB//oIAYp2cmwNegk5jWZvgYL1epMsAOsSKzA KjM5wbQUPjy/E8KyoqEmlSI= X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 08 Jan 2017 17:22:12 -0000 On 2017-01-08 18:01, Allan Jude wrote: > On 2017-01-08 10:18, Nils wrote: >> Hello, I'm fighting to get vbox vdi images to run under FreeNAS and >> don't know what else to try. I've filed and commented on these two bugs: >> https://github.com/pr1ntf/iohyve/issues/227 >> https://github.com/pr1ntf/iohyve/issues/228 >> >> ...but I think the problem is not with bhyve itself or with iohyve, but >> either with grub-bhyve or ZFS. >> Running installation ISOs etc. works fine, but I need to get the VDIs >> going., >> >> Any pointers are welcome... >> Thanks >> Nils >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" >> > How are you converting the .VDI to a raw image? bhyve does not yet > support the .VDI format, only raw. > I've done the conversion to raw with both VBoxManage and qemu-img, same result. I'm not sure where to add teh text flag, but I don't think that it's a problem, as grub should be running in a text console. What bothers me is that grub at the prompt claims not to recognize the (hd0): |grub> ls (hd0) Device hd0: No known filesystem detected - Total size 16777216 sectors ... where extracting the MBR and looking at it with fdisk shows the partitions... |