<div dir="ltr">I also tried using the QEMU parameters, which are attached.</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sun, Jan 12, 2025 at 5:00 PM Sayed Mohammad Badiezadegan <<a href="mailto:mbzadegan@gmail.com">mbzadegan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I entered <b>"?"</b> and then following the example I entered<b> "hammer2:vbd0s1a"</b> but it did not work as I took the screenshot and then attached it with this email.<div><br></div><div>I think this is a DragonflyBSD problem with its legacy boot option.</div><div><br></div><div>Thank you for your assistance.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jan 12, 2025 at 2:06 AM Sergey Zigachev <<a href="mailto:s.zi@outlook.com" target="_blank">s.zi@outlook.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> I attached my QEMU parameter command line screenshot which is very close to your parameters except*-cpu* that I should use *max* and I can not use kvm or other CPU options because I got other errors about them.<br>
<br>
On the screenshot there's a hint on what you can do. I haven't tried it, but you can enter "?" to list available boot devices and then use one if there are any. If there aren't then something is off with the QEMU drives configuration.<br>
<br>
</blockquote></div>
</blockquote></div>