Quantcast
Channel: Hyper-V forum
Viewing all 19461 articles
Browse latest View live

Hyper-v switch vlan trunk

$
0
0

Hi

i have a server with two nic in teaming on wich i have a trunk with different vlans, when i create the hyper-v switch i associate it with the microsoft multiplexor driver that belongs to the teaming, i need to say to hyper-v switch that it has all the trunks, in order to pass them to the vm nics where i can choose the vlan id, the question is, the hyper-v switch is also the interface for the host so how can i say only to the host that it belong to a specific vlan id? the host say should belong to vlan id 2 but should pass all other vlan id to the vms


Adding windows 2019 on DC with Windows 2008 r2

$
0
0
Is it possible to promote windows 2019 server as DC on a prod env with Windows 2008 r2 as DCs? Or should first join with eval version of Win 2016 and promote and then promote 2019, considering I only have license for Windows 2019

Adding Windows server 2019 on windows 2008 r2 DCs env

$
0
0
Is it possible to promote windows 2019 server as DC on a prod env with Windows 2008 r2 as DCs? Or should first join with eval version of Win 2016 and promote and then promote 2019, considering I only have license for Windows 2019

how to reconnect to a previously active LUN (ISCSI) with hyperv core

$
0
0

I'm currently using Hyper-V core (2016 and 0219) along with netgear readynas via ISCSI LUNs.  the hyperv's are in workgroups not joined to a domain.

once I present a LUN to one of the hyperV (lets say A), and then present it to hyperv-B, B will see the LUN as inactive.

I understand that two Hyper-V's cannot own the LUN at the same time for obvious reasons, so my question is if hyperv-A dies and I want hyperv-B to take ownership of that LUN without formatting, is there a command to do it?

I used this command to format the disk orginally

Initialize-Disk–Number <Disk_Number> –PartitionStyle GPT –PassThru | New-Partition –AssignDriveLetter –UseMaximumSize | Format-Volume

would it be set-disk to get it online and readable to hyperv-B?

thanks

VM's cannot connect to virtual machine configuration storage after a host is removed from cluster - help please

$
0
0

We had a 2 host cluster with 2 vm's on host A and 1 vm on host B.

I exported the vm from host B and imported it into host A.  I then removed host B.  Now have 2 the 2 original vm's that were in host A.  Both say they connect connect to virtual machine configuration storage and the vm i imported no longer appears.

Any help would be very much appreciated.

Thanks

Driver for "Microsoft Hyper-V Video"

$
0
0

Contrary to popular belief, the driver for the OS running on the virtual machine (Microsoft Hyper-V Video") is added to the Microsoft operating systems as any other driver, presumably when virtual machines were first added. The driver, "Microsoft Hyper-V Vide") is released (and therefore, incorporated) into systems that released after it -- Windows 7 had it, Windows 8, 8.1 and 10 got them all. The ones before, such as the (beta) of Longhorn or the more familiar XP or Win 2K don't, so there will forever be this "question-mark" video adapter.

I would assume that the best move here is to not install a adapter, although ATI Rage 128 Pro was the one I used physically on my win2K build.

Eh ... hmm my virtual Win 2K crashed (BSOD) when I am browsing screen savers. interesting ...

I NEED THE DISPLAY ADAPTER DRIVERS!!!!!!!

And hey, this "adapter" clearly doesn't support hardware-based acceleration. Seen in V2K by the displaying of corrupt images (desktop icons!) and some corruption after cursor movement.

That being said, I am still wondering what are the other two "unknown devices". Infrared? Bluetooth? Windows linked by USB? I don't see those in Virtual Machine settings ...

Or at least tell me how to extract those from a Windows installation disk.


Hyper-V - Unable to delete multiple Checkpoints

$
0
0

We have two Hyper-V servers running on Windows Server 2016. One is one main server, the other one is the replica server where the main one replicates to.

We took down the replica server for maintenance and Hyper-V was unable to replicate to it and we think that due to this, one of the VM's wasn't ahppy and created a number of checkpoints (it may or may not be realted to this).

Regardless of the cause, one of the VM's on the main server now has 3 checkpoints which is creating a storage issue for us.

There is no option to delete the checkpoints and if I click delete on any of them, I get the error:

Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID AF4E3BE9-9A1A-4E34-9F7D-F6F7A84531BF.
Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF').

No matter what I do, I cannot delete them. I scheduled maintenance for the VM and powered it down thinking that it could be because it was started, same issue.

I tried changing the storage file to the newer file created but because it was an avhxd it wouldn't start because it needs the vhdx file to do so.

I read that you needed to do it via PowerShell, but I get the same error using that.

We're now running into a problem whereby we'll run out of storage space because the original VM is 600GB in size and while we had plenty of space, it's now created a number of checkpoints also reaching the same size.

So...

What can I do to resolve this?

One option I can think of is to export the VM, delete everything and re-import the exported VM and that should fix it?

Any advise would be greatly appreciated.

Thanks.

PowerShell output below.

    PS C:\Users\Administrator> Get-VMSnapshot -VMName "My VM Name" -ComputerName SERVERNAME | Remove-VMSnapshot
    Remove-VMSnapshot : 'My VM Name' failed to remove checkpoint.
    Cannot delete checkpoint: Catastrophic failure (0x8000FFFF).
    Virtual machine failed to generate VHD tree.
    'My VM Name' failed to remove checkpoint. (Virtual machine ID 33E39D27-D0DB-4F89-A080-6A50E112B941)
    Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID 

AF4E3BE9-9A1A-4E34-9F7D-F6F7A84531BF.
Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF').
At line:1 char:67
+ ...  -VMName "My VM Name" -ComputerName SERVERNAME | Remove-VMSnapshot+                                                         ~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Remove-VMSnapshot], VirtualizationException+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.RemoveVMSnapshot

