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

Hyper-V in Windows Server 2012 R2 Essentials - Newbie information gathering question

0
0

Hello:

I am new to virtualization in general.  I am trying to figure out what I can do to install management software that uses SQL Server 2017.  As you know, SQL Server does not like to be installed on a domain controller which is the Windows Server 2012 R2 Essentials operating system. Rather than buy another server just to run SQL Server 2017 and buy another operating system, I was wondering if its possible to install the Hyper-V role and use the Hyper-V to create a virtual machine just for SQL Server 2017, the management software and the remote access into the management software thru an IIS website that has an SSL Certificate.  Would I be able to leave the existing operating system the way it is if I am able to use Hyper-V? I am interpreting some web sites as saying I could have 2 copies of my operating system then. One being virtual.. then other websites I interpret it as it becomes 2 virtual machines.. one basic, one with all roles and features.  I am not sure what to do, if its possible or if I should be looking another direction. Again, I am totally green to this whole area so need some direction.  I don't want to affect what the server is doing right now.. I don't want to cause it issues by installing SQL Server 2017 on it.. possibly...

if this is possible at all in hyper-v... could someone point me in the right direction to learn more as a newbie and figure out how to configure it and access it etc...


Error exporting Hyper-V VM

0
0

I am running 2 VMs in Server 2008 R2 with Hyper-V. But am running out of space on the partition where the VMs were created. I have another larger partition on the same Hyper-V server and want to move the VMs to this larger partition.

I was able to successfully export one of the VMs to the larger partion and import it succesfully. The process ran perfectly.

However when I try to export the second VM the following error is is generated...

-------------------------------------------------------------------------------------
An error occured while attempting to export the virtual machine.
Export filed for virtual machine 'SALVO'.
Export failed for virtual machine 'SALVO'
(41322DFC-B316-4CF8-9B19-7753078F0D4B) with error 'The system cannot find the file specified.' (0x80070002).
-------------------------------------------------------------------------------------

What can I do to resolve this error. The VM is functioning fine. I don't understand why I am not able to export it. At one point in time I did have a second vhd attached to the system. But I removed it long ago and there were no observable side effects.

Thanks, David

HyperV Cluster Replica Broker error - "object could not be found" from Enable-VMReplication Powershell

0
0

Ok I admit it. This one is driving me crazy ;)

1) I have two Server2016 (Standard) HyperV Clusters - Source01 and DR01. Both part of same forest/domain.

2) Both Source01 and DR01 clusters have a HyperV Replica Broker installed and replication settings configured for Kerberos, Port80 and allow from any server.

3) I can initiate VM Replica successfully in both directions using the FailoverClusterManager UI. It creates the replica, transfers the initial data and everything appears to work.

However....

I need to create the replica using Powershell, but when I try to do it using the Enable-VMReplication powershell command it fails with:

I must be doing something wrong as the UI works. Perhaps some remote permissions not enabled? Remote WMI? something? hopefully some rookie mistake...

1) I've turned the firewall of DR01 off (just in case, just until figure out this issue)

2) The hyperV virtual machine management service is running correctly on both Source01 and DR01

3) the HyperV console on Source01 can correctly connect to DR01 and view/manage the VMs in the console - and vice versa.

Anyone got any ideas? Or seen this behaviour before?

thanks

Joe.

Hyper-V 3.0 VM stuck in "Stopping" state

0
0

We are running Hyper-V on a 2012 server and for the 20nd time in as many months I've logged into a VM and restarted or migrated to another host it but it's stuck in the "stopping" state in Hyper-V 3.0 and doesn't give me any Turn Off, Shutdown, Save, Pause or Reset options.  The only thing I've been able to do is to schedule a time to reboot the Hyper-V server.  Has anyone else experienced this?  Is there any command I can run get the VM  top turn off  w/o having to reboot or restart the Hyper-V service?

Our host environment as below:

HP C7000 Blade Chasis

16x ProLiant BL460c Gen8 Server (Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz (8 Cores) - 256GB Ram)

Blades server have Hp FlexFabric 10Gb 2-port

2x HP VC Flex-10 Enet Module on Chassie

HP VC 8Gb 20-Port FC Module on Chassie

Also We turned off tcp checksum offloading but it didn't work.

We've opened case to HP support but they analyzing our system and didn't find any problem to themself.

Does anybody have any fixes for these problems?

Kerberos error when attempting to connect to Hyper-V Server from Hyper-V manager

0
0

When I am attempting to connect to the Hyper-V Server from the Hyper-V manager i get this error:

https://rakhesh.com/windows/hyper-v-between-windows-10-windows-8-1-in-a-workgroup/

