I don't have a current patch or anything, and I'm not near a PC, but look
in LibvirtComputingResource.java and elsewhere for references to lsmod or
KVM and comment any out. Then go into LibvirtVMDef.java and look at the
strings that build the XML. You will want to start some VMS on your host
manual
I agree it makes sense to have nested virtualization enabled on the host, but
can you please share the exact changes that you made to allow qemu , just for
testing?
On Jul 5, 2013, at 2:48 PM, Marcus Sorensen wrote:
> On a side note, I've made the modifications required once to run qemu
> wi
On a side note, I've made the modifications required once to run qemu
without the kvm modules, as a test. You have do do several things, not
just disable the checks (that are there for a reason, to ensure that
everything will work). You'd have to disable several checks, and then
edit the XML defini
You only need to run package.sh when you've tested everything and made
sure it's ready. Then you package the final product. For testing, you
can just edit utilities.py in its installed location on the server.
You can run the agent in a VM if you're using vmware-fusion or KVM,
you just have to enab
Hi,
I am attempting to make a simple change in the
cloudstack/dist/rpmbuild/SOURCES/cloudstack-4.2.0-SNAPSHOT/python/lib/cloudutils/utilities.py
script , so that the cloudstack-setup-agent script does not throw an error
and exit if it cannot fine /dev/kvm (usage scenario - running cloudstack
insid