Yes that is fine if the
paravirtualized drivers are used in HVM then we can put hooks on that. But it
is different case, how actually shype/ACM works in case of VMExit/VMEntry.
Since in case of
VMExit/VMEntry there are no hypercalls, then how sHype/ACM implements security.
I mean to ask that how
sHype/ACM works in case of HVM guest.
From: Stefan Berger
Sent: Monday, April 02, 2007 7:19
Subject: Re: [Xense-devel]
Shype/ACM for HVM guest.
wrote on 04/02/2007 05:40:39 AM:
Does Shype/ACM architecture for implementing
> xen supports HVM guest also? I mean to
say that, as per my
are supported in so far that the configuration of an HVM is checked when the VM
is started. This is done in xend where resource assignments (disk access)
> knowledge in xen 3.0.4
shype/ACM is implemented. Does this
> shype/ACM work also for the HVM (windows)
As per my understanding shype/ACM
puts hook on
> hypercalls from the hypervisor, and consult
with the ACM. But in
> case of full virtualization, hypervisor does
not have hypercalls to
> communicate with HVM guest. There is
correct. Though, if paravirtualized drivers are used in an HVM, also they will
need to go through the hooks for grant table access and event channels.
> communication, in which guest state and host
state are saved. Since
> there are no hypercalls in case of full
virtualization then how the
> actually shype/ACM works. Where does it put
hooks? Or is there any
> other mechanism through which it implements
security in HVM guest.
If any one has information regarding it please reply.
> Praveen Kushwaha
> Xense-devel mailing list