On Sun, May 07, 2023 at 07:36:49PM +0300, Michael Tokarev wrote: > Control: tag -1 + moreinfo > > 07.05.2023 19:17, Martin Maney wrote: > > > Like qemu-system-x86, which xen-utils recommends in Bullseye and > > earlier, qemu-system-xen needs to depend on ipxe-firmware or attempts > > to start an HVM domU using uefi will fail with "failed to find romfile" > > error. > > What the failure is, exactly? qemu will fail to boot in this case if it is > told to boot from network. If you boot it from a hard drive, it will warn > about being unable to find the bootroms, but that's just warning. > > So I want to know what the details about *failure*, exactly.
This is all it would tell me: xen-qemu-system-i386: -device rtl8139,id=nic0,netdev=net0,mac=22:61:34:54:31:30: failed to find romfile "efi-rtl8139.rom" It was not asked to boot from the network! The boot target was a cdrom ISO image, and that seems to have worked after I installed ipxe-qemu manually. After that the error went away and now I've advance to trying to find the VNC connection (it SEEMS like it booted - no other log messages until I killed the domU). In case it's not clear, I've never had any reason to use HVM before... been using Xen since there was nothing but PV, which has been all I need. Don't actually need HVM now, just trying to help the xen team get some feedback before worm is released. -- ...and of course you must be careful not to overwrite the bounds of memory blocks, free a memory block twice, forget to free a memory block, use a memory block after it's been freed, use memory that you haven't explicitly allocated, etc. We C++ programmers have developed tricks to help us deal with this sort of thing, in much the same way that people who suffer severe childhood trauma develop psychological mechanisms to insulate themselves from those experiences. -- Joseph A. Knapka
