Re: Hurd starts stop with: sd0: timeout waiting for identify

--000000000000872bd40645249971
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I am now trying with

qemu-system-x86_64.exe \
        -accel tcg \
        -machine type=3Dq35 \
        -m 4g \
        -nic user,model=3Dvirtio-net-pci \
        -drive format=3Draw,file=3D"/c/iso/debian-hurd-amd64-20250807.img" =
\
        -vga qxl

What just gives an unbootable media: "/c/iso/debian-hurd-amd64-20250807.img=
"

Changing it to

qemu-system-x86_64.exe \
        -accel tcg \
        -machine type=3Dq35 \
        -m 4g \
        -nic user,model=3Dvirtio-net-pci \
        -drive
if=3Dpflash,format=3Draw,file=3D"/mingw64/share/qemu/edk2-x86_64-code.fd",r=
eadonly=3Don
\
        -drive
if=3Dpflash,format=3Draw,file=3D"/mingw64/share/qemu/edk2-i386-vars.fd" \
        -drive format=3Draw,file=3D"/c/iso/debian-hurd-amd64-20250807.img" =
\
        -vga qxl

it is the same mess: does not find a bootable device.

On Thu, Nov 20, 2025 at 9:25=E2=80=AFPM Michael Kelly <[email protected]=
k> wrote:

> Thomas,
> On 20/11/2025 08:46, Thomas Schweikle wrote:
>
> On Thu, Nov 20, 2025 at 9:14=E2=80=AFAM Michael Kelly <[email protected]=
.uk>
> wrote:
>
>> I've been involved in some recent changes in this area but cannot
>> reproduce what you experience. Are you referring to the
>> 'debian-hurd-amd64-20251105.img.tar.xz' image, for example?
>>
> Yes. Or the others:
>
> debian-hurd{,-amd64,-amd64-20250807}.img{.gz,.tar.gz,.tar.xz,.zip,}
>
> If you also see these problems in 20250807 images then the problem does
> not relate to recent interrupt code changes as I supposed.
>
> unpacked they are all the same. And
>
> debian-hurd-2025-amd64-NETINST-1.iso
>
> Tried the i386-images too, but with same results.
>
>> Can you present the qemu configuration that you are using so that I can
>> attempt to reproduce?
>>
> Here it is:
> /usr/bin/qemu-system-x86_64 -name guest=3Ddhu,debug-threads=3Don -S \
>   -object
> {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/li=
bvirt/qemu/domain-11-dhu/master-key.aes"}
> \
>   -machine
> pc-q35-5.0,usb=3Doff,vmport=3Doff,dump-guest-core=3Doff,memory-backend=3D=
pc.ram,hpet=3Doff,acpi=3Don
> -accel kvm \
>
> What software are you using to produce this qemu invocation? I am unable
> to generate a virtual machine with the deprecated machine type of
> 'pc-q35-5.0' so have no way of knowing if this is contributing to these
> issues. Presumably your qemu version is 9.2.1 but that doesn't match with
> this machine type either.
>
> Regards,
>
> Mike.
>


--=20
Thomas

--000000000000872bd40645249971
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I am now trying with</div><div><br></div><div>qemu-sy=
stem-x86_64.exe \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -accel tcg \<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 -machine type=3Dq35 \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -m 4=
g \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -nic user,model=3Dvirtio-net-pci \<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive format=3Draw,file=3D&quot;/c/iso/debian-=
hurd-amd64-20250807.img&quot; \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -vga qxl<br>=
<br></div><div>What just gives an unbootable media: &quot;/c/iso/debian-hur=
d-amd64-20250807.img&quot;</div><div><br></div><div>Changing=C2=A0it to</di=
v><div><br></div><div>qemu-system-x86_64.exe \<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 -accel tcg \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -machine type=3Dq35 \<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -m 4g \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -nic use=
r,model=3Dvirtio-net-pci \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive if=3Dpflas=
h,format=3Draw,file=3D&quot;/mingw64/share/qemu/edk2-x86_64-code.fd&quot;,r=
eadonly=3Don \<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive if=3Dpflash,format=3Dr=
aw,file=3D&quot;/mingw64/share/qemu/edk2-i386-vars.fd&quot; \</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 -drive format=3Draw,file=3D&quot;/c/iso/debian-hur=
d-amd64-20250807.img&quot; \</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 -vga qxl=
<br><br></div><div>it is the same mess: does not find a bootable device.</d=
iv></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"l=
tr" class=3D"gmail_attr">On Thu, Nov 20, 2025 at 9:25=E2=80=AFPM Michael Ke=
lly &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></=
u>

 =20
   =20
 =20
  <div>
    <p>Thomas,</p>
    <div>On 20/11/2025 08:46, Thomas Schweikle
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div dir=3D"ltr" class=3D"gmail_attr">On Thu, Nov 20, 2025 at
            9:14=E2=80=AFAM Michael Kelly &lt;<a href=3D"mailto:mike@weathe=
rwax.co.uk" target=3D"_blank">[email protected]</a>&gt;
            wrote:</div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div>
                <p>I&#39;ve been involved in some recent changes in this
                  area but cannot reproduce what you experience. Are you
                  referring to the
                  &#39;debian-hurd-amd64-20251105.img.tar.xz&#39; image, fo=
r
                  example?</p>
              </div>
            </div>
          </blockquote>
          <div>Yes. Or the others:</div>
          <div><br>
          </div>
          <div>debian-hurd{,-amd64,-amd64-20250807}.img{.gz,.tar.gz,.tar.xz=
,.zip,}</div>
        </div>
      </div>
    </blockquote>
    If you also see these problems in 20250807 images then the problem
    does not relate to recent interrupt code changes as I supposed.
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_quote">
          <div>unpacked they are all the same. And</div>
          <div><br>
          </div>
          <div>debian-hurd-2025-amd64-NETINST-1.iso</div>
          <div><br>
          </div>
          <div>Tried the i386-images too, but with same results.</div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div>
                <p>Can you present the qemu configuration that you are
                  using so that I can attempt to reproduce?</p>
              </div>
            </div>
          </blockquote>
          <div>Here it is:</div>
          <div>/usr/bin/qemu-system-x86_64 -name
            guest=3Ddhu,debug-threads=3Don -S \<br>
            =C2=A0 -object
{&quot;qom-type&quot;:&quot;secret&quot;,&quot;id&quot;:&quot;masterKey0&qu=
ot;,&quot;format&quot;:&quot;raw&quot;,&quot;file&quot;:&quot;/var/lib/libv=
irt/qemu/domain-11-dhu/master-key.aes&quot;}
            \<br>
            =C2=A0 -machine
pc-q35-5.0,usb=3Doff,vmport=3Doff,dump-guest-core=3Doff,memory-backend=3Dpc=
.ram,hpet=3Doff,acpi=3Don
            -accel kvm \</div>
        </div>
      </div>
    </blockquote>
    <p>What software are you using to produce this qemu invocation? I am
      unable to generate a virtual machine with the deprecated machine
      type of &#39;pc-q35-5.0&#39; so have no way of knowing if this is
      contributing to these issues. Presumably your qemu version is
      9.2.1 but that doesn&#39;t match with this machine type either.</p>
    <p>Regards,</p>
    <p>Mike.</p>
  </div>

</blockquote></div><div><br clear=3D"all"></div><br><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr">Thomas</div></div>

--000000000000872bd40645249971--