Hi,

I have a Windows Server 2008 R2 failover Cluster and I installed a new VM running Windows Server 2012. When I configured the backup to this VM using DPM 2012, the backup is offline (Saved State). 

I've checked with diskshadow and the Hyper-V vss writer, always gives me the same thing, backup to this VM will be using saved state.

Why can't I run an online backup, using snapshot? Is'it a problem with Hyper-V R2 and Windows 2012 Child VM?

Note: I already checked all the conditions why the backup of a VM could be running on saved state and none of them are applicable to my scenario.

Regards,

Carlos.

Hi,

I am not sure this is even possible, but I would like to be on the domain and use the internet from a windows 8 laptop using the wifi card.

But also to be able to use the Ethernet card for hyper-V traffic only (and for it to be able to also talk to the laptop).

Is that possible and if so how would I do it?

I have already joined to the domain using the wifi card.

Once plugging an Ethernet cable in as well - wireless disconnects shortly after login (yes I did tick the connect automatically box) - if I manually connect again it says it is connected with both interfaces (wireless and Ethernet)

--------

In dns on the server (2012) - it has 2 entries for the laptop with 2 different ip addresses (I hope that's ok?) also pinging from another computer or the server says the laptops wifi IP which is a good sign.

--------

So to recap:

1) How can I make sure only hyper-v traffic goes over the Ethernet card and not the wifi and vice versa.

2) Any way I can make windows 8 stay connected to wireless even with an Ethernet cable in - it connects automatically but disconnects shortly after login even with the 'connect automatically' box ticked.

3) Can any of this even be done (safely) for hyper-v client for windows 8?

Thank you in advance - I know its a bit of a mad question :)

Timez82

Hi,

I (as a proffesor) use Virtual PC in classroom simulating Windows XP connecting to domain on Windows Server 2003. I have created organizational unit in active directory and applied group policy with for exampe two restrictions: Control Panel disabled and not allowing Windows Movie Maker to run (in computer section). On older machines (P4~) group policy mainly have not been appied! Last school year (2011/12) I have woked in newer classroom- dual core processors... and everything has worked perfectly- "old" problem occured again when I have tried same thing with Windows Server 2008. Than I have "concluded" that "problem" is due to weak processor performance. This year "problem" occured in the "new" classroom with dual core processors- on almost all (except 2) computers! Can someone help me with this issue?. /in some similar problems as a solution was suggested changing network settings which I have tried but with no result.../

Thank You in advance, sincerely Drago Percic

I run Windows Server 2012 RTM Hyper-V and I can occasionally not access the second virtual hard drive (dynamically expanding VHDX) attached to the VM through the virtual SCSI controller. I can however access the first hard drive that is connected with the virtual IDE controller.

I get the following warning in the event log under “Administrative Events” every 30 seconds when this happens:

• Log Name: System
• Source: Storvsc
• ID: Storvsc
• Message: “Reset to device, \Device\RaidPort0, was issued.”

I get this error once or twice a week and it has caused serious problems since one of the virtual servers that have this problem is a fileserver and the second hard drive contains all the data.

The only quick solution to the problem that I have found is to force the virtual machine to stop using the “Turn Off” feature since a normal shut down does not work (stops at shutting down the event log or similar) and then start the virtual machine again.

You can also wait for about 30 minutes or longer until the disk for some reason becomes accessible again by itself.

My research into this problem shows that:

• Only 2 of the 10 VMs running Windows Server 2012 RTM that I have, have this problem.
• Both these VMs have a second virtual hard drive (dynamically expanding VHDX) that cannot be accessed for 30 minutes or longer.
• Check Disk of the virtual hard drive shows no errors.
• The second hard drive is attached to the virtual SCSI controller.
• I can find no problems at all with the physical storage on the (not related) 4 hosts that I have. The problem exists only in the VMs.

I have now attached the second virtual hard drive to the virtual IDE controller to see if this permanently fixes this problem (i.e. does not happen for at least a week).

Is there something wrong with the virtual SCSI controller or the virtual SCSI device driver that comes with Windows Server 2012 RTM? Does anyone else have this problem?

Hi,

We have just rolled to server 2012 for our HyperV hosts. I have configured three NIC Teams as follows:

Now my question is :

Should the Multiplexer adapters have an IP address ? they do receive address via DHCP. Is that normal?

There are now 3 Different NIC Adapters, 1- Physical Nic Adapter, 2- Microsoft Network Adapter Multiplexer Driver, 3- vEthernet (Microsoft Network Adapter Multiplexor Driver Virtual Switch) --> what are these network cards do in relation to HyperV.

Pardon my lack of knowledge in this respect.

Thanks

Hi,

I need help with a production rollout for Hyper-V. I work for a small school which has neglected any server updates for close to 10yrs. We have a storage server that if I need to restart it during the day, it could take close to 3hrs to restart and become operational, I can't defrag it because partitions are too small and don't have enough space, and I have data corruption so I can't re-size them, plus parts are getting difficult to get, so needless to say it's time to replace the box. I really would like to move everything to Hyper-V and make all my servers virtual machines. I recently got my hand on 6 used HP DL380 G5 servers, making the total to 8 of these boxes. I plan on upgrading the servers I need to: dual processor, 8 core servers with 16gb of ram. Here is where I need help.

