I have Windows 10 on my 2009 iMac Core 2 Duo, runs fine, booting into it is troublesome. Windows 10 is OK, El Capitan is a disappointment.

Looked into moving the license to my 2014 Mac Mini (i5 2-core), but the system backup failed, so moving it is out.

Now thinking about buying Windows 10 Pro, installing it under Bootcamp and running OS X as a guest OS. Wicked backwards eh? I would be able to run either OS with Bootcamp, but having them both at the same time is the goal. VMs are great.

All the information I get when I Google this combination is people wanting to run OS X on PC hardware and the license, etc. issues therein.

What I want to do does not violate Apple or Microsoft licensing (outwardly). It is Apple hardware legally running El Capitan. The Windows 10 will be licensed (purchased). The processor (4278U) does technically support the VM requirements AFAIK.

However, OS X is not listed as a guest OS for the Windows VM. Obviously, this is due to the Apple hardware license problem. I will not be violating the Apple OS license AFAIK. This should be legal and permissible in a perfect world. Apple Hardware and Microsoft software, what could go wrong?

So, can this be done or should I give up and just get the Windows Home version and depend on Bootcamp?

Thanks,

SK!

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 ");
        }

Hi there,

I have got windows 10 pro on my workstation computer and I need to run quite a lot of virtual machines on it at the same time. I found out tha VMware workstation has got a fixed upper limit of 64 VMs running simultaneously, so I need to find a different solution. 

How many virtual machines will be hyper-v able to run at the same time on windows 10 pro? Apart from the question of hardware, I want to know if there is some kind of a hard limit as I wasnt able to find out by googling.

Thank you!

Are there any dangers in hosting our virtual machine vhd's on a network drive within the same datacenter? We have multiple host servers and a storage server. I have begun testing the durability by moving some of the virtual machines vhd's to the storage server and cannot pick up  and noticable issues performance wise but i am concerned that having multiple vhd's open over network may degrade network performance or cause damage to a vhd if in the event that the host account connect to the vhd.

I understand the other option for us is to create iScsi drives - my concern with this is that we'll effectively be putting vhd's in a vhd which does not make that much sense to me. 

As this kind of setup is nothing new, what is the correct way to manage this?

Hello all,

We have set up Hyper-V Replication between two Failover Clusters, but we experience some issues. I think this is more related to the storage or its setup, but maybe some of you have experienced this or have some advice on what to check.

In short, our setup is as follows (if more information is needed, let me know):

2 failover clusters, both running on the following hardware:

Hardware: Dell VRTX with 2 M520 blades, 

Storage: integrated within Dell VRTX, connected via Dual Shared PERC8 via MPIO using RAID 6 

(one uses a volume of 14TB, the other uses a volume of 6TB)

Virtual Disks were initialized using ReFS partitions. These are now in use by the Cluster Shared Volume (managed by Failover Cluster Manager)

Issues during initial setup

A while ago I set up 8 virtual machines to replicate via Hyper-V Replica between both clusters. The first 24 hours this seems to be running fine, afterwards issues started to show as ReFS was taking the volume offline, it had several issues (ReFS event IDs 133/134, followed by 5120 from FailoverClustering, showing the volume was paused)

Second Try

Since then I have stopped all replication to try and set it up again, monitoring all events. I have now set up 2 virtual machines for replication. The replication health seems to be normal, and replication has been successful over the past few days. However, the following warning appears every time a replication cycle starts (currently set to 15 minutes):

---

---

Before setting up more Virtual Machines for replication, I would like to investigate these issues and whether they can cause issues. I have the feeling that when I enable replication for multiple VMs to replicate every 5 minutes that it may be to busy to handle all requests... Just an assumption, considering ReFS was taking the volume offline earlier on.

Does anyone have advice on where to continue looking or may have experienced similar issues?

We have Windows Server 2012 R2 Hyper-V, configured with virtual HBA. This is working fine with windows machine. Now we have configured one virtual machine with CentOS version 7, everything looks fine and HP 3PAR SAN also showing connectivity with virtual machine. But in the CentOS does not shows WWPN or any sort of connectivity with SAN storage. If anyone experience this please advise.

Regards,

Muji35

Majid Rehan

I have two Windows 7 SP1 machines running on the same Server 2012 R2 Hyper-V host (in a failover cluster). They have the latest updates and integration services. The two have the same hardware settings. 