I got my notebook and server connected to the switch which are not having internet. I configured the IP-addresses and subnets and they can ping to each other. I can also start a remote session on the server from my notebook. They both are also in the same workgroup.

I already configured the Windows Hyper-V 2016 Server as TrustedHost on my notebook and TrustedHost on the server of my notebook also both with CredSSP. I followed this video: https://www.youtube.com/watch?v=ffsRoZxUFGI&t=952s

Anyone knows if I need to activate or code something more? I have read that there were new updates that caused this error. The ISO file of the server is an evaluation file which I downloaded today. My notebook is running Windows 10 Pro with the newest updates and build 1803. It is a HP Probook notebook.

Don't mind my English language, I am a Dutch student and I still need to learn some better English :)

Thanks in advance.

Server Service

0
0

Hello,

Does hyperV Host server need the server service to operate?

I want to lock down smb and file share access to the server from network clients. 

Hyper-v Converged network

0
0

Hi,

Im setting up a new 2016 failover cluster. I just want to clarify that im understanding the concept and design of this converged network. On my physical server i only have two 10Gb Nics which i need to team. The switchports in which the NICs are connected as an etherchannel LACP and the etherchannel is an Access port.

So traditionally, i'd fire the LbfoAdmin console and configure NIC teaming on the management OS. In a Hyper-v Converged network, im not going to do this. Instead, Im going to team the NICs on the vSwitch itself. So id run a powershell that looks something like this: New-VMSwitch -Name vSwitch -AllowManagementOS $True -NetAdapterName NIC1,NIC2 -EnableEmbeddedTeaming $True.I will then configure vNICs and assign to appropriate vlan. When the packets from a VM with a vNiC configured for vlan 20 will leave the physical NIC and onto the switch, it will be tagged with vlan 20, likewise for ingress and Hyper-v will understand where to deliver the packet. 

Is the above correct? I have two questions:

  1. In order for this work, i need to configure the switchport as a trunk port. However, would i need to remove the etherchannel LACP considering that EmbeddedTeaming is must likely not going to perform an LACP negotiation, or will it?
  2. Part of the traffic is obviously storage, ISCSI. I would like to configure MPIO between two NICs, or is it unnecessary because the EmbeddedTeaming takes care of aggregating and failing over? If not, then can i still configure MPIO?

Hyper-V build 1703 generation 2 PXE has faulty ARP implementation

0
0

Since build 1703 came out for Windows 10 Enterprise x64, with Hyper-v enabled, the ARP protocol does not work correctly in a Gen2 vm during a PXE boot. The result is that the DHCP protocol does not work in a gen2 vm, and thus, pxe booting is broken in a gen2 vm on the 1703 build.

Host and guest are on subnet: 10.1.29.x /24
DHCP server IP: 10.1.1.3
PXE server IP: 10.1.1.3

Here is correct ARP behavior, on a gen1 vm, notice arp for default gateway mac address, and subsequent successful DHCP, then successful download from the WDS server at 10.1.1.3.

gen1-vmguest-1703host-ARP-correct

Here is the faulty arp behavior as found in a Gen2 vm on the same host as above.Notice the ARP protocol trying to get the mac address of a remote subnet IP. Anyone that understands the ARP protocol recognizes immediately that this can never work.

gen2-vmguest-1703host-ARP-failure

Somewhere during the 1703 dev cycle this ARP regression was introduced. This needs to be investigated by the developers as there is no way to "configure" how hyper-v's gen2 embedded PXE code implements the ARP protocol.

Please don't comment regarding "how to pxe boot in hyper-v" this PXE infrastructure is perfect. UEFI and BIOS based physical PCs on the 10.1.29.x subnet can PXE boot just fine from 10.1.1.3. Additionally, reverting the host hyper-v OS back to 1607 build, gen2 vms can successfully PXE boot. The ARP traffic change is the smoking gun for this regression.

This ARP bug is only present in build 1703, with a generation 2 vm.

Hope this is useful to help get this critical regression bug fixed.

-Ben


Server 2016 Hyper-V Virtual Machine Always Turns Off

0
0

If I try to restart a virtual machine, hyper-v always turns them off instead of rebooting.  I have to use the hyper-v manager to manually start every instance if a restart was issued within the VM.  It does not seem to matter what OS the VM is, it happens with Linux, server 2016 and 2012 R2 instances.

I notice an error:  'VM-****' could not reinitialize. (Virtual machine ID *******-****-****-****-************)

I thought at first it might be permissions but the hyper-v host is in an OU with blocked inheritance.

What might be causing VM's to fail to reinitialize? 

Hyper-V Server 2016 - HNV 1.0 - configuration lost after a while

0
0

Hi Expert,

