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

Snapshots in Hyper-V

0
0
I am new to snapshots in Hyper-V.  I have a server setup for a classroom training environment, which uses Sharepoint to set up individual SSP's for each training course.  I keep running out of "disk space" and suspect I have extra snapshots that need to be deleted.  I have read many forums, which all seem to agree that they need removed via the Hypervisor, as opposed to Windows Explorer.  What is the step by step procedure (Right click here, left click there, etc)? I have also read that a P2V works well using less time to complete (What is a P2V?) the merge.  Do I complete a merge first, then delete the old snapshots, or is that done automatically by doing something with the latest snapshot?  Is there a setting for automaticcaly creating these snapshots and if so, how would I turn it off?

Hyper-V 2012 Replication: planed failover "Failed to resolve the Replica Server"

0
0
I have 4 Server 2012 Hyper-V Servers HV1, HV2, HV3 and HV4
HV4 is used to recive replicatations from the other 3 servers. I can do a Planed Failover from any of the 3 to HV4 with no issue. If I attempt to do a Planed Failover back I always get the error "Failed to resolve the Replica Server".  I have also tested between the other servers and in some directions I also get the same error. Ultimatly this is what appears to be happening.
Replication is setup to go from hv1.domain.com to hv2.domain.com.  A Planed Failover works. But when I try to go back the other direction I get the abvoe error like this "Failed to resolve the Replica Server 'hv4.domomain' name." This is the last step in the Planed failover test where it is verifying that it can automaticly "reverse" replicatioin. You will notice in the name that the ".com" is missing, so yes it can not resolve the name. Why does the system seem to be dropping the .com in the computer name somtimes?
Yes I have theroughly checked DNS and it is in great shape. But even a perfiect DNS can not resovle a name that is getting truncated somhow by the process.

Hyper-V Exchange 2010 Guest CPU latency

0
0

New Hyper-V host that's been running smoothly since deployment 1st week of January. It has 3 guests. The ones running fine are a P2V W2K3 box and a backup DC. The Exchange guest is giving me problems.

The Exchange 2010 guest started running with very high CPU utilization (the host never reported over 11% but in the guest OS it was maxed out most of the time, usually from task manager) sometime this morning near as I can tell. It was unresponsive via OWA, MMCs would crash so I couldn't bring up an event viewer. I tried to remotely view event logs but I got a network timeout.

Rebooted but several exchange services timed out and won't start. Safe mode booted up fine but I can't find the cause for the latency. I ran procexplorer to make sure the signatures were legit and they seem fine.

I suspected transaction logs but the disk is far from full (only about 10 GB in use out of 360). I did notice that the Exchange backups had been failing (the destination network share went away) and transaction logs go back to 1/27. There's about 8000 of them.

I did start a backup pointed to a valid destination but due to the latency it's moving at a snail's pace, it later timed out waiting for a VSS backup. I'm not sold that it's the transaction files, but I am at a point where I'm not sure what to do with that.

Watching the guest's heartbeat it occasionally goes to "Lost Communication" for about 15 seconds or so then switches back to OK for 5-10 secs and then repeats.

Even in safe mode, the guest runs impossibly slow. 

The VM host is running very smoothly, no errors or latency. I'm completely befuddled.

Thanks in advance for any help you can offer me!

Windows 2012 HyperV and Novell / IPX

0
0

 I have a Windows 2012 HyperV server running  a virtual Windows 2003 server that has Novell /IPX running.

The machine starts and everything works fine except the Novell portion. Is there anyway to get this to work?

I have tried it on a Windows 2008R2 Hyper V and I don't have any problems running Novell.

Hyper-V Live Migration Performance - is this normal?

0
0

Hi,

I have a cluster of 4 hyper-v hosts. These have been up and running with an average of 8 VMs on each host for over a year now, however I decided to look at live migration performance for the first time today.

For the benchmark, I had two VMs running on the same host. I set VM1 (10.0.31.2) pinging VM2 (10.0.31.3). I then live migrated VM2 to a different Hyper-V host. VM2 has two vCPU cores and 12GB of RAM (with around 9GB in use). The network setup is simple (VMs connected to a NIC dedicated to VM traffic only, no VLAN tagging) and both hosts are connected to the same physical switch. The VMs are using the iSCSI initiator for data drives (however this should have no impact on the live migration as this is all in-guest).

