Hi All,

I'm planning to configure a backup solution for hyper-V VM's. I have tried to backup hyper-V host configuration details like virtual switch details, VM's, etc using in inbuilt windows system backup. But it fails to backup hyper-V virtual switch configuration details.

Is there any way to backup my virtual switch configuration details along with VM's?

Regards, Loges

Dear All

I have the following setup.

1. Host Server which is also ADS server and DNS Server. This is the physical server. WS2012R2 is the Base OS.

2. 4 x Hyper-V Guest Servers running WS2012R2 Std Edition configured  onto this server.

3. One of the Hyper-V Servers is a Terminal Client Server. We have about 50 Thin Clients connecting to this server. Another is the application Server.

4. The Thin Clients have Win7 OS embedded on them. The Thin Clients connect to TS server first and then they can access the application server.

Problem :

Sometimes when Thin Clients try to log in ; they get message TS-Server could not be located ; i.e. the TS-Server is not accessible. But when the Thin Client is rebooted

Some times the problem goes away after a few minutes. Without doing anything.

Sometimes we have to reboot the TS Server ( Virtual).

Sometimes we have to shutdown all servers and reboot the physical host server and restart everything all over again. But the problem comes up again in next 2-3 days.

We have installed all the windows updates and patches and we do it weekly for all servers.

Any suggestions ?

Hi Guys,

I have had a quick look through the forum but cant seem to find anything on my problem.

The setup I have is as follows;

3 x Hyper V 2012R2 (Domain) Servers - IP 192.168.1.x

1 x Hyper V 2012R2 (Workgroup Test) Server - IP 192.168.9.x

I have on my Windows 10 1607 Machine the OS built it Hyper V Manager. - (Domain)

Now the problem starts here;

I can contact the other Hyper V Servers on the Domain (which I expected) but I'm having problems connecting to the workgroup server.

I have tried HVREMOTE tool to setup the trust relationship between my windows 10 machine and the workgroup server so that the manager can connect.

The HVREMOTE tool reports NO errors regarding the configuration.

There is no doubt a problem with trust relationship between W10 and the HyperV server but WHERE!!!!.

I have trawled through hundreds of internet fixes and broken many a hyperv server by doing so but nothing so far fixes the problem.

The message I get is below showing a very generic error.



But if I use different credentials (that I know has admin rights on that server) I get this error;

So I'm at a loss of where the problem lies and how to resolve it.

Has anyone had a similar problem using the Windows Hyper V Manager to contact a Domain -> Non Domain server.

Any information would be grateful.

Regards

I have an AD with a range of Server 2008R2 machines that I wish to migrate from their old physical hosts to new Hyper-V infrastructure.

My question; if I host on Hyper-V Server 2016, do all my 2008R2 server user CALs have to be replaced with 2016 Server CALs despite my users actually accessing the 2008R2 servers?

thanks.

Hi, i have a doubt.

I have an Microsoft Hyper-V Server 2016. On this server its running an Oracle Linux VM with a Oracle Database on top. The Oracle Database its configured to use ASM storage (standalone with local disks, not a RAC Cluster).

Actualy the server phisical disks are old 512 bytes SAS disk (here its Brazil Guys, i bougth a new Dell Poweredge 630 server and Dell send me these old technology disks), not the new 4K disks.

We all know that for database servers, larger blocks/stripe sizes are better for performance, but now im limited by the phisical hardware.

I want to know if i move the already in use VHDXs to a new storage (new local 4k disks or even a better iscsi storage) the linux will automaticly be beneficied by the changes or if i will have to use new VHDXs (or format the old ones) to use the updated phisical disks enhancements?

To exemplify my problems here are some the disks configurations on Hyper-V Server and on the Linux VM

PS C:\Users\administrador.CN> Get-PhysicalDisk | sort-object SlotNumber | select SlotNumber, FriendlyName, Manufacturer,
 Model, PhysicalSectorSize, LogicalSectorSize | ft -autosize

SlotNumber FriendlyName         Manufacturer Model            PhysicalSectorSize LogicalSectorSize
---------- ------------         ------------ -----            ------------------ -----------------
           FreeNAS iSCSI Disk   FreeNAS      iSCSI Disk                   131072               512
           FreeNAS iSCSI Disk   FreeNAS      iSCSI Disk                   131072               512
           DELL PERC H730P Mini DELL         PERC H730P Mini                 512               512
           DELL IDSDM           DELL         IDSDM                           512               512
           WD My Passport 0741  WD           My Passport 0741               4096               512


