xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* how to check for already existing hypervisor?
@ 2012-06-20 23:00 palutke.ralph
  0 siblings, 0 replies; 3+ messages in thread
From: palutke.ralph @ 2012-06-20 23:00 UTC (permalink / raw)
  To: xen-devel

Hi guys, 

let me shortly introduce myself. I'm a student and recently work on my bachelor thesis. My goal is to write a little hypervisor.
I'm not quite sure if this is the right mailing list, but i guess you'll gonna tell me.
i have two quick questions:

1. before i can use the vmxon instruction i do have to set vmxe flag in cr4 register. but what if some hypervisor is already running? is there a way to check 
if one is running??

2. before i set the vmxe bit in cr4, i check if it is already enabled. i do this while my module gets loaded. but i observed a strange thing. sometimes
the vmxe bit seems to be set while the other time it isn't. do you have any explanation for that behaviour? do i have to check if the bit is set before 
actually setting it? I've looked at a few hypervisor projects and it seems that no one does it. my primary thought was, if the bit is set a hypervisor is running, 
but i don't think that's true anymore. so do i need the check?

greetings 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* how to check for already existing hypervisor?
@ 2012-06-21  0:44 palutke.ralph
  2012-06-25  9:07 ` Tim Deegan
  0 siblings, 1 reply; 3+ messages in thread
From: palutke.ralph @ 2012-06-21  0:44 UTC (permalink / raw)
  To: xen-devel

Hi guys, 

let me shortly introduce myself. I'm a student and recently work on my bachelor thesis. My goal is to write a little hypervisor.
I'm not quite sure if this is the right mailing list, but i guess you'll gonna tell me.
i have two quick questions:

1. before i can use the vmxon instruction i do have to set vmxe flag in cr4 register. but what if some hypervisor is already running? is there a way to check 
if one is running??

2. before i set the vmxe bit in cr4, i check if it is already enabled. i do this while my module gets loaded. but i observed a strange thing. sometimes
the vmxe bit seems to be set while the other time it isn't. do you have any explanation for that behaviour? do i have to check if the bit is set before 
actually setting it? I've looked at a few hypervisor projects and it seems that no one does it. my primary thought was, if the bit is set a hypervisor is running, 
but i don't think that's true anymore. so do i need the check?

greetings 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: how to check for already existing hypervisor?
  2012-06-21  0:44 palutke.ralph
@ 2012-06-25  9:07 ` Tim Deegan
  0 siblings, 0 replies; 3+ messages in thread
From: Tim Deegan @ 2012-06-25  9:07 UTC (permalink / raw)
  To: palutke.ralph; +Cc: xen-devel

At 02:44 +0200 on 21 Jun (1340246688), palutke.ralph@gmx.de wrote:
> Hi guys, 
> 
> let me shortly introduce myself. I'm a student and recently work on my bachelor thesis. My goal is to write a little hypervisor.
> I'm not quite sure if this is the right mailing list, but i guess you'll gonna tell me.
> i have two quick questions:
> 
> 1. before i can use the vmxon instruction i do have to set vmxe flag in cr4 register. but what if some hypervisor is already running? is there a way to check 
> if one is running??

A lot of hypervisors report their presence in CPUID leaves - have a look
at xen-detect in the tools/ directory for how to spot Xen. 


Tim.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-06-25  9:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-06-20 23:00 how to check for already existing hypervisor? palutke.ralph
  -- strict thread matches above, loose matches on Subject: below --
2012-06-21  0:44 palutke.ralph
2012-06-25  9:07 ` Tim Deegan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).