The live migration itself (initiated through SCVMM) took 6 1/2 minutes. This seemed a little long, but the worrying thing was the ping reponce times I was getting during the live migration (see end of the post). Both before and after the live migration, ping responce times were showing as <= 1ms or =1ms. (More worrying as these responce times could possibly corrupt an iSCSI volume).

I ca not believe this performance is normal, and I would not concider it acceptable for a production environment, so my question is: what could be wrong and how can I improve the performance duing live migration.

Thanks,

Chris

Reply from 10.0.31.3: bytes=32 time=2ms TTL=128
Reply from 10.0.31.3: bytes=32 time=2ms TTL=128
Reply from 10.0.31.3: bytes=32 time=2ms TTL=128
Reply from 10.0.31.3: bytes=32 time=527ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=221ms TTL=128
Reply from 10.0.31.3: bytes=32 time=592ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=284ms TTL=128
Reply from 10.0.31.3: bytes=32 time=668ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=405ms TTL=128
Reply from 10.0.31.3: bytes=32 time=3ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=81ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=30ms TTL=128
Reply from 10.0.31.3: bytes=32 time=309ms TTL=128
Reply from 10.0.31.3: bytes=32 time=729ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=37ms TTL=128
Reply from 10.0.31.3: bytes=32 time=458ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=183ms TTL=128
Reply from 10.0.31.3: bytes=32 time=643ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=17ms TTL=128
Reply from 10.0.31.3: bytes=32 time=403ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=52ms TTL=128
Reply from 10.0.31.3: bytes=32 time=451ms TTL=128
Reply from 10.0.31.3: bytes=32 time=669ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=28ms TTL=128
Reply from 10.0.31.3: bytes=32 time=736ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=39ms TTL=128
Reply from 10.0.31.3: bytes=32 time=416ms TTL=128
Reply from 10.0.31.3: bytes=32 time=2ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=43ms TTL=128
Reply from 10.0.31.3: bytes=32 time=464ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=162ms TTL=128
Reply from 10.0.31.3: bytes=32 time=2ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=199ms TTL=128
Reply from 10.0.31.3: bytes=32 time=510ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=274ms TTL=128
Reply from 10.0.31.3: bytes=32 time=592ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=6ms TTL=128
Reply from 10.0.31.3: bytes=32 time=315ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=81ms TTL=128
Reply from 10.0.31.3: bytes=32 time=422ms TTL=128
Reply from 10.0.31.3: bytes=32 time=853ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=166ms TTL=128
Reply from 10.0.31.3: bytes=32 time=538ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=215ms TTL=128
Reply from 10.0.31.3: bytes=32 time=623ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=288ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=10ms TTL=128
Reply from 10.0.31.3: bytes=32 time=439ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=141ms TTL=128
Reply from 10.0.31.3: bytes=32 time=555ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=356ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=57ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=110ms TTL=128
Reply from 10.0.31.3: bytes=32 time=439ms TTL=128
Reply from 10.0.31.3: bytes=32 time=731ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=59ms TTL=128
Reply from 10.0.31.3: bytes=32 time=400ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=157ms TTL=128
Reply from 10.0.31.3: bytes=32 time=494ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=176ms TTL=128
Reply from 10.0.31.3: bytes=32 time=466ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=175ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=294ms TTL=128
Reply from 10.0.31.3: bytes=32 time=557ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=298ms TTL=128
Reply from 10.0.31.3: bytes=32 time=676ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=96ms TTL=128
Reply from 10.0.31.3: bytes=32 time=346ms TTL=128
Reply from 10.0.31.3: bytes=32 time=743ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=125ms TTL=128
Reply from 10.0.31.3: bytes=32 time=485ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=230ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=41ms TTL=128
Reply from 10.0.31.3: bytes=32 time=370ms TTL=128
Reply from 10.0.31.3: bytes=32 time=732ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=141ms TTL=128
Reply from 10.0.31.3: bytes=32 time=492ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=89ms TTL=128
Reply from 10.0.31.3: bytes=32 time=485ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=168ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=240ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=24ms TTL=128
Reply from 10.0.31.3: bytes=32 time=412ms TTL=128
Reply from 10.0.31.3: bytes=32 time=778ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=212ms TTL=128
Reply from 10.0.31.3: bytes=32 time=539ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=105ms TTL=128
Reply from 10.0.31.3: bytes=32 time=420ms TTL=128
Reply from 10.0.31.3: bytes=32 time=637ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=336ms TTL=128
Reply from 10.0.31.3: bytes=32 time=717ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=19ms TTL=128
Reply from 10.0.31.3: bytes=32 time=468ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=224ms TTL=128
Reply from 10.0.31.3: bytes=32 time=572ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=161ms TTL=128
Reply from 10.0.31.3: bytes=32 time=510ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=170ms TTL=128
Reply from 10.0.31.3: bytes=32 time=486ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=180ms TTL=128
Reply from 10.0.31.3: bytes=32 time=480ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=137ms TTL=128
Reply from 10.0.31.3: bytes=32 time=512ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=29ms TTL=128
Reply from 10.0.31.3: bytes=32 time=275ms TTL=128
Reply from 10.0.31.3: bytes=32 time=560ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=224ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=26ms TTL=128
Reply from 10.0.31.3: bytes=32 time=335ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=259ms TTL=128
Reply from 10.0.31.3: bytes=32 time=561ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=110ms TTL=128
Reply from 10.0.31.3: bytes=32 time=422ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=252ms TTL=128
Reply from 10.0.31.3: bytes=32 time=534ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=22ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=32ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=199ms TTL=128
Reply from 10.0.31.3: bytes=32 time=531ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=273ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=205ms TTL=128
Reply from 10.0.31.3: bytes=32 time=471ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=122ms TTL=128
Reply from 10.0.31.3: bytes=32 time=473ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=166ms TTL=128
Reply from 10.0.31.3: bytes=32 time=492ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=202ms TTL=128
Reply from 10.0.31.3: bytes=32 time=527ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=119ms TTL=128
Reply from 10.0.31.3: bytes=32 time=456ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=193ms TTL=128
Reply from 10.0.31.3: bytes=32 time=626ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=175ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=59ms TTL=128
Reply from 10.0.31.3: bytes=32 time=319ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=219ms TTL=128
Reply from 10.0.31.3: bytes=32 time=475ms TTL=128
Reply from 10.0.31.3: bytes=32 time=153ms TTL=128
Reply from 10.0.31.3: bytes=32 time=17ms TTL=128
Reply from 10.0.31.3: bytes=32 time=16ms TTL=128
Reply from 10.0.31.3: bytes=32 time=54ms TTL=128
Reply from 10.0.31.3: bytes=32 time=107ms TTL=128
Reply from 10.0.31.3: bytes=32 time=4ms TTL=128
Reply from 10.0.31.3: bytes=32 time=93ms TTL=128
Reply from 10.0.31.3: bytes=32 time=130ms TTL=128
Reply from 10.0.31.3: bytes=32 time=102ms TTL=128
Reply from 10.0.31.3: bytes=32 time=9ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=25ms TTL=128
Reply from 10.0.31.3: bytes=32 time=98ms TTL=128
Reply from 10.0.31.3: bytes=32 time=142ms TTL=128
Reply from 10.0.31.3: bytes=32 time=22ms TTL=128
Reply from 10.0.31.3: bytes=32 time=139ms TTL=128
Reply from 10.0.31.3: bytes=32 time=2ms TTL=128
Reply from 10.0.31.3: bytes=32 time=23ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=51ms TTL=128
Reply from 10.0.31.3: bytes=32 time=39ms TTL=128
Reply from 10.0.31.3: bytes=32 time=215ms TTL=128
Reply from 10.0.31.3: bytes=32 time=55ms TTL=128
Reply from 10.0.31.3: bytes=32 time=55ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=290ms TTL=128
Reply from 10.0.31.3: bytes=32 time=21ms TTL=128
Reply from 10.0.31.3: bytes=32 time=56ms TTL=128
Reply from 10.0.31.3: bytes=32 time=16ms TTL=128
Reply from 10.0.31.3: bytes=32 time=49ms TTL=128
Reply from 10.0.31.3: bytes=32 time=20ms TTL=128
Reply from 10.0.31.3: bytes=32 time=23ms TTL=128
Reply from 10.0.31.3: bytes=32 time=17ms TTL=128
Reply from 10.0.31.3: bytes=32 time=9ms TTL=128
Reply from 10.0.31.3: bytes=32 time=8ms TTL=128
Reply from 10.0.31.3: bytes=32 time=35ms TTL=128
Reply from 10.0.31.3: bytes=32 time=19ms TTL=128
Reply from 10.0.31.3: bytes=32 time=684ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1479ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1143ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1724ms TTL=128
Reply from 10.0.31.3: bytes=32 time=799ms TTL=128
Reply from 10.0.31.3: bytes=32 time=223ms TTL=128
Reply from 10.0.31.3: bytes=32 time=21ms TTL=128
Reply from 10.0.31.3: bytes=32 time=304ms TTL=128
Reply from 10.0.31.3: bytes=32 time=61ms TTL=128
Reply from 10.0.31.3: bytes=32 time=44ms TTL=128
Reply from 10.0.31.3: bytes=32 time=51ms TTL=128
Reply from 10.0.31.3: bytes=32 time=154ms TTL=128
Reply from 10.0.31.3: bytes=32 time=23ms TTL=128
Reply from 10.0.31.3: bytes=32 time=46ms TTL=128
Request timed out.
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128
Reply from 10.0.31.3: bytes=32 time=1ms TTL=128
Reply from 10.0.31.3: bytes=32 time<1ms TTL=128