However, one of them shows a value for dynamic RAM demand and status of OK, but the other has empty for memory demand and status.  I restarted the Win 7 desktop, but it didn't help.  Why is it not reporting?  I have a feeling it won't expand either if needed.

I have recently taken over an environment with more than 300 VMs, Multiple Hyper-V Clusters and SCVMM in place apart from other Services. While looking at these VMs within SCVMM, I decided to export their information in an Excel for better reporting. This is of course easy using Get-VM Command. Unfortunately because of poor naming convention, I am unable to know the role of each machine or at least specific role when the technology is known. For e.g. SCOM has multiple servers with just 01,02,03 added to the end. Nothing defines whether they are Gateway, Database or Management Server.

I would now like to utilize PowerShell to set the Descriptions of these VMs. I already have the CSV with VM names and other information but description column is blank. If possible, I would like to update the CSV with Description and run a command loop to update all the VMs. I can make the script, i just want to know if we have CommandSet to set Description from PowerShell?

Thanks!

Is there a way to re-attach VMs to a Hyper-V server? My Server 2012 box died, but as my VMs were stored on another disk (D:\) I thaught I could quickly put this VM-disk in my 2012 R2-box and re-attach the VMs.

I know the proper way is exporting and importing, but I couldn't export the VMs properly so I choose to register the VM, and it comes with an error:

The wizard cannot import virtual hard disks from source folder 'D:\Vms\VM1\'

Failed to get the disk information.

Failed to open attachment 'D:\VMs\VM1\VM1.vhd". Error: 'The file cannot be accessed by the system.'.

Hi,

I was hoping someone could help me out.

