Thank you. Karel Grulich, MCSE, SBS
Hello,
I'm running Win 2019 SRV with HyperV and two (2) VMs.
My main server has 8 cores and 64GB RAM and it running on RAID6 10k SATA drives.
I setup the VMs as one processor and dynamic RAM from 1GB to 10GB.
One VM is running the Kaspersky Management Console only.
The other is running as a RDP Server.
These are the only functionalities these two VMs run.
When I login into the host, the login is really fast. When I login into the VMs, the login takes more time.
Should I change something here to make the VMs faster to login and perform faster?
Thank you. Karel Grulich, MCSE, SBS
I took my Windows Server 2016 Datacenter test server in my home lab (Dell R710 with two X5650s and 32GB of RAM) and installed Server 2019 Datacenter on it to try out the new features that are centered around VMs (Hyper-V) and data deduplication. The OS install went fine, but after enabling Hyper-V in Server Manager, the system goes through its normal reboot that occurs during Hyper-V enablement, then it proceeds to boot loop. Windows Server 2019 install media's boot repair does not fix the issue, and I cannot get in via Safe Mode. Any advice would be greatly appreciated.
We are planning to migrate from a physical machine to Hyper-V structure.
In our Hyper-V environment test, we get, in simple queries, better (or almost the same) response time than in physical machine.
But, in more sophisticate forms, the performance decreases about 10 times. For example: in physical machine the response time is less than 2" versus 22" in VM.
Could you help me, please?
Here are the details:
1. Isolated VBA code:
WkConnectionString= "Provider=SQLOLEDB;Data Source=INSTANCENAME;Initial Catalog=DBNAME;User ID=USERID;Password=XXXXX;"
For WkI = 1 To 20
Set CnConexioDBNAME = New ADODB.Connection
CnConexioDBNAME.Open WkConnectionString
CnConexioDBNAME.Close
Set CnConexioDBNAME = Nothing
Next WkI
** This code takes less than 2" to answer when runs in physical machine and 22" in VM
2. MsAccess forms:
- The more sophisticated ones, have 12 Combo Box with a pass-trough query as data source in every one.
- Plus, three sub forms.
3. Languages and OS:
- Forms developed in MsAccess 2013 (x86) with VBA.
- SQL Server 2014 (SP3) (x64)
- Installed in Windows Server 2012 R2 Standard (in the Physical machine)
- DELL. 16Gb RAM. 2.4Ghz (2 processors). x64.
- Installed in Windows Server 2016 Standard (in the Hyper-V VM)
- DELL. 8Gb RAM, 1.7Gh, SSD. x64
- Microsoft ODBC Driver 13 for SQL Server (x86)
3. Hyper-V VM (hyperv-2016 core)
- VHDX on SSD
- Virtual machine Switch external
- Generation 2.
- Configuration 8.0
4. Clients
- When accessing from W7 or WServer 2008 to the VM, the response time is 8"
- When accessing form W10 or WServer 2012 to the VM, the response time is 22"
- However, in both cases, when accessing to the physical machine, the response time is less than 2"
5. Hardware
- NIC Intel i350,i210, broadcom netxtreme
- VMQ: Disabled
- BIOS: saving energy : High Performance power plan
Hello there!
I've heard various debates on this but nothing current and no real good sources for reasoning. It would be good to find the current standing of this in 2019:
What is the ideal configuration of the Hyper-V Integrated Time Synchronization service in an environment where NTP is also used? For example, let's say there are a 4-6 VMs acting as NTP servers for other VMs on a network (please don't instead focus that it isn't a 'best practice' configuration -- that is off topic). Will the two time services interact with each other? Should Hyper-V Time Sync be disabled on the client VMs and/or the VMs running NTP services?
Thanks in advance!
Could not find any info how to convert them. Need to upgrade HV to 2016, so eventually I can use replication of shared disks
Of course with "liitle" vhdx I can do just d-2-d data copy, but with disk of few Tb I simply do not have same space on array to create them one more time & then wait for data copy to happen
Thanks
Seb
Hello,
I am sure this question has been asked before, however I have been unable to get this issue fixed. First, let me describe what I am trying to do. I want to setup a home lab with 3 servers, one to be the AD/DC, another for SharePoint and finally a SQL server. I have 3 server 2016 datacenter servers setup currently. No other software installed at this time. I wanted to get the network issues fixed before proceeding. Right now I have network access on all three servers using "obtain …. automatically".
So far every attempt I have made to give what will be the AD/DC server a static IP has failed. No network connectivity.
I am more of a programmer and network connection issues are not my specialty.
Any advice on setting up the Hyper-V network?
thank you
Hello, I just upgraded my machine to Windows 10 and now my Hyper-V Manager cannot connect to and manage our Server 2012R2 Hyper-V Hosts. I get the following error.
"An error occurred while attempting to connect to server xxxxx. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server."
I've read in multiple places that Hyper-V Manager in Windows 10 and Server 10 will support managing Server 2012 and 2012R2 hosts. I'm not sure why it's not working though.
Any help would be appreciated.
Hello,<o:p></o:p>
We had experienced a virtual machine crash, and the virtual machine could no longer boot.<o:p></o:p>
Host: Windows Server 2012 (Hyper-V host)<o:p></o:p>
Guest VM: Windows Server 2012<o:p></o:p>
I then made a copy of the virtual machine and configuration to attempt recovery from a Windows Server 2016 for recovery.<o:p></o:p>
I tried to use the Inspect Disk function on the .AVHDX file, which then it asks to Inspect Parent disk. Once I try to inspect the parent disk, the same error occurs where it says the parent .VHDX is corrupt.<o:p></o:p>
“An error occurred when attempting to retrieve the virtual hard disk<o:p></o:p>
…\VM_Disk_0_HD_E6701573-EB9F-413… on server UNIREC.<o:p></o:p>
Failed to get the disk information.<o:p></o:p>
An unexpected error occurred: The file or directory is corrupted and unreadable. (0x80070570).<o:p></o:p>
Failed to get the disk information.<o:p></o:p>
The Hyper-V Virtual Machine Management service encountered an unexpected error: The file or directory is corrupted and unreadable. (0x80070570).”<o:p></o:p>
<o:p> </o:p>
EventID 27000 is logged in the Hyper-V VMMS storage log with the following error:<o:p></o:p>
Failed to open attachment 'E:\Hyper-V\virtualboot\VM_Disk_0_HD_E6701573-EB9F-4131-AC77-89C05EC878AC.vhdx'. Error: 'The file or directory is corrupted and unreadable.'.<o:p></o:p>
Any help would be appreciated!
Thanks!
Hello,
we have a Dell R730XD server that until last weekend run with Windows Server 2012. That server has dual Xeon CPUs and 256 GB RAM, RAID 10 of SAS disks and another one of SSD disks.
This server has 35 VMs and it did not show any performance issues. 11 of those VMs have replication enabled, and that also worked fine.
Now we have this server running Windows Server 2016, it has all updates and drivers installed, and without any other change the same VMs on the same hardware cant have replication enabled because the IO usage is extremely high. The IO its higher before the replication actually begins, when its creating a Reference Point.
The IO usage gets so high that event the SSD RAID 10 gets killed by it. This behaivior cant the normal, those same machines had replication without any issues with Windows 2012. I searched on the forum and uninstalled Windows Defender, some said that it can cause this kind of issued, but there was no luck.
Does anyone experience this issue? Any ideas are welcome!
Best regards,
Juan.
Consider the following scenario:
Customer stores secondary backups of their Hyper-V VMs in the Acronis cloud backup service, as a fallback in case the primary offsite backup system fails or the buildings burn down or something. They want to perform test restores to validate this approach,
which essentially means downloading VHD files from Acronis's service to a Synology NAS, creating new VMs on a hypervisor, and attaching the downloaded VHD files to them. The files still live on the NAS, not the hypervisor, because the files are very
large and the hypervisor's own SSD storage is very expensive.
The 'portability' of these VHD files has never been an issue; we've always been able to copy them between hypervisors and run them. However, this is the first time we're attempting to run a VM that has its VHD file on a NAS vs. direct-attached storage
on the hypervisor itself. The NAS share hosting the VHD files is mapped as a network drive on the hypervisor, which runs Server 2016 Standard.
When I attempt to attach a VHD file that's on the NAS to a new VM, I get the following error:
We've tried the following:
--mounting a NAS-hosted VHD file using the hypervisor's Disk Management snap-in, to verify that we can see data there (works fine)
--as mentioned by
this Brian Posey article, granting "Everyone" full control of the file temporarily, just to see if we can attach it to a VM (same error). Before anyone yells at me about security, this hypervisor and NAS are on a separate air-gapped network, and
we undid the change immediately.
--using the icacls fix suggested in the same article (same error)
--copying one of the NAS-hosted VHDs to the hypervisor's own direct-attached storage, and attaching it to a VM. (works fine!)
Neither the NAS nor the hypervisor are joined to an AD domain, so we're using passthrough authentication (same local admin account on both hypervisor and NAS). Accessing the NAS's share via the hypervisor, we have no issues browsing subfolders, creating test .txt files, or changing permissions on test files, suggesting it's not a permissions or authentication problem.
What should we be trying next? Thanks for your help!
I'm setting up a migration test server. I have a Dell R610 with 2016 STD installed and Hyper-V for the host. The server is connected to and a member of my work domain. I'm using two nics on the host machine, one connecting to the network (static ip) and a second (also connected to the network) for the VMs. I've created a virtual switch that uses the second nic.
I've created a Server 2016 STD VM. I can not get it to connect to anything. I've tried leaving the virtual nic to dynamic ips and I've tried to add static ips. But nothing is working. What am I missing?
Hi Guys,
i'm looking for some advice please.
We have 2 x host servers (A+B).
Both hosts have 6.54TB of total size.
Host B only has 1 live SQL Server VM which is not replicated but is receiving 2 VM Replicas.
SQL Server VM has a total size of 2.13TB of VHDX
Total disk cost of all VMs on HOST B leaves this host with around 1.71TB free.
Windows Server Backup runs from 6PM to 3AM and is running a full backup each time.
I believe that during this time the differencing disks are using up all the free space which is putting my running VM in to a saved state and does not recover automatically.
On top of this I am unable to have replication for the SQL VM because of the similar symptoms caused by WSB. The differencing disks werent clearing out.
Is there something I can do to get WSB to do incremental backups of these VHDXs files or is this expected to have to back up the full VHDX each time on a SQL VM?
Do you think I should replicate to Host A and back up host A instead?
Or, do I need to increase my disk capacity?
I must add that Host A running the two live VMs is having no issues with backup or replication. My issue is the SQL VM only.
thanks!
Like the title says, We are having an issue with our hyper-v host servers crashing on the initial startup of guest vm's.
Everything works fine during the creation of the guest vm, then when we go to power up the guest vm about 10-20 seconds later the host crashes. Doesn't happen on every vm setup, but quite a few (say 1/3).
I have found examples of others having the same issue or similar. See https://www.youtube.com/watch?v=ytP-RfhdBWY (not my video, but same sort of issue).
I haven't seen anything in event viewer that would indicate a problem with the host. no crash logs are saved when it does crash, just a hard black screen (no BSOD).
Any thing you guys can point me to look for here? I am at a total loss on this.
Thanks,
Hi,
Is it possible to create or import a Linux VM into windows 2008 r2 Hyper-V server?
Hi Team,
I have a critical file server running on Windows server 2012 R2 two node Hyper V cluster, one of the data volume is running out of space, when i tried to expand the VHD the edit option is grayed out like shown in the below screenshot.
I read some articles which says if there is a checkpoint available on the VM,i will not be able to edit the VHD, as you can see there is a checkpoint taken on 12/01/2018
I am worried if i delete the checkpoint , will i loose data , my question are as below.
1) Will deleting the checkpoint allow me to edit and expand the VHD is the checkpoint preventing me from expanding the VHD?
2) What is correct way to delete the VHD?
3) Will there be a data loss if i delete the VHD?
Regards
TechGUy,System Administrator.
When I set up my VM I saved as below:
Click Connect.
Now I want to change the settings. Where are the settings saved? I just want to edit the settings!
I've tried to turn enhanced session mode off then hope to be prompted again to choose the settings, but it didn't work. All I want to do is save some files from my VM to a USB drive.
I've tried to use: 'VMConnect.exe <ServerName> <VMName> /edit'
But all that command does is bring up the window that you can get to in Hyper-V manager.
I know I can access the USB drive because I have another VM that can access the USB drive.
