Hi All ,
I`ve file server windows 2008 cluster (2 nodes) and I need to perform p2v using disk2vhd so any recommendation regarding its procedures? or normally I can convert node by node normally? what about the file server storage after virtualize the server? what about quorum disk?
Edward
We have two new servers, each at different clients running Server 2012 R2 and I heard that Microsoft will allow us so spin up another Server 2012 R2 free in Hyper V. I wanted to post here to see how that works as I typically use VMWare but since this seems to be included I would like to use it. My question is once install the Hyper V role and create another 20120R2 VM will it ask me for a product key or will it activate on its own? Not sure how the licensing works for this yet. Can someone shed some light on how this works?
Hi,
look please at a screenshot...
D: partition is on dedicated vhdx and set as dynamically expanding.
The strange thing I cannot explain:
1.The VHDX size is 100 GB
2. in Windows I have 39GB of free space
3. When in Hyper-V manager the Current file size is about whole 100GB
For example for partition C: on dedicated VHDX it correctly matches Windows free space and current file size.
The final result is that total VM folder size is influenced by 100GB current file size. So I am loosing 40GB.
Why it could happen? Should I convert the drive to gain back 40GB. It is not a static drive...
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Been at this for HOURS.. I am playing with VLANS in Hyper-V. Trunking, access ports and so on. Didt get it to work, so I deleted all the VLAN's and now nothing works. First I ran: Set-VMNetworkAdapterVlan-VMName VM1-Trunk-AllowedVlanIdList 7-12-NativeVlanId 10 and after that Get-VM VM1 | Set-VMNetworkAdapterVlan-Untagged. I have restarted the VM's, reset the tcp/ip stack. I installed Wireshark, I see no icmp packets at all when pinging any computer in the same network. Deleted the vSwitch, did nothing..
Anyone have any idea?
Edit: Deleted the vNics and now it works. But... When adding the same IP and naming the vNics with the same name it says its already in use. How do I get rid of that?
Hi,
not sure where to post this really so i've posted it here because of trying to configure time for existing virtual domain controllers
so, we have the following setup for how time works:
Server1 is a virtual domain controller, it gets its time from the integration components in hyper-v
Server2 is the hyper-v host, it gets its time from Server3
Server3 is a physical domain controller, it gets its time from Server1
The above was all shown using w32tm /query /source on each server
This causes a loop of dependencies, but out of curiosity - how on earth did my time not drift by hours/days/weeks in this setup - its been running for at least a year like this, its a closed loop. Neither Server1 or Server3 are the PDC, that's actually another domain controller not included in the above. Can anyone shed any light on this? it's no big deal, my time was only out by like 2 minutes but im puzzled by how it would be only 2 minutes because server1 would have accumulated some clock skew.
Cheers
Steve
I can't create a Hyper-V Generation 2 Virtual Machine. There is a link to the screenshot of the problem below, but basically it says "no uefi-compatible file system was found" on the SCSI DVD and SCSI Disk, and also "DHCP failed" for the network adapter. The host and guest OS are both Windows 10 Pro x64 and my laptop has an i7 4720hq and 16 gb ram (and I don't know if it matters, but my BIOS is set in UEFI boot mode).
Any solutions or workarounds?
Thanks!
https://i.stack.imgur.com/apxVB.png
I am running a esxi lab within hyper-v and the vms within this do not want to connect to the network. I have been told that I need to enable promiscuous mode on the virtual switch and I can't find the option anywhere. I cannot get guest OSes to connect to the network under the vmware vsphere.
Is there any way to enable this? Please respond. Thank you.
Hello,
Currently, my host machine can not arp the gateway address of 10.0.1.1/24. It was able to get internet access before the hyper-v vm was configured on the 2012 R2 Server.
When the external V-switch was made the Hyper-v manager made a new interface on the server called "Data" and transferred my server ip address to this new interface. The server has the ip address of 10.0.1.11/24 and a gw of 10.0.1.1/24. After, creating the switch, the Vm was booted and installed to the disk. The Vm has a ip address 10.0.1.13/24. It was after the Vm was created that my server lost connection to the gateway. When I ran the window troubleshoot Diagnostic tool on the V-switch interface,internet access was back but lost after the arp entry expired.
I'm assuming that the troubleshoot tool block the vm machine for second that allowed my machine to arp the gateway.
My route table has a default route to the proper gateway address
The Arp table has the VM, 2012 Server, and some other statics that are in place by the machine. The gateway address is not in the arp table after about 3 mins.
I'm not sure if the correct V-switch is being used. Or if i should create a internal version and bridge it to the VM.
We started having issues with Intuit Software within RDS in our Server 2012 R2 Standard, both Quicken 2017 Home & Business and QuickBooks Pro 2017 are constantly complaining about installer error (QB ins asking to run the setup.exe every 5s, and Quicken does not allow the data file association to open downloaded content from financial institutions...
Researching online only brings reference to Server 2003, and therefore irrelevant to our situation!
Contacting Intuit Support is worthless as they try desktop approach to the server environment, which won't work for obvious reasons... ;)
Any help is greatly appreciated!
Hi All,
We have 3 Hyper-V servers 2 of which are part of a cluster, 2 physical adaptors have been dedicated to iSCSI and LUNs are presented to the hosts for shared storage. Disk failover is controlled by the iSCSI MPIO.
We have a requirement for VM's to have direct iSCSI connection(s) to access the data on the disks, i think this is called a RAW connection (correct me if i'm wrong). To configure this my thoughts were to create two vSwitches and have each vSwitch connect to the physical iSCSI interface (all iSCSI vSwitchs will have the same name across all hosts).
With this is mind it raises questions:
I look forward for all of you professional guidance.
Trying to get VLAN & Trunking to work in Hyper-V.
I have two VM's on the same Network. SCVMM and Host1. Host1 should be a Trunk for VLAN 7-12 and Native VLAN 10. I then put SCVMM on VLAN7 via the GUI. Does not work! If I set Native Vlan to 7 it works. If I not use Trunking it works (both VMs on VLAN 7).
VMName VMNetworkAdapterName Mode VlanList
------ -------------------- ---- --------
Host1 Network Adapter Trunk 10,7-12
Remote Network Adapter Untagged
Remote Network Adapter Untagged
RRAS Network Adapter Untagged
RRAS Network Adapter Untagged
RRAS Network Adapter Untagged
RRAS Network Adapter Untagged
SCVMM Network Adapter Access 7
SCVMM Network Adapter Untagged
SCVMM Network Adapter Untagged
What Am I doing wrong, or not understanding?
Its this LAB I am setting up.
https://blogs.msdn.microsoft.com/excellentsge/2016/10/06/deploying-sdn-on-one-single-physical-host-using-vmm/
Hi
I removed a team Server 2012 R2 Server with Hyper-V Roles installed. When I go to recreate the team I don't get any adapters listed even though they are there and have picked up ip addresses. I tried to create it using powershell and get the following
PS C:\Users\trcadmin> new-netlbfoteam -name "Virtual Production Team" -TeamMembers "Production Virtual Network A", "Production Virtual Network B" -TeamingMode SwitchIndependent
new-netlbfoteam : Member 'Production Virtual Network A' cannot be teamed as it has a Hyper-V role enabled on it
At line:1 char:1
+ new-netlbfoteam -name "Virtual Production Team" -TeamMembers "Production Virtual ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam
], CimException
+ FullyQualifiedErrorId : MiClientApiError_InvalidParameter,New-NetLbfoTeam
Hi All
I am having issues mounting Server2012R2 VHDx files with PowerShell. When I try and mount the VHDx files I get the error
Mount-VHD : The Hyper-V Management Tools could not access an expected WMI class on computer xxxx
This may indicate that the Hyper-V Platform is not installed on the computer or that the version of the Hyper-V Platform is incompatible with these management tools.
I can however mount the images via Explorer.
Hyper-V Module for Windows PowerShell is installed ( As well as all other management tools)
Any help would be appreciated.
Thanks
Tim
The blue screen is occurring randomly on all four nodes of my newly created Windows 2012 R2 Hyper-V Cluster.
Each Server:
Not all servers are rebooting at the same time. They will sporadically do this with no event indicators of any failures prior to the event. This appears to be a hyper-v memory management error which usually indicates bad memory or something like that, but this is extremely unlikely because the events are occurring on all four servers that are identical. The only reason I can see this being the case is if I have some BIOS issue that is undiscovered as of it. This can always be a possibility but HP has been pushing me to Microsoft because of the cross device consistency of this.
There simply is nothing in any log that shows a build up to this issue.
The other suggestion I am being given is to reinstall the server. But that means the entire cluster as they are seeing the same thing.
There are references to this covering Windows 2008 R2 and one even shows a hotfix, but that isn't 2012 R2 and does not help as well.
Daren
Hi all,
I was hoping to be able to stand up new VMs with a minimum of fuss, but the Import-VM functionality seems woefully limited.
I created Win2016Template, sysprepped it and then exported it.
Now when I run Import-VM, the VHDs and the VM itself, retain the old settings, as I can't tell the import job that the "new"/imported VM should actually be called something else, Win2016DC01, and then name the VHDs and the VM itself correctly.
I suppose I could fudge it with PowerShell one by one, but that's inconvenient if I want to stand up 10 VMs in one go..
So, what is my best choice for importing/creating new VMs based on a template and ensuring they have the correct settings with a minimum of fuss? And by fuss I mean administrative work.
Hi,
I have strange issue and I hope that someone can help me. I am configuring Storage Replication and replication is failing on Physical sector size.
Server 1 Physical sector size is 512
Server 2 Physical sector size is 4096
I understand that all disks needs to have same size, same sector etc. but that what I don't understand is if I take one drive from server 2 and import it in server 1 physical sector size changes from 4096 to 512 and I am not able to change it back.
Can someone explain what is going on, please?
Dear all,
We use one Hyper-V server on Windows Server 2016 to host some virtual machines. We need a virtual machine which requires:
-16GB RAM
-2TB of disk
After doing some researches on the Internet, I finally created a VHDX file and I configured the size for 2 TB. I created it through Hyper-V Manager on my client computer connected to the remote Hyper-V server.
Although it took forever to create the vhdx file, I suddenly plug off my cable without thinking about it (damn!). Now, I cannot see the virtual hard disk process anymore (and I cannot see if it is finished or not, even if it says the file is currently in use when I try to delete my vhdx).
Do you have any solutions so that I can see again the process? If not, a way to cancel it and recreates it (during the night this time, because it takes forever and it slows down the other virtual machines)? The host hyper-V is in production.
Regards,
Lucas
Trying to access Hyper-V running on Server 2012 R2 from Windows 10 LTSB 2016 and I only get an error:
The Hyper-V Management Tools could not access an expected WMI class on computer....
Same server accessed from Windows 8.1 H-V Management Tools is working fine.
Anybody any idea?
According to this it should be no issue
Seb
