Hey Andrei,
sorry for the late reply.
On 11.01.2017 17:34, Andrei Borzenkov wrote:
You misunderstand. What is missing is the way to transport information
about VLAN from firmware (UEFI) to GRUB. How it is represented*inside*
GRUB is technical detail.
As this scenario is not uncommon, think hypervisor host with just one
interface which is a VLAN trunk, how should I go about filing issues for
this?
Sure you can, but please understand that someone who has access to
hardware in question needs to actually write a patch. You can help by at
least providing information about UEFI device tree here - start with
netbooting EFI Shell and providing output of "devtree" and "dh".
I configured a VLAN to be used for PXE but it doesn't appear anywhere in
the devtree or dh output on the UEFI cli.
There are variables like "VLAN" there, but all show "0".
Did I miss anything here or could it be that the VLAN used for the
initial PXE is not populated / exposed to the NBE?
Regards
Christian
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
