New Virtual hard disk wizard hangs after creating new vhd from huper-v manager on windows 7

New Virtual hard disk wizard hangs after creating new vhd from huper-v manager on windows 7 workstation.
Windows 2008r2 hosts the hyper-v server. I can create VMs and VHD's when connecting to the server locally with the hyper-v manager.
The issue arises when I try to connect to the hyper-v server from my workstation which runs windows 7.
I have installed The Windows6.1-KB958830-x64-RefreshPkg.msu that was suggested for windows 7 sp1.
I can connect to the hyper-v server, create vm's but I cannot create vhd's the gui just hangs with no errors in event log or on screen.
The files are there on the hyper-v hard drive but i suspect they are just created by windows as they are written and are not valid.

I've had just the same solution. Both did Hang Fixed size and flexible.
Two parts were taken:
1 - KB939820 for Windows 2003 server based domain controllers
2 - disable using IPv6 on your NIC
Result - both types of VHD's are created normaly.
-----Infrastructure----
Windows 2003 Domain upgtraded to 2008R2
Windows Server 2008R2 Hyper-V - virtualisation clustered
Windows 7 Pro - Hyper-V management
Feel free to use --Mark as answer-- or --Propose as answer-- option and rate if a comment helps you or seemed usefull. -------------- Не забывайте использовать кнопки --От&#1084;етить как ответ-- или --Предложить как ответ-- и проголосовать, если
ко&#1084;&#1084;ентарий ва&#1084; по&#1084;ог или кажется полезны&#1084;.

Similar Messages

Creating a Master virtual hard disk and using the same for all other VM's

Hi,
We would like to create a master virtual hard disk and use the same for all other VM's. Can we do that ?
my requirements :
1) create 10 VM's
2) first create a master virtual hard disk with win OS and use the same to create the 10 VM's.
3) After creating the VM's change the HDD size.
              -- if i have created master virtual disk with 500GB , and use the same for creating a virtual machine. can we change the HDD size to 1TB ?
After creating the VM's ,i will change the system names and activate the windows accordingly.
Will there be any implications ,if we can/will do like this.
Thanks.

Hi Suren424,
I think Using Differencing Disks may cover your needs .
Please refer to following setps:
   "Create the Parent Virtual Machine Configuration and Virtual Hard Disk
    Install the Operating System, updates, and common software
    Generalize the installation
    Prepare the parent virtual hard disk
    Create the differencing disks
    Create virtual machines that use the differencing disks
For details please refer to follwing link:
http://social.technet.microsoft.com/wiki/contents/articles/1393.hyper-v-virtual-machine-vm-parent-child-configuration-using-differencing-disks.aspx
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hi, I just put a new internal hard disk to my MacBook after formattimg it and I don't know how to install the OS X? Any help please

Hi, I just put a new internal hard disk to my MacBook after formattimg it and I don't know how to install the OS X? Any help please

Be sure you have prepared the new drive correctly:
Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.
When formatting has completed quit DU and return to the installer. Complete the OS X installation.

Resize the CentOS LVM inside VM from a secondary virtual hard disk

