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

[Xen-devel] System call exits for unmodified guests


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Methos <methos.oldest@xxxxxxxxx>
  • Date: Fri, 11 Mar 2011 12:50:03 -0500
  • Delivery-date: Sat, 12 Mar 2011 07:21:44 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=XGbTqv49EBWru1BEuVBmRqFidp5LzNPFQOPmh+ervO4Ake4Qbu2iA5tvGPqlkWWyqL n60YE1LkgKf0efSJbUKhacZwKthuXyuCCnYMgAFS/DfLlUOhMXWxT4bOPI4NBUNBlYKm rdUjkQ2L8w0W65H51yz5jKZt/KgcIFqw5vu6U=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I am new to xen hypervisor technology. I wanted to know if there is any way to register callback in the hypervisor that would be called whenever a guest application makes a guest os system call. That is whenever a guest VM performs "int 80" or "sysenter", the vm should exit and pass the control to the hypervisor. If its possible to do so, which bits should be set in VMCS?

I tried to look through the intel manual for VT, but could not actually find out specific information. I would appreciate some information about this.
The guest OS is unmodified and not paravirtualized.

Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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