Remove-VMSnapshot : 'My VM Name' failed to remove checkpoint.
Cannot delete checkpoint: Catastrophic failure (0x8000FFFF).
Virtual machine failed to generate VHD tree.
'My VM Name' failed to remove checkpoint. (Virtual machine ID 33E39D27-D0DB-4F89-A080-6A50E112B941)
Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID CE0939F2-4E67-4833-905B-C4D8C62A57D8.
Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF').
At line:1 char:67
+ ...  -VMName "My VM Name" -ComputerName SERVERNAME | Remove-VMSnapshot+                                                         ~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Remove-VMSnapshot], VirtualizationException+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.RemoveVMSnapshot

Remove-VMSnapshot : 'My VM Name' failed to remove checkpoint.
Cannot delete checkpoint: Catastrophic failure (0x8000FFFF).
Virtual machine failed to generate VHD tree.
'My VM Name' failed to remove checkpoint. (Virtual machine ID 33E39D27-D0DB-4F89-A080-6A50E112B941)
Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID 5C2D8EA1-8DEA-4087-B40D-CC4E99216ECF.
Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF').
At line:1 char:67
+ ...  -VMName "My VM Name" -ComputerName SERVERNAME | Remove-VMSnapshot+                                                         ~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Remove-VMSnapshot], VirtualizationException+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.RemoveVMSnapshot

PS C:\Users\Administrator>

Hyper-V: Checkpoint operation faild

$
0
0

Hello everybody,

I am running Hyper-V 2016 on Windows Server 2016 with the latest updates and I get this error when trying to make a checkpoint.

- I tried to move the data to another ClusterShared Volumen, but this wasn´t the solution.

- I also tried to check and renew all permissions for the files but also without any success.

- Restart the VM

- Disabled Checkpoints / Enable Checkpoints

- Remove from Failovercluster / add to Failovercluster

-Check the Status for the VSS --> all ok.

Does anybody have another idea? I tried so many things and I used Google :-) now for the last 4 Hours, but this is a really special problem I guess.

