A small update:
Yesterday, I also ran a simple libguestfs test[1], which creates a
light weight appliance (i.e. an L2) guest , with and without nesting
to see some over-head.
Summary:
-------------
L0 (bare-metal):
- guestfish run: ~ 3 seconds
L1 (guest):
- w/o nesting, guestfish run: ~ 52 seconds
- w/ nesting, guestfish run: ~ 8 seconds (Almost 6 1/2 times
speed improvement)
To clarify, by "w/ nesting" what I meant is, L1's qemu-kvm cli will have:
-cpu Core2Duo,+vmx # or whatever the model is.
And, "w/o nesting": No -cpu parameter in L1's qemu-kvm cli.
Details:
---------
On libguestfs mailing list --
https://www.redhat.com/archives/libguestfs/2013-May/msg00033.html
[1] The baseline measurement mentioned there --
http://libguestfs.org/guestfs-performance.1.html
Thanks.
Details: https://www.redhat.com/archives/libguestfs/2013-May/msg00033.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