Requirement:
Airwave installed on a VM, with a secondary virtual hard disk.
we have a KB "Resizing the centOS LVM inside VM", is only useful if we have one hard disk for that VM instance.
https://arubanetworkskb.secure.force.com/pkb/articles/FAQ/Resizing-CentOS-LVM-inside-VM
However, This KB will be helpful in the scenario's where VM Administrators has to create a secondary virtual Hard disk, instead of increasing the disk space for current hard disk (could be for any reason for example: he cannot increase the disk space for the same disk as the pool that provides space to that disk has no space etc..).
Solution:
In this case, when we have added a secondary virtual hard disk, when we do # fdisk -l, we will see the secondary disk as /dev/sdb as shown below:
[root@localhost mercury]# fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes
255 heads, 63 sectors/track, 5221 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000650f3
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1          13      102400   83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              13        5222    41839616   8e Linux LVM
Disk /dev/sdb: 17.2 GB, 17179869184 bytes
255 heads, 63 sectors/track, 2088 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup00-LogVol01: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup00-LogVol00: 38.5 GB, 38520487936 bytes
255 heads, 63 sectors/track, 4683 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
And this is the # df -h, command output, before the LVM extension:
[root@localhost mercury]# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                       36G   11G   23G 32% /
tmpfs                 3.7G     0 3.7G   0% /dev/shm
/dev/sda1              97M   37M   56M 40% /boot
We need to extend the sdb disk space to VG group to combine to use the disk space as shown below in the configuration:
Configuration:
1. First, we need to create a partition in /dev/sdb
[root@localhost mercury]# fdisk /dev/sdb
# n {new partition}
# p {primary partition}
# 1 {select partition number, by default 3 is the next available}
# use the default cylinder values for First and last
# t {select partition id we just made (1)}
# 8e {Linux LVM partition}
# p {print. the new device should be described as Linux LVM}
# w {write to memory}
2. We need pv reate /dev/sdb1:
[root@localhost mercury]# pvcreate /dev/sdb1
3. Execute the command to extend the VG to sdb1:
[root@localhost mercury]# vgextend VolGroup00 /dev/sdb1
4. Enter the command to extend the LV to sdb1:
[root@localhost mercury]# lvextend /dev/VolGroup00/LogVol00 /dev/sdb1
5. Resize the VG:
[root@localhost mercury]# resize2fs /dev/VolGroup00/LogVol00
Done.
Verification
Now look at the # df -h, output, which will be different:
[root@localhost mercury]# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                       52G   11G   38G 22% /
tmpfs                 3.7G     0 3.7G   0% /dev/shm
/dev/sda1              97M   37M   56M 40% /boot

Hi Eric,
"My first thought was to do is reduce the drive, which I know cannot be done. I then thought to convert the disk but it consumes the whole of the dynamic potential, which somehow is a maximum of 2TB."
Yes , we can not get the disk space less than 2TB .
As a workaround , you can try the following steps :
1) defrag the volume  in VM , after that shutdown the VM
2) use "edit disk" in hyper-v manager to compact the VHD file
3) start that VM then shrink the volume that the disk space is larger than the VM needs in disk manager
This may limits the expansion accordingly .
Hope it helps
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Solved: I cannot manage (bring online, initialize, partition, format, or write to) a VHDX hard drive once it has "Enable Virtual Hard Disk Sharing" enabled.

Hello,
Issue:
On a Virtual Machine with a secondary VHDX attached, I cannot manage (bring online, initialize, partition, format, or write to) the VHDX hard drive once it has "Enable Virtual Hard Disk Sharing (VHD Sharing)" enabled.
Questions:
Should I be able to manage (bring online, initialize, partition, format, and write to) a VHDX hard drive once it has VHD Sharing enabled? If I should be able to manage it, what am I missing?
Topography:
One SuperMicro Cluster In a Box (CIB) with 2012 R2 Data Center on each node. Microsoft Failover Cluster installed and working on each node. The Failover Cluster Servers on each host passes all cluster validation tests. Two Hyper-V 2012 R2 Data Center Virtual
Machine (VM) servers, one on each node. 1 common Cluster Shared Volume (CSV) and 1 Generation 2 Scale-Out File Server (SOFS) shared volume both Resilient File System (REFS) formatted. One 5 Gigabit (Gb) Virtual Hard Drive Type X (VHDX) file on the CSV and/or
SOFS. Integrity bit and read only turned off on VHDX file.
Each of the two Hyper-V VMs have one 127Gb VHDX Generation 2 primary hard drive and 1 VHDX secondary hard drive attached, both on SCSI Controller #1.
Background:
If I start VM1 without the VHD Sharing enabled on the secondary hard drive, I can bring the drive online, initialize, partition, format, and write to the drive.
If I enable VHD Sharing, I can no longer modify the drive in Disk Management in any way. With or without VM2 running.
Both VMs and the CSV and SOFS are on the same host cluster server, or not, no difference…
The VHDX is referenced either by the CSV name C:\ClusterStorage\Volume1\TEST1.VHDX
or a Shared Folder name
\\sharedfolder\folder\Test1.VHDX .
If I start VM1 with VHD Sharing disabled and I format the drive, then shut down and enable VHD Sharing, the drive is offline and requests initialization which fails with an "I/O device error", every other attempt to manage the drive fails with
the same "I/O device error", error.
Events:
VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
Log Name:      System
Source:        Virtual Disk Service
Date:          3/3/2015 11:39:18 AM
Event ID:      10
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server1.Domain.local
Description:
VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Virtual Disk Service" />
    <EventID Qualifiers="49664">10</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-03T19:39:18.000000000Z" />
    <EventRecordID>27318</EventRecordID>
    <Channel>System</Channel>
    <Computer> Server1.Domain.local </Computer>
    <Security />
