FireBoxV Kernel Panic on KVM

rolandrizkallah

Hello,

I am able to deploy the .qcow2 FireBoxV image on my device and it boots normally.
But when trying to create an instance in an OpenStack KVM based cloud, it does not boot.
The instance keeps rebooting every 30 seconds and I get the same following error :

kernel panic not syncing: VFS: unable to mount root fs on unknown-block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.83 #1

I was wondering what might be the problem...
Any ideas ?

Thanks !

rv@kaufmann.dk

Non supported KVM maybe?

rolandrizkallah

@rv@kaufmann.dk said:
Non supported KVM maybe?

Can I modify the image so it can be compatible ?
By changing the drivers for example...

rv@kaufmann.dk

@rolandrizkallah said:

@rv@kaufmann.dk said:
Non supported KVM maybe?

Can I modify the image so it can be compatible ?
By changing the drivers for example...

I think this would be a question for WG support.

james.carson

We do support KVM for Fireware 12.6.2 and better

https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/firebox_v/fbv_intro.html

Based on your error, it looks like one of the partitions, (likely sysa) is not mounted. Please check what you did against this guide:
https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/firebox_v/fbv_setup_kvm.html

If that's not working, I'd suggest opening a support case so we can get more details on what's gone wrong.

kilian

FYI if anyone has the same error :
Had a similar Issue with Proxmox.

Turned out I attached the qcow2 via VirtIO SCISI.
When I attached it again via SATA it worked fine.