Slow network performance (Only once Hyper-V role is installed)

0
0

I've recently isolated the cause of some network performance issues I've had for some time.  It seems that network performance decreases drastically when the Hyper-V role is installed on a pair of Server 2008 R2 boxes.  This first became apparent to me when I recently installed Intel X520 10G adapters and didn't see performance increase much.  After the upgrade I did see occasional peaks of ~1.5 Gbps which made me think everything was working, but I was never able to realize much of a performance increase when doing file transfers.

Since then I have pulled the adapters and started testing them on my bench using different hardware.  What I have found is the following:
Intel NetEffect CX4 10 Gbps Adapters (SMB Push):  4.4 Gbps (Avg, No HV) down to 1.05 Gbps (Avg, HV)
Intel X520 10 Gbps Adapters (SMB Push):  5.5 Gbps (Avg, No HV) down to 1.05 Gbps (Avg, HV) (Avg, HV)
Broadcom 8100 Series 1 Gbps Adapters (SMB Push):  0.99 Gbps (Avg, No HV) stays the same at 0.99 Gbps (Avg, HV)

Something I have noticed is that CPU utilization stays about the same while throughput is much reduced with the hypervisor installed.  I have to wonder if there is really just this much overhead when the hypervisor is active.  Note that this problem occurs even when the NICs aren't part of a virtual switch--it's just the hypervisor itself being installed and active that is enough to cause the problem.  No combination of advanced adapter configuration settings seem to make an appreciable difference, but if someone has a magic cocktail of parameters I'd still like to hear them.