Checkpoint-VM : Checkpoint operation failed.
Checkpoint operation was cancelled.
'AZS00001' could not initiate a checkpoint operation.
Could not create auto virtual hard disk
C:\ClusterStorage\Volume03\AZS00001\AZS00001-DISK2_EDD4EDD1-855D-4ED4-B693-4131232B666D.avhd: Th
cannot be created..
Checkpoint operation for 'AZS00001' failed. (Virtual machine ID CDA47693-7962-4086-8283-2A0655D5
Checkpoint operation for 'AZS00001' was cancelled. (Virtual machine ID CDA47693-7962-4086-8283-2
'AZS00001' could not initiate a checkpoint operation: The directory or file cannot be created. (
machine ID CDA47693-7962-4086-8283-2A0655D53146)
'AZS00001' could not create auto virtual hard disk
C:\ClusterStorage\Volume03\AZS00001\AZS00001-DISK2_EDD4EDD1-855D-4ED4-B693-4131232B666D.avhd: Th
cannot be created. (0x80070052). (Virtual machine ID CDA47693-7962-4086-8283-2A0655D53146)
At line:1 char:1
+ Checkpoint-VM -Name AZS00001 -SnapshotName "test"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Checkpoint-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.CheckpointVM

Kind regards, Andreas


Server 2019 VM running on 2019 Host - Slow!!!!

$
0
0
Has anyone come across this?  I have a 2019 Host server running 2 Server 2019 VMs, 2012R2 VM and a 2016 VM.  The speed of the 2019s is very slow even just to launch File Explorer or anything really compared to the non 2019 VM servers.  Even the 2019 Host server runs fine.  Any help appreciated.

When we can upgrade vm configuration version to 9.1?

$
0
0

Hi Experts

When I run the cmd "Set-VMProcessor vmname -Perfmon @("ipt")" in powershell, It returns "Set-VMProcessor: Cannot modify device "Processor".Unable to modify processor settings.The processor setting "EnablePerfmonIpt" cannot be modified without upgrading the virtual machine version first.(Current version: 9.0. Required version: 9.1).".

How can I set the vm processor to support for intel pt?

When we can upgrade vm configuration version to 9.1?



Hyper-V 2019 VM Cluster Replication

$
0
0
Ever since upgrading our 2 Hyper-V clusters to 2019 from 2012 R2 when trying to set up a new VM replication I get errors. Works for existing VMs replicating that were created before the upgrade but any new VMs fail. Enabling the replication seems to create the VM fine on the replica and creates drives at 4,096KB ready for replication but trying to start the initial replication fails with the error:

Start-VMInitialReplication : Hyper-V failed to start replication for virtual machine 'VM': Operation aborted
(0x80004004). (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Hyper-V could not find the virtual machine 'VM' on the Replica server and will connect to the Hyper-V Replica
Broker in the next retry interval. (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Replication operation for virtual machine 'VM' failed. (Virtual machine ID
E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5) (Primary server: 'Host1', Replica server:
'Broker')
At line:1 char:1
+ Start-VMInitialReplication -VMName 'VM'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Start-VMInitialReplication],
   VirtualizationOperationFailedException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVMInitialReplicationCommand


Doing the same process through the failover cluster gui I get a similar error. Says the replication was enabled successfully however initial replication could not be started. And goes on to say Hyper-V could not find the virtual machine on the replica server.

Has this yet to be recognized as a bug in Windows Server 2019?

Windows XP VM VirtualBox to Hyper-V / Ctrl-Alt-Del issue

$
0
0

I have few Oracle VirtualBox VM's and I wanted to move to them to Microsoft Hyper-V as it is more stable and easy to use Virtualization platform.

I converted one of my Windows XP VM's VDI to VHD file (VirtualBox to Hyper-V) from  VirtualBox Media Manager.  

Then I created a new VM in Hyper-V and attached the converted VHD as a Disk to the new Hyper-V VM

I also  installed the Hyper-V guest additions to the newly created VM 

I can start the VM and it is giving me the option to Ctrl-Alt-Del screen, but the  Ctrl-Alt-Del input is doing nothing.  I tried both by clicking the screen icon on the top left, and also by selecting Action-> Ctrl-Alt-Del.  Also the mouse pointer is not moving.  

So I am stuck here without getting the login screen


Cannot select merged drive for virtual machine

$
0
0

Hi all,

I just merged an AVHD into a VHD for a virtual machine using the Edit Disk option under the action menu after all of the snapshots had been deleted, but the VM not shut down afterwards for a long time.  I'd done this on a different virtual, and Hyper-V automatically figured out where the new drive was.  With this one, I got a progress bar regarding the merge, which filled to completion.  However, the VM refused to boot, because it can't find the AVHD file that was merged away.  When I try to change the virtual, I get a message saying:

Cannot change disk since a disk merging is pending.

However, I can't figure out how to get Hyper-V to give tell me the progress of that merge.  Any ideas?

Unable to connect to a fresh HyperV server

$
0
0

Hi

I'm unable to connect to my new Hyper-V Server 2016 using HyperV Manager from my Windows 10 client.

Both computers are fresh installations and they are in workgroup.

When I launch the HyperV Manager I type the ip address of the HyperV Server and the administrator credentials. Clicking on the Connect button it asks me if I want to Enable credentials delegation and I allow. Then it returns the error:

"Delegation of credentials to the server 192.168.1.XXX could not be enabled.  CredSSP authentication is currently disabled on the local client.  You must be running with administrator priviledges in order to enable CredSSP"

This is exactly what I did from the beginning:

- on server side I installed HyperV Server 2016, ran powershell commands "Enable-PSRemoting" and "Enable-WSManCredSSP -ROle Server"

- on client side I installed Windows 10 1909, ran powershell commands "Start-Service WinRM" and "Set-Item WSMan:\localhost\Client\TrustedHosts -Value "SERVER IP ADDRESS"", then enable local group policy on the computer:Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials with NTLM-only server authentication and add "wsman/SERVERIPADDRESS" in the Show tab, then installed the HyperV feature and disabled the W10 firewall

Any help?

This is my first time on HyperV and I didn't figure it so difficult to connect after a fresh installation....compared to Vmware it looks excessively intricate 

Thanks in advance

Thanks

External Ethernet Adapter is already bound to the microsoft virtual switch protocol

$
0
0

Hi,

I have a Virtual Switch that already bound to a Physical Adapter, and I would like to create another Virtual Switch to be bound to the same Physical Adapater, but I'm getting an error: "External Ethernet Adapter is already bound to the microsoft virtual switch protocol" Any help?


Hyper-V - Some questions on CPU / NUMA settings

$
0
0

Hi!

I'm trying to unterstand how CPU / NUMA settings are working (Windows Server 2019). I know how NUMA basically is working, but there some additional I was not able to figure out. I know that each CPU has direct address access to the assigned RAM. But there are some question how this is exactly working. Until now I only had one CPU, so NUMA wasn't a topic until now.

Following setting:

  • 2x CPU with 8 Cores per CPU (Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz)
  • HT enabled => 16 vCPU's (Threads) per physical CPU
  • 4x 16GB RAM, 2x 16GB each CPU
  • NUMA spanning enabled

  1. Case
    VM1 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB
    VM2 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    How is the physical CPU usage? Are running VM1 & VM2 on the same physical CPU (because there enough vCPUs and RAM to handle both on one physical CPU) or the vCPUs are used random over the 2 physical CPU's? If is random between the physical CPU => does this affect the performance because data in RAM's are splitted over the two nodes?

  2. Case
    VM1 = 20GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB
    VM2 = 20GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    How is now the usage? Is each VM now fixed to one physical CPU, because only each physical CPU can handle the amount of RAM without spanning and performance issue?

  3. Case
    VM1 = 40GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 40GB
    VM2 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    Is now spanning active because VM1 uses more RAM than 1 physical CPU has directly attached?

  4. Case
    VM1 = 10GB RAM (static), 16vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB
    VM2 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    How does the usage look like in this case? Is the usage between the CPU's random (assuming VM1 has only 10% CPU usage) or fixed?

  5. Case
    VM1 = 20GB RAM (static), 16vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB
    VM2 = 20GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    Now each VM fixed to one physical CPU?

  6. Case
    VM1 = 10GB RAM (static), 20vCPU, NUMA => max. CPU = 20vCPU's, max. RAM = 30GB
    VM2 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    Is this even possible => VM1 shared over two physical CPU's and VM2 fixed to one physical CPU? => are there performance issued to expect?

  7. Case
    VM1 = 40GB RAM (static), 20vCPU, NUMA => max. CPU = 20vCPU's, max. RAM = 40GB
    VM2 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    Possible performance issue because VM1 needs spanning between nodes?

  8. Case
    VM1 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB
    VM2 = 10GB RAM (static), 8vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB
    VM3 = 10GB RAM (static), 16vCPU, NUMA => max. CPU = 16vCPU's, max. RAM = 30GB

    Is now VM1 = CPU1, VM2 = CPU1 and VM3 = CPU 2?

I was not able to figure out how this is exactly working. I don't want to configure something without unterstanding it and then I'm wondering why I'm having later performance issues.

I have one additionally question which is more ore less related:

Same physical setting as above, and this VM config:
VM1 (SQL-Server) = 8vCPU
VM2 (IIS-Webserver) = 8vCPU

SQL-Server is licensed for 8 Cores (8 physical Cores / 8 vCPU's). Is Hyperthreading enabled in this case useful? Is the peformance better with hyperthreading enabled or not (or doesn't it matter)? So is Hyperthreading only necessary if I want to use more than two VM's (or one VM of this two needs more than 8vCPU's)? But if I'm disabling Hyperthreading I should reduce the Cores of VM2 because the HOST needs also cores to work.

As I understand: If SQL-Server fully needs 8 physical Cores with 100% CPU usage, enabling Hyperthreading will not help because the CPU has no more capacity?

Sorry for this many questions but reading articles on the web and books has not answered my questions.

Lost Pass-Through Disks After Planned Shutdown

$
0
0

I am setting up a home server for my father who has, up until this point in time, clung to the Windows Server 2003-based Windows Home Server 1.0 product.  The box I'm using is an AMD A8 based machine with an ASUS AMD A88X based motherboard.  I'm running Hyper-V Server 2019 as the host OS and I have a single VM running Windows Server 2019 Essentials.

The drive configuration is as follows:

60GB SSD - OS drive for Hyper-V Server 2019

256GB SSD - VMs drive for Hyper-V VM (currently it's only housing the aforementioned VM with Windows Server 2019 Essentials)

4TB HDD - One of four HDDs being used as pass-through disks for the WIndows Server 2019 Essentials VM

4TB HDD - "

6TB HDD - "

4TB HDD - "

As stated above, I was using the four hard drives as pass-through disks for the Server 2019 Essentials VM.  I was going to create a storage spaces drive pool from them on which my father would serve files to his other computers and then slowly add or remove drives as he saw fit.

Now for the problem: Everything was running well.  I had finished setting up everything and so I shut down the VM and then the host in preparation to move it to where it would operate most of the time.  Nothing unusual happened during any of this.

When I went to turn on the host this morning, it powered on just fine, but my Server 2019 Essentials VM failed to start.  I have no indication as to why it won't start other than the fact that neither the host, nor Hyper-V Manager, nor Windows Admin Center will recognize the four hard drives.  It's like they vanished.  The BIOS of the box sees them just fine and I have verified that they're still connected.  But nothing within Hyper-V Server 2019 itself nor any console connected to it can see it.  DiskPart only sees the two SSDs and I've even tried changing the SAN policy to Online with no avail.

Any advice in getting my drives back up and running (and hopefully the Windows Server 2019 Essentials VM with it) would be seriously appreciated.  Thanks in advance!

Server 2012 VM won't boot after RAID array failure

$
0
0

We've got a Dell R710 running Server 2012 with Hyper-V that had two disks go bad last week. Luckily we run RAID 6, so it just needed a rebuild after the drives were replaced.


This server runs a fileserver inside a VM. The VM will no longer boot after the rebuild. It runs the "Hyper-V Please Wait..." screen, then just stops with a black screen. I tried pinging the IP address of the VM but it's unreachable, so it doesn't seem to simply be a display error.


I tried creating a second VM using the same parameters, with the VHDX file as the disk, but it still wouldn't boot. So I mounted the Server 2012 DVD ISO to the VM so I could run the recovery environment and try some repairs:

sfc /scannow /offbootdir=C:\ /offwindir=C:\windows - says that it can't repair some of the corrupted files.

DISM /image:C:\ /cleanup-image /restorehealth - seemed to work ok, no warnings or errors.

chkdsk /f C: - took almost two days (the VM is 8TB and has millions of tiny files), and said it fixed a number of errors.

Unfortunately, none of those fixed the issue, and the VM still doesn't boot. I looked in Event Viewer at all the Hyper-V logs, but there are no related warnings or errors to help me further diagnose.

I'm now restoring a backup of the VM, hopefully that backup will boot properly.The restore operation will take a while due to the size of the VHDX, so while I'm waiting I figured I'd ask if there's anything else I can try.

Thanks!






Hyper-V Vm network disconnect continuously 10 to 15mins

$
0
0

 Hi Techies,

We have server 2016 vm which hosted on server 2016 data center (Server Model: Dell R 540), that VM network disconnecting in 10 to 15mins

We have checked event logs and find that "Miniport NIC 'Microsoft Hyper-v network Adapter #4 is halting" and Miniport NIC 'Microsoft Hyper-v network Adapter #4 is paused"

recently we have updated below patches.

KB4516044

KB4512574

KB4509091

Any one have idea on this, please help us.

Early reply will be highly appreciated.

Regards

Vajram Gajengi 

Setting up "host-only adapter" equivalent

$
0
0

Quick background to help explain the situation, I'm a cybersecurity student and i'm used to using virtualbox to learn the ins and outs of pen testing, we using kali and vulnerable OSs like Metasploitable to simulate attacks, this is what I'm trying to set up on hyper-v.

when you're using VMware or Virtual Box you have the option to setup a host-only adapter https://imgur.com/a/TVeZbd3 (screenshot host-adapter in VB), this allows VMs to communicate with each other and access the internet while being isolated from your host computer, this is obviously something you want to do when dealing with vulnerable OS's, u dont what them to create an opening to your host computer or internal network while while simulating pen testing.

I've tired for hours to set and "host-only" equivalent on hyper-v to avail... Any ideas? is this even possible to achieve with hyper-v?  


Kind Regards, and thank you in advance for your time.

Viewing all 19461 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>