Get rid of `virtme-run` and other legacy code

[mhartmay]

Right now we have a lot of duplicated code if we add new features to virtme-ng and then often also to virtme. Are there any plans to get rid of the virtme-run executable?

[matttbe]

Personally, I still have scripts not using vng, but directly using virtme-run and virtme-configkernel instead. They were created before virtme-ng, and vng has never been needed for them (the build part and other features from virtme-ng are already handled by these scripts).

Having said that, I understand it would be better to re-organise the code, and get rid of the old "legacy CLI" in a future virtme-ng 2.0. We probably need to accept loosing features from this legacy CLI to ease the maintenance (or they can be added later on).

[arighi]

Yeah, many people are still using the old virtme-run commands, so we need to support it. Something that we could do is to move most of the code in virtme-run to a proper python module and use this module both from virtme-run and vng. And keep implementing new commands / options only in vng. Then at some point we should be able to deprecate virtme-run and remove it.