PS C:\Users\administrador.CN> exit

C:\Users\administrador.CN>wmic partition get BlockSize, StartingOffset, Name, Index
BlockSize  Index  Name                   StartingOffset
512        0      Disco #4, Partição #0  135266304
512        0      Disco #3, Partição #0  33685504
512        1      Disco #3, Partição #1  17408
512        0      Disco #0, Partição #0  1048576
512        1      Disco #0, Partição #1  315621376
512        2      Disco #0, Partição #2  554696704
512        3      Disco #0, Partição #3  85900394496
512        0      Disco #2, Partição #0  135266304
512        1      Disco #2, Partição #1  17408
512        0      Disco #1, Partição #0  4194304

Physical Disks on Hyper-V Server

PS C:\Users\administrador.CN> Get-VHD -Path "g:\vhds\*" | FT Path, LogicalSectorSize, PhysicalSectorSize -Autosize

Path                               LogicalSectorSize PhysicalSectorSize
----                               ----------------- ------------------
g:\vhds\nostromo-oracle-bin.vhdx                 512               4096
g:\vhds\nostromo-oradata01.vhdx                  512               4096
g:\vhds\nostromo-oradata02.vhdx                  512               4096
g:\vhds\nostromo-oradata03.vhdx                  512               4096
g:\vhds\nostromo-oradata04.vhdx                  512               4096
g:\vhds\nostromo-redo-ctlvhdx.vhdx               512               4096
g:\vhds\nostromo-root.vhdx                       512               4096
g:\vhds\nostromo-swap.vhdx                       512               4096

Virtual Disks on the server

[root@nostromo ~]# cat /sys/block/sdh/queue/optimal_io_size
0
[root@nostromo ~]# cat /sys/block/sdh/queue/minimum_io_size
4096
[root@nostromo ~]# cat /sys/block/sdh/queue/physical_block_size
4096
[root@nostromo ~]# cat /sys/block/sdh/queue/max_sectors_kb
512
[root@nostromo ~]# cat /sys/block/sdh/queue/max_hw_sectors_kb
512
[root@nostromo ~]# cat /sys/block/sdh/queue/hw_sector_size
512
[root@nostromo ~]# fdisk -l /dev/sdh | grep "Sector size"

WARNING: GPT (GUID Partition Table) detected on '/dev/sdh'! The util fdisk doesn't support GPT. Use GNU Parted.

Sector size (logical/physical): 512 bytes / 4096 bytes
[root@nostromo ~]# parted -l
Model: Msft Virtual Disk (scsi)
Disk /dev/sda: 85,9GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Sinalizador
 1      1049kB  2098MB  2097MB  fat32              boot
 2      2098MB  4195MB  2097MB  ext4
 3      4195MB  85,9GB  81,7GB  ext4


Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdd: 215GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name     Sinalizador
 1      2097kB  215GB  215GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sde: 215GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name     Sinalizador
 1      2097kB  215GB  215GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdf: 34,4GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system     Name  Sinalizador
 1      1049kB  34,4GB  34,4GB  linux-swap(v1)  SWAP


Model: Msft Virtual Disk (scsi)
Disk /dev/sdg: 107GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name  Sinalizador
 1      1049kB  107GB  107GB  ext4


Model: Msft Virtual Disk (scsi)
Disk /dev/sdh: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdi: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdj: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdk: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary

Partitions inside Linux VM

Ps.: Sorry about my bad english.

Hi All,

We have 3 Hyper-V servers 2 of which are part of a cluster, 2 physical adaptors have been dedicated to iSCSI and LUNs are presented to the hosts for shared storage. Disk failover is controlled by the iSCSI MPIO.

We have a requirement for VM's to have direct iSCSI connection(s) to access the data on the disks, i think this is called a RAW connection (correct me if i'm wrong). To configure this my thoughts were to create two vSwitches and have each vSwitch connect to the physical iSCSI interface (all iSCSI vSwitchs will have the same name across all hosts).

With this is mind it raises questions:

1. Is the correct way to do this?
2. How do the VMs deal with disk failover events if the host is controlling the disk pathing via MPIO? My thoughts were to enable the 'NIC Teaming' option by ticking 'Enable this network adaptor to be part of a team in the guest operating system' within 'Advanced Features'. Would this allow the VMs to continue to work gracefully in the event of a  failover when the hosts utilises MPIO for redundancy/load balancing?

I look forward for all of you professional guidance.

Trying to access Hyper-V running on Server 2012 R2 from Windows 10 LTSB 2016 and I only get an error:

The Hyper-V Management Tools could not access an expected WMI class on computer....

Same server accessed from Windows 8.1 H-V Management Tools is working fine.

Anybody any idea?

According to this it should be no issue

Seb

Hello Community,

I have a Windows Server 2012 R2 Host with 6 VMs. suddenly the host went inaccessible across the network due to MAC address conflict which was logged in the event log as below.

(Warning) MAC conflict: A port on the virtual switch has the same MAC as one of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver.

I've seen a resolution in one of the MSDN wiki (http://social.technet.microsoft.com/wiki/contents/articles/31357.hyper-v-mac-address-conflict-event-16945.aspx) but doesn't seems to be the right way of resolving this (Change the MAC Address Manually - not a good practice at all !)

To Describe more on the setup - we have 4 VMs connected to Production Switch (Shared NIC) | 2 VMs connects to DMZ Network (VLAN Directly binds to VM, Not Shared). When the Host gone inaccessible, All VMS became inaccessible.

Appreciate any thoughts !

Hardware:

2x Dell PowerEdge R510

1x Dell PowerVault MD3220i

Background:

Servers connected to SAN via ISCSI through 2 host ports each via a Dell PowerConnect Layer 2 switch.

Running two Nodes with Hyper-V Core installs and Failover Feature Enabled.

Validated and setup Failover Cluster for server.

Failover works (IE. VMs will be moved to Node 2 when Node 1 goes offline)

Migrations will work (live, move and quick).

Problem:

When both servers where recently shutdown for power maintenance in the building, after being turned back on both servers failed to mount the Cluster Shared Volume properly.

The Shared Volume is showing Online in the FailOver manager, but in iscsicpl.exe the mount point for the volume is not set to c:\clusterstorage\volume1 but instead it /?/volume/{GUID}/

When trying to direct to c:\clusterstorage\volume1 it is listed but freezes when trying to access it.

If you remove the volume from shared it mounts properly.

TL:DR

Cluster shared volume doesn't mount after simultaneous restart of servers, only show the mount point as /?/volume/{GUID}/ cannot remount as shared.

Hi all,

Windows Server 2003 is not supported as a guest VM on Hyper-V 2016.

But I have a case where we need to keep an old Windows Server 2003 running for approx another 5 years.

Has anybody tried to run Windows Server 2003 as a VM under Hyper-V 2016?

If yes - any problems/fixes/need-to-know-trics I should be aware of?

Thx.

PS: I know Windows Server 2003 is EOL and should be long gone, but it's not going to happen in this case!

Hi all,

i'm trialing Hyper-v 2016, enabled Hyper-v in one of the VMs and also enabled MAC address spoofing on the NIC.

The issue is, even though the Hyper-v VM got MAC spoofing enabled however the nested VM cannot access network.

When I look at the network status of the VM using Hyper-v manager I don't see the MAC address of the nested VM either, seams like the MAC of the nested VM is not learnt

Any suggestions? 

We have Windows Server 2012 R2 Domain Controller.. and have 4 ADC at different location.

when I take new PC in domain it gives me following error first. when I restart PC 2-3 times it connect to domain ..

It should connect to nearest Domain Controller but it's not connect to nearest DC... showing logon server after this cmd set l..

....

We have a 2 nodes Hyper-V cluster.

Failover VM setting "Cluster-controlled offline action" is Save

Hyper-V VM setting "Automatic Stop Action" is Shutdown

1) What happens if a shutdown a host ?? Will VM move to other host ??

2) What happens if a move a VM (domain controller) to other host ?? Is supported live migration on DC without shutdown computer ??

While testing the Xamarin project on Windows Phone Emulator I get <g class="gr_ gr_19 gr-alert gr_gramm gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="19" id="19">error</g> that there was some error starting the VM.

