From Fedora Project Wiki
No edit summary |
(may be wrong about currentMemory, link to my test results) |
||
| Line 1: | Line 1: | ||
[[User:Dale|Dale]] 06:25, 7 May 2009 (UTC) | [[User:Dale|Dale]] 06:25, 7 May 2009 (UTC) | ||
There isn't any guest configuration in <code>/etc/xen</code> since F8 or F7. | There isn't any guest configuration in <code>/etc/xen</code> since F8 or F7. | ||
| Line 22: | Line 22: | ||
* See that <code>free -m</code> in guest now reports 519 total. | * See that <code>free -m</code> in guest now reports 519 total. | ||
Actually, I think I may be confused about the meaning of currentMemory as I could balloon down from 519 and back up to it, but could not go above the value of currentMemory. <ref>[[User:Dale/Test_Day:2009-05-07_Virtualization:XenDomU#Memory_Ballooning]]</ref> | |||
<references /> | <references /> | ||
Latest revision as of 06:54, 7 May 2009
Dale 06:25, 7 May 2009 (UTC)
There isn't any guest configuration in /etc/xen since F8 or F7.
Memory for guest can be set in libvirt[1]
- Dump XML config if 'virsh edit' is not available (i.e. on F8 libvirt-0.4.4)
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 that
free -min guest now reports 519 total.
Actually, I think I may be confused about the meaning of currentMemory as I could balloon down from 519 and back up to it, but could not go above the value of currentMemory. [2]