Are you talking about modifying the KVM client image?
There may be reasons, why this is impossible or at least highly undesired.
Before virtualisation developers of embedded stuff need to seal away
their whole machines for their development and test environment
together with sample hardware.
Now using virtualisation they can at least virtualize their development
and test environment, save lots of cost and not risking that their sealed
away hardware will not start again, when they need to fix a critical bug
10-20 years later.
Now try to have them change the KVM client image :-)
Extreme special case, not worth optimizing for, I know. But that special
case is a legal one like any other special case we care about now.
Best Regards
Ingo Oeser
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html