Currently we've set a bunch of Windows 8.1 Pro hosts with Hyper-V role installed. They're intended to let users run one or two VMs on their own, for testing and development purposes, with the only limitation of not being able to connect them to external network nor making changes on networking configuration of the host (there's a virtual switch configured on each W8.1 host, set to internal working only).

Users have non-administrator accounts on the hosts, and we've managed the above through the using of AzMan. To the date, everything is working as expected.

But it's possible that we will move to Windows 10 Pro soon, and I've learned that AzMan is deprecated since W2012, so we're considering other alternatives.

As far as I know, if we want to do something similar without considering non-MS products, it seems as if the only way is using SCVMM, which looks overkill for a few hyper-v hosts. Furthermore, such hosts are running on slightly advanced desktop computers, not powerful Hyper-V dedicated servers.

Does anybody knows if we can manage Windows 10 Hyper-V role enabled hosts in a such way with SCVMM? we're not going to run these testing VMs on W2012R2, and all the VMM-related info I've found seem to obviously deal with W2012R2 hosts.

Thanks in advance.

Hello I am looking for advice and steps on the best way to accomplish the following:

Current Hyper-V infrastructure consists of single standalone Hyper-V host with local storage (Server 2008 R2)

We are adding a second host.

Final vision is to have a 2 host Hyper-V cluster, Running windows server 2012 R2 using local disk as shared storage (cluster storage pool)

This is probably a ridiculously simple question/answer, but how do you enable the hyper-v event logs that don't appear to be enabled by default? I specifically interested in Hyper-V-SynthStor. The search engines give me nothing and there's nothing obvious in configuration.

TIA

David Mowers

We have 3 clients that we setup with almost identical setups. A host with 2 VM's. One VM is our Exchange Server and the other VM is our Application server.

Our Exchange server seems to function properly but our Application servers at all clients suffer from poor performance.

Our AppServer vary in what application are installed. But, Symantec Endpoint Protection and SQL. I feel that there is something configured incorrectly since this is an issue at 3 of clients.

The host and the VM's are sharing the 1 network card that is installed. Not sure if it makes a difference but I'd like to share as much info as possible.

Here are the operating systems for the Host and VM's.

Client 1

Host - Server 2012

VM Exchange - Server 2008r2

VM AppServer - Server 2012

Client 2

Host - Server 2012r2

VM Exchange - Server 2012r2

VM AppServer - Server 2012r2

Client 3

Host - Server 2008r2

VM Exchange - Server 2008r2

VM AppServer - Server 2008r2

Any ideas on where I should start looking?

Hi,

I am getting this error in SCOM 2012 (SP1). I notice that this happens a minute or 2 after VSS activity (most likely DPM 2012 is doing backups).

This may sound like a silly question, but how do I check the actual health status of the VHDX file it refers to? When I click "Inspect" button in VM settings, I don't see any indicator of the actual health status of the vhdx file. My experience is mostly with VMware, and I am pretty new to Hyper-V.

Please advise.

No health status here. Where can I see an actual current health status for this virtual hard disk?

Can we migrate/failover a VM having Pass through disks attached to it.

regards,

Samuel yj (samuelyohan@outlook.com)

Hi,

I just setup a couple of Windows Server 2012 Hyper-V boxes and enabled the replica of a VM. All seems to work fine. These 2 boxes are connected to corporate LAN through a NIC and each other through a crossover cable over another NIC. As I can see, the replica trafic flows through corporate LAN. I'm trying to move it over the crossover lan, to save corporate bandwith for VMs, but I can't figure out how. I tryed to setup the replica using the IP address of the "crossed lan", but in this case the replica setup fails with a kerberos error (maybe because that lan is detected as public and not as a domain one). I've not tryed with certificate authentication, but this seems to me quite cumbersome considering that both servers are members of the same domain (Kerberos seems the smarter choice).

Has anyone ever tryed this kind of configuration ? What's the best thing to do ?

Thanks a lot.

Massimo Piceni.

Hi,

What is the best way to repair a corrupt VHD/VHDX file? Is there a correct process to go through and if the tools by Microsoft don't work, what other 3rd party tools do you guys recommend?

Thanks

Hi, few years ago we followed this thread :

https://social.technet.microsoft.com/Forums/sharepoint/en-US/24fce42a-d486-4789-af4d-0b216b821f45/hyperv-replica-over-dedicated-network?forum=winserverhyperv

to make Replication working, and it works like a charm!

However, We try to implement the same method for an extended replica host but apparently this method does not work.

Trying to register dns correctly, changing host files to point to correct extended replica servers on each host and on the extended replica server itself (pointing to replicated hosts).... and It always use the second NIC and not the dedicated.

The replication between each host is working well using the dedicated NIC but only the extended do not care of the host file and only use management network...

Is anyone here has some idea how to make this works, I will appreciate a lot.

Thank you.

Regards

Apologies if this is not the right forum.

So I was preparing a new server to host virtual machines. This is a Dell PE r710, Dual quad-core Xeon processors, 48 GB RAM, 2x 72 GB SAS drives. The server has Hyper-V Server 2008 R2 installed. iSCSI volumes hosted in a Dell EqualLogic SAN will host the actual virtual machines. We have 5 of these with similar setups, 3 of which are setup in a cluster. We have 2 set aside for additional projects. These will not be clustered as they will be hosting Lync virtual machines. Anyway we have 1 server setup and working with 2 VM's. The 2nd server will initially host 2 additional VM's. My goal was to format the iSCSI volume on the 2nd server and prepare it to host VMs. Except I accidentally logged into the 1st server (it's one of those days - I was interrupted as I was typing in the server name into Remote Desktop and it auto-populated the first server instead of the 2nd) and begin formatting the volume. Needless to say Lync stopped working and the VMs crashed. I immediately recognized my mistake and stopped the format but obviously it was too late.

I was hoping I could recover the data on that volume. We have a trial of this software called GetDataBack NTFS edition. It can recognize the volume ok and it can scan it and see files. Unfortunately it does not see actual VHD files. Instead what happens is that it sees the VHD files as separate volumes/partitions/etc and recovers the data within the VHD files. Not sure if it should do that, waiting on a response from Runtime. Kind of cool in a way if we ever needed to recover data within a VHD file. Anyway, does anyone know of software that can recover data from a volume but not scan the contents of the vhd file and include that data in the recovery? By this I mean I want to recover the actual VHD files, not the data within. Perhaps Virtual Machine Manager can do something? We do have it installed and manage our VM's with it. It would save us the trouble of re-deploying Lync. Apparently there's a lot of ADSI edits needed to undo the changes Lync did to AD/ Even migrating users back requires some ADSI edits. Trying to find those online someplace just in case.

We did not have backups yet of these 2 VMS as we just recently got them setup and have moved a few users over (some of us from IT). We still had some configuration/tweaking/adjustments to make before migrating the remainder of our OCS users. I know, I know, backup backup backup. The SAN we have can even do snapshots of iSCSI volumes but we didn't even think of enabling it yet.

Regardless in what happens with the VM's, I enabled Windows Server Backup and will immediately setup nightly backups once the VM's are operational again. I will also have our SAN admin enable snapshots, and just for laughs I will also enable snapshots on the individual VM's. We're also currently testing out Data Protection Manager. Kind of wish we already had it implemented....sigh...

Thanks,

Banging my head against a board with a nail in it...