</System>
<EventData>
    <Data>8007045D@02070008</Data>
</EventData>
</Event>
AND
Log Name:      System
Source:        disk
Date:          3/3/2015 12:16:42 PM
Event ID:      153
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Server1.Domain.local
Description:
The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\MPIODisk1) was retried.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="disk" />
    <EventID Qualifiers="32772">153</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-03T20:16:42.017090000Z" />
    <EventRecordID>27333</EventRecordID>
    <Channel>System</Channel>
    <Computer>Server1.Domain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>\Device\Harddisk1\DR1</Data>
    <Data>0x0</Data>
    <Data>1</Data>
    <Data>\Device\MPIODisk1</Data>
    <Binary>0F01040004002C00000000009900048000000000000000000000000000000000000000000000000000020488</Binary>
</EventData>
</Event>
Thanks again for any help,
Robert

Hi All,
I had to buy a Willy Wonka bar and spend a golden ticket to get an answer to this one.
We found that the default LogicalSectorSizeBytes of a VHDX is 512b. It needs to be 4kb.
The Host drive doesn't seem to matter CSV or SOFS. Below is a way to create a VHDX with the correct LogicalSectorSizeBytes.
In Power Shell, type --> New-VHD -Path C:\ClusterStorage\Volume4\Cluster2DataDisks\Cluster2Disk1.vhdx -SizeBytes 200Gb -PhysicalSectorSizeBytes 4kb -LogicalSectorSizeBytes 4kb
Attach the resulting file to your guest cluster servers and set the Enable Virtual Hard Disk Sharing option on both server. You should now be able to bring the drives on-line and initialize them. They will also add to the guest cluster pool.
Change the size, path and file name above to fit your Cluster Servers configuration.
Thank You
Sachin Kumar Support Engineer | Windows Server Setup Team | Microsoft Enterprise Platform for finding the answer to this one.
Hope this helps others.
Robert

A problem was encountered opening a virtual hard disk in the chain of differencing disks -- when try to import vm in hyper v

Hi All,
I am new to the hyper V stuff. I have managed to install hyper-V on Windows 8. Now I am trying to import VM which got three foleders and one file batch file
Snapshots
Virtual Hard Disks
Virtual Machines
VM-Pre-Import 10961A-LON-CL1 (Batch file)
but I am getting this error
Please help me.
Thanks

Hi Tom,
Thanks for giving me direction. I am student and totally new to this hyper-v, so bit slow in understanding right now
This is the location of the files when i had extracted from rar file
Directory of C:\Program Files\Microsoft Learning\10961\Drives\10961A-LON-CL1
06/13/2014 07:54 AM    <DIR>          .
06/13/2014 07:54 AM    <DIR>          ..
03/16/2013 12:05 AM    <DIR>          Snapshots
06/13/2014 07:25 AM    <DIR>          Virtual Hard Disks
06/13/2014 06:25 AM    <DIR>          Virtual Machines
03/15/2013 07:38 PM               135 VM-Pre-Import-10961A-LON-CL1.bat
               1 File(s)            135 bytes
               5 Dir(s) 477,346,160,640 bytes free
when I opened the bat file -- location of the file
SET SUBDIR=%~dp0
mklink "%SUBDIR%Virtual Hard Disks\Base12B-W8.vhd" "C:\Program Files\Microsoft Learning\Base\Base12B-W8.vhd"
pause
and then i have changed the dir path to
SET SUBDIR=%~dp0
mklink "%SUBDIR%Virtual Hard Disks\Base12B-W8.vhd" "C:\Program Files\Microsoft Learning\10961\Drives\10961A-LON-CLI\Base12B-W8.vhd"
pause
When I tried to run the batch file then I got following message -- Can't creat a file when that file already exists.
Please advise

How do I access virtual "Hard Disk 2"?

I have created a new virtual machine. I have a initially created a Parent drive and set it as READ ONLY. In my new VM I created Hard Disk 1 as a Differencing disk that references the parent drive. I created Hard Disk 2 as a Dynamic Disk. When I launch
the machine I only have the single virtual "C" drive available. I was expecting another drive to be available. How do I access Hard Disk 2 - or am I not understanding the purpose of the additional hard disks?

