[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Can anyone explain this communication mechanisms in case of full virtualization.

  • To: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: aditya shevalkar <aditya27783@xxxxxxxxxxx>
  • Date: Mon, 19 Feb 2007 16:37:58 +0530 (IST)
  • Delivery-date: Mon, 19 Feb 2007 03:07:15 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=GCeAJZ1Grx/AjEMjfN6A7y0tiWh1TV+u+znVmezr9fMIWJDvcB1ahs/SRiU5RBvZWsagoh+plXSo7ktBUt9yfjhha28uKC2hsrUXD/0En7NM5sJgBZdhEUAcnr5bqe1FCjCF1MN59hKrWAUZq3SLcatYdQWS3ACoPtwYHWI10VE=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

For the communication between guest OS(windows OS) and xen VMM in full 
virtualization how does the following 
Concepts are used/implemented or what are the equivalent of these concepts in 
case of full virtualization:
Event channels,
Shared memory,
     Grant Tables,
     Xen daemon,
     Device data(I/O).
(    How does this IO data is transferred between guest OS windows XP 
     and Xen VMM in case of full virtualization).
Specially Shared memory,grant tables and xen store.
Does all these concepts applicable to full virtualization case also?
Are their any other mechanisms for the communication(direct or indirect).
Thanks and Regards,

Yahoo! India Answers: Share what you know. Learn something new

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.