The real kicker is that once Hyper-V has been installed, even uninstalling it doesn't return performance to pre-HV role installation levels.  They stay stuck at ~1.05 Gbps.

My question I suppose is this:  Is this behavior typical?  If not, what might be done to improve the situation?

Hyper-v and very slow network

0
0

Dear all,

I have a big problem with my hyper-v server and network card. I've found a lot of topic around this question but none of them helped me.

I have a Win 2008 R2 Server with only Hyper-V installed. I have 3 NIC , one is reserved to the host management and the others two are reserved for virtual machine .

All NIC are Intel, one is integrated on the Intel motherboard and the others are Intel Gigabit ET Dual port .

Before installing the role of Hyper-V all NIC worked perfectly with speed around 1Gb (file transfer average 90 MB/Sec, of course I have a Gigabit LAN) .

After Hyper-V install, the host system  is going very slow and the network file transfer using the dedicated NIC is about ten time slower (9-10MB /sec) . Same problem with all VM off and also if I remove all VM !

I tried all of suggestion found in old post (disabling TCP checksum / offload ...) but nothing happens.

What is really strange is that by removing all network card all the Host operating system seems to improve the speed... but, of course, I can't use  my LAN :(

I need help because every night I must make a full backup of Virtual hard disk from the host to a backup server in my lan.

My configuration:

- Server Win 2008 R2 SP1 with Hyper-V and no others role

- 2 Virtual Machine (one Win 2008 R2 and one Win 7 Ultimate)

- NAS Linux (access via SMB with no problem)

- Various Windows 7 Pro client

 

Thanks in advance to everybody,

Luca M.

How to add a user to manage only specific virtual machines?

0
0

Hello everybody,

I want to grant a user access to a Hyper-V host to use some hosted virtual machines without adding him to the Administrators group.

Is it possible grant access only to specific virtual machines?

Both the user and the Hyper-V host are in the same domain.

Regards,

Simon



Hyper-V 2012 with guest OS running IPX

