Live Migration Failed After Yum Update on 2.2.2

Hi,
I've live migrated vm's from node2 to node1 (master server). Put node2 into maintenance mode, then reconfigure ntp.conf to sync with our new ntp server. While in maintenance mode, I've also ran yum update which updated the kernel from 2.6.18-128.2.1.4.37.el5xen to 2.6.18-128.2.1.4.44.el5xen. In the process, xen was also updated from 3.4.0-0.1.32.el5 to 3.4.0-0.1.39.el5.
After rebooting, I've put node2 back into active mode. But now I can't live migrate the vm's back into node 2. From node1, ovs_operations.log:
"2012-06-23 11:03:28" INFO=> migrate_vm: vm('/OVS/running_pool/1210_vm05') start...
"2012-06-23 11:03:29" INFO=> xen_migrate_vm: migrate with ssl enabled failed, do failover(no ssl). vm('/var/ovs/mount/54DA5753709A48B3BFAEE65C2EAECCE0/running_pool/1210_vm05') -> tgt_srv('node2')
"2012-06-23 11:03:30" ERROR=> xen_migrate_vm: failed. vm('/var/ovs/mount/54DA5753709A48B3BFAEE65C2EAECCE0/running_pool/1210_vm05') -> tgt_srv('node2') =><Exception: xen_migrate_vm: migrate without ssl failed either.>
From node2 ovs_operations.log:
"2012-06-23 11:03:30" INFO=> ha_join_dlm_domain: =>success
"2012-06-23 11:03:30" ERROR=> ha_set_dlm_lock:failed. lock('6f1cb211-ecef-4ac6-af2b-091fc6fd5966') name('1210_vm05')=> <Exception: create lock('/dlm/ovm/f1cb211ecef4ac6af2b091fc6fd5966') failed. <OSError: [Errno 26] Text file busy: '/dlm/ovm/f1cb211ecef4ac6af2b091fc6fd5966'>
Is this due to the different xen versions after the update? How can I live migrate the vm's back to node2 so that I can take node1 into maintenance mode to reconfigure ntp.conf and run yum update?
Thanks!

The next thing to try is to work though the steps in [[Error loading web sites]]. Though if this is happening on all of your computers it might have something to do with your internet connection. Maybe resetting that will help.

Similar Messages

Live Migration failed using virtual HBA's and Guest Clustering

Hi,
We have a Guest Cluster Configuration on top of an Hyper-V Cluster. We are using Windows 2012 and Fiber Channel shared storage.
The problem is regarding Live Migration. Some times when we move a virtual machine from node A to node B everything goes well but when we try to move back to node A Live Migration fails. What we can see is that when we move the VM from node A to B and Live
Migration completes successfully the virtual ports remain active on node A, so when we try to move back from B to A Live Migration fails because the virtual ports are already there.
This doesn't happen every time.
We have checked the zoning between Host Cluster Hyper-V and the SAN, the mapping between physical HBA's and the vSAN's on the Hyper-V and everything is ok.
Our doubt is, what is the best practice for zoning the vHBA on the VM's and our Fabric? We setup our zoning using an alias for the vHBA 1 and the two WWN (A and B) on the same object and an alias for the vHBA 2 and the correspondent WWN (A and B). Is it
better to create an alias for vHBA 1 -> A (with WWN A) and other alias for vHBA 1 -> B (with WWN B)?
The guest cluster VM's have 98GB of RAM each. Could it be a time out issue when Live Migration happen's and the virtual ports remain active on the source node? When everything goes well, the VM moves from node A with vHBA WWN A to node B and stays there
with vHBA WWN B. On the source node the virtual ports should be removed automatically when the Live Migration completes. And that is the issue... sometimes the virtual ports (WWN A) stay active on the source node and when we try to move back the VM Live Migration
fails.
I hope You may understand the issue.
Regards,
Carlos Monteiro.

Hi ,
Hope the following link may help.
To support live migration of virtual machines across Hyper-V hosts while maintaining Fibre Channel connectivity, two WWNs are configured for each virtual Fibre Channel adapter: Set A and Set B. Hyper-V automatically alternates between the Set A and Set B
WWN addresses during a live migration. This ensures that all LUNs are available on the destination host before the migration and that no downtime occurs during the migration.
Hyper-V Virtual Fibre Channel Overview
http://technet.microsoft.com/en-us/library/hh831413.aspx
More information:
Hyper-V Virtual Fibre Channel Troubleshooting Guide
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
Hyper-V Virtual Fibre Channel Design Guide
http://blogs.technet.com/b/privatecloud/archive/2013/07/23/hyper-v-virtual-fibre-channel-design-guide.aspx
Hyper-V virtual SAN
http://salworx.blogspot.co.uk/
Thanks.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SOLVED Key board and mouse fail after last update

Both my wireless keyboard and mouse failed after I updated yesterday. I'm using KNOPPIX to post they both work with knoppix so its not a hardware problem.
KDE 4.1
Logitech keyboard and mouse
Last edited by normc (2008-11-08 00:05:37)

Thanks a lot
Just want to add that I had to edit grub at start up and add "single" at the end of the kernel line.
The reason is that switching to runlevel 3 didn't work for me.

VM stays in Status Stopping after live migration failed/was canceled

I have a hyper-v Cluster running on Windows 2012 r2. I tried a live Migration from one node of Cluster to another node of the same Cluster. It got stuck by around 65% (if remembered correctly). After 45 minutes nothing has changed so I canceled the Job in
the Failover Cluster Manager. The VM went into a Status of "Stopping". After 5 hours it is still in Status "stopping". I haven't found any Information on why it got stuck on the 65% and have just found the error message that the Job got
canceled using Failover Cluster Manager events. But nothing saying why it stays in "Stopping" Status. Searched the Internet but I have Trouble finding anything related to the issue I see.
Any ideas?

Hi Saren90,
Please try to disable the process "vmwp.exe " corresponding to the VM in host's task manager.
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.

Server 2012 r2 live migration fails with hardware error

Hello all, we just upgraded one of our hyper v hosts from server 2012 to server 2012 r2; previously we had live replication setup between it and another box on the network which was also running server 2012. After installing server 2012 r2 when a live migration
is attempted we get the message:
"The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine. Virtual machine migration failed at migration source."
The servers in question are both dell, currently we have a poweredge r910 running server 2012 and a poweredge r900 running server 2012 r2. The section under processor for "migrate to a physical computer using a different processor" is already checked
and this same vm was successfully being live replicated before the upgrade to server 2012 r2. What would have changed around hardware requirements?
We are migrating from server 2012 on the poweredge r910 to server 2012 r2 on the poweredge r900. Also When I say this was an upgrade, we did a full re install and wiped out the installation of server 2012 and installed server 2012 r2, this was not an upgrade
installation.

The only cause I’ve seen so far is virtual switches being named differently. I do remember that one of our VMs didn’t move, but we simply bypassed this problem, using one-time backup (VeeamZIP, more specifically).
If it’s one-time operation you can use the same procedure for the VMs in question -> backup and restore them at new server.
Kind regards, Leonardo.

Live Migration Fails with error Synthetic FiberChannel Port: Failed to finish reserving resources on an VM using Windows Server 2012 R2 Hyper-V

Hi, I'm currently experiencing a problem with some VMs in a Hyper-V 2012 R2 failover cluster using Fiber Channel adapters with Virtual SAN configured on the hyper-v hosts.
I have read several articles about this issues like this ones:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baca348d-fb57-4d8f-978b-f1e7282f89a1/synthetic-fibrechannel-port-failed-to-start-reserving-resources-with-error-insufficient-system?forum=winserverhyperv
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
But haven't been able to fix my issue.
The Virtual SAN is configured on every hyper-v host node in the cluster. And every VM has 2 fiber channel adapters configured.
All the World Wide Names are configured both on the FC Switch as well as the FC SAN.
All the drivers for the FC Adapter in the Hyper-V Hosts have been updated to their latest versions.
The strange thing is that the issue is not affecting all of the VMs, some of the VMs with FC adapters configured are live migrating just fine, others are getting this error.
Quick migration works without problems.
We even tried removing and creating new FC Adapters on a VM with problems, we had to configure the switch and SAN with the new WWN names and all, but ended up having the same problem.
At first we thought is was related to the hosts, but since some VMs do work live migrating with FC adapters we tried migrating them on every host, everything worked well.
My guess is that it has to be something related to the VMs itself but I haven't been able to figure out what is it.
Any ideas on how to solve this is deeply appreciated.
Thank you!
Eduardo Rojas

Hi Eduardo,
How are things going ?
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.

Hyper-V live migration failed

There is Hyper-V cluster with 2 nodes. Windows Server 2012 R2 is used as operating system.
Trying to live migrate test VM from node 1 to node 2 and get error 21502:
Live migration of 'Virtual Machine test' failed.
'Virtual Machine test' failed to fixup network settings. Verify VM settings and update them as necessary.
VM has Network Adapter connected to Virtual switch. This vSwitch has Private network as connection type.
If I set virtual switch property to "Not connected" in Network Adapter settings of VM I get successful migration.
All VM's that are not connected to any private networks (virtual switches with private network connection type) can be live migrated without any issues.
Is there any official reference related to Hyper-V live migration of VM's that have "private network" connection type?

I can Live Migrate virtual machines with adapters on private switches without error. Aside from having the wrong name, the only way I can get it to fail is if I make the switch on one host use a different QoS minimum mode than the other and
enable QoS on the virtual adapter. Even then I get a different message than what you're getting. I only get that one with differently named switches.
There is a PowerShell cmdlet available to see why a guest won't run on another host.
Here's an example of its usage.
There's a way to use it to get it to Live Migrate.
But there is no way to truly Live Migrate three virtual machines in perfect lockstep. Even if you figure out whatever is preventing you from migrating these machines, there will still be periods during Live Migration where they can't communicate across that
private network. You also can't guarantee that all these guests will always be running on the same host without preventing Live Migration in the first place. This is why there really isn't anyone doing what you're trying to do. I suggest you consider another
isolation solution, like VLANs.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think."

Boot fails after security update

Greetings,
In installed the most recent security update this morning, and after restarting, my machine won't boot up.
I've followed the existing threads (in case you've also had this problem, the most informative was here:
http://discussions.apple.com/thread.jspa?threadID=1545171 )
Here's my machine's current state; I'd appreciate any input!
I booted to single user mode, and checked the disks using /sbin/fsck -fy . there were no errors reported.
I booted from my Install Disk 1, repaired the disk (again, no errors), and verified the disk.
Now, it still does not boot independently; it stalls at the apple logo. Safe boot does not work. It doesn't appear to be a PRAM or SMC issue.
What should my next move be? Thanks again!

There are no guarantees, but following this procedure when installing updates and upgrades on your Mac, or even re-installing them, will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO or security update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.10 to 10.4.11. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta. If Safari 3.1.1 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 3.0.4 (or worse still, version 2) when running 10.4.11 or 10.5 can have repercussions, as Safari 3.1.1 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely, and may entail you having to reinstall an earlier operating system.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
• /Library/InputManagers
• ~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).

Call fails after last update

Can anyone help me, after the last update from Apple to my iphone 3g I get call fail after call fail. It is getting embarassing at work where I rolled these phone out.

Standard troubleshooting is
1)Reset: reset your iPhone by pressing the home and sleep buttons until you see the Apple logo, ignoring the slider. Takes about 5-15 secs of button holding and you won't lose any data or settings.
2)Restore as new or from backup: see page 141 of the manual for details...http://manuals.info.apple.com/enUS/iPhone_UserGuide.pdf
Note the last sentence of the Restore paragraph... "In iTunes, you can also restore from a backup without deleting data stored on iPhone."
Message was edited by: paulcb

Hotsync fails after Microsoft update

I am using a Treo 650 (Sprint) and running WinXP Pro with Outlook 2002. Everything was working just fine until I got a message from Windows indicating that I needed to update Windows for a critical update. After the update I can no longer get my Treo 650 (Sprint) to connect for a hotsync. When I plug in the chord windows gives a recognition boop that new hardware have been detected; however, when I press the hotsysc button the hotsync fails indicating that it could not find the connection.
I have downloaded the latest software from Palm and installed it but that did not help.
Any help would be greatly apprecitated...
Post relates to: Treo 650 (Sprint)
Post relates to: Treo 650 (Sprint)
This question was solved.
View Solution.

You will need to do a "clean" uninstall of Palm Desktop. Here are the instructions.
You should first make a copy of your data to have just in case something
happens. You can find your data files by going to C:\Program Files\Palm or
Palm One. Highlight your Palm Desktop username and right click and copy.
Then go to your PC desktop, right click on a blank spot and select paste.
For Palm desktop 6.2, look in the following location for the folders and files, my documents, PalmOS desktop. You will find the username folder in this location.
Now you want to uninstall Palm Desktop and remove everything that has to do
with Palm Desktop from your computer. Like the above folder, delete the Palm folder. Once this is done, you will need to delete some registry keys
from your PC Operating System registry.
Word of warning, going here and deleting the wrong thing can cause your PC
to not start up, crashing and deletion of programs and data. If you feel
you are unsure of yourself, see if you have a friend that can help you or a
PC technician that you can pay to help you. This will show them everything
they need to delete. To retain your current Registry settings, we need to do a backup of the Registry.
On the PC, go to start and run type "regedit" without quotes
Highlight MY COMPUTER, go to File --> export. Should pop up with a Save As
box. Current location is fine should be in My Documents or you can change to a location you will remember. In the file name box, type "Regbackup[todaysdate]" i.e. Regbackup07072008. Next, the hard part.
The easiest way to make sure your working with the correct key, highlight the key i.e. palm quick install, and press delete on your keyboard. It will ask you, are
you sure. Say yes. Do the same thing for all keys below.
If you make a mistake, stop what you are doing. And call a PC technician.
BUT do not turn off your computer.
The reg keys are as follows (Note: some of theses reg keys will not be here
but if they are delete them)
* HKEY_CURRENT_USER\Software\U.S. Robotics\Palm Quick Install
* HKEY_CURRENT_USER\Software\U.S. Robotics\PalmOne File Transfer
* HKEY_CURRENT_USER\Software\U.S. Robotics\Pilot Desktop
* HKEY_CURRENT_USER\Software\Palm
* HKEY_CURRENT_USER\Software\Palm, Inc.
* HKEY_CURRENT_USER\Software\PalmDesktopAutorun
* HKEY_CURRENT_USER\Software\palmOne
* HKEY_CURRENT_USER\Software\PalmSource
* HKEY_LOCAL_MACHINE\Software\PalmSource or anything else that says palm
Next reboot your computer
Then reinstall your Palm desktop from the CD and do a hotsync. If it asks
you for a username and you synced your device before, put in 'test" if you
did not sync before you create a hotsync name.
For reference purposes, click on the following link for the support page for your device on the kb.palm.com webpage
http://kb.palm.com/SRVS/NUA/launchTab.asp?t=home&fn=treo&mn=650&cn=sprint
There are links on the page to the user guide, troubleshooting, how to's, downloads, etc.
Post relates to: Palm i705

Live Migration - Failed to establish a connection because of an unsupported protocol version (protocol version 5.0)

I'm getting a not the disk and everything) back to the host I originally had it on. Here is my setup:
Host 1 - Microsoft Storage Server 2012 Standard (NAS)
Host 2 - Microsoft Hyper-V Server 2012 (All connected virtual hard drives use the SMB 3.0 protocol to connect to the NAS - Host 1)
Delegation is setup on both of these hosts to include:
-Trust this computer, Use Kerberos only, Services - cifs, Hyper-V Replication, Microsoft Virtual Console Service, Microsoft Virtual System Migration Service
Live Migration is setup on both of these hosts to include:
-Enable incoming and outgoing live migrations using Kerberos
-Use any available network for live migration
I was able to migrate the VM from host 1 to host 2 with no problems. But when I try to migrate the VM host 1 that's when I encounter the error.
I saw a KB article similar to the issue I'm having but it only effects Server 2008 R2 (KB2705759)
I've rebooted both hosts but still get the error. The VM that is on host 2 has it's hard drive on host 1 run's fine so there are no connection issues there.
I've searched the Internet for this issue and keep coming up empty handed. I even named the virtual switch on both hosts the same to see if that would work. Please help! I'd rather not do an export and import of the VM because I'm evaluating
this product so I want to make sure it works before I put it into production.

Hi PPlbrad,
Agree with Shabarinath .
We can just live migration the VM from low version (2012) to high version (2012R2) but the reverse is not ture .
So do hyper-v replica (just for updating )
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.

Mac App Store Connection Failed After Mavericks Update

Hi y'all,
immediately after I updated my Lion to Mavericks (10.9.1), I could not access no more Mac App Store: as I enter my (valid and active) Apple ID credentials, I receive a "Connection Failed" message (in red, in the same login dialog, under the user id field).
So I've tried to set to "Always Trust" all of my Class 3 Certificates in my Keychain, I removed all of the Mac Appstore plist files (appstore and storeagent), I've also tried to remove the network preferences plist file to reset my network interfaces preferences, I've also deleted the ocsp and crls cache files, and I've setup the ocsp and crls certificates preferences in my Keychain Access to off.
I obviously checked out my App Store account and it's correct and active - I'm also currently using it on my iPhone, iPad and iPod with no problem at all!
Anyway I wanted to try creating a new App Store account from the Mac AppStore itself: after I validated it, I tried to login into Mac AppStore... with no success!
So, NONE of the above mentioned attempts solved the problem, and I'm WORRIED and astonished wondering HOW APPLE COULD RELEASE A MAJOR O.S. UPDATE THAT SMASHES THE MAC APP STORE, WHICH IS ONE OF THE CORE APPS OF THIS O.S.!!! I use Mac OSes since many years and I never had O.S. problems (only some minor issue with third party applications out of Apple's scope and solved with some simple workaround).
CAN ANYBODY PLEASE HELP ME? :-)
THX IN ADVANCE,
DANI

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Migration/Live Migration fails with shared storage (SMB), but not all the time

I have 2 Hyper-V Hosts using shared storage via SMB. I'm having intermittent issues with migrations failing. It'll either go through the motions of doing the whole move and fail and/or when I try to start it again I get the following:
I've done a lot of reading on this and have done various things that have been recommended. For each Hyper-V host I've setup delagation via Kerberos. ie. HV_Host1 has CIFS - HV_Host2; CIFS - SMB Server; MS Virtual System Migration Service - HV_Host2 and
vice versa.
On the actual SMB share on the Shared Storage server I added permissions to the folder for HV_Host1, HV_Host2, Storage Server, Domain Admins and my user account for full access.
In Group Policy, I've blocked Inheritance for the OU containing the Hyper-V hosts, though I have added some of the Group Policy's manually that I needed.
Last thing, I also added Domain Admins to the Local GP on each Host for "Log on as a Service" and "Impersonate a client after authentication" as shown in this thread: http://social.technet.microsoft.com/forums/windowsserver/en-US/7e6b9b1b-e5b1-4e9e-a1f3-2ce72ea1e543/unable-to-migrate-create-vm-hyperv-cluster-2012-logon-failure-have-to-restart-the-hyperv
I get these failed migrations regardless if I start them on the actual Host or via the admin console from Win8.
At this point I'm not sure what else to check or the next step to take for this.

Hi Granite,
Please refer to following article to build hyper-v over SMB :
http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3
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.

Live Migration Failed while Quick Migration is Ok...Virtual machine with synthetic FC HBA !

When I migration the virtual machine with synthetic FC HBA in windows server 2012 R2 Cluster,it fails
but I do it in the style of quick migraton ,it secceed!
The error event here
Live migration of 'Virtual Machine PTSCSQL01' failed.
Virtual machine migration operation for 'PTSCSQL01' failed at migration destination 'PTCLS0106'. (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
'PTSCSQL01' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
'PTSCSQL01' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
My virtual machine's synthetic FC HBA setting here
做微软的先行者，享受用户体验

Yes, definitely check your zoning/masking. Remember that with vHBA you have twice as many WWPNs to account for. Performing a live migration makes use of both pairs during the transfer from one host to the other - one set is active on the machine
currently running and the second set is used to ensure connectivity on the destination. So if you are using Address Set A on Host1, Host2 will try to set up the fibre channel connection using Address Set B. If you do a quick migration, you would
continue to use the same Address Set on the second host. That's why you most likely need to check your zoning/masking for the alternate set.
. : | : . : | : . tim

[SOLVED] GTK applications failing after latest update

Several GTK applications are failing after the latest updates.
So far, I have found Bleachbit and Gtkpacman are crashing, but there may be more.
They all give the same error messages (obviously, the application name/line number in the first line varies):
File "/usr/bin/bleachbit", line 41, in <module>
import gtk
File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module>
from gtk import _gtk
ImportError: /usr/lib/python2.7/site-packages/gtk-2.0/gtk/_gtk.so: undefined symbol: gtk_combo_box_set_entry_text_column
How do I fix this?
Many thanks in advance.
Last edited by myrlin (2011-05-07 10:17:03)

How do you manage to reply to my problems before I've finished typing, Wonder??
VERY many thanks once again.
pacman -Q pygtk gtk2 give different versions, as I haven't yet been able to fix my previous problem with Firefox 3.6 (machine in constant use), so I guess that's the problem.
Thank you SO much for your help, support and patience.

Live Migration Failed After Yum Update on 2.2.2

Similar Messages

Maybe you are looking for