Background and issue:

  1. Hypervisor: Hyper-V Server 2016 (note that it's not Windows Server 2016)
  2. Deployment Model:Standalone
  3. Host Network: NIC teaming is used, and 2 physical NICs
  4. Hyper-V Network Virtualization: 1.0 (just consider it's supported by Hyper-V Server 2016 since both HNV1 & HNV2 are supported by Windows Server 2016)
  5. Want to implement network isolation by using HNV 1.0
  6. run the following PowerShell command: 
New-NetVirtualizationLookupRecord -VirtualSubnetID "5001" -CustomerAddress "10.156.1.1" -ProviderAddress "172.31.153.101" -MACAddress "00155D971F27" -Rule "TranslationMethodEncap"

    7. after that, I can view the lookup record by running get-NetVirtualizationLookupRecord, but almost 3-5 minutes later, run get-NetVirtualizationLookupRecord again, no any output, seems that the configuration is totally lost.

Thanks in advance!


amoschb

Windows Server 2016: Virtual Machines randomly lose disk access

0
0

Greetings all,

I've recently migrated my Hypervisor from Windows Server 2012 to Windows Server 2016 DC. In the three days since moving, three of my VMs, Two Windows Server 2016 and One Ubuntu Linux 1604, have suddenly and unexpectedly seemed to have lost disk access at different times.

In the case of my Ubuntu VM, tools such as htop and ps fail and my root fs has transitioned to ro mode. 
In the case of my Windows VMs, tools and applications still "work" but tools such as Resource Monitor report 0 disk activity. 

In all three cases, the VMs hang on shutdown/stopping and nothing short of a full reboot of the hypervisor has helped.  Other virtual machines will successfully start/stop/reboot without a problem.  The hypervisor will actually not reboot, hanging stopping the "Hyper-V Virtual Machine Management" service requiring a hard power-off.

After a reboot, the affected VMs are fine, outside of the Ubuntu VM experiencing some disk corruption.

Server hardware:
E5-1650v4
192G DDR4 2400Mhz
4x4TB Raid 10
2x I210 Gbit Ethernet

Any ideas?


Virtualize SQL cluster

0
0

Hi all,

We have a customer who has a two-node windows 2012 R2 cluster, on top of that cluster he has four clustered instances: two file server instances and two sql cluster instances; my question if it is possible to do P2V for this physical cluster to be running in Hyper-V cluster environment? Note that the Hyper-V cluster is using fiber not iSCSI

Video remoting was disconnected

0
0

After last Win10 update I couldn't reach my VM, with constant error "Videoremoting was disconnected".


Live Migration - Failure issues within Hyper-V Cluster

0
0

Hi All

We have two dell hosts within a cluster I am having massive issues with.

Host01:

OS - Server 2016 DC

Model - Dell PowerEdge R730xd

CPU - Intel(R) Xeon(R) CPU E5-2650 v3 - Intel64 Family 6 Model 63 Stepping 2

Host02:

OS - Server 2016 DC

Model - Dell PowerEdge R740xd

CPU - Intel(R) Xeon(R) Gold 5115  - Intel64 Family 6 Model 85 Stepping 4

Live migrating from host01 > host02 - flawless.

Migrating from host02 > host01 flags errors all over the place for every VM:

"Live migration of 'Virtual Machine MOD01' failed.

Virtual machine migration operation for 'MOD01' failed at migration destination 'HOST01'. (Virtual machine ID)

The virtual machine 'MOD01' is using processor-specific features not supported on physical computer 'HOST01'. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine. (Virtual machine ID)"

The compatibility checkbox is very enabled - quick migration (from a started state) won't start the machine at all on host01. Only way I can migrate within this cluster is with the servers offline which isn't especially cluster like and will cause issues during the next CAU update window (yes - this has previously successfully performed CAU just last month!)

I've googled to the extreme and all I can find is "enable the checkbox" which is already enabled. The VM's are in a mixture of Configuration version 5.0 and version 8.0. Previously I was able to migrate majority of servers with only one or two having the error (which were just test machines so shutting them down wasn't a major issue) but now - its every machine on the newer host.

Is anyone able to provide any direction for this one as I am at a complete loss here.

Thanks.

Cannot perform Planned Failover

0
0

When trying to first time perform PFO I get an error that primary server does not authorize the replica server to send replication data. Both Hyper-V are running on Windows Server 2016 and both are on the same domain.


Hyper V with NIC Teaming

0
0

Hi

I have to create Hyper Failover cluster and i will host 22 VMs with multiple Vlans ( vlan 33 , vlan 34 , vlan 42 Vlan 22)

my question:

After i create teaming and Virtual switches and Vnics

what is the TCP /IP configuration for Vnic ( Management , Live Migration , Clusters , etc)  is it required to put Gateway or ip & subnet only ??

What is the configuration for NIC teaming card ? shall i put ip adreess for Tnic?

I will create Vswitch for each different Vlan , what is the configuration in the VM itself to stick its vlan on its traffic?

Thanks


MCP MCSA MCSE MCT MCTS CCNA

Migration from Hyper v 2012r2 to Hyper v 2016

0
0
Hi,

We have 3 Hyper v clusters running on Windows 2012 R2 and using SCVMM 2012 R2 to manage this clusters.

We are introducing a New infra with new Servers and Storage in environment

On new servers we have installed Windows Server 2016 and enabled the hyper v role.

Now we want to migrate SCVMM from 2012 r2 to SCVMM 2016, also want to move the VMs from Windows 2012 r2 hyper v to Windows 2016 Hyper v.

Please suggest how to migrate the SCVMM and VMs.

VMs not restarting properly in Server 2016

0
0

I have several VMs running in Hyper-V on Server 2016 that we shutdown remotely and then reboot the host. They're all configured to automatically restart upon the host's reboot, with a startup delay varying between 30 and 600 seconds (each VM is different). 

SOME of the VMs will happily restart.  SOME of the VMs do not start at all.

Looking in the Hyper-V event logs, there are absolutely no errors or complaints logged at all. It's as if it never even tries to restart those VMs. 

We're not doing anything weird storage-wise; all VMs are using the same HDD storage area. We're well within the available RAM of the host machine (128GB). There's nothing odd about their boot options. Several of these VMs are identically configured to each other, and one will start while the other won't. 

What in the world is going on?

Hyper-V 2016 DDA issue: a VM boot fails when a drive is connected to an opposite NUMA node

0
0

Brief description: the host is Windows Server 2016 Datacenter Build 14393 (UEFI) running Hyper-V role. SR-IOV and Intel VT are enabled. 4x Intel® Optane ™ SSD 900P 280GB PCIe NVMe 3.0 drives are connected to the host. To check DDA support, I execute the PowerShell script that returns OK, DDA is supported. Ubuntu Server 16.04 (gen 2) VM is deployed. All required packages were installed to the VM. Then, I've connected those 4x Optane SSDs to the Ubuntu Server VM via DDA. After that, additional settings -LowMemoryMappedIoSpace 1Gb -HighMemoryMappedIoSpace 4Gb were applied. So, VM has passthrough connected 4x NVMe drives. The reboot/shutdown/power-on the Ubuntu VM works without a problem. Also, there are no issues with the connectivity between drives and VM.

The problem case: when the Windows Server host reboots, the boot of Ubuntu Server VM fails.

From what I found, I assume a NUMA node configuration is the problem. The VM's boot fails because of NVMe SSDs that are connected to another NUMA. For the information, 2x SSD drives are connected to #0 NUMA node and another 2x SSDs have the connection to #1 NUMA one.

So VM's boot runs on the #1 NUMA node and fails. The VM boots only when NVMe SSDs running on #0 NUMA are disconnected.

Hyper-V failover solution for systems generating large number of files

0
0

Hi All,

In our environment we have a 2 node cluster, we also have a cluster located at our DR site that we are using to replicate our VM's to in case of the event of a DR failure. Our production site has 10 VMs (plus many others), the 10 servers receive data from our users and write the data back to a PRIMARY server. The PRIMARY server then tags the data, indexes them and saves it to a folder that is created daily. On average, our users/servers generate 10,000 files a day totalling 2GB.

As you can see we have single point of failure with the PRIMARY server and we are looking for a solution that will allow us to have redundancy should the PRIMARY server fail. We have discussed serveral options however none of them feel right due to other issue they my present or it being extremely complicated.

We have discussed the option to:

  1. Create two new VM's on the cluster/nodes and within the two VM's create another cluster, we would then add the file share role between them hosting a UNC/file share. We would replicate the VM's to DR via Hyper-V and use SAN replication for the data.  - The issue we have with this is the VM's are hosted on the existing cluster, we could need to connect ISCSI directly to the VM's however the attached storage would not have failover/MPIO capabilities as they are not CSV's.
  2. Add the file server role to the existing cluster and the 10 servers would all write to the UNC path - The issue here is fail-over with regards to DR. Since our DR cluster is separate from our production site how would we replicate the file server/share role to the DR cluster?
    We could use DFRS however i am not sure DFRS is a good idea give the amount of files and data being generated.

I am reaching out to everyone to see if you have any other solutions we could use to achive a our goal simplisticly. I look forward everyone's suggestions.

Viewing all 19461 articles
Browse latest View live




Latest Images