[Bug 714629] Re: BIOS doesn't load when read() returns less than the full ROM length
This seems to have been fixed by commit 1f40547f5ce0c135faa7d14f066b97002fd8c204. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/714629 Title: BIOS doesn't load when read() returns less than the full ROM length Status in QEMU: Fix Released Bug description: When qemu is running over a 9p filesystem (e.g. when running underneath -virtfs of another qemu), and probably some other network filesystems, it fails to read its BIOS image. This is because it uses a single low-level read() call on the bios.bin, asking for the full file. However read() may return less than the full length, and it's the caller's responsibility to call it repeatedly if necessary. When read does come up short, qemu doesn't repeat the call, and reports an error instead. The attached patch fixes the one problem I saw, but I haven't tried to cover the general case (e.g. extension ROMs). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/714629/+subscriptions
[Bug 714629] Re: BIOS doesn't load when read() returns less than the full ROM length
Fix included in QEMU v4.0.0. ** Changed in: qemu Status: New => 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/714629 Title: BIOS doesn't load when read() returns less than the full ROM length Status in QEMU: Fix Released Bug description: When qemu is running over a 9p filesystem (e.g. when running underneath -virtfs of another qemu), and probably some other network filesystems, it fails to read its BIOS image. This is because it uses a single low-level read() call on the bios.bin, asking for the full file. However read() may return less than the full length, and it's the caller's responsibility to call it repeatedly if necessary. When read does come up short, qemu doesn't repeat the call, and reports an error instead. The attached patch fixes the one problem I saw, but I haven't tried to cover the general case (e.g. extension ROMs). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/714629/+subscriptions
[Qemu-devel] [Bug 714629] Re: BIOS doesn't load when read() returns less than the full ROM length
** Patch added: Fix loading of BIOS file over 9p/network filesystems https://bugs.launchpad.net/bugs/714629/+attachment/1836057/+files/rom_read.patch -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/714629 Title: BIOS doesn't load when read() returns less than the full ROM length Status in QEMU: New Bug description: When qemu is running over a 9p filesystem (e.g. when running underneath -virtfs of another qemu), and probably some other network filesystems, it fails to read its BIOS image. This is because it uses a single low-level read() call on the bios.bin, asking for the full file. However read() may return less than the full length, and it's the caller's responsibility to call it repeatedly if necessary. When read does come up short, qemu doesn't repeat the call, and reports an error instead. The attached patch fixes the one problem I saw, but I haven't tried to cover the general case (e.g. extension ROMs).
