Subject: [9front] Advice on PXE boot, "no boot filename received"
Date: Tue, 6 Sep 2022 20:18:44 +0000 [thread overview]
Message-ID: <20220906201844.GA2911881@tilde.team> (raw)
I am trying to PXE boot a laptop terminal via a wired ethernet connection to a 9front qemu guest, but
I can't get past "No boot filename received" on the terminal.
I thought it was a problem of the terminal and the qemu guest not seeing each other's network,
however after the terminal boots from its local disk, I can telnet from the terminal
to the guest via a port I've forwarded in qemu, and I can ping the terminal from the
qemu guest. So at least it seems possible for the two to reach each other.
Maybe I need to configure a bridge as suggested in IRC, but perhaps my config is wrong though
so I would appreciate any help.
Here's the config I have:
cpu% cat /lib/ndb/local
# the qemu guest
sys=gene ether=525400123456 authdom=qemu auth=10.0.2.15 ip=10.0.2.15 tftp=10.0.2.15
ipnet=qemu ip=10.0.2.0 ipmask=255.255.255.0
# the laptop terminal
sys=ursula dom=ursula.qemu ether=0016d3c16297 ip=10.42.0.156 bootf=/386/9bootpxe
cpu% cat /cfg/gene/cpurc
cpu% cat /cfg/pxe/0016d3c16297
And the qemu startup:
qemu-system-x86_64 -enable-kvm -cpu host -m 2G \
-net nic,model=virtio,macaddr=52:54:00:12:34:56 \
-device virtio-scsi-pci,id=scsi \
-drive if=none,id=vd0,file=9front.qcow2.img \
-device scsi-hd,drive=vd0 \
Just out of curiosity, I've wondered why the bootf and the bootfile are different (and there is no 9pc in /386/
on the qemu guest). Is 9pc somewhere else at first?
next reply other threads:[~2022-09-06 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 20:18 wakyct [this message]
2022-09-08 9:24 ` wakyct
2022-09-08 19:02 ` Xiao-Yong Jin
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).