Hi Team,
i got issue,
After perform P2V from SCVMM 2012 Sp1, remote desktop to my VM always failed.
other services is no issue, only RDP problem.
can you help me to solve this issue ?
note : i cant find event viewer related this RDP problem.
somehow it can display logon pages, and then lost connection
Thanks
Hi Hyper V Guru,
I have encountered funny issues. Currently, I am trying to attach a blank VHD to my VM (Test1). Below are the details of my VM
HDD: 100GB (Fixed VHD)
RAM: 4GBd
OS: Windows Server 2008 R2
All of files of the VM are stored in D Drive.
I created one blank VHD for my database called "TestDB1) and store the VHD in E Drive. After that, I am trying to attach the VHD by adding HDD in IDE Controller 0 from the VM's setting inside the hyper-v manager.
However, when I tried to boot up, I encountered the blue screen and it will keeps rebooting nonstop. below are the error message. The error will disappear when I remove the added VHD file.
Please help on this.
Thanks so much for your attention.
Hi
I have exported VM from 2008 R2 and then try to import in 2012 R2 but its giving me an error.
here is the error.
Pragnesh
Edit: I was able to work around this. From what I've read, a bare metal restore from a physical to virtual machine is not supported, but that's what I tried and it worked beautifully. The only thing that went right today.
So, disk2vhd isn't needed (and as we've seen, didn't work). Instead I took these steps:
1. Control Panel -> File History. After it finishes searching for drives, at the bottom left of the page is a link to System Image Backup. Run it, and select a target drive for the backup. I used a 64Gb key drive. Next, it will show you the volumes that will be backed up. It automatically selects (and you cannot deselect) the volumes required for a bare metal restore. Any additional volumes are optional. You'll probably want to deselect the target drive for the backup.
2. After the backup is complete, either move the drive over to the Hyper-V host or access it over the network.
3. In Hyper-V Manager, create a VHDX virtual disk from the backup drive. Then create a blank VHDX that is at least the size of the original machine's system disk (which may have multiple volumes). In my case, this was a 2Tb disk, to which I added an extra 128Gb just to be sure. This isn't the size of the image backup, it's the size of the disk from which the image backup was taken. I made my disks fixed size. I don't know if it would work otherwise.
4. Create a Gen 2 virtual machine (this was necessary for me since my original machine used EFI boot). On the SCSI host adapter, attach the blank disk that will take the image restore, and attach a second disk containing the image backup (this can be deleted later).
5. Create a second SCSI host adapter and attach a DVD drive to it (also may be deleted later). Not sure if you really need the second adapter but I was just being cautious. Assign the ISO image for your original machine's install disc (Windows 8.1 Pro Update 1, in my case) to the DVD. Set the DVD to boot.
6. Run the VM and press a key when prompted to run from the DVD. Select the Repair option, and drill down until you get to a page with the option for a System Image Restore. Click on that and then select the drive containing your backup when prompted. It will inform you that drive C: (your blank drive) will be wiped out and resized to match the original system drive that was backed up. Then let it run. In my case it took maybe three or four minutes, but it was a very sparsely populated 2Tb drive.
7. After the restore completes, you should be good to go. After testing the new VM, I deleted the second SCSI disk with the backup image, as well as the DVD and its host adapter.
=================================================
I ran disk2vhd on a recently built Windows 8.1 x64 machine. The conversion completed successfully, but I'm having no luck finding the right recipe to booting it in Hyper-V on a Server 2012 R2 machine. I've tried both Gen 1 and Gen 2 (with and
without Secure Boot enabled). In both cases it apparently fails to find a boot loader. The virtual disk is VHDX.
I ran disk2vhd twice. Once including the additional volumes Windows creates for EFI, and once without. The result is the same either way.
Any help much appreciated.
Hi
I am using Hyper-V manager ver 6.1 to manage all VM's on 2008, 2008 R2 and 2012 but i cannot manage VM's on 2012 R2, is there something i can do about.
Pragnesh
It looks like there is a problem with the KB2920189 update.
When trying to install it via Windows Update on some servers, they all fails the installation of this update - they are all running 2012 R2 inside generation 2 Hyper-V machines.
Has this update been tested with the UEFI implementation inside Hyper-V?
Dear All,
I have created a NIC Team of two physical NICs and then created two team interfaces from the Team NIC. I am using two different networks on the team interfaces which are working as well. Due to naming convention
of the NIC Team, I had to only use the team interfaces so I am not using the parent NIC Team. So, I disabled it. Both team interfaces are working even after disabling the parent Team NIC. Can I keep it that way with team interfaces enabled
and parent NIC Team disabled? does it have any consequences? I am using both the team interfaces in a Hyper-V failover cluster with one network interface for management and other for cluster communication. Kindly, confirm if it would be okay to
keep it that way?
Thanks in advance.
Dear All,
I have created a Hyper-V Failover Cluster and I want you to confirm if the configuration I have done is okay and I have not missed
out anything that is mandatory for a Hyper-V Failover Cluster to work. My configuration is below:
1. Presented Disks to servers, formatted and taken offline
2. Installed necessary features, such as failover clustering
3. Configured NIC Teaming
4. Created cluster, not adding storage at the time of creation
- Added disks to the cluster
- Added disks as CSV
- Renamed disks to represent respective CSV volumes
- Assigning each node a CSV volume
- Configured quorum automatically which configured the disk witness
- There were two networks so renamed them to Management and Cluster Communication
- Exposed Management Network to Cluster and Clients
- Exposed Cluster Communication Network to Cluster only
5. Installed Hyper-V
- Changed Virtual Disks, Configuration and Snapshots Location
- Assigned one CSV volume to each node
- Configured External switch with allow management option checked
1. For minimum configuration, is this enough?
2. If I create a virtual machine and make it highly available from hyper-v console, would it be highly available and would live
migrate, etc.?
3. Are there any configuration changes required?
4. Please, suggest how it can be made better?
Thanks in advan
Dear all,
I have a customer which has a 8 node hyper-v cluster running w8k r2 and all the VMs are also w8k r2. However the customer is looking at upgrading the DCs and other applications and members servers to w12k but I have advised them to also look at their cluster servers.
The customer has enough capacity on the cluster to start building w12k DCs and then depromo the w8k DCs out (note there is one physical DC) They can also start building new member servers and cut over applications and data and eventually move away from having any w8k r2 servers, except the hyper-visors. The hyper-visors are running w8k r2 and are on the same domain.
I have advised the customer to look at upgrading OS on the hyper-visor and also the servers (hardware). The obvious reason I can provide at this time is the life-cycle of the OS and server hardware, however the customer does not feel this out-ways the cost saving if they were left as they are. Therefore I would like some advise on whether this type of setup and some strong arguments for using w12k hyper-visors appose to w8k r2.
We want to create a Hyper-V Guest Domain Controller. Is there a URL indicating the OS\Hyper-V requirements for the HOST and Guest?
TIA,
edm2
Dear Team ,
Today i am visit one site than i am show there one server 2008 r2 standard . there install Hyper v if they open ther 4 server showing running theypinging also but 2 and 3 server not coming remote from this application but if i take rdp its come .
Kindly suggest me .
My ALT id hemant.rawat1989@gmail.com
Regards
Hemant Rawat
Hello all,
We have a new hyper-v infrastructure deployed in two brand new Dell R720 Servers with 384GB of Memory and dual Intel e5 2670-v2 processors. This infrastructure is replacing an existing hyper-v 2008 R2 and all the guests are being migrated to this new cluster.
The issue we are seeing is our 2008 r2 guests blue screening ocasionally with 0x0000001a,0x0000004e or 0x00000050 bugchecks.
All this guests are configured with dynamic memory and with the integration components up to date. These same guests were running with no problems in the hyper-v 2008r2 cluster.
When searching i found this article from vmware that pretty much describes what we are facing:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2073791
Are you aware of the same problem with this kindd of hardware on windows 2012 r2 hyper-v?
Thanks!
Nuno Carvalho
I have a guest cluster of two nodes using a shared vhdx. What is the practice for expanding the shared disk? When I try to expand it the regular way, I get the following error message:
the requested operation cannot be performed on the virtual disk as it is currently used in shared mode
Thanks
Rob Nunley
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:
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:
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?
I have an odd issue I've been trying to tackle for a while now and am no closer to solving.
I"m running 2 Hyper-V Hosts currently not in a cluster (to likely change soon).
Each host has 2 Physical NIC's in a team with a switch "Virtual Switch" for Hyper-V. I recently also created new virtual switches for Migration and Cluster to prepare for the Hyper-V cluster.
So on my VM's I'm seeing Adatpers show up with "TAP-Windows Adapter v9 #2" or "TAP-Win32 Adapter OAS#3". There can be as many as 1 or in a current case 6. Removing them does nothing as they eventually will come back.
The IP's are generally 169.254.x.x though I have seen a 10.x.x.x IP.
For some time I did run a VPN on Server 2012, this was through a serve role. I do not run OpenVPN and I switched my VPN to run on my DD-WRT router.
This has frustrated me for some time, so any help is greatly appreciated.
I have noticed in Hyper-V 2012R2 when migrating a VM around it leaves behind an empty folder structure. Is there a way cleaning this up automatically after the successful migration?
For instance,
VM located at C:\clusterstorage\FOLDER_A\VM
Moved to C:\clusterstorage\FOLDER_B\VM
But.... The FOLDER_A\VM still exists after a successful migration. This should be deleted to prevent confusion and allow a VM if migrated back to FOLDER_A to reside in a folder called VM and not VM_1.
I'm planning to install Hyper-V 2012 + Win7 + ubuntu
I have many questions
1: is it possible to easily enable/disable the virtualization, i.e. switch from win7 running on top of Hyper-V and back easily, maybe using a pass-through disk instead than fixed or dynamic?
2: how much reliable a vhdx file is? I'm reading that it gets corrupted with abrupt power off? how much should I be concerned. Does it ever happen that I can't recover/fix a corrupted vhdx file?
3: what is the performance degradation of Hyper-V? should I expect that win7 will run 10%, 20% slower?
4: In the above configuration (Hyper-V 2012 + Win7 + ubuntu) and only one physical hard drive, should I create 3 partitions in it or only one and put all the vhdx files in it? what is best choice in terms of reliability and performance?
5: I've read that Hyper-V assigns only 4 processors to Win7. Does it means CPUs or Cores?
For example my Xeon has 2 quad-core CPUs, i.e. 8 cores. Does it means that with Hyper-V I'll have Win7 using only 4 cores?
Thanks in advance for any answer, even if only to some of them.
M