I launched <g class="gr_ gr_15 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="15" id="15">Hyper V</g> manager and I see a VM for emulator

When I start the VM from <g class="gr_ gr_17 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="17" id="17">Hyper V</g> Manager, I see error as 

An error <g class="gr_ gr_21 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="21" id="21">occured</g> while attempting to start the selected virtual machines(s)

'Mobile Emulator 10.0.14393.0 WVGA 4 Inch 512MB.a_2' failed to change state.

The operation failed with error code '32788'

Note: The emulator of android works well.

Jignesh

I have been tasked with deploying Windows 10 on Hyper-V on Windows 10 Enterprise for a small group of testers to use to test Office 365 environments. I ma fairly new at this. 

My predecessor had created a USB drive which contained the following:

1.  Windows 7 Base Image (sysprepped)

2.  An unattend.xml file

3.  An Executable that basically starts Batch Script which in turn starts a PowerShell script.  

4.  A folder containing a PowerShell and Batch script

The PowerShell script is pretty great:

It does a bunch of checks (usb drive name, proper cred's, windows 10 installed, verifies naming scheme with company policies) before checking for hyper-v and turning that on if missing.  It then creates a modified version of the pc name based on computer script is run on and adds VM.  Then is copies the template hard drive (#1 above) and the unattend.xml.  It then adds the user credentials provided by user to the unattend.  Next it mounts the hard drive and copies the modified unattend, and then dismounts drive.  A virtual switch is created, the hard drive is renamed according to naming standards, and the vm is created and started.  It works really, really well for the Windows 7 image.

I am trying to convert this to do the exact same thing for Windows 10 and having issues.  

I have a VM that is set up like I want and I sysprep it. I need to copy a VHDX file, but it seems to me that a avhdx file is created.

Where is the basic directions for doing this located?    

Matt Dillon

Hi

2 fysical hosts running Windows 2012r2 with all windows updates/hyper-v patches.

Today i updated both host servers with newer broadcom nic drivers. 2 nics are used to iSCSI and 4 nics for all other hyper-v traffic. Before updating the first server, i drained all rules, so the second server had all guests running.

Updated nic drivers, rebooted, undrained all roles and then drained the second host server. Same procedure.

After both hosts was updated with new nic drivers and running normally, I noticed all my guest (both windows and linux) had rebooted. Just like if i did a hard reset from hyper-V.

This has not happened before, where I live migrated machines.

Any idea why the below happened?

Host2 Eventlog when host1 server was paused:
Cluster node 'Host1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Ownership of cluster disk 'Quorum Disk' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

Cluster resource 'Quorum Disk' of type 'Physical Disk' in clustered role 'Cluster Group' failed.

The Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Clustered role 'Cluster Group' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made to bring the role online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

The Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

regards

robert

Back story

Thanks to this annoyance Here's my setup.

Single Test Hyper-V Nano 2016 TP5 on a Laptop, Single NIC. Cisco switch configured as follows

 description Connection to test hyper-V
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 21
 switchport trunk allowed vlan 21,30-35
 switchport mode trunk

This finally allowed me to have a trunk port for the laptop while still allowing the non-vlan tagged traffic to be allowed.

The problem now is, I connected to the server from my workstation using Hyper-V Manager Snap-in.

My first issue was how difficult it was to mount an ISO for the new VM. You can only specify the hosts DVD drive (How this is remote management beats me), can't copy anything to the Hyper-V server through Hyper-V Manager (AFAIK). I literally had to copy the ISO onto a USB stick, plug that into the laptop, open cmd and copy the file to the hyper-v's local storage. Man that is painful.

Attempting to connect to a hyper-v system that isn't domain joined. Also Really difficult (When connecting from a domain joined machine anyway).

And finally my biggest pet peeve from this testing.

I went to create a "external" vswitch on hyper-v manager. I created an external vswitch, using the only NIC available (the only one it has) specify the vlan ID for it (Wow amazing MS didn't forget to add that :S). Sure enough it says connections will fail while making the changes. Sadly I lost 6 pings, then 3 pings came back, and then it completely died. I can't reach it. When I login directly I can no longer ping the gateway.

How can I create a "external" vswitch, while retaining the non-vlan tagged mgmt IP... or better yet... how can I add a mgmt vlan ID to the dang MGMT network!!!!??!?!?! ARGGGGG