0
0
Hello all. I have a client running an old legacy app on Netware 3.12. It can only communicate over IPX. We installed a new server running Server 2012 Standard with Hyper-V 2012. I converted a terminal sever to a VM using Disk2VHD. When I boot it up, it cannot see the Netware server. All IP communication works fine. I can see the Windows network and access the intenet. If I take that VM and load it up on Windows 2008R2 with Hyper-V, I can see the Netware server and login. What I need to know here is if Hyper-V 2012 supports a guest OS using IPX to communicate or did they leave out IPX support in the new hypervisor.

Guide to remote manage Hyper-V servers and VM's in workgroups or standalone

0
0

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012

The following guide will enable you to:

1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager

! This should also work for Core installations of server 2012, but I haven't tried.

This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.


* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.

- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.


> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)

1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.

! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012

2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.

> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
----------------------------------------------------------------------


> Next, is to get the MMC firewall snap-in working.
   The reason for this, is to have a GUI available to configure it.
   If you're happy without it, you may skip this and use a shell instead to do so.

? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)

! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level 
# (In other words: allows the firewall to be remotely managed)

! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.

? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.

! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done

! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon, 
# and choose run as admin on the bar below.

! Client: application MMC: select "file" --> Add/remove snap-in 
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)

* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.

-------------------------------------------------------------------------------

! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.


! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.

! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate

# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
#
# I recommend to choose yes; unless you like to pull some more hairs...

! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
!  select yes

! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server

Done.

You can now manage your remote server through the familiar computer management GUI.

! Right-click your remote server, and select "Computer Management"

--------------------------------------------------------------------------

A few side notes:

? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.


If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.

Cheers!

  

Virtual Test Lab ( Base-Configuration) Building

0
0

Hi guys,

Im trying to build a virtual test labs on Hyper-v. I've managed to finish building almost the devices from the base-configuration. But there's something wrong. Can some one give me a hints pls .

