KVM: add max_mem test case

[atlarator]

No description provided.

[atlarator]

It seems that the api vm.get__totalmem_sys() is just used in boot_check.py, and the all_memory testcase doesn't claim a constant value for the size of the memory using in the case, when the assertion about system memory and the parameter memory is used, this case must fail.
Maybe I need the reference for vm object array to decide how to make the assertion works for all these memory cases.
Despite this, lgtm.

[atlarator]

RFR

[xhao22]

For the 2 commit:
What's the purpose of the 1st: "gitignore: ignore pycache"?
Can you follow the previous new added case, change the commit title to "KVM: add max_mem test case"?

[xhao22]

no need such line, "is_max_mem = no", right?

[atlarator]

why

[xhao22]

is it used? if not, please remove it.

[atlarator]

For the 2 commit: What's the purpose of the 1st: "gitignore: ignore pycache"? Can you follow the previous new added case, change the commit title to "KVM: add max_mem test case"?

if not, the default behavior of git will track KVM/qemu/tests/__pycache__ which is generated everytime when avocado runs, as an intermidiate component, it shouldn't be tracked by VCS.

[atlarator]

For the 2 commit: What's the purpose of the 1st: "gitignore: ignore pycache"? Can you follow the previous new added case, change the commit title to "KVM: add max_mem test case"?

if not, the default behavior of git will track KVM/qemu/tests/__pycache__ which is generated everytime when avocado runs, as an intermidiate component, it shouldn't be tracked by VCS.

for other scene which python would be byte-compiled, pycache will always be generated so it's necessary to ignore it.

[atlarator]

should I squash the two commits as one or leave them separated is OK?

[xhao22]

should I squash the two commits as one or leave them separated is OK?

Leave them 2 commits.