I was really exited when i first started ready about all the new features that Microsoft promised in Hyper-V 2012.
But after I experimented with it, I'm rather disappointed at the gap between the marketing hype and the actual capabilities.

So I can now Build a "Cluster in a box".

But in order to move beyond this, there are 2 problems which I can not find an obvious/cost effective solution to:

1. How to make the storage resilient
2. How to scale this beyond 2 hosts.

For Question 1 the only answers I know of is:

• Buy an expensive SAN
• Buy starwind's iSCSI SAN software
  
  After reading over and over again that 2012 removes the need for a SAN, this is very disappointing.
  Please share if there are other solutions out there I am not aware of.

For Question 2:
For what I have read I could use one of the following to get more than 2 hosts into my Cluster.

• Use a SAS switch (few grand)
• Use a SAS expander such as this one: http://www.intel.com/content/www/us/en/servers/raid/raid-expander-res2cv.html (few hundred)

With either solution I start to to wonder about I/O limitations.
When I use a non-expander backplane, I get 1 SFF cable per 4 discs, so I'd need pretty amazing discs to max out the interface
But when I use SAS-expanders, I get 1 SFF cable for all my discs;  Now I can get into situations where the discs have greater I/O than the interface.

Please let me know if there are other solutions out there I am currently not aware of.

Hello All,

my apologies if this has been asked before - I don't even know what keywords to use for a search.

Does anyone here see a problem with attaching/adding a virtual switch to either the host's cluster NIC ports and/or iSCSI NICs?
Seems like a waste of NIC ports to reserve extra NICs for the guests - with MPIO that would be six dedicated NICs (three for the host and three for the guests - virtual switches) per host.

Thx in advance for comments and opinions!
Rgds - Marcus.

My ISP provides a static public IP after I establish my PPPoE tunnel. I am going to plug my ADSL model directly into the my server's ethernet port and I want to establish the PPPoE tunnel directly from the MS Server 2008 R2's ethernet interface. My cpanel application that really needs this address is running on Cent OS in a VM on this server. When I setup the VM, I specified that it would be connected to the external interface. So my question is, when I establish the PPPoE tunnel, the public IP will be assigned to my host's interface, will that same IP be assigned to my VM's is interface? Or is NAT happening between the host and VM's interface. I notice that there were some virtualization interfaces established after setting Hyper V so perhaps a private internal address is assigned to my VM's interface.

If so, is there a way to bridge the address to the VM since I am told that NAT will break the application. 

If this doesn't work could I use the host to establish the PPPoE session on the physical interface, assign it an "unnumbered" address and bridge the public IP onto the VM's interface?

Or if that doesn't work could establish the PPPoE session directly from the VM's interface and have it traverse the host's interface back to ISP, where the IP address response will bypass the host and end up on the VM's interface? 

Hi,

Does any one know how can I troubleshoot VM movement , in other word what is the event ID of moving VMs

Thanks,

Kareem Behery

Hi

We need to P2V some old server into Hyper-V 3.0 environment (on of them is also a Domain Controller for AD domain)

We don't have System Center, so are there any other free tools or options to do 'live migration' from physical-to-virtual ?

I know vmWare has a great free tool vmWare Converter Stadard that do exactly what we need, but it only converts it to VMDK format ?

We found free tool disk2vhd, but it's not so elegant as vmWare converter, but if there is nothing else we'll have to go with it.

Regards,

Mike

I am trying to virtual a domain controller using MSVMM2012 but everytime it converts the domain controller the physical machine boots backup in to windows as well. I havent successfully converted it yet due to NIC issues but is this normal behaviour as looking on the web everything says that the phyical machine should never be brought back on-line becuase USN rollback.

Am i missing something or is this not a potential risk if the physical machine is booted back up my the process.

Jason Vearncombe | www.aboutmymeal.com | Restaurant Feedback Website

I run a small 2008 R2 training LAN to train students in the rudimentary principles of 2008 Administration.

The students host machines are also running 2008 R2 (member servers) and they use Hyper-V to build and manage a hypothetical forest.

I use authentication manager to allow the students to run Hyper-V to create and manage these VMs.

Due to an ongoing tech refresh our machines are being replaced rather peicemeal.

Q. Instead of going round and setting up the authentication manager on each member server when the box is changed, how can i control the settings of each authentication manager from my "real" DC?? (Hope this question makes sense!)

I was able to replicate 2 out 5 VMs on our server but I am not sure what this error refers to.  Any ideas... The VMs are up and Running

Thanks

Topology is this

Storage Server - 172.31.250.2 with multiple application shares provisioned for Hyper-V Storage

