public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
* Using UEFI Network Protocols in QEMU-OVMF
@ 2022-07-12 14:31 Ayush Singh
  0 siblings, 0 replies; only message in thread
From: Ayush Singh @ 2022-07-12 14:31 UTC (permalink / raw)
  To: devel; +Cc: mikuback, michael.d.kinney, jabeena.b.gaibusab, jiewen.yao

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

Hello everyone. I am trying to implement networking in Rust std using 
the TCP4 and TCP6 UEFI Protocols (It is required for running Rust CI 
tests). For providing the network device in qemu, I am using the 
following options:

```

-netdev user,id=net0,hostfwd=tcp::12345-:12345 -device 
virtio-net-pci,netdev=net0,mac=00:00:00:00:00:00

```

I am using these options since they are what are used by other Rust qemu 
targets. Anyway, the thing is, when I query for 
`EFI_TCP6_SERVICE_BINDING_PROTOCOL`, using the 
`BootServices->LocateHandle()` function, I get a buffer containing 8 
Handles.

Since I only supply one network device, I expected to get at-most 1 
device with this handle. So can anyone explain what is going on here? 
Can the same device publish the Service binding protocol multiple times?

Using `-net none` option gives 0 Handles, so that works how I would expect.


Yours Sincerely

Ayush Singh

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-07-12 14:31 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-07-12 14:31 Using UEFI Network Protocols in QEMU-OVMF Ayush Singh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox