Users must reboot after live migration

Has anyone had trouble with users needing to reboot after a server is live migrated? I migrate a virtual server from one node to the other the users cannot connect until they reboot. This does not seem right to me. Any help?
This topic first appeared in the Spiceworks Community

I'm creating a visual basic application and I am getting super confused by this bit of code.It keeps returning a 404 error at "Dim reader = client.DownloadString("http://themeq.xyz/other-domain/poro/api/communicator.php?i=c&p="; & todo)", but I know the website works and exists. Can anyone see what I am doing wrong, it doesn't work with or without a proxy.VB.netx = "http://www.google.co.uk"VB.netTry proxy = client.Proxy Dim proxyuri = proxy.GetProxy(New Uri("http://www.google.co.uk")).ToString client.UseDefaultCredentials = True client.Proxy = New WebProxy(proxyuri, False) client.Proxy.Credentials = System.Net.CredentialCache.DefaultCredentials Dim nbyt As Byte() = Encoding.UTF8.GetBytes(x) Dim todo = Convert.ToBase64String(nbyt) Dim reader = client.DownloadString("http://themeq.xyz/other-domain/poro/api/communicator.php?i=c&p=" & todo...

Similar Messages

RDS 2012 re-connection after live migration.

Is there a way to speed up the re-connection after a live migration?
So if i am in a vm that live migrates it feels like it hangs for about 10 seconds the reconnects and is fine..... While this is OK its not ideal. Is there a way to improve this?

Actually 10 seconds sounds like a very long time to me. In my experience using Shared Nothing Live Migration I've seen the switch being almost instantaneous, with a continual ping possibly dropping one or two packets, and certainly quick enough that it's
unlikely any users would notice the change. So in terms of whether it can be improved I'd say yes.
As you can see from the technical overview here
http://technet.microsoft.com/en-us/library/hh831435.aspx the final step is for a signal to be sent to the switch informing it of the new MAC address of the servers new destination, so I wonder if the slow switch over might be connected to that, or perhaps
some other network issue.
Is the network connection poor between the servers which might cause a delay during the final sync of changes between the server copies? Are you moving between subnets?

VM windows 2008 Cluster on Hyperv 2012 Server FC Disk error after Live Migration of the active VM Cluster Node

Deployed a 2 nodes Windows 2008 R2 SP1 Failover Cluster on a HyperV 2012 Server cluster deployed on IBM HS23 blade.
Disk susbsystem is IBM Storwize V7000. MPIO driver installed plus IBM DDSM.
Lun presented to the VM are connected with Virtual FC Adapter and everything works fine in the cluster until we start a live migration of the VM which hold the cluster disks online.
After migration complete positively, at the moment the MPIO of the migrated VM goes crazy with a lot of errors (source: mpio eventID 16 ) and warnings (source: mpio EventID: 17) in the system event log. After that the disks becomes unavailable.
Consequently everything hangs until power off the migrated vm, so the services on the cluster switchs on the second node.
I try to set the registry key HKLM\CurrentControlSet\Services\Disk\TimeOutValue to 190 as i found on various articles but nothing seems to change....
Any idea?
vannig

Hello,
I've just been through the IBM interoperability matrix and came across this statement:
Hyper-V on x64 based systems is supported with the following guest OS: Windows 2003 32bit, Windows 2003 64bit, Windows 2008 32bit, Windows 2008 64bit.
Clustering of guest OS is not supported at this time. When using Emulex HBAs with Hyper-V please select the settings mentioned in the Host Attachment section of SVC Info Center
http://publib.boulder.ibm.com/infocenter/svc/ic/index.jsp
Thanks

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.

Failover Cluster 2008 R2 - VM lose connectivity after live migration

Hello,
I have a Failover Cluster with 3 server nodes running. I have 2 VMs running in one the the host without problems, but when I do a live migration of the VM to another host the VM lose network connectivity, for example if I leave a ping running, the ping command
has 2 response, and 3 packets lost, then 1 response again, then 4 packets lost again, and so on... If I live migrate the VM to the original host, everything goes OK again.
The same bihavior is for the 2 VMs, but I do a test with a new VM and with that new VM everything Works fine, I can live migrate it to every host.
Any advice?
Cristian L Ruiz

Hi Cristian Ruiz,
What your current host nic settings now, from you description it seems you are using the incorrect network nic design. If you are using iSCSI storage it need use the dedicate
network in cluster.
If your NIC teaming is iconfigured in switch independent + dynamic, please try to disable VMQ on VM Setting for narrow down the issue area.
More information:
VMQ Deep Dive, 1 of 3
http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-1-of-3.aspx
I’m glad to be of help to you!
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!
thank you for your reply!
Yes, We are using iSCSI storage, but it has its own NICs for that (2 independant NIcs just to connect the server with the storage) and they are configured to not use those NICs to cluster communication. The team configuration is just for the LAN connectivity.
The NIC teaming is configured using BACS4 software from a DELL server and in Smart Load Balancing and Failover (as you can see here
http://www.micronova.com.ar/cap01.jpg). The link you passed is for Windows Server 2012 and we are running Windows Server 2008 R2, BUT as you can see in the following capture the NICs has that feature disabled
( http://www.micronova.com.ar/cap02.jpg ).
One test that I'm thinking to do is to remove teaming configuration and test just with one independant NIC for LAN connection. But, I do not know if you think another choice.
Thanks in advance.
Cristian L Ruiz
Sorry, another choice I'm thinking too is to update the driver versión. But the server is in production and I need to take a downtime window for test that.
Cristian L Ruiz

Change Tracking has been marked inconsistent after live migration

We run a 3 node Server 2012 R2 cluster and backup using DPM 2012 R2
Everytime a VM is live migrated to another node, when DPM next tries to back it up, the recovery point fails with the "Change Tracking has been marked inconsistent" error and a consistency check needs to be done.
This is fine if one VM is Live Migrated but when we have to put a host in Maintenance mode for some reason and 50 VM's need to be migrated off, it them means 50 consistency checks and our backups go from 2 hours to 8 hours.
Is there a way around this or is this just the way DPM works?
Simon Holman
Expeed Technology
Australian Web Hosting

Hi,
<snip>
please give this on a try: http://support.microsoft.com/kb/2848751
>snip<
Please DO NOT add the forcefixup key - that will make EVERY recovery point use consistency check workflow under the covers - so we basically abandon using the dpmfilter to track block level changes.
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. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Outlook Users connection issues after Mailbox Migration from 2007 to 2013

Hi,
We have a coexistance between Exchange 2007 SP3 and Exchange 2013 CU7. There is an issue when after migrating the user from exchange 2007 mailbox to exchange 2013, the outlook keeps on prompting for password when it is being launched. Checking the Connection
Status we found that there is a connection to the old 2007 Server and the type is Exchange Public Folder. I have migrated the public folder and checked the Mailbox of the user and found that the DefaultPublicFolderMailbox is set to the 2013 Public Folder Mailbox.
If I check my 2013 MailboxDatabase Properties, It sill shows that PublicFolderDatabase Properties is still pointing to the 2007 Public Folder Database. Any resolution on this?
Another issue is, We set outlook anywhere on the 2013 to use basic authentication, however, when users are migrated to 2013 the Outlook client changes to NTLM. even if we set the outlook to basic to make it work, it still comes back to NTLM after a while.
I did most of the resolutions online to use powershell to make changes to outlook anywhere but no luck. any suggestions is highly appreciated.
Thanks & Regards,
Arthur

Hi,
For the first problem, please check the msExchHomePublicMDB attribute for mailbox database in Exchange 2013, you can check this attribute in ADSIEdit.
If this attribute is pointing to Exchange 2007 public folder database, please set to blank. After that, please restart the information service.
And for the second question, I suggest we open a new case for this issue. In order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one
issue per thread in order to find a resolution efficiently.
Thanks for your understanding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Physical disk for OS and read only filesystem after live migration

I am running OVM 3.1.1 connected to an EMC storage array. I have a situation where physical disks are being used for OS and binary filesystems (i.e. /u01, etc..) rather than virtual disks inside a repository. When a VM is migrated from one host to another, I sometimes get a message stating the size of the disk changed and shortly afterwards the filesystem is changed to read only and I have to reboot to fix the problem. Is this an unsupported configuration or do I have potential problems with my LUN mapping? Has anyone seen this problem before?

I am running OVM 3.1.1 connected to an EMC storage array. I have a situation where physical disks are being used for OS and binary filesystems (i.e. /u01, etc..) rather than virtual disks inside a repository. When a VM is migrated from one host to another, I sometimes get a message stating the size of the disk changed and shortly afterwards the filesystem is changed to read only and I have to reboot to fix the problem. Is this an unsupported configuration or do I have potential problems with my LUN mapping? Has anyone seen this problem before?

Reboot after applying patch 112915-05 realy necessary?

Hi,
I have a short question about the patch 112915-05 which i have to apply to our sol9 servers. The patchdescription tells me to reboot the server after the installation.
But now i woundering about the patch content. Only the file /usr/sbin/snoop will be replaced with this patch. I have downloaded the patch and had a short look into it, there is realy only the snoop binary in the patch. Is this a wrong information in the patch description or is the reboot realy necessary?
Thanks for Help
[http://sunsolve.sun.com/search/document.do?assetkey=112915|http://sunsolve.sun.com/search/document.do?assetkey=112915]
Files Included in this Patch:
/usr/sbin/snoop
Special Install Instructions:
NOTE 1: Perform patch installation in single user mode.
Reboot the system after patch installation.

For patch 119810-05 ( http://sunsolve.sun.com/search/document.do?assetkey=1-21-119810-05-1)
Installation Requirements:NAThis means no reboot required and you don't even have to be in single-user mode to do the install of this patch.
Contrast this with a patch where you MUST be in single-user and MUST reboot after patch installed:
For patch 127111-10 ( http://sunsolve.sun.com/search/document.do?assetkey=1-21-127111-10-1 )
Installation Requirements:Reboot immediately after installing this patch on an active boot environment to bring the system to a consistent state. An alternative may be specified in the Special Install instructions.
Use Single User Mode (run level S) when installing this patch on an active boot environment. An alternative may be specified in the Special Install Instructions..
Special Install Instructions: -----------------------------
NOTE 1: Before installing this patch, please install the latest patch
utilities patches for your OS. This list of patches is defined
at - http://sunsolve.sun.com
Please use the pull down list which appears after the text:
"Latest Patch Update: To ensure the correct functioning of the
patching utilities on your system, stay up to date on the
following patches"
README -- Last modified date: Friday, March 7, 2008

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.

No matter how many times i reboot after installing Firefox 8.0, still get "Must reboot to complete previous installation"

tried to upgrade to 8.0 without realizing that my son had switched my account to limited instead of administator and made himself administrator. installation did not complete. I changed my account back to administrator and retried. Keep getting "must reboot" message . Tried to uninstall, same message. tried system restore, same message. tried making son's account administrator and reinstalling, same message. can't install, can't uninstall, can't run program, now what?

See http://kb.mozillazine.org/Software_Update (Software Update not working properly)
Remove the files in the updates and updates\0 folder:<br />
C:\Documents and Settings\<user>\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox\updates
(%USERPROFILE%\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox\updates)
C:\Program Files\Mozilla Firefox\updates
Do a clean reinstall and download a fresh Firefox copy from http://www.mozilla.com/firefox/all.html and save the file to the desktop.
Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.<br />
Don't remove personal data when uninstalling.
It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
You can skip the step to create a new profile, that is not necessary for this issue.

User must change password after reset?

I am looking at the password policy settings and am wondering what "User must change password after reset� actually does. I turned it on. I tried changing some passwords in an ldap client and didnt get any messages or errors after authn again. And I didnt see a special attribute in the persons entry. Any clues?

When the flag is enabled and the password is changed by "cn=directory manager", the next time the user authenticate, the server returns the Password Expired Control (with a Success code) and all requests other than modify of userPassword are rejected.

After startup firefox will not open immediately sometimes must reboot laptop ??

after start-up I double click on the desktop icon or right click to open and FF will not open. I then must reboot the laptop and it usually opens. It seems to reopen ok later after closing the browser during the day. I had a box appear on opening for awhile that showed some upgrades for some apps (that I always declined) and then it went away after while. Sometimes when I go to open the box appears very briefly and as just a border of the box and then disappears. Could that be the reason for the hangup? Any input would be helpful. Should I maybe just reload the latest upgrade. thanks ahead of time helpful people. :o))

Try a clean reinstall.
* Download a fresh Firefox copy and save the file to the desktop.
* Firefox 7.0.x: http://www.mozilla.com/en-US/firefox/all.html
* Uninstall your current Firefox version.
* Do not remove personal data when you uninstall the current version or you lose your bookmarks and other data in the profile folder.
* Remove the Firefox program folder before installing that newly downloaded copy of the Firefox installer.
* It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
Your bookmarks and other profile data are stored elsewhere in the Firefox Profile Folder and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.
* http://kb.mozillazine.org/Profile_folder_-_Firefox
* http://kb.mozillazine.org/Profile_backup

Cluster node reboot and Quick Migration of VMs instead of Live Migration...

Hi to all,
how can one configure a Windows Server 2012 multi-node failover cluster, that vms are migrated per Live Migration and NOT per Quick Migration, if one node of the failover cluster will be rebooted.
Thanks in advance
Joerg

Hi Aidan,
only for the record:
We get the requested functionality - Live migrate all VMs on reboot without first pausing the cluster- when we do the following:
Change the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PreshutdownOrder
from the default
vmms
wuauserv
gpsvc
trustedinstall
to
clussvc
vmms
wuauserv
gpsvc
trustedinstall
Now the cluster service stops at first, if we Trigger a reboot and all VMs migrate as configured per MoveTypeThreshold cluster setting.
Greetings
Joerg

Hypev "automatic start action" not retained after live motion

Hi,
We have a hyper-v cluster of 2 windows 2008 R2SP1 nodes.
We found that the settings we made in the VMs "automatic start action" were reset to "none" after migration between the nodes .
We need to have it maintaned
thanks
Stefano

Hi ,
I think there may be something unclear in my previous email. Ok, I will detail it.
If you make a virtual machine high available, the Automatic Start Action will not work after you perform a live migration. Which means the following setting will not be "failovered" to another host.
You should set this via the Cluster Manager by the following setting:
This is what I said:
If you change the configuration of a virtual machine, we recommend that you use the Failover Cluster Manager snap-in to access the virtual machine settings. When you do this, the cluster is updated automatically with the configuration changes. However, if
you make changes to the virtual machine settings from the Hyper-V Manager snap-in, you must update the cluster manually after you make the changes. If the configuration is not refreshed after networking or storage changes are made, a subsequent failover may
not succeed or may succeed but result in the virtual machine being configured incorrectly.
Thanks. Feel free to let me know if anything is unclear.
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.
Hi Aaron ,
yes I think there's a misunderstanding about the question .
When you say
"If you make a virtual machine high available, the Automatic Start Action will not work after you perform a live migration. Which means the following setting will not be "failovered" to another host."
you mean that it is supposed to work this way ?
I mean , If you make a VM HA with clustering is it an accepted behaviour that the setting of " automatic start action " ( not the stop action you posted the picture of ) is not maintaned after a live migration even if such setting is made through the failover
cluster manager ?
If you are telling me that this is what it is supposed to work I don't agree , because I wish I can have a way to set a priority in VM startup in the case of complete shutdown/reboot .
Working with vsphere as well this is possible and I thought it was the same with Hyper-v
To solve this problem I had to create a group policy's startup script for the cluster nodes in which I start the VM in the correct order with some timeout .
Thanks
Stefano Colombo

Users must reboot after live migration

Similar Messages

Maybe you are looking for