Have you gone into Disk Manager and initialized the drive? When you create a new VHD, it's just a blank virtual hard disk. You need to initialize, partition, and format it before it's usable in Windows.

The storage where the virtual hard disk is located does not support virtual hard disk sharing. (Hyper-v / Windows 10 Enterprise Tech. Preview)

I am attempting to create new virtual machines in Hyper-V on Windows 10 Enterprise Tech. Preview and I am continually getting the error "The storage where the virtual hard disk is located does not support virtual hard disk sharing.". I am not trying
to setup a shared VM or VHD, just a basic VHD.
Does anyone have any suggestions on how to resolve this issue?

This issue is listed in the release notes and currently there is no fix on our side. Have to wait for the next build.
"Known issues in Build 10049
If you have Virtual Machines hosted on your PC running Windows 10, you will want to move to the Slow ring and wait for the next build as this build breaks the ability to run VMs. "
The statement is miss-quoted. It was about Hyper -V. An update KB3053898
was released to fix that
See the blog
Here :
excerpt........notice the statement has been crossed off in the blog.
UPDATE: You cannot enable Hyper-V on this build. If you have Hyper-V already enabled and you upgrade to this build, Hyper-V will continue to work. <del>If you have Virtual Machines hosted in Hyper-V on your PC running Windows 10, you will want to move
to the Slow ring and wait for the next build as this build breaks the ability to run VMs.</del>

Hyper-V Error 0x80070050 Virtual Hard Disk already exists.

Hi All,
I'm new to this form and virtualization. I was able to create a Virtual computer with Hyper-V but ended up deleting it due to an error I couldn't resolve during the OS installation process. When I try to create a new virtual computer with the same name I
get an error saying "The system failed to create a virtual hard disk (hard disk path and name .vhdx) the file already exists 0x80070050" I can not find that file anywhere to remove it even though I already deleted the virtual computer. Anyone ideas
on how to fix this, I don't want to always have to make new unique names if I delete one to make a new one. I'm using this server to learn on and I will most likely be doing a lot of deleting and creations.
Thank you,
James

James,
Most likely under "c:\ProgramData\..." which is a hidden folder by default on your system. Look around under this directory - "c:\ProgramData\Microsoft\Hyper-V" or something similar.
BTW - You can configure Hyper-V to tell it where to store the VHDs.
Regards,
-Steve

Error adding VM through Powershell: Virtual hard disk in the chain of differencing

I'm trying to programmatically create a VM from a .vhd file - my code is below. I'm getting a weirdo file not found error about disk chaining, but I've TRIPLE checked all my paths. Help is much appreciated!!!
Thanks,
Error:
ADD-VMHardDiskDrive : 'Testing' failed to add device 'Virtual Hard Disk'. (Virtual machine ID ADC7CF7D-2EC5-4428-B27C-6EDCF29F5922)
Failed to open virtual disk 'E:\will\VMTesting\Flash.480x800.vhd'. A problem was encountered opening a virtual hard disk in the chain of differencing
disks, 'E:\will\VMTesting\Flash.vhd' (referenced by 'E:\will\VMTesting\Flash.480x800.vhd'): 'The system cannot find the file specified.' (0x80070002).
My PowerShell code:
$n = "Testing";
$directory = "E:\will\VMTesting";
$vhdxPath = "$directory\$n.vhdx";
$vhdPath = "$directory\Flash.480x800.vhd";
$vm = Get-VM $n;
if($vm -ne $null) { Remove-VM $n -Force; }
New-VM -Name $n -MemoryStartupBytes (Invoke-Expression "1000MB") -Path $directory;
Set-VMMemory -VMName $n -DynamicMemoryEnabled $true -MinimumBytes 512MB -MaximumBytes 4096MB -StartupBytes 2048MB -Buffer 20;
ADD-VMHardDiskDrive -VMName $n -Path $vhdPath;
Start-VM $n;

