Thank you for your reply
and domain builder acts as bootloader ,and then guestos-linux will
setup and control its own memory ,is it right? of course,any memory-map
will incur xen to related map or so.
but in the rational linux, it will know how many physical memory it owns
and linux know that all the physical memory it owns is there
naturally.
In the xen ,guest-linux know how many physical memory it owns but
doesnot know that all the physical memory it owns is there,for some of
them is not to allocate,is it right?
this is correct -- for a paravirtual guest. for a hvm guest, it needs to
work a little different, of course.
how does hvm guest deal with its physical memory?
when it boots up, is its physical memory allocated and its virtual
memory not all allocated or what does its do?
could you help me
Thanks in advance
that is during guest-linux
running,it will request some memory which it will get ,for the
guest ,its memory (both its physical memory and its virtual memory)is
dynamical allocated,while raditional linux has its physical memory when
it boot up ,while gets virtual memory dynamically,is it right?
yes. see the xen interface manual on this topic, namely the chapters on
memory management and the hypercall reference for page table and
physical memory management. not sure if this gets entirely clear,
though, i sometimes tend to get confused myself. especially guest side
vm tends to be complex, but that's quite natural.
could you help me
thanks in advance
hth,
dns
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home