Date: Thu, 12 Jan 2017 08:10:08 +0100 From: Nils <internationils@gmx.net> To: freebsd-virtualization@freebsd.org Subject: Re: Help getting vbox .vdi imares to run under Freenas Message-ID: <9ec1e04b-28f7-5a09-bda3-0a5b1507c652@gmx.net> In-Reply-To: <d3ac7c00-3f0f-635a-819a-ed23ca17f28a@freebsd.org> References: <9bcff734-5ed5-a228-df5e-5ff35cf9e3ff@gmx.net> <4b65f427-07dc-8b0c-1ac9-59c3c1533336@freebsd.org> <201dbbc3-53de-ba98-6a88-16dd06444bc5@gmx.net> <13af4cda-44d7-5b2c-7dbe-862b3fc8be40@freebsd.org> <d3ac7c00-3f0f-635a-819a-ed23ca17f28a@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-01-08 19:04, Peter Grehan wrote: > There's some additional info at > https://github.com/pr1ntf/iohyve/issues/228 - >> grub> ls >> (hd0) (cd0) (host) >> grub> ls (hd0) >> Device hd0: No known filesystem detected - Total size 16777216 sectors > ... so it looks like grub isn't able to auto-detect the partitions. Anything that I can do to debug that? https://github.com/grehan-freebsd/grub2-bhyve doesn't appear very active... would runningit under gdb make sense, or are there any other diagnostics that you can think of? All the diagnostics I've done have said that the image looks good (extracting MBR, looking at it with fdisk -l under Linux, etc.) Thanks Nils
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ec1e04b-28f7-5a09-bda3-0a5b1507c652>