Hyper-V Host - 172.31.252.57 & 172.31.250.3

Both Servers running 2012 in a single 2012 domain

On the Hyper-V host within Windows Explorer I have mapped multiple shared drives located on 172.31.250.2

When I run the migrate storage wizard on this host and come to the point at which I can browse for a destination to migrate storage too, the drives do not show. If I open a windows explorer box at the same time they are visible there?

If I type the UNC path in as the destination instead of browsing for them from within the wizard this works and the storage is migrated. The network drives are a mix of hidden and unhidden shares and the behaviour is the same with both - they are all not shown when browsing.

Even though the storage migration appears to work, I am concerned though that the drives do not appear from the wizard when browsing, when I can see nothing to suggest why they arent appearing?

Paul

Hi,

 Hyper-V VM's are having timesync issues, Event 51 Time-Sevice is reported during the whole day/night. This results in the problem that time is always 1~10 seconds off. This is generating problems with some applications.

We are using Domain structure for time and have disabled the  Hyper-V Time integration service for the VM's

Our env consists of a root- and child domain. The Root domain PDC is a VM and has no event ID 51 error. This root PDC syncs time with an internetsource.

The PDC of the child domain (physical hardware) is syncing time with the Root domain PDC and has no event ID 51 error.

We have  some Hyper-V host, installed with 2008r2 sp1 in the childdomain. These hosts sync time with the physical child domain DC's. The VM's Running on these Hyper-V hosts are having the event id 51 timesync issue.

These hosts are running 2008R2 SP1 VM's.

Any Ideas how to get proper time sync for the VM's?

I'm getting many events of id 4098 in my host Hyper-V Server 2012 event log.  The guest (Server 2012) for the event is on a pass through disk being backed up by DPM Server 2012 SP1 with an agent installed in the VM.  All integration services are being offered to the guest.

I have another guest (Server 2008R2) with pass through disks on another host (Server 2012) being backed up with DPM in the same manner and I do not receive these events.  DPM agent is also installed on this guest and all integration services are being offered as well.

Both guest systems have the current integration services installed.  Does anyone know the cause of this message?  The event text is:

'GUESTSYSTEMNAME': The Virtual machine D5C3A563-DD00-4CFA-A08A-826E37720499 cannot be hot backed up since it has one or more volumes with differencing areas located on different volumes

Thanks.

All,

I would like to share my (free!) solution for installing software on a Hyper-V guest, when that installer checks for usb support.

My problem was that I tried to install a HP printer and scan driver in a Windows XP guest, running on Windows 8 Hyper-V. The installation failed with a message that no USB hardware and drivers were found and setup could not continue...
Duhhhh, I am trying to install it as a network printer/scanner, you HP morons!

After searching the web, I found various solutions. One of them was installing the Guest OS under VMWare Workstation, install the HP printer software (since VMWare workstation has USB support) and then migrate the VMWare guest to Hyper-V. I thought this was way too much work!

Then I stumbled on the KernelPro usb-over-ethernet solution. I downloaded the free client and installed it on the Windows XP guest under Hyper-V. I did not connect to any usb-over-ethernet server, as I do not have one. However, having the usb-over-ethernet client running, made the HP installer believe the Hyper-V guest had full USB support and happily installed the software.

Here you can find the free download for the KernelPro usb-over-ethernet client:http://www.usb-over-ethernet.com/download.html.

Kind regards,

Erik Cheizoo

excellence & Difference - the art of identity management
http://www.XenD.nl

eXcellence & Difference - We keep your business running

Hi,



I have 2 physical Hyper-V servers. On them are several VMs each. Both servers have 2 physical NICs (one for external internet; one for internal private access) with static IP addresses.



The two physical servers can ping each other over their internal IPs, but I cannot ping from physical server > VM or VM > VM (whether the VMs are on the same host or different hosts).


Each physical server will host a DC (2 domain controllers > 1 domain), so obviously these have to be reachable from all locations.



Host #1 has an external NIC shared with the management OS and an internal NIC on the private NIC.

Firewalls etc all disabled. Pings that fail result in destination host unreachable or timeouts.

IPCONFIG of the host #1:



Windows IP Configuration

   Host Name . . . . . . . . . . . . : HV3-DEV
   Primary Dns Suffix  . . . . . . . : INFRASTRUCTURE.SHAREPOINT.LOCAL
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : INFRASTRUCTURE.SHAREPOINT.LOCAL

