Error 13206
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums scvmm 2012 r2 error 13206 Answered by: Error (13206) Virtual Machine Manager cannot locate
Error (13206) Virtual Machine Manager Cannot Locate The Boot Or System Volume
the boot or system volume. System Center - Virtual Machine Manager > Virtual Machine Manager – Hyper-V Question 0 Sign in to vote Hello, I am trying to build a new virtual machine unattendedly , using a SCVVM template. I have put an ISO (Server 2003 CD) and a blank VHD in the library and attached them to the template, and selected the CD as the first boot device. The job gets 42% through and gives the error: "Error (13206) Virtual Machine Manager cannot locate the boot or system volume on virtual machine Terminal Server Test. The resulting virtual machine might not start or operate properly. " If you start the VM in Hyper-V manager then the VM starts and boots from the CD. Any help would be much appreciated. Monday, November 09, 2009 9:06 AM Reply | Quote Answers 0 Sign in to vote Isn't it the one like yours: http://social.technet.microsoft.com/Forums/en-US/virtualmachinemanager/thread/071a3f42-5fa0-42a8-a0af-ced8f5b94161/ ? --- Paul Svirin StarWind Software developer ( http://www.starwindsoftware.com ) Marked as answer by Carmen SummersMicrosoft employee Tuesday, March 30, 2010 12:57 AM Tuesday, November 10, 2009 10:53 PM Reply | Quote All replies 0 Sign in to vote Hiya, Is your boot disk using IDE controller?It wont work if you got your boot disk on a SCSI controller. Tuesday, November 10, 2009 2:39 PM Reply | Quote 0 Sign in to vote Isn't it the one like yours: http://social.technet.microsoft.com/Forums/en-U
21, 20084 0 0 0 When creating a new VM from scratch with a blank VHD or a VHD with a non-Windows OS, you will get the warning (VMM does peak inside the VHD as part of the creation process to determine this). This warning can be ignored. To have the VM autostart after completion, make sure the ‘Start the VM after deploying…’ checkbox is check at the end of the wizard: When creating a new VM from template, and that template contains a blank VHD or a non-Windows OS or a Windows OS that has not been generalized (i.e. the OS is not sysprepped), then the job will fail because VMM expects https://social.technet.microsoft.com/Forums/systemcenter/en-US/e3fb766f-5592-4263-a429-0cc5b89c0685/error-13206-virtual-machine-manager-cannot-locate-the-boot-or-system-volume?forum=virtualmachingmgrhyperv a VM from template to go through the sysprep customization process (hence why we ask for an OS profile). VMM will crack open the VHD and check of the OS is in a sysprep state. If not, then the job will fail. To create a proper template, you can use an existing Vm with a running Windows OS (right click on it and select New Template… this will kick off sysprep in the OS and then store the VM to Library as template… https://blogs.technet.microsoft.com/hectorl/2008/08/21/digging-deeper-into-error-13206-virtual-machine-manager-cannot-locate-the-boot-or-system-volume-on-virtual-machine/ this removes the original VM). Or… if you already have VHDs that have been sysprepped, simply import them to the Library and then when you create a new template… attach that VHD instead of the blank one. Last… you can create a new template that does not require a sysprepped OS by selecting ‘Customization Not Required’ from the Guest OS profile dropdown: Keep in mind that of the VHD is blank or contains a non-Windows OS, it will complete with the same warning. Below are the job views to confirm that we are on the same page New VM from blank VHD (warning) New VM from template from a blank VHD (error) New Vm from template from blank VHD with ‘Customization Not Required’ (warning)
Comments (4) Cancel reply Name * Email * Website Anonymous says: October 10, 2016 at 10:19 am Hi, Just to let you know: I got this error message while creating a template from a Windows 7 VM (beta, build 7000). I assume VMM cannot deal with this new type of OS. Reply Jeff Bryant - Avanade says: October 10, 2016 at 10:19 am While this only creates a warning, it does take to long for VMM to get past the step of trying to install the VM components. If it does peak into the VHD and not see any OS, then it should move on and not hang for 5 minutes or more. RStart here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://serverfault.com/questions/718902/scvmm-error-13206-failed-to-install-vm-components more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SCVMM Error 13206 Failed to Install VM components up vote 0 down vote error 13206 favorite I'm running a MS Windows Failover Cluster with 4 nodes and one SCVMM host. All servers have the latest update of Windows Server 2012 R2. What I'm trying to do is create some virtual machines on the SCVMM Host and then migrate them onto the cluster and vice versa. The problem occurs every single time when migrating to or from Node 4. If I create 4 VMs and migrate them to the 4 nodes, 3 complete scvmm 2012 r2 successfully and the 4th one fails. The only difference I noticed is one extra step introduced when working with Node 4. The step is Install VM components. Successful migration to all other nodes: Move virtual machine VM-3 from VMMHost to Node-3 using SAN Run pre checks for transfer Change virtual machine status Export Hyper-V virtual machine Deploy file (using LAN) Deploy file (using LAN) Deploy file (using SAN transfer) Import Hyper-V virtual machine Remove virtual machine Failed migration with the extra step to Node 4: Move virtual machine VM-4 from VMMHost to Node-4 using SAN Run pre checks for transfer Change virtual machine status Export Hyper-V virtual machine Deploy file (using LAN) Deploy file (using LAN) Deploy file (using SAN transfer) Import Hyper-V virtual machine Remove virtual machine Install VM components The same step occurs even when I attempt the process with 8 VMs instead of 4. Any other number (1,2,3) of VMs does not encounter the additional step. The issue also occurs when migrating from cluster to host with the same error on the same VM and the same Node. This is the error shown by VMM: Error (13206) Virtual Machine Manager cannot locate the boot or system volume on virtual machine VM-4. The resulting virtual machine might not start or operate properly. I checked the Roles and Features on all the nodes and they are the same. Also