| Message ID | 20230901120822.1.Ic1e930902ae178ecee565ab48b9579482d03056c@changeid |
|---|---|
| State | Accepted |
| Commit | 9804e572cf1ade7a0aae000740e6159a1e5394fd |
| Delegated to: | Bin Meng |
| Headers | show |
| Series | x86: doc: Document the -cdrom issues I ran into | expand |
On Sat, Sep 2, 2023 at 2:08 AM Simon Glass <sjg@chromium.org> wrote: > > Add a note about using -cdrom with QEMU. > > Suggested-by: Bin Meng <bmeng@tinylab.org> > Signed-off-by: Simon Glass <sjg@chromium.org> > --- > > doc/board/emulation/qemu-x86.rst | 3 +++ > 1 file changed, 3 insertions(+) > Reviewed-by: Bin Meng <bmeng@tinylab.org> applied to u-boot-86/next, thanks!
diff --git a/doc/board/emulation/qemu-x86.rst b/doc/board/emulation/qemu-x86.rst index 15f56b6bc70..c604e42990e 100644 --- a/doc/board/emulation/qemu-x86.rst +++ b/doc/board/emulation/qemu-x86.rst @@ -193,6 +193,9 @@ Linux is selected from grub, e.g. with `debian-12.1.0-i386-netinst.iso`:: The bochs video driver also seems to cause problems before the OS is able to show a display. +The QEMU `-cdrom` option is intended to work with the original ISO-format +images, not the recently invented ISOHybrid image. + Finally, the use of `-M accel=kvm` is intended to use the native CPU's virtual-machine features to accelerate operation, but this causes U-Boot to hang when jumping 64-bit mode, at least on AMD machines. This may be a bug in U-Boot
Add a note about using -cdrom with QEMU. Suggested-by: Bin Meng <bmeng@tinylab.org> Signed-off-by: Simon Glass <sjg@chromium.org> --- doc/board/emulation/qemu-x86.rst | 3 +++ 1 file changed, 3 insertions(+)