On Tue, 2007-02-13 at 05:41 +0000, rahul gundecha wrote:> hi,
>
> 1) When we install guest linux inside Xen using paravirtualization,
> how actually guest linux code is modified. Whats the actual process.
not sure whether i understand your question correctly, but it might be
me.
the passably witty answer would probably be ''manually''.
paravirtualization is based on the assumption that system virtualization
is well worth the effort of _modifying_ systems to suit a virtual
environment better. this leads to improved efficiency, and is thereby in
contrast to the more traditional (and technically challenging) method of
making unmodified operating systems think they actually _own_ the
hardware they operate on. which they don''t. xen does now.
-- thanks alot for elobarating in simple language. but I was actually interested
in
knowing actual process followed in SUSE 10.2 when we install a guest OS.
Because when we install a guest OS, we are just giving normal OS source/CD,
same as what we do in normal OS installation. So who does this
paravirtualization of guest OS?
--Also the reason why I am saying SUSE 10.2 is that it gives boot option of XEN.
Why there is need of another kernel ? Can''t we accomodate VMM inside
native
kernel. Uptil now whatever I read, there was nothing mentioned about the host OS
(domain 0 ), whether it should be paravirtualized or not.
Its mentioned everywhere that we install VMM inside domain-0.
Nothing more about domain-0.
the linux kernel is a very portable thing, and used to run on different
platforms since its earliest revisions. so there''s x86, powerpc, mips
and so on. xen-linux is basically a port to yet another platform, with
the major difference being that this platform does not an interface
defined by hardware, but in software.
d''you know what a system call is? user programs you run on linux use
them to acquire resources (e.g. storage or IPC). xen is very similar in
that respect. a (comparatively small) set of well-defined functions
needed to supplement a whole bunch of operating systems on top of it.
> 2) I am using suse 10.2. After installing xen package which comes with
> it, the new boot menu "SUSE (XEN)" gets added up. What are the
> difference between the kernel which runs this SUSE-XEN & original
> kernel.
in the case of the kernel mentioned by your grub.conf, comparatively
small.
as you might have noticed you get to boot xen, and xen boots on into a
special VM commonly called ''dom0''. dom0 hosts a paravirtual
kernel as
described above, but additionally armed with the typical set of device
drivers necessary to put your peripheral hardware work, and privileged
enough by xen to apply them.
additional guest systems booted are even different. they don''t require
hardware device drivers, since the first one already does that. instead,
they communicate with dom0 for peripheral I/O.
xen maintains cpu(s) and memory. linux in dom0 almost anything else, so
xen does not have to (because writing device drivers is such an
expensive business).
I guess now my question is clear.
Anyways thanks for this prompt and elaborative reply,
it helped me clear out all the doubts I had other than above mentioned questions
Waiting for some more light on my questions.
Regards,
-Rahul
---------------------------------
Heres a new way to find what you''re looking for - Yahoo! Answers
--0-743237738-1171373136=:40895
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
<pre><font size="2">On Tue, 2007-02-13 at 05:41 +0000,
rahul gundecha wrote:<br>><i>
hi,</i><br>><i> </i><br>><i>
1) When we install guest linux inside Xen using
paravirtualization,</i><br>><i> how actually guest
linux code is modified. Whats the actual
process.</i><br><br>not sure whether i understand your
question correctly, but it might be<br>me.<br><br>the passably
witty answer would probably be
''manually''.<br><br>paravirtualization is based on
the assumption that system virtualization<br>is well worth the effort of
_modifying_ systems to suit a virtual<br>environment better. this leads to
improved efficiency, and is thereby in<br>contrast to the more traditional
(and technically challenging) method of<br>making unmodified operating
systems think they actually _own_ the<br>hardware they operate on. which
they don''t. xen does now.<br></font><br>-- thanks
alot for elobarating in simple language. but I was actually interested in
<br>knowing actual process
followed in SUSE 10.2 when we install a guest OS.<br>Because when we
install a guest OS, we are just giving normal OS source/CD, <br>same as
what we do in normal OS installation. So who does this
<br>paravirtualization of guest OS?<br><br><br>--Also
the reason why I am saying SUSE 10.2 is that it gives boot option of XEN.
<br>Why there is need of another kernel ? Can''t we accomodate VMM
inside native <br>kernel. Uptil now whatever I read, there was nothing
mentioned about the host OS<br>(domain 0 ), whether it should be
paravirtualized or not.<br>Its mentioned everywhere that we install VMM
inside domain-0. <br>Nothing more about domain-0.<br><font
size="2"><br><o:p></o:p></font><font
size="2">the linux kernel is a very portable thing, and used to run
on different<br>platforms since its earliest revisions. so
there''s x86, powerpc, mips<br>and so on. xen-linux is basically a
port to yet another platform, with<br>the major difference being that this
platform does not an
interface<br>defined by hardware, but in
software.<br></font><br><font
size="2">d''you know what a system call is? user programs
you run on linux use<br>them to acquire resources (e.g. storage or IPC).
xen is very similar in<br>that respect. a (comparatively small) set of
well-defined functions<br>needed to supplement a whole bunch of operating
systems on top of it.</font><br><br><span
style="font-style: italic;">> 2) I am using suse 10.2. After
installing xen package which comes with</span><br
style="font-style: italic;"><span style="font-style:
italic;">> it, the new boot menu "SUSE (XEN)" gets
added up. What are the</span><br style="font-style:
italic;"><span style="font-style: italic;">>
difference between the kernel which runs this SUSE-XEN &
original</span><br style="font-style: italic;"><span
style="font-style: italic;">> kernel.</span><br
style="font-style: italic;"><br style="font-style:
italic;"><span style="font-style: italic;">in the case
of the
kernel mentioned by your grub.conf, comparatively</span><br
style="font-style: italic;"><span style="font-style:
italic;">small.</span><br style="font-style:
italic;"><br style="font-style: italic;"><span
style="font-style: italic;">as you might have noticed you get to
boot xen, and xen boots on into a</span><br style="font-style:
italic;"><span style="font-style: italic;">special VM
commonly called ''dom0''. dom0 hosts a paravirtual kernel
as</span><br style="font-style: italic;"><span
style="font-style: italic;">described above, but additionally armed
with the typical set of device</span><br style="font-style:
italic;"><span style="font-style: italic;">drivers
necessary to put your peripheral hardware work, and
privileged</span><br style="font-style: italic;"><span
style="font-style: italic;">enough by xen to apply
them.</span><br><br><font size="2">additional
guest systems booted are even different. they don''t
require<br>hardware device drivers, since the first one
already does that. instead,<br>they communicate with dom0 for peripheral
I/O.<br><br>xen maintains cpu(s) and memory. linux in dom0 almost
anything else, so<br>xen does not have to (because writing device drivers
is such an<br>expensive business).<br></font><br>I guess
now my question is clear.<br>Anyways thanks for this prompt and
elaborative reply, <br>it helped me clear out all the doubts I had other
than above mentioned questions <br>Waiting for some more light on my
questions.<br><br>Regards,<br>-Rahul
<br><br></pre><p> 
<hr size=1></hr>
Heres a new way to find what you''re looking for - <a
href="http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/">Yahoo!
Answers</a>
--0-743237738-1171373136=:40895--
--===============0071224338=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
--===============0071224338==--