On Wed, Mar 5, 2014 at 7:22 AM, Kurt Lidl wrote:
>
>
> I ran into this same problem a couple of weeks ago when I first played
> with the ZFS boot support in userboot.so.
>
> The following set of operations on the hypervisor can be used to add
> bootable support to your zfs installation.
>
> (I don
Hi,
I encountered problems with the new changes to userboot
to boot ZFS.
About a month ago, I created a FreeBSD 10 VM with the following
layout:
=> 34 419430333 md0 GPT (200G)
341281 freebsd-boot (64K)
16220971522 freebsd-ufs (1.0G)
2097314
Hi Craig,
Can this flag be passed via bhyveload, and if so, how?
It can't yet: the API to userboot has to be changed to allow this to
be passed through.
later,
Peter.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/
On Tue, Mar 4, 2014 at 2:24 PM, Peter Grehan wrote:
> Hi Craig,
>
>
>> ZFS: i/o error - all block copies unavailable
>>
>> I don't fully understand all this logic. Is there a bug that can be fixed
>> here?
>
>
> Yes - a flag needs to be passed to userboot to tell it to ignore ZFS
> filesystems.
Hi Craig,
ZFS: i/o error - all block copies unavailable
I don't fully understand all this logic. Is there a bug that can be fixed here?
Yes - a flag needs to be passed to userboot to tell it to ignore ZFS
filesystems. This is analogous to the decision to use boot2 (implicit
UFS) vs zfsboo
Hi,
I encountered problems with the new changes to userboot
to boot ZFS.
About a month ago, I created a FreeBSD 10 VM with the following
layout:
=> 34 419430333 md0 GPT (200G)
341281 freebsd-boot (64K)
16220971522 freebsd-ufs (1.0G)
2097314
