Cannot start any VM (new or using existing VHD) after installing Hyper-V RC0
After installing RC0 on my W2008 Ent x64 RTM, I cannot start any VM.
I deleted all old VM's, snapshots, virtual networks etc etc, as decribed on this forum. Created a new VM and linked it to the extisting VHD, etc etc. but I cannot start any VM.
I created a complete new VM and I get the same eror when I try to start it.
How can I solve this problem, or un-install hyper-v RC0.
I get the following error when I start the VM (named Vista), and it is at 50%:
An error occurred while attempting to change the state of virtual machine Vista.
'Vista' failed to start
Microsoft Synthetic Ethernet Port (Instance ID
{9C5C0CF3-827C-4DB0-.....}): Failed to
Power On with Error 'The specified network resource or device is
no longer available.'
'Vista' failed to start. (VMID
C5E8C74F-85B4-4A5E.....)
My hardware Setup;
MB Asus DSEB-DG (with 4 onboard network adapters, 1 in use, 3 disabled)2x Xeon 5420 quad core
16GB Ram
Highpoint Rocketraid 3520 Raid 5 SATA
Answers
I think I found the problem:
After installing Officescan antivirus from Trendmicro, I got the same problem as in the first posting:
Microsoft Synthetic Ethernet Port (Instance ID
{9C5C0CF3-827C-4DB0-.....}): Failed to
Power On with Error 'The specified network resource or device is
no longer available.'
and the VM I tried to start was deleted from Hyper-V manager.
After un-installing Trendmicro, I suddenly can start VM's, new and existing VM's. Also I did not get the error about not finding a usable certificate anymore.
Looks like Hyper-V is working again, only now I have to findout why Hyper-V RC0 and Trendmicro are causing problemen. With the previous version of Hyper-V I did not have this problem.
Trendmicro officescan is also installed on all my VM's and working without any problems.
When you try, can you also try with the firewall of Trend disabled. In the past I had serious problems with all my W2003 servers in a domain after upgrading to the latest version of Trend. After disabling Trend's firewall these problems were solved.
With TrendNicro Officescan; Exclude the Virtual Server Configuration directory from RealTime scanning and this fixes the problem
All Replies
Similar problem here....
I got it to work again:
- recreate the virtual network, adopt the IP settings etc again
- I also found from event logs that the local "Network Service" had no access to the folder where the virtual machine configs where stored
After above two, everything worked again
Would have been nice if that ws in the instalation instructions of RC ...
Good luck
Unfortunately this did not solve my problem.
I still get the same error.
What I noticed: When I get the error msg. the VM state in Hyper-V is 'Starting' but when I close the Hyper-V manager, and re-open it, the VM is not in the list anymore. When I check the harddisk, I still see the VHD file, and the virtual machine config files.
Microsoft should provided better installation instructions!
Now I cannot use Hyper-V at all, I can't even un-install RC0 and use the version supplied with w2008 RTM :-(
edit:
In the Application event log I see the following error:
Faulting application vmwp.exe, version 6.0.6001.18004, time stamp 0x47db830c, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x0000000003493a80, process id 0xa34, application start time 0x01c897d53eb52b09.
In the Server Roles Custom Event Viewer I see error:
The description for Event ID 19060 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Vista
1DA1E845-E6F0-445A-A467-64475512A7F2
%%3222072877
0xC00CEE2D
The locale specific resource for the desired message is not present
'Vista' Microsoft Synthetic Ethernet Port (Instance ID {A81D8109-8DF6-4945-83B7-21434F9C40A0}): Failed to Power On with Error 'The specified network resource or device is no longer available.' (0x80070037). (VMID 1DA1E845-E6F0-445A-A467-64475512A7F2)
Latest update:
I did a complete new installation of W2008 Ent 64bit.
Installed the Hyper-V role, and installated RC0. (rebooted the machine everytime when requested).
Now when I try to start a new VM or a VM linked to an existing VHD, I get the following error:
An error occured while attempting to change the stat of Virtual Machine Vista.
Failed to initialize machine remoting system. Error: 'Unspecified error' (0x80004005).
Failed to find usable certificate. Error. 'Unspecified error' (0x80004005).
'Vista' failed to initialize. (VMID 9D761........)
'Vista' failed to initialize machine remoting system. Error: 'Unspecified error' (0x80004005). (VMID 9D761........)
'Vista' failed to find a usable certificate. Error: 'Unspecified error' (0x80004005). (VMID 9D761........)
I think I found the problem:
After installing Officescan antivirus from Trendmicro, I got the same problem as in the first posting:
Microsoft Synthetic Ethernet Port (Instance ID
{9C5C0CF3-827C-4DB0-.....}): Failed to
Power On with Error 'The specified network resource or device is
no longer available.'
and the VM I tried to start was deleted from Hyper-V manager.
After un-installing Trendmicro, I suddenly can start VM's, new and existing VM's. Also I did not get the error about not finding a usable certificate anymore.
Looks like Hyper-V is working again, only now I have to findout why Hyper-V RC0 and Trendmicro are causing problemen. With the previous version of Hyper-V I did not have this problem.
Trendmicro officescan is also installed on all my VM's and working without any problems.
- Did you have installed rc0 update on the Hyper-V console machine too ?
I installed RC0 on the host. I do not have a seperate console computer.
As soon as I install Trendmicro officescan on the host I cannot start any VM anymore, and the VM is deleted from the Hyper-V manager (the VM still exists on disk) when I try to start it.
Trendmicro does however run without any problems on the VM's.
I have noticed this as well. If trend is installed on the Host i can not create any VM with a network attached to it. If i have no NIC attached the VM is created but fails to start. If I stop the Trend service i can create machines with NIC just fine but need to start the machine one time with the Trend Service off. After that the client machine will run fine with Trend running.
I was thinking of adding some of the hyper V files in the exclusion list. havent had a chance to try it.
When you try, can you also try with the firewall of Trend disabled. In the past I had serious problems with all my W2003 servers in a domain after upgrading to the latest version of Trend. After disabling Trend's firewall these problems were solved.
- We are using Microsoft's Forefront for our antivirus solution on Windows 2008 and I can verify that it causes the exact same issue azs Trend Micro. Once I disable the Forefront services, I am able to open up the VM's again. I did find that if you do not assign a network to the VM, the machine will also start without issue. At least with Forefront is does.
As soon as I have Trendmicro installed and running, I cannot start any VM, even not if there is no network assigned to the VM.
If I do try to start a VM it failes at 50% and the VM is deleted from the Hyper-V manager.
The registry patch provided by Microsoft for Forefront is not valid for Trendmicro:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MpFilter\Parameters]
"ScanOnCleanup"=dword:00000000
With TrendNicro Officescan; Exclude the Virtual Server Configuration directory from RealTime scanning and this fixes the problem- @BruiserB, Thank you! This solved my problem.
- Thanks BruiserB. This also resolved the exact same issue using Microsoft Forefront virus protection client.
- Big Thanks BruiserB.
This is what I did:
Logged on to the TrendMicro OfficeScan management console.
Networked Computers > Client Management > (note you can select a specific client computer here if you do not wish to exclude this directory from all desktops. Just browse for the desktop in question and then click Settigns button) Settings button > Real Time Scan Settings
Add directory exclusion. In my case I added in C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines.
Snusmumriken- Proposed As Answer byGavin Walker Wednesday, August 05, 2009 1:12 AM
- BruiserB,
Thanks so much for your solution. It has fixed my problem!
I have been working so hard on the same problem during my July 4th weekend. Now, I feel better!
Joy - Hi , I also get this problem, at last , I uninstall Trend Micro officescan ,and the Hyper-v works well, so i think trendmicro cause this. If you install TrendMicro on windows2008 hyper-v , don't forget to do a exception on RealTime scan of Trend.
- Snusmumriken, great post. Since I was storing my virtual hard drives in an alternate location, I also had to exclude files with an extension of .VHD. Now I have all these virtual machines that won't start and won't delete that I created while trying to figure this issue out. Anyone know how to manually delete out these virtual machines that failed to start?
- You need to take over ownership of the folder, and all files and subfolders, each VM is in.
Then you can set your permissions to full control, also for files and folders.
You do this using the Advanced button of the Security tab of the folder properties. - Guys, I am experiencing the same problem here.
1. A happily running set of VM's are running with SnapShots, let me repeat that...WITH VALUABLE SNAPSHOTS.
2. The VM's immediately stop after creating a SnapShot.
3. You go to the Hyper-V console and look at the VM's.....POOF! PRESTO! WHAMOZAMO! ALACAZAM! The VM's are completely vanished from the list!
4. SnapShots and any unsaved work is lost and apparantly unrecoverable. VM must be re-created and hope the VHD mounts.
Has anyone actually recovered the snapshots when this ridiculous "recovery" method takes place?
Why is Hyper-V so bloody inept and useless when this happens? I've seen VM's dissappear from the console before with no apparant reason. This needs to be fixed big time! HORRIBLE user experience! Especially when you have VMWare ESX servers that don't do this. At least when their VM's break THEY ARE STILL IN THE FREAKIN LIST, Microsoft!
I would think there should be a way to recover ALL the data. Nothing is actually wrong with the files!!!! Here's the little WARNING, not ERROR, but WARNING in the event log below. You would think it would send off a giant flare stating VM DOWN, VM DAMAGED, VM GO BYE-BYE instead of this lame warning error. Great creativity with "Event 1" Yeah I give it a #1 myself!
Also, this is on the current release of Hyper-V, not R2.
Thanks.
-Lee
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Log Name: System
Source: vhdparser
Date: 8/5/2009 4:00:09 PM
Event ID: 1
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: IC14-HyperVLab2.AtHoc.com
Description:
The parent virtual hard disk appears to have been modified without using the differencing virtual hard disk located at "...\\v-QA2k8MSIx86_CF674C1A-D88D-41A7-B82A-930E4DAF0F7D.avhd". Modifying the parent virtual hard disk may result in data corruption. It is strongly recommended that you lock the parent virtual hard disk to prevent this in the future. If you recently changed time zones on your computer, you can safely continue using this virtual hard disk.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="vhdparser" />
<EventID Qualifiers="32773">1</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-08-05T23:00:09.767Z" />
<EventRecordID>38308</EventRecordID>
<Channel>System</Channel>
<Computer>HostComputerName</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>...\\v-QA2k8MSIx86_CF674C1A-D88D-41A7-B82A-930E4DAF0F7D.avhd</Data>
<Binary>00000000020030000000000001000580000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Technology Enthusiast