Here's my planned scenario:

Setup two clusters, 1st in the main office and the 2nd a failover in the high school. Both clusters will have 2 servers for Hyper-V host, the 1st cluster will have 5 vms between both hosts. I plan on having 2-73gb hard drives in mirror for Hyper-V server 2012, and 6 -146GB hard drives in Raid 5 or 6 (haven't decided that yet). The VMs will be hosted on the servers hard drives.  For the file storage server I plan on either getting a used DL320s and setting it up as a ISCSI target, or using a MSA60 and attaching it to both Hyper-V hosts for HA.

My questions are:

1) Which would be a better option: MSA60 on both clusters and somehow replicate both clusters, or using a DL320S. Both of the will kind of have the same functionality, just don't know if a DAS can be used like that in Hyper-V.

2) If the 1st cluster (main office) loses power, can hyper-v auto-failover to cluster 2, if so what would be the expected downtime.

3) Switch, am I looking for anything particular. Right now we have a hp 4104gl, and all the servers are hooked up to 10/100 (which annoys the hell out of me), I plan on getting and 5308xl or 4108Gl and running all vms on gigabit ports. Will the two switches I mentioned work.

Sorry for the long winded post, but the lack of priority on upgrading tech is frustrating. I could not do anything on their network because of political reasons. Now I can, so I really want to fix this and get their network to proper standards. They have no plan of action if any of their servers fail and no way to resolve single point of failure. If I contact a reseller to help and they give me a high quote, I know the school will say no and ignore these problems, so any help would be appreciated.

Thanks in advance

I've got a 2 node Server 2012 Hyper-V cluster, and each node has 6 gigabit NIC ports. 2 are dedicated to iSCSI traffic, but the other 4 are in a Team. When I Live Migrate 20+ VMs, it seems to me that I should be able to achieve at least 2-3Gbps (adjusting for network overhead and such) transfers. I realize there are a great number of ways to configure a team in Server 2012, and I've experimented with all of them: Static Teaming, Switch Independent, LACP, and each of these can either be Address Hash or Hyper-V port. I've occasionally seen brief spikes up to 1.5Gbps, but that's it. The rest of the time it's at a very steady 1Gbps.

I've got these servers connected to 2 ProCurve 2910al switches with a 10gb backplane, and the switches are not being taxed with any other workloads. When I use the LACP teaming, I have tried both LACP-enabled trunks and enabling Active LACP on the relevant ports. 

My biggest question is: is this even feasible? Has anyone achieved 2Gbps+ Live Migration speeds without using 10gb NIC cards?

Anyone? Bueller?

Hello,

I am in the process of preparing our migration to Hyper-V 2012. At the moment I am a little bit stuck on my desision with network layout to chosse.

Our future datacenter enviroment will have 2 Hyper-v clusters (1 five node for production and management systems and a 1 two node cluster for DMZ) and it will host about 150 VMs.

There will be no dynamic in the physical infrastructure. The systems are planned to have the capacity needed over the next 3 to 4 years.

Converged Fabric

I have done some experiments with the converged fabric aproach (without havig VMM managing the fabric) and ran into several small issues.

I have had dublicate MAC addresses because some hosts had the same local MAC pool. And the vNICs for the Hosts got served by the local MAC pool.

The VMM dhcp switch extension has to be installed and activated before joining them to the cluster and managing them with VMM.

All this could be avoided by using VMM to manage the fabric or by manually managing local MAC etc.

Having VMM manage the fabric would require VMM to run outside the cluster on a seperate server and some effort in the initial setup of VMM.

Tradional Setup

This is straight forward, having 3 teams (Host Management, CSV and Live Migration) for the host and one team for VM traffic. Without all the initial overhead to setup fabric management by VMM or doing everything by hand.

VMM could run inside the cluster and manage only the virtual enviroment, like we have VMM 2008R2 doing it now.

Since we are a small IT department with 4 admins and one CIO and have 500 workstations, 200 physical and virtual servers and 600 users to manage I am a little bit afraid that the "converged fabric" aproach would add an additional layer of complexity in the setup and afterwards in the diagnosis of problems that may occur without giving us a real benefit.

I would appreciate any input on this topic.

This posting is provided "AS IS" with no warranties.

I'm using Hyper-V 2012.

I'm creating my first virtual machine and I the only option I have for "Configure Networking" is to start the VM "Not Connected". The drop down menu does not have any other option to select a network adapter with the VM creation.

Do you have to create a "virtual switch" before creating your VMs? If I want to VM to have regular WAN/LAN connectivity, is there any thing special I'd need to know/configure?

Ed

