From Fedora Project Wiki
(Created page with '= Install = Worked for * dom0 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux : AMD Opteron(tm) Processor 848 : flags: fpu tsc msr pae mce c...')
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Install =
+
Notes from virtualization test day [[Test_Day:2009-05-07_Virtualization]]
 +
specifically for [[Test_Day:2009-05-07_Virtualization:XenDomU]].
 +
= Xen DomU =
 +
 
 +
== Install ==
 
Worked for  
 
Worked for  
 
* dom0 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
 
* dom0 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
Line 7: Line 11:
 
** domU 64b works
 
** domU 64b works
  
= Memory Ballooning =
+
== Memory Ballooning ==
== 32 bit guest ==
+
=== 32 bit guest ===
=== Balloon Up - fail? ===
+
Original guest was 1G. Test was:
 +
<pre>
 +
virsh shutdown f11
 +
virsh dumpxml f11 > f11.xml
 +
</pre>
 +
* Add currentMemory parameter which defines minimum memory given to guest at boot.
 +
<pre>
 +
<memory>1048576</memory>
 +
<currentMemory>524288</currentMemory>
 +
</pre>
 +
* Enact this guest config  in Xen via libvirt.
 +
<pre>
 +
virsh define f11.xml
 +
virsh start f11
 +
</pre>
 +
See: [[QA_talk:Testcase_Virtualization_XenDomU_Memory_Ballooning]]
 +
 
 +
==== Balloon Up - fail? ====
 
<pre>
 
<pre>
 
[root@felix tmp]# grep -i memory f11-32.xml
 
[root@felix tmp]# grep -i memory f11-32.xml
Line 28: Line 49:
 
After few minutes guest <code>free -m</code> still reports 519.
 
After few minutes guest <code>free -m</code> still reports 519.
  
=== Balloon Down - PASS ===
+
==== Balloon Down - PASS ====
 
<pre>
 
<pre>
 
[root@felix tmp]# virsh setmem f11-32 $(( 1024 * 256 ))
 
[root@felix tmp]# virsh setmem f11-32 $(( 1024 * 256 ))
Line 41: Line 62:
 
Guest <code>free -m</code> reports 256.
 
Guest <code>free -m</code> reports 256.
  
=== Balloon Back Up - PASS ===
+
==== Balloon Back Up - PASS ====
 
Apparently I'm mistaken in my understanding of <code><memory></code> and <code><currentMemory></code> tags.
 
Apparently I'm mistaken in my understanding of <code><memory></code> and <code><currentMemory></code> tags.
 
I was not able to balloon above 519.
 
I was not able to balloon above 519.

Latest revision as of 07:03, 7 May 2009

Notes from virtualization test day Test_Day:2009-05-07_Virtualization specifically for Test_Day:2009-05-07_Virtualization:XenDomU.

Xen DomU

Install

Worked for

  • dom0 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
AMD Opteron(tm) Processor 848
flags: fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up
    • domU 32b works
    • domU 64b works

Memory Ballooning

32 bit guest

Original guest was 1G. Test was:

virsh shutdown f11
virsh dumpxml f11 > f11.xml
  • Add currentMemory parameter which defines minimum memory given to guest at boot.
<memory>1048576</memory>
<currentMemory>524288</currentMemory>
  • Enact this guest config in Xen via libvirt.
virsh define f11.xml
virsh start f11

See: QA_talk:Testcase_Virtualization_XenDomU_Memory_Ballooning

Balloon Up - fail?

[root@felix tmp]# grep -i memory f11-32.xml
  <memory>1048576</memory>
  <currentMemory>524288</currentMemory>

# guest is running...
[root@felix xen]# virsh setmem f11-32 $(( 1024 * 1000 ))

[root@felix tmp]# grep 'memory target' /var/log/xen/xend.log |tail -1
[2009-05-06 23:24:23 28390] DEBUG (XendDomainInfo:664) Setting memory target of domain f11-32 (7) to 1000 MiB.

[root@felix xen]# virsh dominfo f11-32 | grep memory
Max memory:     1048576 kB
Used memory:    524288 kB

After few minutes guest free -m still reports 519.

Balloon Down - PASS

[root@felix tmp]# virsh setmem f11-32 $(( 1024 * 256 ))

[root@felix tmp]# grep 'memory target' /var/log/xen/xend.log |tail -1
[2009-05-06 23:36:08 28390] DEBUG (XendDomainInfo:664) Setting memory target of domain f11-32 (7) to 256 MiB.

[root@felix tmp]# virsh dominfo f11-32|grep memory
Max memory:     1048576 kB
Used memory:    262144 kB

Guest free -m reports 256.

Balloon Back Up - PASS

Apparently I'm mistaken in my understanding of <memory> and <currentMemory> tags. I was not able to balloon above 519.

[root@felix tmp]# virsh setmem f11-32 $(( 1024 * 1000 ))

[root@felix tmp]# grep 'memory target' /var/log/xen/xend.log |tail -1
[2009-05-06 23:40:04 28390] DEBUG (XendDomainInfo:664) Setting memory target of domain f11-32 (7) to 1000 MiB.
[root@felix tmp]# virsh dominfo f11-32|grep memory
Max memory:     1048576 kB
Used memory:    524288 kB

Guest free -m reports 519 again.