Boot hangs on rocket in QEMU

[bitigchi]

I am getting the following error on latest nightly after the rocket icon:

qemu-x86_64-softmmu: warning: global PIIX4_PM.disable_s3=1 not used

It stopped working around two weeks ago, before that I am not able to give an estimate since I have been a bit busy.

[waddlesplash]

Please post a full syslog (obtained via -serial stdout on QEMU should work.)

[bitigchi]

syslog

[waddlesplash]

Nothing apparent in the log, all looks well there anyway.

I see however that you are on hrev55592. Could you try updating to hrev55595?

[bitigchi]

Tried with hrev55602. Still the same error, nothing evident in the new syslog as well.

[bitigchi]

hrev55621

qemu-x86_64-softmmu: warning: Spice: record:0 (0x7f868b86ea00): setsockopt failed, Operation not supported on socket

No obvious error on the syslog.

[waddlesplash]

QEMU boots occasionally fail randomly for me, too, but only 1 in 10 times or so. I haven't yet investigated that.

[waddlesplash]

Seems to happen more than 1 in 10 times for me actually.

[bitigchi]

I’ve managed to boot using a fresh QEMU config, but this time Deskbar fails to load every other reboot. I have to launch Team Monitor to be able to relaunch. Shall I open a new ticket for that?

[waddlesplash]

I would bet it is somehow related, at least for now.

[waddlesplash]

This seems to be much easier to reproduce with the Storage Kit compiled in debug mode...

app_server is started as per my logs, so it seems the real culprit is probably once again the launch_daemon failing to start the desktop.

[waddlesplash]

The problem is specifically that the launch_daemon is starting the user session before the initial_volumes_mounted event is registered. This should not matter as the messages should be forwarded to the user launch_daemon anyway, but for some reason it seems they are not.

[waddlesplash]

Proposed fix: ​https://review.haiku-os.org/c/haiku/+/4968

CC'ing axeld just for good measure on this, too. :)

[waddlesplash]

Merged in hrev55878.