We have a new Win2008 R2 Failover cluster with 3 nodes and a set of 30+ VM's exported from a series of stand alone Hyper-V hosts. Each VM has between 6 and 30 snapshots. All hosts and VM's have the same virtual network name. When imported on a cluster node all network settings are ok and all snapshots work.

If we move or migrate a VM to another node than where it was imported, all snapshots on the VM show a configuration error on their network adapter. The guest OS has no network anymore and the snapshot config does not allow for it to be changed.

What is the point of migrating anything if it break everything that isn't running on its original host? How can I fix this?

Hi Guys,

I got the following error on an HP ML180 g6 server which hosts a single 2003 guest:

Port 'SWITCHPORT-SM-9A3E1BCC-1D22-42EA-BA42-3DCC42C9EC53-0-1' was prevented from using MAC address '00-15-5D-64-08-01' because it is pinned to port '39CFB32B-2760-461D-B'.

No changes were made to either of the servers or to their near environment - after almost a year and a half of flawless operation, this issue came completely out of the blue.

I tried recreating the virtual network, updating network drivers and even removing and adding the Hyper-V role again, but the issue wasn't resolved.

I then moved the 2003 guest to another HP ML350 g5 server, and I get the same error.

HP servers' NICs are NOT teamed, and I disabled all TCP/UDP offloading.

What might it be?...

EDIT: both hosts are 2008 R2

Hi there.  I need to move a bunch of VMs from one SAN to another, but to keep them on the same host.

I'm running Hyper-V on windows 2008 R2.  I reckon the best way to go about this is the old export/import method, but I'd got a few questions.

1. If I export, then import again, how do I change the location of the VM?  when I export and import again, the VM appears to have moved to the C drive of the host, even after I've move the exported files to the new SAN before importing!  Any ideas?

2. I then copied the files over to the new SAN and manually changed the file path of the VM and the VHDs in the properties of the VM, but I cannot delete the old VM as it's in use still. 

Any help would be appreciated.  thanks,

Jonny

Hello,

I have a Virtual Machine configured with Windows 7-64bit running on an ESXI 5.1 Host. I would like to migrate this VM to another host running Windows Server 2008 R2 configured with Hyper-V.

I've tried looking at other blogs, etc but they are all using different versions than I am.

Does anyone have any step-by-step guides on how this can be done? Please note that I am not yet running server 2012 so I don't think I will be able to use the "Free Tool" that's mentioned in other blogs.

Any help would be appreciated.

Thank You.

Hi,

we are a small company and have a Hyper-V failover cluster environment, used for virtual servers. We will be getting new servers in a month or so, so I wanted to create the environment the best I can this time. It works now, as we have it (server 2008 R2 x64) but we do have some problems, so here's the quick details list...

We will have 3 new servers, identical to oneanother, together with SUN storage and plenty of network cards in servers. We also have 2 switches we use specifically for this, and one main domain router. What I intended to do was:

- each server gets WnServer 2012 x64 with hyper-v and failover clustering

- they all get connected to SUN storage via iSCSI, with two network cards from each server going to storage (redundant network). Each network card would be connected to different switch, so card#1 goes to storage via switch#1, and card#2 goes to storage via switch#2. Each has different IP/subnet. Storage also has 2 network ports, 2 controllers, so everything should be redundant. Those cards won't be used for anything else, just for iSCSI.

- each server has it's card#3 connected to our domain, and is used with fixed IP. To be used for server-domain communications.

- each server has it's card#4 also connected to our domain, but with different IP from card#3, and is used for virtual machines only (as MS calls it "virtual network switch - external). All the VM's would use this adapter to connect to domain.

Is this setup OK? Or is there another, better way to do it? Now, with 2008R2, we have a "bug" we didn't manage to resolve yet, but since we're reinstalling everything with new servers, we let it stand as it is. The "bug" is that once a week, more or less, for a reason unknown, the communication with the domain gets interrupted. What happens then is that physical servers also lose their internal communication, even though they are not directly connected to main router, but are connected to a switch, which is then connected to the router. I believe the should remain able to communicate between themselves even if the main router is completely disconnected, since they're on the same switch, but that is obviously not the case since, as I said, when router drops communication, the nodes can't talk with oneanother, and the whole cluster shuts down. It lasts for just a short time, but all the VM's get shut down, cluster shuts down, then communication (router) restores and everything goes back up again. Also, even though we can live-migrate VM's between servers, if we try to change CSV's owner, the CSV gets lost for a second, causing all VM's on it to get blue screen. 

As I said, we stopped looking for solution to those two "bugs" and decided that maybe the fresh installation, due in a month or two, maybe would resolve the situation.

So, any advice I can gather in advance to install the failover cluster in the best possible way would be appreciated!

Hi,

I am having a problem with HyperV and ISCSI disk pass though. I have configured my LUNs to point at the VM host, however I can't seem to mount >12 MS ISCSI virtual disks on the VM server. They aren't appearing in disk manager. HyperV is also hung on trying to select a disk to pass through. Is this a known bug? Running Server 2008R2 SP1 with latest updates.