public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: per_sundstrom@yahoo.com
To: devel@edk2.groups.io
Subject: Initial PXE boot over IPv6
Date: Fri, 27 Mar 2020 08:51:26 -0700	[thread overview]
Message-ID: <ZmVE.1585324286657675586.AVVl@groups.io> (raw)

[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]

Hi,
I want to exclusively use PXE/IPv6 when deploying a set of physical machines with some QEMU/KVM virtual machines on top.

So far, the only [hacky] way I have managed to do this is to:
1) Bring up a VM with OVMF
2) Set the wanted boot-order with PXE over IPv6 at the top
3) Save this to the NVRAM
4) Repete the above for a set of VMs with different MAC addresse
5) Keep these NVRAMs as "canned" templates (with associated fixed MACs)
4) Later use one of these NVRAM as a template for VMs with the associated MAC

Obviously this does not scale to hundreds of VMs

Reading through the code is seems that it might be possible to disable PXE over IPv4 with
the PCD variable "IPv4PXESupport" = <one byte binary zero>.

I have tried with
<qemu:arg value='-fw_cfg'/>
<qemu:arg value='opt/ovmf/X-PcdIPv4PXESupport,file=/var/lib/libvirt/qemu/nvram/zero'/>

where the file is a one byte binary zero and I have verified that it shows up in /sys/firmware/qemu_fw_cfg.
linux-u7u9:/sys/firmware/qemu_fw_cfg/by_name # ls opt/ovmf/X-PcdIPv4PXESupport/
key  name  raw size
linux-u7u9:/sys/firmware/qemu_fw_cfg/by_name # cat opt/ovmf/X-PcdIPv4PXESupport/size
1
linux-u7u9:/sys/firmware/qemu_fw_cfg/by_name # od -b opt/ovmf/X-PcdIPv4PXESupport/raw
0000000 000
Is this something that should work, or is this variable compiled in ?
Are there other ways of acomplishing what I try to do ?

Thanks,

/Per

[-- Attachment #2: Type: text/html, Size: 1872 bytes --]

             reply	other threads:[~2020-03-27 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 15:51 per_sundstrom [this message]
2020-03-27 17:05 ` [edk2-devel] Initial PXE boot over IPv6 Andrew Fish
2020-03-27 17:38   ` per_sundstrom
2020-03-27 23:01   ` Laszlo Ersek

Reply instructions:

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZmVE.1585324286657675586.AVVl@groups.io \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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