Hyper-V in VMWare environment

Home Forums Virtualization VMware Virtualization Hyper-V in VMWare environment

This topic contains 3 replies, has 3 voices, and was last updated by Avatar danzmanz 8 years, 11 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • Avatar
    danzmanz
    Member
    #152921

    Greetings,

    We are running a VMWare environment on esxi servers. We need to enable hyper-v in the bios of the esxi servers in order to add a role in w2k8 servers.

    Just wondering if this will affect our environment in any way if we have hyper-v enabled in a vmware environement??

    danzmanz

    Avatar
    Maish
    Member
    #326145

    Re: Hyper-V in VMWare environment

    If you are looking to run Hyper-V as a VM under ESXi – this is not possible.

    Avatar
    danzmanz
    Member
    #366964

    Re: Hyper-V in VMWare environment

    not as a vm but we wish to add the remote fx role which requires hyper-v to be enabled at bios level.

    Avatar
    vonPryz
    Member
    #347551

    Re: Hyper-V in VMWare environment

    danzmanz;228644 wrote:
    not as a vm but we wish to add the remote fx role which requires hyper-v to be enabled at bios level.

    Hyper-V is not enabled at BIOS. It is an OS feature. In BIOS, one must enable no-execute and virtualization support. If you are running VMWare, it is highly likely the features are already enabled.

    No-execute, usually XD (execution disable, Intel term) or NX (no execution, AMD term) means that a memory page can be flagged as data or code, and trying to execute instructions from a data page will throw a hardware exception.

    Virtualization support is called AMD-V (sometimes Pacifica) or Intel VT-x (aka Vanderpool). This provides some additional CPU features which are used to give the host OS more control the processor whilst running a full-featured guest OS.

    -vP

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.