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

Server 2012 R2 And Hypervisor Issues

$
0
0

Im having some issues and Supermicro customer support is not being very helpful. Anyone have any thoughts on this.

 Please see below:

I have a SC846e1:

MB: X8DTE-F

PR: x5660 (2)

Mem: 32gig Samsung EEC 1333

Raid: adaptec 6805 (slot 4)

OS:Samsung 850pro SSD (2) (direct to the raid card, raid 1)
Files: HGST 3tb NAS (6) (enhanced JBOD) (using StableBit BD to pool)

 I am trying to enable Hyper-V on a new build with Server 2012r2. I have added the role and it caused a boot loop which I found to be due to having "execute-disable bit capability" enabled. I disabled this and it booted up but hypervisor will not start and states that virtualization  andexecute-disable must be turned on.

I have reset the bios to "optimal defaults" and have only changed: (did a complete power off to validate change)

  • numlock: disabled
  • execute-disabled: disabled (due to boot loop)
  • IPMI: configured

 

There is also a mention in the error for hypervisor not starting that states thatvt-d and trusted execution must be disabled.

VT-D: is confirmed to be disabled

 Trusted execution: cannot be found which i believe is TPM which is not showing up in he bios and while looking at the manual and board can only find a TPM header but no jumper to disable it as per the instructions in the manual. (Manual states to disable TPM with a jumper)

 Is TPM what is causing my issue? and causing the boot loop when execute-disabled enabled?

 Also checked boot loader and hypervisorlaunchtype: Auto

 Any assistance you can provide would be greatly appreciated

 

Long Story short....I have reformatted and reinstalled with no changes before implementing the role. once the role is implemented and then rebooted it goes into a boot loop that can only be stopped is when BITS is disabled. Supermicro has no idea why it would be having a boot loop and the VT-D should be enabled. Ive tried it both ways with no effect.

Hyper-V Dynamic memory, Driver Locked

$
0
0

Hello All,

I've been wondering about the following.

I have 2 Dell R910 (Windows Server 2008R2 SP1) machines as my Hyper-V host machines, with around 40-50 VMs running on it. For most of my servers I've enabled dynamic memory, but on some of these machines I've seen the following:

For some reason this machine running Remote Desktop Services (with Web Access) is using around 3.8GB of memory.

Processes list only a fraction of the actual Memory being used.

But RAMmap shows that 2.5GB is being used by Kernel Drivers. From what I've read this might be the balooning effect of the dynamic memory. However, the RAM usage was the same yesterday evening (12h before I took these screenshots), when no one was actually working on this server.

I've seen this happen on multiple of my guest machines, the machines are running Windows Server 2008 R2 SP1 Datacenter Edition.

Can anyone explain to me why it is doing this?

Thank you.

Kind Regards,

Tom

Connect is not working on Hyper-V Manager on Windows 8.1 ( vmconnect does not work )

$
0
0

Hi all,

I have been running Windows 8.1 and in Hyper-V Manager, i can see 2 VM ( 1 Linux-Ubuntu , 1 Win 7 ) for couple of months.

Few days ago as usual i wanted to connect one of them while they were running but it did not work. I tried actions below already:

- Checked the event logs and they were saying vmconnect is crashing

Faulting application name: VmConnect.exe, version: 6.3.9600.16384, time stamp: 0x5215cae5
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0x6c0
Faulting application start time: 0x01d02e59f75297d7
Faulting application path: C:\WINDOWS\system32\VmConnect.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 351cf3fd-9a4d-11e4-beaf-7446a0bad879
Faulting package full name:
Faulting package-relative application ID:

=================================

Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
   at Microsoft.Virtualization.Client.Interop.IMsRdpClientNonScriptable3.set_NegotiateSecurityLayer(Boolean)
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.SetSecureModeOn()
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.CreateRdpClient(Boolean)
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)
   at Microsoft.Virtualization.Client.InteractiveSession.InteractiveSessionForm..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)
   at Microsoft.Virtualization.Client.InteractiveSession.VmisApplicationContext.TryParseCommandLine(System.String[])
   at Microsoft.Virtualization.Client.InteractiveSession.Program.Main(System.String[])

=================================

