[Qemu-devel] [Bug 1543163] Re: VMs unable to boot from network with e1000 since 2.2

2019-04-16 Thread Thomas Huth
Ok, thanks for checking. Closing now. ** Changed in: qemu Status: Incomplete => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1543163 Title: VMs unable to boot from network

[Qemu-devel] [Bug 1543163] Re: VMs unable to boot from network with e1000 since 2.2

2019-04-16 Thread John Doe
I have 3.10 and I managed to boot with e1000 at least in BIOS mode. I am not sure about UEFI mode, because I get no output on "screen" for whatever, perhaps unrelated reason. Anyway, I think we may close it for now. -- You received this bug notification because you are a member of qemu-

[Qemu-devel] [Bug 1543163] Re: VMs unable to boot from network with e1000 since 2.2

2019-04-15 Thread Thomas Huth
Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1543163] Re: VMs unable to boot from network with e1000 since 2.2

2016-08-08 Thread John Doe
The UEFI PXE issue was caused by a typo in DHCP server config file; the server then did not send DHCP option, if I remember correctly, 67. Nevertheless, that inspired me and I will further investigate the original issue with SCCM and focus on DHCP options. -- You received this bug notification

[Qemu-devel] [Bug 1543163] Re: VMs unable to boot from network with e1000 since 2.2

2016-08-07 Thread John Doe
Probably the same issue in different scenario: DHCP server is running on the host machine (VMs use virtual NICs connected to a bridge) and is also configured to do PXE, which works, but only when VMs are launched in BIOS mode. When launched in UEFI mode using Tianocore, they fail. Now the