Ethernet adapter vEthernet (Private Virtual Switch):

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
   Physical Address. . . . . . . . . : 00-15-5D-71-54-0B
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::30af:5a2d:85ac:b85b%45(Preferred) 
   Autoconfiguration IPv4 Address. . : 169.254.184.91(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 754980189
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-8E-C8-52-00-25-90-59-70-19
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (Intel(R) 82576 Gigabit Dual Port Network Connection #2 - Virtual Switch):

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physical Address. . . . . . . . . : 00-25-90-59-70-18
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 23.29.113.84(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.248
   Default Gateway . . . . . . . . . : 23.29.113.81
   DNS Servers . . . . . . . . . . . : 23.29.113.88
                                       192.211.59.59
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) 82576 Gigabit Dual Port Network Connection
   Physical Address. . . . . . . . . : 00-25-90-59-70-19
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::756b:b502:53cb:40fc%12(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.6(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 251667856
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-8E-C8-52-00-25-90-59-70-19
   DNS Servers . . . . . . . . . . . : 192.168.0.7
                                       192.168.0.13
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{1E37D92C-83E9-44C7-8DAF-9BA6B177045F}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{6242D0F8-8F49-463A-9DCA-D87FF8AC9FD1}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{CE077CBD-CB1F-45BB-9C0F-F2E15F24B804}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2002:171d:7154::171d:7154(Preferred) 
   Default Gateway . . . . . . . . . : 
   DNS Servers . . . . . . . . . . . : 23.29.113.88
                                       192.211.59.59
   NetBIOS over Tcpip. . . . . . . . : Disabled



Host #2



Windows IP Configuration

   Host Name . . . . . . . . . . . . : HV3-DEV-16
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter vEthernet (External Virtual Switch):

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physical Address. . . . . . . . . : 00-25-90-25-D5-38
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b404:cc71:5db:d550%19(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.211.59.58(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.248
   Default Gateway . . . . . . . . . : 192.211.59.57
   DHCPv6 IAID . . . . . . . . . . . : 318776720
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-96-6F-C9-00-25-90-25-D5-39
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-25-90-25-D5-39
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::99aa:3aad:a090:80%13(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.13(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.211.59.57
   DHCPv6 IAID . . . . . . . . . . . : 268445072
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-96-6F-C9-00-25-90-25-D5-39
   DNS Servers . . . . . . . . . . . : 23.29.113.88
                                       192.211.59.59
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{21474172-0C51-4520-A832-1D706BC09DEE}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{30EE1DB6-2647-4731-B67E-5E315483788B}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft 6to4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2002:c0d3:3b3a::c0d3:3b3a(Preferred) 
   Default Gateway . . . . . . . . . : 
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Disabled


VM running on host #1:






Windows IP Configuration

   Host Name . . . . . . . . . . . . : HV3-INFRASTRUCTURE-DC001
   Primary Dns Suffix  . . . . . . . : INFRASTRUCTURE.SHAREPOINT.LOCAL
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : INFRASTRUCTURE.SHAREPOINT.LOCAL

Ethernet adapter Ethernet 11:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #11
   Physical Address. . . . . . . . . : 00-15-5D-71-54-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::552a:f428:afc0:3d84%38(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.7(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 637539677
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-7A-66-0D-00-15-5D-8A-BA-00
   DNS Servers . . . . . . . . . . . : 127.0.0.1
                                       192.168.0.12
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 10:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #10
   Physical Address. . . . . . . . . : 00-15-5D-71-54-06
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::19a0:5a03:9498:2fe8%25(Preferred) 
   IPv4 Address. . . . . . . . . . . : 23.29.113.88(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.240
   Default Gateway . . . . . . . . . : 23.29.113.81
   DHCPv6 IAID . . . . . . . . . . . : 620762461
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-7A-66-0D-00-15-5D-8A-BA-00
   DNS Servers . . . . . . . . . . . : ::1
                                       192.211.59.59
                                       127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{14DEF9F6-3292-47EB-B336-C3B8F29385A2}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft 6to4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2002:171d:7158::171d:7158(Preferred) 
   Default Gateway . . . . . . . . . : 
   DNS Servers . . . . . . . . . . . : ::1
                                       192.211.59.59
                                       127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{EE4F3970-3571-409C-9DCC-0D7F2AEAEDFA}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

When I try accessing Hyper-V Server 2012's Device Manager via MMC I get "Make Sure that this computer is on the network, has remote administration enabled, and is running the "Plug and Play" and "Remote registry" services.

The Error Was: "The machine selected for remote communication is not available at this time.

I disabled the Hyper-V Firewall and followed the steps outlined here for "Allow remote access to the Plug and Play interface":
http://mikefrobbins.com/2010/12/02/enabling-remote-access-to-device-manager-on-server-core/

Any ideas?

The Hyper-V Manager works as-well-as the Policy Editor, just not Device Manager.

Hello,

I am stuck with Hyper-V Replica.

My Scenario: I have 2 node Hyper-V 2012 Cluster and I want to test Hyper-V Replica. So i had setup a standalone Hyper-V Replica Server for this cluster. I have created a Hyper-V Replica Broker role and Enabled Replication on my VM which was successful. Planned Failover is half success since i have not  configured replication setting in my replica broker role. Planned failover throws a warning that reverse replication is not configured so perform a reverse replication manually.

Now I got totally confused what to configure in replica broker role. Which Primary server and storage are to be configured?

please put me out this.

Regards

Hari Rama K

I'm using the native (C++) function CreateVirtualDisk to copy a source VHD to a new destination VHD and am getting the error message "A Virtual Disk Provider for the specified file was not found".

There aren't many results for that message - all on 2008R2 and most mention changes to the registry (which I've made but to know effect).

I do need/want to support both Hyper-V 2008R2 and 2012 with the same binary - so I'm limiting myself to VERSION_1 of the API.

        HRESULT st = 0 ;

        VIRTUAL_STORAGE_TYPE vst;

        vst.DeviceId = VIRTUAL_STORAGE_TYPE_DEVICE_VHD;
        vst.VendorId = GUID_NULL; // unknown vendor

        CREATE_VIRTUAL_DISK_PARAMETERS params;
        params.Version = CREATE_VIRTUAL_DISK_VERSION_1;
        params.Version1.UniqueId = GUID_NULL;
        params.Version1.MaximumSize = 0;
        params.Version1.BlockSizeInBytes = CREATE_VIRTUAL_DISK_PARAMETERS_DEFAULT_BLOCK_SIZE;
        params.Version1.SectorSizeInBytes = CREATE_VIRTUAL_DISK_PARAMETERS_DEFAULT_SECTOR_SIZE;
        params.Version1.ParentPath = NULL;

        std::wstring srcWS( src.begin(), src.end() );
        params.Version1.SourcePath = srcWS.c_str();

        HANDLE h = 0;

        
        std::wstring destWS( dest.begin(), dest.end() );
        const wchar_t * destPathStr = destWS.c_str();

        std::wcerr << "src '" << params.Version1.SourcePath << "'" << std::endl;
        std::wcerr << "dest '" << destPathStr << "'" << std::endl;

        try {
            st = CreateVirtualDisk(
                    &vst,
                    destPathStr,
                    VIRTUAL_DISK_ACCESS_ALL,
                    NULL,
                    CREATE_VIRTUAL_DISK_FLAG_NONE,
                    0L,&params,
                    NULL,&h);
        }
        catch ( ... ) {
            throw Poco::Exception( "3D82D20 : CreateVirtualDisk threw exception "); 
        }

Trying to install the all-in-one Hyper-V core from en_microsoft_hyper-v_server_2012_x64_dvd_915600.iso

System is an MB is an Intel P2600CP2 board with dual xeon E5-2620 processors

I have a 120gb SSD sata 6gb/s drive attached to a PCIe gen 2 controller card (this is where I will be installing the hypervisor)

I have 2 3TB sata drives attached to the 6gb/s ports on the motherboard (these will be setup in RAID 1 for VM storage)

When installing the iso, all disks show"This computer's hardware may not support booting to this disk" with details indicating that the disk's controller may not be enabled in the BIOS.

All disks are enabled in the bios.

Looking at this post - http://support.microsoft.com/kb/925481 - led me to believe that the mulitple disks were confusing the install. So I disconnected the 2 3TB from the motherboard. No luck... same thing.

ESXi v5.1 installed just fine.

Any ideas?

gimme some slamming techno!!!!

Atenciosamente Julio Araujo

Hello Everyone,

My current enviroment consists of;

1) Windows Server 2012 server being used as SMB 3 share for ,

1) Windows Server 2012 Hyper V Host with 6 virtual machines

1) Windows Server 2012 Hyper V host with 10 virtual machines

The SMB 3 file server has two shares; vmShare1 and vmShare 2.

vmShare1 is used for storage for Hyper V Host1

vmShare2 is used for storage for Hyper V Host2

Is there any reason why I could not combine the two different shares into just one share and have both of the Hyper V host connect to the one share?

Just have all my virtual machines on 1 smb3 share, and both hosts use the  same one share?

The host are two stand alone machines, non-clustered

DJ

Hello,

need to uninstall Integration services from server 2008 sp1 R2 VM.

The integration services not appear under Programs(control pannel). No uninstall switch for setup.exe in command line.

Help of integration services Setup.exe shows 2 available switches: quiet and norestart.

What to do?

Thx.