Hi Will ,
According to the error message , please try to check the chain of differencing disk via "inspect disk.." .
# Create our New Differencing Disk
New-VHD –ParentPath T:\02R2June2012\08R2TemplateJune2012.vhdx –Path T:\lab50\lab50-PSDiffDiskVM\lab50-PSDiffDiskVM.vhdx -Differencing
For creating a differencing disk please refer to following link:
http://lyncdup.com/2012/06/creating-hyper-v-3-differencing-disks-in-server-2012-with-gui-and-powershell/
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How does one SUCCESSFULLY transfer Time-Machine backup to a new (larger) hard disk drive using OSX 10.5.8

I have read a number of articles about how to transfer a complete Time-Machine backup to a new (larger) hard disk-drive. Some of these articles are specifically for OSX10.6 users, which are not applicable to me since I am operating with OSX 10.5.8.
However, I have tried several times to use the Disk Utility 'Restore' function, dragging my old time-machine volume into the 'Source:' box and my new volume into the 'Destination:' box. This works, of sorts, BUT the newly created volume on the new larger hard disk-drive remains the same size as the original volume on the old Time-Machine HDD, with no apparent way of increasing the new volume's size. So I am not really any better off:
E.g. the total capacity of my new HDD is stated by 'Disk Utility' to be 465.8 GB, of which I'm told 228.2 GB is used for the Backups.backdb folder, but only 4.6 GB of free space is actually available. Yet under the 'Partition' tab of 'Disk Utility' it tells me that there is still 236.4 GB of available space.
Does anyone know how to resolve this issue without upgrading to OSX 10.6?

First, how did you prepare your new drive? See:
Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
If you plan to partition this new drive then be sure you create a larger partition for TM than your old volume.
Next, clone your old TM volume:
Clone using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4.Check the box labeled Erase destination.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.

The server encounter an error while attaching Virtual Hard Disk in Windows Server 2008R2

Unable to add an existing virtual hard disk in new VM(windows server 2008r2).

Please repost here:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverhyperv
And include the actual and full error message.

Virtual Hard Disks

i was add new hard disk in my VM and choose the parent is my old one but it overwrite on the basic Virtual Hard Disk and i lost all data i only have file .avhdx same size for the old Basic virtul hard disk .i need to back an recover my data can i use the
.avhdx file to recover my data? or how can i do that?
please urgent.

If you had an AVHDX, then you had a checkpoint / snapshot.
If this was the case, you should not edit the configuration directly, but instead mange checkpoints.
Simply attach to the correct AVHDX and you will see the data contained within the AVHDX.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

SCVMM 2012 RC - Unable to remove a VHD in the library because it has a dependency (Virtual Hard Disk deployment configuration)

When attempting to delete a VHD in the library, I am getting the below error message. Any thoughts on where I might look for the dependency "Virtual Hard Disk deployment configuration"?
Exact error message:
The library object (os_disk) cannot be removed because following objects are dependent on it:
Virtual Hard Disk deployment configuration
Please ensure that no objects are dependent on this library object and try the operation again.
ID: 848

On the final version (tested in 2012 SP1)
Suggest this instead of hacking around in the database:
You will receive a message that objects are dependent on the library object. Note the name that is listed after "VM Template"
Go to powershell in scvmm
Run:
remove-scvmtemplate -vmtemplate "NAME_YOU_RECORDED_FROM_ERROR"
Then, you can delete the template from SCVMM,
Wow Microsoft, Wow.

Help - The chain of virtual hard disks is corrupted

I took a snapshot of a VHD that I tried to expand to 40GB. After expanding I tried to restart the VM but got the error that "The Chain of virtual hard disks is corrupted".
Apparently because I expanded the Parent VHD it threw up this error ( i assume because the snapshot differed in size?)
This led me to Vhdtool which I ran: vhdtool.exe /repair parentvhdfile.vhd snapshotvhdfile.vhd /quiet
This appeared to have run okay. However when I went to restart the VM again I got the error:
Servername Failed to start
Microsoft emulated IDE controller failed to power on with error - the chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk.
Failed to open virtual disks. The size of the vurtua;l disk is not valid.
etc...
I notice that my parent VHD = 40GB in size, whilst the Snapshot (avhd) file = 109K
I think I need your help, I don't know what to do!!

If you made changes to the parent drive, your chain will be corrupted. Changes to the parent disk invalidate all the child disk.
Do you have a backup of the original parent disk?

New Virtual hard disk wizard hangs after creating new vhd from huper-v manager on windows 7

Similar Messages

Maybe you are looking for