Cisco Firepower Threat Defense Virtual for KVM - won't boot

[Gera]

Hi all,

I was wondering if anybody cracked the mystery that is FTDv on Proxmox. The issue being that it can't find /dev/sda1 once it bootstrapped itself.

The file i am using is: Cisco_Firepower_Threat_Defense_Virtual-6.2.3-83.qcow2
from here: https://software.cisco.com/download/home/286306503/type/286306337/release/6.2.3

The deployment instructions for KVM are here:
https://www.cisco.com/c/en/us/td/docs/security/firepower/quick_start/kvm/ftdv-fdm-kvm-qsg.html

I tried the qcow2, raw, vmdk, ova on local storage as well as qm importdisk into lvm. Same result every time.
Virtual Environment 6.0-6

It looks like this.


When i use the above ova/vmdk in vmware workstation, it boots correctly. It looks like this:


So I figured, in vmware workstation, let's see what's wrong with these disks. Nothing looks strange to me.


fdisk shows the disks


I am not sure what is going on. Obviously the boot process is not normal. It bootstraps the asa image first on hd(0,0)
and then tries to find /dev/sda1 to boot from.

Anybody encounter this before?


Thank you,
Gera

 

[AllanM]

I would start simple (because that's all I know how to do... )...

Try adjusting various hardware parameters for the VM. Like... use an emulated "IDE" controller instead of "SATA/NVME" or vice versa.

 

[Gera]

Pretty much. Once I had more time I started trying variations. Stripping out everything that's unnecessary.

Here is the magic that makes it boot for anyone else trying to use free snort with appid.


And then it boots as it should



Cheers

 

[big-dumb-network-dude]

Hey man I know this thread is from 5 years ago. Im in a similar boat right now trying to get FTDv 7.6 on proxmox. What were hard disk settings ie scsi/ virtio..and what about bios?

 

[AllanM]

Keep the VM settings simple/generic. Use IDE or SATA for the disk.

 

[deaderbug]

Hey man I know this thread is from 5 years ago. Im in a similar boat right now trying to get FTDv 7.6 on proxmox. What were hard disk settings ie scsi/ virtio..and what about bios?

looks like the video console dies at the "booting the kernel" message...

add a serial port to the VM and use the xterm.js console rather than the NOvnc console