> On Fri, Mar 23, 2018 at 1:04 PM, Rodney W. Grimes
> <freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > [ Charset UTF-8 unsupported, converting... ]
> >> On Fri, Mar 23, 2018 at 9:58 AM, Rodney W. Grimes
> >> <freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >> >> On Fri, Mar 23, 2018 at 3:56 AM, Joe Maloney <jmalo...@ixsystems.com>
> >> >> wrote:
> >> >> > We narrowed the issue down to how vm-bhyve attaches a null.iso when
> >> >> > starting
> >> >> > the VM.
> >> >> >
> >> >>
> >> >> What exactly are the contents of this null.iso? It sounds like we're
> >> >
> >> > touch "null.iso"
> >> > -rw-r--r-- 1 root wheel 0 Dec 3 22:55 /home/vmbhyve/.config/null.iso
> >> >
> >> > It is litterly a 0 byte file. This is just there to appease windows
> >> > installer that you have a cd drive.
> >> >
> >> > You can test with bhyve yourself this problem by adding:
> >> > -s 3:0,ahci-cd,${vm_dir}/.config/null.iso
> >> > to your bhyve command.
> >> >
> >>
> >> Thanks for that! A couple hundred printf's later, I think this might
> >> be a firmware bug or something of the sort (?).
> >>
> >> In this loop [1], the address at 'dp' is getting immediately clobbered
> >> by the efi_lookup_devpath on every iteration, so we end up looking at
> >> basically all of the partitions and this null.iso unfortunately meets
> >> this criteria [2] for removable media with no media present.
> >> Therefore, we detect absolutely no disks.
> >>
> >> The only candidate in efi_lookup_devpath [3] is the firmware itself
> >> having overwritten the devpath at that address. We can confirm this
> >> with a printf just after the efi_lookup_devpath- the pointer it's
> >> returning is in fact exactly match 'dp' every single time.
> >>
> >> Is there a newer/different firmware you can try? This seems like
> >> really peculiar behavior for a firmware to be exhibiting.
> >
> > What happened to the boot device on the hd?
> > There should be another -s x:0, ahci-hd drive that it boots from.
> > -s 4:0,ahci-hd,${vm_dir}/${vmname}/disk0.img
> >
>
> Right, it's there but we think it's removable media with no media
> present because of the above-mentioned clobbering by the firmware. We
> could probably work around it for this specific case, but I don't know
> if that's a great idea- there be snakes here...
Perhaps take a look at how and why this was working fine with
the forth boot code?
--
Rod Grimes rgri...@freebsd.org
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
