Opened 3 weeks ago
Last modified 37 hours 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)
Change History (22)
by , 3 weeks ago
| Attachment: | Screenshot 2024-09-02 9.15.26 AM.png added |
|---|
comment:2 by , 3 weeks ago
| Keywords: | virtio added |
|---|---|
| Platform: | x86-64 → All |
comment:3 by , 3 weeks ago
And sometimes it just works. Usually after I reset or restart the vm instead of a cold start.
follow-up: 8 comment:4 by , 2 weeks ago
Do we have support for virtio-gpu? I usually default o 'default' which I believe is VESA in Proxmox.
comment:5 by , 2 weeks 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. Attaching screenshot.
by , 2 weeks ago
| Attachment: | boot-kdl-virtio-gpu.jpg added |
|---|
by , 2 weeks ago
| Attachment: | GPF-virtio_gpu_boot.jpg added |
|---|
comment:6 by , 2 weeks 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 , 2 weeks ago
| Component: | Drivers/Graphics → Drivers/Graphics/virtio |
|---|---|
| Keywords: | virtio removed |
| Owner: | changed from to |
comment:8 by , 2 weeks 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 , 8 days ago
Could you please check with a current beta5 revision? it has received some virtio changes.
comment:10 by , 8 days 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.
comment:11 by , 5 days 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 , 5 days 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 , 5 days 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:15 by , 38 hours 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 , 37 hours 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.
kernel panic