First thing that comes to mind is to modify your system vm template for
this scenario with virt-what swapped out with a dummy script to say
whatever you want. It's a hack for sure, but the other obvious alternative
involves editing CloudStack code.
On Mon, May 4, 2015 at 3:34 PM, Ian Duffy wrote:
Hi all,
This is a very edge case problem but I'm interested in hearing some
possible solutions to it.
I've been playing with running a full KVM basic networking Cloudstack
environment on AWS.
Running nested virtualization on the AWS cloud comes with some interesting
issues. I'm using a service p
