We've worked around the reboot problem for VMs using DHCP, and VMs using

static addressing have to powercycle to even get their new config, so
they'll all be past the point where the problem could've happened.  Stop
mentioning it.

diff --git a/doc/xvm/renumbering.mdwn b/doc/xvm/renumbering.mdwn
index 5ec565d1485a73926954523cb2e0626d0cff2d56..66ae0aa0cbcc5ebdb1215e6705bc0eac541d8e41 100644 (file)
--- a/doc/xvm/renumbering.mdwn
+++ b/doc/xvm/renumbering.mdwn
@@ -120,16 +120,6 @@ Once your migration has occurred, the "IP:" line on the info page and
 the IP address on the line for your VM on XVM's main webpage will show
 your new address, which begins with `18.49`.
 
-## I rebooted my VM after its IP migration happened, and now I can't reach it on the network.  What should I do?
-
-The very first time you restart your VM after its IP migration has occurred,
-it is necessary to do so by completely turning it off and then turning it
-back on.  A reboot is not sufficient due to some internal state on the
-XVM infrastructure servers that is not cleared out when a VM reboots without
-being turned completely off.  Once the VM has been through one complete
-powercycle, further reboots should work fine.  We apologize for the
-inconvenience.
-
 ## My VM's networking is statically configured.  What should I do?
 
 The simplest and best way to handle this is to reconfigure your VM to
@@ -167,12 +157,9 @@ that point.
 
 You should wait for your VM's IP address to be migrated.  Once that
 happens, you will need to either restart your AFS client, or (perhaps
-more easily in some cases) turn your VM off and then back on (note that
-a reboot will not result in a functioning network connection; the very
-first time that you restart your VM after its IP migration, you must do
-so by completely turning off the VM and then turning it back on).  If you
-are curious about the technical reasons for this, see the next paragraph.
-You do not need to contact us about this.
+more easily in some cases) reboot your VM.  If you are curious about the
+technical reasons for this, see the next paragraph.  You do not need to
+contact us about this.
 
 Restarting the AFS client after you are renumbered is necessary because
 after your AFS client starts up, the first time it talks to each of
@@ -206,10 +193,7 @@ their configurations will encounter errors.
 We will work out a time with you when your IP address can be migrated.
 At that time, we will set your VM to migrate, and you will change the
 configuration files for your daemons.  Once the machine's IP address
-migrates, you will restart the daemons or turn your server off and then
-back on (note that a reboot will not result in a functioning network
-connection; the very first time that you restart your VM after its IP
-is migrated, you must do so by turning it completely off and then back on).
+migrates, you will restart the daemons or reboot your server.
 
 ## Should I contact you about my VM's renumbering?  When do I need to contact you by?