Cisco Firepower Management: runs in VMWare & VirtualBox but not Hyper-V?

[PliotronX]

Does anyone know of a way to inject the Hyper-V modules into the archaic version of LILO that Cisco uses? Linux Live CD's won't touch the volumes for some reason. I can't find a good article that applies to the situation. Don't care whether Cisco supports Hyper-V or not, I have been able to run their other virtual appliances successfully without any ill effect in Hyper-V. Thank you for any thoughts!

 

[Scarpozzi]

I've never touched it, so I'm just posting... Is it possible to install it on Virtualbox and export it to Hyper-V somehow?

Your kernel may not like it and you may get to recompile it. The question I would ask is "why do they not support it?" (not wanting a complicated support matrix or perhaps not wanting to deal with some specific limitation of hyper-v)

 

[PliotronX]

Thanks, yeah I wish VB would do this but it will only export to the OV* format (not VHD). I tried a conversion with VMWare infrastructure on an ESXi host and that also will not export to the Hyper-V format. Will it accept any recompiled kernel or does it have to be the very specific kernel? It reports that it is 3.10.53 and unlike other Cisco VAs being recognized as RHEL, this one just says generic Linux. I cannot do anything with LILO but boot to the default selection, according to Sourcefire pre-Cisco buyout, there was an option to restore the system which may have been helpful, but that's nowhere to be found in this release. Gah, and I thought Snow Leopard was a PITA to virtualize D:

 

[PliotronX]

Just a thought I'm kicking around, can you compile a kernel for a secondary volume? Possible from Windows using ext2fs and Cygwin?