Opened 2 months ago

Last modified 7 weeks ago

#19044 new bug

kernel panic with virtio_gpu

Reported by: tsimblist Owned by: korli
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/virtio Version: R1/beta5
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

hrev57937+84 on Proxmox virtual machine. Unstable behavior. Sometimes it boots up with virtio-net not working. Sometimes kernel panic. Sometimes stuck on rocket icon.

Attachments (6)

Screenshot 2024-09-02 9.15.26 AM.png (116.9 KB ) - added by tsimblist 2 months ago.
kernel panic
Screenshot 2024-09-02 9.49.26 AM.png (53.7 KB ) - added by tsimblist 2 months ago.
virtio-net not working
qemu_cmd.txt (2.5 KB ) - added by tsimblist 2 months ago.
qemu command
Screenshot 2024-09-02 12.46.16 PM.png (124.1 KB ) - added by tsimblist 2 months ago.
just works
boot-kdl-virtio-gpu.jpg (249.1 KB ) - added by Coldfirex 2 months ago.
GPF-virtio_gpu_boot.jpg (231.8 KB ) - added by Coldfirex 2 months ago.

Download all attachments as: .zip

Change History (23)

by tsimblist, 2 months ago

kernel panic

by tsimblist, 2 months ago

virtio-net not working

by tsimblist, 2 months ago

Attachment: qemu_cmd.txt added

qemu command

comment:1 by tsimblist, 2 months ago

seems similar to ticket #19003

comment:2 by waddlesplash, 2 months ago

Keywords: virtio added
Platform: x86-64All

comment:3 by tsimblist, 2 months ago

And sometimes it just works. Usually after I reset or restart the vm instead of a cold start.

by tsimblist, 2 months ago

just works

comment:4 by Coldfirex, 2 months ago

Do we have support for virtio-gpu? I usually default o 'default' which I believe is VESA in Proxmox.

comment:5 by Coldfirex, 2 months ago

I just a fresh install of B5 TC0. I was able to install Haiku, and then one first reboot I got a KDL for virtio_gpu. Looks to be different than the initial one tsimblist listed though. I can create a different ticket if needed. On 2nd boot attempt I got the same GPE KDL. Attaching screenshots.

Last edited 2 months ago by Coldfirex (previous) (diff)

by Coldfirex, 2 months ago

Attachment: boot-kdl-virtio-gpu.jpg added

by Coldfirex, 2 months ago

Attachment: GPF-virtio_gpu_boot.jpg added

comment:6 by waddlesplash, 2 months ago

The address in RAX isn't a canonical address, hence the GPF. If we have corruption or invalid data being used here, it's expected that the KDLs will vary.

comment:7 by waddlesplash, 2 months ago

Component: Drivers/GraphicsDrivers/Graphics/virtio
Keywords: virtio removed
Owner: changed from nobody to korli

in reply to:  4 comment:8 by tsimblist, 2 months ago

Replying to Coldfirex:

Do we have support for virtio-gpu? I usually default o 'default' which I believe is VESA in Proxmox.

I have been using virtio-gl on beta4 with no issues. When I upgraded to beta5, the kdl appeared. I changed to virtio-gpu and the problem persisted.

comment:9 by korli, 2 months ago

Could you please check with a current beta5 revision? it has received some virtio changes.

comment:10 by tsimblist, 2 months ago

upgraded to hrev57937+112 and rebooted. GPF like before.

Then I did a reset on the VM and it came up with virtio-net not working like before.

Did a Shutdown/Restart and it started up with no issue like before.

Seems like there are no changes in symptoms.

Edit: using virtio-gl for this test.

Last edited 2 months ago by tsimblist (previous) (diff)

comment:11 by tsimblist, 2 months ago

upgraded to hrev57937+114 and rebooted. KDL with vm_page_fault.

Then I did a reset on the VM and it came up stuck on rocket icon.

Another VM reset and it came up with virtio-net not working.

Shutdown/Restart and it came up fine.

Shutdown and changed VM display from virtio-gl to Standard VGA

Started VM and it came up with virtio-net not working. Didn't expect that.

Shutdown/Restart and virtio-net still not working. Tried again and it came up fine.

So maybe virtio-net is the real problem here?

comment:12 by korli, 2 months ago

tried switching to e1000? I didn't manage to build images with virtio-net on r1beta5 yet. I had to switch to e1000.

comment:13 by tsimblist, 2 months ago

Changed display back to virtio-gl and changed virtio-net to e1000.

Cold start on VM produces the GPF like original report. Reset VM and it comes up fine.

Shutdown, changed display back to Standard VGA. Cold start VM comes up fine.

So it would appear that both virtio graphics & virtio-net have issues.

Note: All configurations I have tested use virtio-scsi controller for virtual disk. I have not experienced any issue with virtio-scsi.

comment:14 by korli, 8 weeks ago

could you try a current nightly image?

comment:15 by tsimblist, 8 weeks ago

I downloaded the hrev58146 nightly iso, but I'm having difficulty installing it.

I can boot the ISO up to "Welcome to the Haiku Boot Loader" but it displays a message at the bottom "Cannot continue booting (Boot volume is not valid)"

If I try the "Select boot volume/state" option it appears that there are only harddrive snapshots to choose from.

What am I doing wrong?

comment:16 by tsimblist, 8 weeks ago

Never mind, I changed the repository to master and performed "pkgman full-sync".

Some quick testing and I haven't provoked a problem yet. With virtio-gl, virtio-net & virtio-scsi.

comment:17 by korli, 7 weeks ago

it seems using q35 as machine type could workaround the issue.

Note: See TracTickets for help on using tickets.