- Stop antivirus Avira, remove Hyper-V, restart add Hyper-V again, restart

- reboot, shutdown computer

- add new VM, delete existing one

-add/delete/modify virtual swtich and add/delete/modify virtual switch accordingly the connected VM

- restart Hyper-V Management services from services.msc

I dont know what is going on... When i open Hyper-V Manager i can start/stop VMs and i can see from preview that they are running.




Not able to communicate to virtual machines running on Hyper-V

$
0
0

Hi team,

i am facing some challenge in my production setup.

My Setup:

  1.       2 Physical Server   (Hyper-v Enabled)
  2.       3 Virtual Machines running on Each physical Machine
  3.       1 Firewall (both physical servers are connected Firewall)
  4.       No VLAN are configured.
  5.    All same subnet (192.168.181.XXX

Issues:

  1.       When I Ping from Physical Server A to Server B and vice versa       [working]
  2.       When I Ping from Physical Server A to Physical Server A Virtual Machines and vice versa [Working]
  3.       When I Ping from Physical Server A to Physical Server B Virtual Machines and vice versa [Not working]
  4.       When I Ping from Physical Server A virtual machine to Physical Server B virtual Machine and vice versa [Not working]

Please help to solve this issue.


k sivakumar


Cannot connect to local VMs after awhile until I reboot

$
0
0

I'm running Hyper-V on Windows 2012 R2 with several VMs. Everything works fine for awhile. After a random period of time, I find that I can't connect to the VMs from the local Hyper-V Manager. When I attempt to connect, eventually a Virtual Machine Connection window will come up with Connecting to <vm name here>. I end up having to just kill the task. If I try to use vmconnect, the program just locks up after selecting the server (localhost) and the machine and hitting OK. I can turn the VMs on and off but that is about it. If I try to look at the properties, it shows the Settings screen with Loading... until I cancel out. All of the VMs function normally otherwise. A reboot of the server always fixes this.

I'm looking for ideas on where to look to fix this.


Dan

Best Practices for settting up Hyper V.

$
0
0

I plan to have 3 servers go virtual.

I'm building a server and trying to figure out how to setup.

Was planning a mirror of 2 x  300 GB SAS drives at 10K for the Hypervisor

And a raid 10  of 4 x 600GB 15K drives for the datastores and storage.

Now I'm wondering if the 300GB mirror is necessary, if I install teh hypervisor on this should I put datastores on this too? and the storage for the data stores on the raid 10?

If I use the mirror of 300Gb for ONLY the hypervisor and all the OS installs and Datastores on the Raid 10, is 300GB overkill? I have been reading about others using flash drives for this, should I downgrade these to 146GB drives then?

Trying to save a few bucks. 

Thank You,


nambi

Restore WIM of a physical computer to a Hyper-V Virtual Machine

$
0
0

Hello and thank you in advance for any help or suggestions

We have a laptop system which contains a lot of important functions (SQL Database, etc) and we have captured an image of the system using the command line imagex tool. The WIM file is saved on a network share.

I tried to use imagex to apply the wim file to a virtual machine and I am having problems getting the virtual machine to start. The machine starts and begins to load Windows, but quickly blue-screens and restarts. I have attempted to run startup repairs tools to resolve the issue without success.

I would like to know if someone has suggestions about how to apply this existing wim file to a virtual machine. The physical computer cannot be sysprepped or modified and if possible I would like to use the WIM file I have already created, I think I am missing a step in the process.

Hyper-V bin file consuming disk space.

$
0
0
Hi,
  
Host OS Configuration:- Windows 2008 Enterprise ,Hyper-V with KB950050 (64bit) update.
Host Hardware Configuration:- Xeon X7350@ 2.9 GHz x 4 CPU / 64 GB

I installed virtual servers on Hyper-V and found that everytime ".bin" file( with GUID) in snapshot folder ( default path is - C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines - this location can be changed using the snapshot location settings in Hyper-V settings) consuming disk space exactly same as memory configured for the guest OS in host system disk.It get disappeared when the guest OS became down.
we require to configure virtual servers with 20 GB RAM or more & found it requires additional disk same as RAM allocated in host system apart from the VHD allocating.

Does this mandatory ? i didnt find any MS article stating anything about it.
there is no snapshot created in hyper-v for virtual servers anyway.
Can we avoid this additional disk space requirement ?

Cannot Get Replication to work Remote Site

$
0
0

I have a fairly simple setup, 3 hyper-v servers replicating 2 VMs.

HVS12 windows 2012 R2 VMs replicating to HVS2 on the same site..

Then I extended replication from HVS2 to HVS3, the replication took place 3 servers show good replication health..

I move HVS3 (with extended replication ) offsite and connect through VPN.

HVS3 can no longer replicate. Evetlog show the 2 errors, one after the other.. all servers can ping back and forth, port 80 is open on all 3 server , confirmed with NMAP.

"Hyper-v failed to replicate changes for virtual machine "FSR21" (virtual machine ID xxxxxx). Hyper-v will retry replication after 30 minutes

Source V-VMMS, event ID 32315

Could not replicate changes for Virtual machine "FSR21" as the replica server "HVS3.mydomain.inter" on port '80' is not reachable. The connection with the server was terminated abnormally (0x00002EFE).

Source V-VMMS, event ID 29292

I have now tried this on 2 separate server (rebuild HVS3), I cannot get the offsite server to replicate, any help would be much appriciated, thanks.


Hyper V 2012 R2 Cluster

$
0
0

Existing Setup:

1. Currently Hyper V is installed on DXBHYP17 (Standalone Server)

2. Total 8 Virtual Machines are running on it

3. 2 TB of LUN is mapped to DXBHYP17 (1.5 TB of data used)

4. Teaming is configured

5. 2TB additional LUN is mapped to DXBHYP17 for backup of VM’s

Requirement:

1. Customer want to make cluster of DXBHYP17 and DXBHYP18

2. All the VM’s has to be migrated to 3TB CSV from 2TB LUN

3. Later 2TB Existing LUN and 2TB Backup LUN should be converted to CSV after successful migration of           VM’s to 3TB CSV

Plan of Action:

1. We have to make DXBHYP18 ready for cluster creation

2. Cluster should be created for DXBHYP17 and DXBHYP18 with 3TB CSV

3. VM’s should be migrated from 2TB LUN to 3TB CSV

Note: I would need to understand here do i need any additional precautions here before creating the cluster.

Also if any one has done it before please share the steps.

Lost Network Connectivity After Creating Virtual Switch

$
0
0

Hi, 

I'm at my wit's end here. I would appreciate some help getting a virtual switch up and running. Here are the details...

  1. I create an External Virtual Switch bound to my Broadcom wireless adapter (allowing OS to share the network adapter).
  2. I select OK to the "Pending changes may disrupt network connectivity" dialog.
  3. A new vEthernet adapter is created, along with a network Bridge, bound to my Wifi adapter.

At this point, my connectivity is effectively gone. I can connect to the wireless network, but Windows reports "No internet access." Ido get a DHCP address assigned, but it goes wonky after that. If I run arp -a, it might show me my router/gateway initially, and I can ping it for a very brief window of about 30-ish seconds, but the ping results are terrible, as in ~800ms, if the ping returns at all. After that window of time, the router disappears off of arp -a and I cannot ping it (or anything except my machine) anymore.

I'm running Windows 8.1 x64, Hyper-V 6.3.9600.16384. I'm trying to connect to a TP-Link Archer C8.

I've tried rebooting my machine and the router, along with a million other things.

I see something going on with the System process (NT Kernel and System) that is taking up a full CPU core. It's spinning at 100% trying to do something, but I'm not sure what. When I remove the Virtual Switch, everything goes back to normal. Otherwise it stays there stuck. Maybe that clue helps, I dunno. I appreciate any help!

Hyper-V integration API

$
0
0

Hi, 

Is there a way to integrate to the Hypervisor level of Hyper-V. 

As it exist in VMware products and others. 

For example: 

Integrating to the networking layer to monitor the network traffic that goes in/out of VMs throw the Hypervisor level?

for integration of  networking product like that:

http://www.checkpoint.com/products/virtual-edition/

[

  • Inspect inter-VM traffic with hypervisor-level integration
  • Secure virtual machines without changing network topology

]

Thanks


VSS errors on Application-consistent replica VM

$
0
0
I have 2 2008R2 VMs and 3 2012 R2 VMs with SQL 2012 Sp2 installed that I have set to do an application consistent replica every 4 hours from one HyperV 2012 R2 host to another.  The integration services are all version 6.3.960.16384 which matches the host.  The Hyper-V 2012 R2 host reports a successful VSS task at the same time the VM is reporting errors.  On the VMs, many VSS writers appear in a failed state after the backup.  I read about a similar issue that affected VMs that were server 2003 and 2008 but I haven't read anything about 2008 R2 or 2012R2 VMs.  We are getting an OpsMgr alert for failed backups every time this goes off.  I don't want to disable the alert in case we actually do have a real backup failure when our normal SQL backups kick off.

Networking with vm's

$
0
0
I am trying ti virtualize 2 servers. i have 1 physical server with server 2012r2 standard installed and running hyper-v. i have created 2 virtual servers, both with server 2012r2 standard, one is my domain controller and the second is a sql server, all are connected to the domain, when i go to a work station i can see both virtual servers. but when i go to either server i can only see the work station, no the other virtual server. any suggestions?

VM Network Speed

$
0
0

Hi all

We have Hyper v 2012 r2 Failover Cluster running . When we copy some Gbs file from lets say Host 1 to Virtual Machines resides on Host1 .

Copy starts and network speed down to 0 kbps . VMQ is disable on Physical Network of Hyper V switch.

Please advise.  Below is the output of Checksum Offloading.

Name                           IpIPv4Enabled   TcpIPv4Enabled  TcpIPv6Enabled  UdpIPv4Enabled  UdpIPv6Enabled
----                           -------------   --------------  --------------  --------------  --------------
NIC                           Disabled        RxTxEnabled     RxTxEnabled     RxTxEnabled     RxTxEnabled

Should we disable Checksum Offloading or it is okay ?

Regards


Networking Issue on Hyper-V VM

$
0
0

Hi all.

I am hoping that someone will be able to help me on this one as I am stumped.

We have a Hyper-V Cluster based on Windows Server 2012.  On this we are running, amongst other things, a Remote Desktop Services farm.  In order to increase the number of hosts in the RDS Farm, I have created a Hyper-V Template by Syspreping an existing server and then attached a copy of the VHD to a new server.

I have created one server, attached a copy of the VHD and started the server up and all is fine, to the point that 20 minutes later I had that server in production.

I have created a 2nd server and attached another copy of the VHD and started the server up and now I cannot get the network to connect, I keep getting Unidentified Network.  I have tried setting a static IP and can still not connect to the network.  I have tried removing the adaptor and re-adding it.  I have deleted the hidden network device.  I have moved the server to an other host and still nothing.  I have even recopied the VHD and tried rebuilding the server and nothing.

There is nothing wrong with the vSwitches as we have other servers on that host and they all work fine.

In general, the issue is: create new server and attach copied VHD that has been sysprep'ed, network adaptors cannot connect to network.

Hoping that someone can help me with this one.

Wayne.

Hyper-V error events: 153,137,140

$
0
0

Hi,

We have started to get a lot of these errors in last couple of days. Is there anyone who knows what this is and how to fix it? We have Exchange and SQL server on this hyper-V host.

Thank you in advanced.


Backing up VM from CSV, VSS writer problems ?

$
0
0

Hi, here is my problem.

I've set up 3 hyper-v hosts windows 2012 R2 in a Cluster.  My problem arise when i try to backup my VM's with Veeam, i can take a crash consistent backup but when i try to use the "Application Aware Processing" it fails.  

Here is the error reported by Veeam :
Unable to create snapshot (Microsoft CSV Shadow Copy Provider) (mode: Veeam application-aware processing). Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'. The writer experienced a transient error. If the backup process is retried, the error may not reoccur. --tr:Failed to verify writers state. --tr:Failed to perform pre-backup tasks.
Make sure VM does not have 'iSCSI Software Target Storage Provider' feature installed.
Retrying snapshot creation attempt (Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'. The writer experienced a transient error. If the backup process is retried, the error may not reoccur. --tr:Failed to verify writers state. --tr:Failed to perform pre-backup tasks.)
Unable to allocate processing resources. Error: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'. The writer experienced a transient error. If the backup process is retried, the error may not reoccur. --tr:Failed to verify writers state. --tr:Failed to perform pre-backup tasks.

 I've reboot my hosts multiple time and retry the backup job multiple times to.I can see, when i use "diskshadow", that the VM's are excluded from backup because the volume is not in the shadow copy set:

Excluding writer "Cluster Shared Volume VSS Writer", because all of its components have been excluded.
Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.
Excluding writer "BITS Writer", because all of its components have been excluded.
Component "\0AE47DB4-FD22-43AB-9789-AB2266B2A8D6" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\150DC140-5057-415E-948A-23B27DB3DC5D" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-SVEX2010-1\ which is not in the shadow copy set.
Component "\362811A4-FDCB-4687-9063-CE04B8FCDEAF" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\4C630BE2-26E2-4103-82A0-2F0EC41ABE62" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\74E78C64-FB7A-4410-AEEC-262D0104687F" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\7B47238C-A13C-4D22-AF9D-286B6A3F0FA1" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\917DA525-F1E2-4D37-BB26-BA4DC19FD1BC" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\9B6B706C-4603-4967-AE90-B58C1E54B7C2" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\9C63A59D-91B1-4AAE-870A-DBB24F9337F9" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-2\ which is not in the shadow copy set.
Component "\D1141663-8B00-4233-BBF1-1517C8E351A0" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\D3E97A71-17C8-4071-A1B6-316E6CA986AB" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\D8F51252-13AF-4ABF-8D7B-2798D4055F17" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\E25D318B-2D76-4771-9A9C-1DD37ED51A2D" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
because it requires volume C:\ClusterStorage\VM-HyperV2012R2-1\ which is not in the shadow copy set.
Component "\BCD\BCD" from writer "ASR Writer" is excluded from backup,
because it requires volume  which is not in the shadow copy set.
The writer "ASR Writer" is now entirely excluded from the backup because the top-level
non selectable component "\BCD\BCD" is excluded.

* Including writer "Task Scheduler Writer":
        + Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":
        + Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":
        + Adding component: \PerformanceCounters

* Including writer "System Writer":
        + Adding component: \System Files
        + Adding component: \Win32 Services Files

* Including writer "Microsoft Hyper-V VSS Writer":
        + Adding component: \Host Component

* Including writer "Registry Writer":
        + Adding component: \Registry

* Including writer "WMI Writer":
        + Adding component: \WMI

* Including writer "COM+ REGDB Writer":
        + Adding component: \COM+ REGDB

* Including writer "Cluster Database":
        + Adding component: \Cluster Database

I have no problem taking backups with Veeam from my Windows 2008 R2 Hyper-V Cluster

Can somebody help me figure out this issue ?

Thank you

ssd disks performance (passthrough) much slower in VM

$
0
0

I have installed 2 HP SSD disks in my MSA 2040 SAN .  I have 2 hosts in cluster.  When I measure disk performance on the host itself I have disk read benchmark of 2700MB... When I create a VM and connect this ssd disk to the VM (passthrough) I got a performance of 600MB...   I have no idea why...  Who can let his light shine on this mistery? host and VM are 2012 R2.

marc


No Hyper-V Checkpoints but data-autorecovery.avhd's

$
0
0

Hi everyone,

We are running Windows Server 2012 R2 Datacenter as a Hyper-V HOST

All of the Hyper-V Guests have NO checkpoints, however a few are showing Data-AutoRecovery.avhd, Data_3A48xxx. avhd etc

When we click "configure shadow copies" we see:

E:\ DISABLED Used 227Gb on Q:\

F:\ DISABLED Used 19.Gb on F:\

M:\ DISABLED Used 38Gb on M:\

P:\ DISABLED Used 193Gb on J:\

One of the VM Guests says "Failed to create VSS shadow copy for the VM on the Hyper-V host machine", vssadmin list writers reports, "status: failed, error:timeout"

How do we remove these .AVHD's when there are no snapshots as a shutdown doesn't MERGE the .avhd's I'm assuming they have something to do with our backup software (ARCSERVE r16.5 which uses VSSADMIN).

Thanks.

Viewing all 19461 articles
Browse latest View live




Latest Images