On Sat, 2020-07-18 at 10:46 +0200, Benjamin Baier wrote:
> On Fri, 17 Jul 2020 23:50:06 -0700
> Aaron Miller <
> aa...@iforgotmy.name
> > wrote:
> 
> > On Fri, 2020-06-12 at 17:46 -0400, George wrote:
> > > On 2020-06-12 11:17 a.m., George wrote:
> > > > [...]
> > 
> > Hey George,
> > 
> > I don't know if you resolved this, but I was able to get
> > further
> > than this loosely following Benjamin's instructions. I skipped
> > the part about the virtio-modules which doesn't seem to be
> > necessary now (and the link is 404 now anyway).
> > 
> > I was able to go through the menu (starting with Install, and
> > skipping the modprobe commands) but DHCP didn't work, and I'm
> > not sure what's broken.
> > 
> > To answer your question, you need to press Esc _after_
> > selecting Install. Maybe that's why you saw the "boot>"
> > prompt.
> > 
> > It worked for me and I just ran lsmod since I didn't have any
> > modules to insert:
> > 
> > ~ # lsmod
> > Module                  Size  Used by
> > virtio_blk             20480  0
> > virtio_net             32768  0
> > virtio_pci             24576  0
> > virtio_ring            24576  3
> > virtio_blk,virtio_net,virtio_pci
> > virtio                 16384  3
> > virtio_blk,virtio_net,virtio_pci
> > 
> > I hope this helps, and please let me know if you or anyone
> > else
> > has an idea of why DHCP isn't working in the guest VM.
> 
> With the virtio modules now included in the installer you can
> skip my
> tutorial. You only need to change bootparameters in GRUB to pass
> vga=off console=ttyS0,115200n8 to the linux kernel.

OK good to know, thanks. I was unaware that the boot parameters
could be specified there rather than by editing TXT.CFG in the
boot image.

> As for DHCP, it depends on your config: is pf blocking DHCP
> traffic?

No.

> is the bridge/switch interface set up correctly?

Perhaps not. I tried a variety of things with bridge0, like
attempting to add my host's egress interface (iwm0) to it,
resulting in a "Device busy" error. I also tried creating a vether
device and attaching that, as described in the Virtualization FAQ.

Using tcpdump on tap0, I was able to see bootp and arp packets
coming from the guest. I did not see any replies from the host
though. Running tcpdump on bridge0 did not show any packets no
matter what I tried.

> is sysctl net.inet.ip.{m,}forwarding set to 1?

Yes.

> do you use vmctl -L (local interface)?
> 

I tried -L but vmctl didn't seem to like that in combination with
a VM specified in vm.conf. I also tried replacing 'interface {
switch "uplink" }' with 'local interface' but that didn't seem to
make a difference.

Thanks for the help so far!
--Aaron

Reply via email to