Re: UEFI-PXE boot to grub2 with BIOS configured VLAN tagging?

[Andrei Borzenkov]

11.01.2017 14:30, Christian Rohmann пишет:
> On 01/09/17 11:55, Andrei Borzenkov wrote:
>> The question is not how to configure VLAN, but how to detect, which
>> VLAN was used to bootstrap us. grub patches I mentioned simply
>> explicitly send tagged VLAN packets over base interface, so they
>> should work on every platform. Revisiting these patches, they do not
>> add user interface (commands) to configure VLAN interfaces though.
>>
>> http://git.savannah.gnu.org/cgit/grub.git/commit/?h=pfsmorigo/vlantag
> 
> So there are two "issues" here:
> 
> 1. The lack of transporting the information about a VLAN tag being used
> to bootstrap (UEFI-PXI boot to Grub2) into grub itself. As I understand
> such variables are usually available with the "net_pxe_" prefix?
> 

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.

> 2. User interface to even manually do anything regarding vlans. This
> would at least enable some sort of "hard coding" a VLAN and continue to
> boot even without the dynamic info about the used VLAN from issue 1.
> 

Yes.

> 
> 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".

Alternatively you can provide step by step instructions how to build
QEMU configuration that supports netboot over VLAN. Then I may look into it.

Anyway, at this point I suppose this discussion belongs to grub-devel :)