VM container-disk: VMI does not include tuned-adm kernel-args

[RamLavi]

When creating the VM container-disks for the vmi-under-test - a tuned-adm command in performed.
This command is supposed to add kernel-args after reboot.
Although the virt-builder used to create the container-disks is performing reboot - the kernel-args are not added.
Before reboot:

[root@rt-vmi-vwrrw ~]# cat /proc/cmdline 
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-4.18.0-348.rt7.130.el8.x86_64 root=UUID=a9332d7d-1762-41cd-a702-6b2cc556c248 ro console=tty0 rd_NO_PLYMOUTH crashkernel=auto resume=UUID=d4ac9572-e828-4c87-9b76-e59c9fa6e426 console=ttyS0,115200

After reboot:

[root@rt-vmi-vwrrw ~]# cat /proc/cmdline 
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-4.18.0-348.rt7.130.el8.x86_64 root=UUID=a9332d7d-1762-41cd-a702-6b2cc556c248 ro console=tty0 rd_NO_PLYMOUTH crashkernel=auto resume=UUID=d4ac9572-e828-4c87-9b76-e59c9fa6e426 console=ttyS0,115200 skew_tick=1 tsc=reliable rcupdate.rcu_normal_after_boot=1 isolcpus=managed_irq,domain,1-2 intel_pstate=disable nosoftlockup nohz=on nohz_full=1-2 rcu_nocbs=1-2 irqaffinity=0

diff:

skew_tick=1 tsc=reliable rcupdate.rcu_normal_after_boot=1 isolcpus=managed_irq,domain,1-2 intel_pstate=disable nosoftlockup nohz=on nohz_full=1-2 rcu_nocbs=1-2 irqaffinity=0

The absence of this diff may be crucial to the succesful performance of the checkup.

[orelmisan]

This problem does not occur after merging #35.
We currently have a sub-optimal solution for tuned-adm which involves a reboot every time the VM boots.

[orelmisan]

PR #56 provides a better solution to this problem.