javajo
asked on
Hyper-V VMs are pausing due to critical errors - might be snapshot problem??
Good morning -
Have a Server 2008 Datacenter ed. Hyper-V server with 10vms running on it.
Plenty of RAM Plenty of CPU..
Imported VHD files over from Virtual Server 2005 R2 into Hyper-V
Vm files along with VHD files are located on iscsi luns mounted inside folders.
For example:
C:\vm\vm01
C:\vm\vm02
C:\vm\vm03
each vm folder points to an iscsi LUN created on a NETAPP SAN.
My typical process for creating a new VM is this:
Create volume on SAN
Create iscsi LUN that points to volume on Hyper-V server
Create new VM pointing all VM files to the iscsi directory.
I had been creating snapshots of all my vms up until recently...
Some of my vms started to pause because of disk space errors
I have since deleted all snapshots.
This weekend i had a vm pause on me...the only way to get it back online again was to copy it's .vhd file to a different folder\iscsi location - then point the paused vm to the new vhd file.
This solved problem.
The only thing is I'm not sure what the issue was...
There was plenty of space on the volume and virtual disk.
I'm looking at the logs this morning and I'm finding these errors:
Log Name: Microsoft-Windows-Hyper-V- VMMS-Admin
Source: Microsoft-Windows-Hyper-V- VMMS
Date: 2/9/2009 10:55:08 AM
Event ID: 14250
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: mkpnycvs01.mkpcap.com
Description:
Cannot find the specified snapshot. (Snapshot ID A801476B-9119-4231-B0FE-2C 7E2AF2CCCE )
and this one
Log Name: System
Source: vhdparser
Date: 2/7/2009 6:29:39 PM
Event ID: 1
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: mkpnycvs01.mkpcap.com
Description:
The parent virtual hard disk appears to have been modified without using the differencing virtual hard disk located at "...\\3AFC8912-960A-4C53-9 3E9-48282E B1F05C\vm1 0_C77E54CC -01FC-4CBE -8E84-715B 69322DFE.a vhd". 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.
Any ideas?
Are there any known issues with importing vhd files from VS 2005?
Have a Server 2008 Datacenter ed. Hyper-V server with 10vms running on it.
Plenty of RAM Plenty of CPU..
Imported VHD files over from Virtual Server 2005 R2 into Hyper-V
Vm files along with VHD files are located on iscsi luns mounted inside folders.
For example:
C:\vm\vm01
C:\vm\vm02
C:\vm\vm03
each vm folder points to an iscsi LUN created on a NETAPP SAN.
My typical process for creating a new VM is this:
Create volume on SAN
Create iscsi LUN that points to volume on Hyper-V server
Create new VM pointing all VM files to the iscsi directory.
I had been creating snapshots of all my vms up until recently...
Some of my vms started to pause because of disk space errors
I have since deleted all snapshots.
This weekend i had a vm pause on me...the only way to get it back online again was to copy it's .vhd file to a different folder\iscsi location - then point the paused vm to the new vhd file.
This solved problem.
The only thing is I'm not sure what the issue was...
There was plenty of space on the volume and virtual disk.
I'm looking at the logs this morning and I'm finding these errors:
Log Name: Microsoft-Windows-Hyper-V-
Source: Microsoft-Windows-Hyper-V-
Date: 2/9/2009 10:55:08 AM
Event ID: 14250
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: mkpnycvs01.mkpcap.com
Description:
Cannot find the specified snapshot. (Snapshot ID A801476B-9119-4231-B0FE-2C
and this one
Log Name: System
Source: vhdparser
Date: 2/7/2009 6:29:39 PM
Event ID: 1
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: mkpnycvs01.mkpcap.com
Description:
The parent virtual hard disk appears to have been modified without using the differencing virtual hard disk located at "...\\3AFC8912-960A-4C53-9
Any ideas?
Are there any known issues with importing vhd files from VS 2005?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i just realized something...
Being a newbie to Hyper V i forgot to create an internal network so my VMs can talk to my Host machine...I'm also getting alot of w32 time errors.
Could this be my problem?
Being a newbie to Hyper V i forgot to create an internal network so my VMs can talk to my Host machine...I'm also getting alot of w32 time errors.
Could this be my problem?
ASKER
scratch that - i have an external network and that should be all i need...
Depending on the role that the VMs have, it is a good idea to uncheck the Time Synchronization under the Integration Services section for your VM.
Be default, we disable this feature for any domain joined VM since the VM will be receiving its time updates from the DCs on the domain.
Philip
Be default, we disable this feature for any domain joined VM since the VM will be receiving its time updates from the DCs on the domain.
Philip
ASKER
thank u all for your help.
The issue was that the LUNS were not big enough to hold all the VM info...
Couldn't see the forest through through the trees...
The issue was that the LUNS were not big enough to hold all the VM info...
Couldn't see the forest through through the trees...
In your VM manager, do you see references to the old snapshots that are now gone?
Philip