As anyone should've known about the base-configuration, there're 5 PCs for the test labs. Im having some pinging problems from that basic topology. Somehow, i can't ping from EDGE1 (10.0.0.2 ) to DC1's Corpnet2 Interface( 10.0.2.1 ) even i added a static route from EDGE1 to that interface ( Here's the command : route add 10.0.2.0 255.255.255.0 10.0.0.1 ).

Anyone has an idea why this happens ?

Thanks in advance.

 

unable to create hyperv replica

0
0

Hi all,

Windows 2012 datacenter servers

I tried to enable VM1 replication on host 1 to host2.  But I am unable to.  I enabled replication on the replica server host2 and it did not work and then I enabled replication on both hosts.

here are errors about time out and no firewall between two sites and windows firewall allows all connections (for test) and ping time is 2 ms with 100 Mbps connection.


Event ID: 29230
Hyper-V cannot connect to the specified Replica server 'host2'. Error: The operation timed out (0x00002EE2). Verify that the specified server is enabled as a Replica server, allows inbound connection on port '80', and supports the same authentication scheme.

Event ID: 32000

Hyper-V failed to enable replication for virtual machine 'VM1': The operation timed out (0x00002EE2). (Virtual Machine ID 1208DF9C-767F-4688-9AA2-B231A52DE339)

Any idea to solve this issue?

Thank you very much!

Domain controller running on Hyper-V 2012 Server no physical DC

0
0

I am Installing a new Hyper-V 2012 server into a data center site, this will host a domain controller and some kind of backup server to store snapshots of VM's. This will be a standalone server or to be clearer this wont be in a cluster, it will however be able to contact other domain controllers in others sites over fast branch office VPN's and a 1GBIt site to site link. no other physical domain controllers will be on site.

I have another hyper-V server in a different data center running 2008 R2, I specifically remember when setting this up that I should not join the hyper-V host to the domain due to installing a domain controller as a virtual guest, as in an emergency situation and my DC's all were off and uncontactable to each other, I wouldn't be able to log into the 2008 hyper-V host if the domain controller hosted within it did not come online. (unless I am mistaken and this only effected clusters)

So my question is, is this still the same in server 2012 (standard)?

I have read that there is a new feature for windows 2012 hyper-V clusters that protects you from this, but I assume this is just for clusters and not for standalone systems. To add a bit of extra detail the domain is 2008R2 function level.

Thanks

 

DHCP reservations

0
0

So I had this same virtual switch connectivity issue with my 2008 r2 VM. Turns out I was experimenting with a 2012 VM and created a DHCP reservation on my router for this VM. What that did was capture the MAC address of Hyper V virtual switch. So when I deleted my 2012 VM (cause I was frustrated with it) it worked fine connecting to the internet. I then installed 2008 R2 and was not able to connect to the internet. What happend was the router captured the MAC address for my 2012 VM and related switch. Deleting this reservation from my router fixed all of my HyperV virtual switch connection problems.

OS for hyper-V 2012

0
0

Now, we get 4 Windows 2012 datacenter licenses for 4 hyper-v hosts.
Can you recommend which OS I should set up for these 4 hosts?  We need
fail over, live migration etc...

there are 3 types of hyper-v: Free hyper-v server 2012,
windows 2012 core with hyper-v and windows 2012 datacenter with
hyper-v...

Thank you.


P2V Migration of a Windows 2008 R2 Server

0
0

Hi,

I hope I am asking this question on the right forum...

I want to P2V a Windows 2008 R2 OEM server to Hyper-V but I am concerned about the fact that it has a OEM license installed (serial number would most likely fail, right?).

I have purchased Open Licenses of Windows Server and I was wondering if I just can go ahead and change the serial number of my server to an Open License before starting the P2V procedure. Will the change of serial number work since this server was installed using an OEM disk?

One thing is sure, if I had to do it again, I would never buy OEM licenses anymore.

Thanks in advance.


Benjilafouine

Slow transfer speeds from host to hyper-v vm

0
0

This is a duplicate post from the Windows Server 2012 forum. I have windows server 2012 setup on physical machine with dual intel 82574l NICs. On this server I am hosting two hyper-v vms. The issue here is that when I transfer files from either host to vm or vm to host I get at best 6MB/s on average I get around 3MB/s. The cards are set for 100 MB Full Duplex and it seems they should be transferring much faster than this. I have read some other posts but could not find anything that helped. Perhaps it is the virtual switch configuration, the host config... I am just not sure. What I do know is that when I try to backup 150 Gb at 5MB/s it takes a very long time. I need this faster. Any information you need to assist in solving this problem please let me know, I am stumped.

Setup:

6 HDD's in Raid 6, 15K

Virtualization is enabled in BIOS, both bits

No AntiVirus

VM switch is setup External, not sharing with host, Allocated 12Gb RAM with Dynamic Memory enables

Using 4 of 8 processors and have bumped all cpu/mem settings to have this VM take precedence. Does not matter if both vm's are running. Still slow.

I have disabled the TCP Offloading on VM, no difference, reenabled

Would setting us the VM with an iSCSI controller make difference, right now it is just set up on hyper-v as IDE controller due to server 2012 os on there, should I modify this to have server 2012 on boot and setup another .vhdx as iSCSI to store data? This vm is a file server.

hyper-v network virtualization gateway

0
0

Hi


I am planning a small testlab for Hyper-V network virtualization and SCVMM 2012 SP1. Now I am confused about the virtualization gateway. My understanding is that when the VMs needs external connection (Internet, other physical host etc.) then I need a virtualization gateway. Right?


So, is it possible to configure a Hyper-V Host itself or a VM as a virtualization gateway for a testlab?


Moreover, when you configure a virtualization Gateway with Windows Server 2012 can you manage it through SCVMM 2012 SP1or do you need maintain it manually?

 

Thx
J0fe

How to create a Windows 2008 R2 VM Template on Window 2008 R2 Hyper-V host server?

0
0
Is there a way to create a a windows 2008 R2 VM template running on a Windows R2 Hype-V host, with the ability to resize both RAM and disk space after a VM is creatingthe said template?

TD

windows 2012 fileserver and dedup within VM

0
0

Hi,

I understand that dedup is not possible on a csv. 

What if I install a VM with Windows 2012, attach a 2nd HDD as vhdx (residing on the csv). 
Can I then use dedup within the Guest VM that serves as file server?

Basically what I want to do: 
- Having a Hyper-V Cluster for HA

- Having a fileserver, that can also failover. 

- Using Dedup. 

I just see following possibilities: 
- having the VHDX on a CSV, so it can be failed over, but not sure about Dedup inside a VM. 

- using a different LUN without CSV, and somehow have it fail over if the VM is moved to another node. (Virtual Fibre Channel doesn't work as our adapter doesn't support it), so didn't find a solution on that yet.

But would be interested if anything is against using it inside VM? 

Thanks
Patrick

Viewing all 19461 articles
Browse latest View live




Latest Images