Enterprise Cloud Knowledge Center
Close the Menu
Home > Enterprise Cloud 2.0 Support Information > FAQ - Enterprise Cloud 2.0 > When I stop and start a virtual server, does it migrate to another physical server?

FAQ

When I stop and start a virtual server, does it migrate to another physical server?

(:Last updated）

No. Even if you stop and start a virtual server, the physical server where the virtual server is accommodated is not changed.

Is this page helpful?

Yes No
  • ECL2.0
    •  
  • Virtual Server
    •  

Related Pages

  • I'm creating a virtual server with BYOL image (ISO file). ISO file is divided to 2 parts, therefore the second part needs to be loaded in the process of installation. Is it possible?ECL2.0, Virtual Server / Construction, Specification

    No. It is not possible to upload divided files as 1 of image.

    Please combine the files by yourself before uploading.

    Is this page helpful?

    Yes No
    Open in a new window
  • We started multiple virtual servers and performed CPU benchmark test at the same time, the performance slightly varied. What are the possible causes?ECL2.0, Virtual Server

    Since it is a service that is running on a shared infrastructure, processing performance may vary depending on the usage of other customers.

    Is this page helpful?

    Yes No
    Open in a new window
  • How to configure enabled/disabled to the HA setting on the Instance.ECL2.0, Virtual Server

    You can configure enabled/disabled to the HA setting via both Portal and API by yourself.
    *) The default HA setting is enabled.
    *) Please note that in case Customers configure the HA settings of their Instance disabled, and the Instance stops due to the maintenance or failures, it cannot be automatically booted. As such, they are required to boot it by themselves.
    *) The required actions are different in the regions where below maintenance is completed. You can find the details in the following page.
    News - Virtual Server/Image Storage maintenance in Japan regions (JP1, JP2, P4, JP5)
    News - Virtual Server/Image Storage maintenance in region (US1, FR1, DE1, UK1, HK1, SG1)

    ■How to configure the HA setting by Portal.
    １．Select "Edit Instance" on the target instance.
    ２．Check or Uncheck on "HA Enabled/Disabled" on Metadata.
    ３．The HA setting will be enabled when checking it.
    The HA setting will be disabled when uncheck it.
    ４．The above Enable/Disable setting will be reflected by clicking "Edit Instance".

    ■How to configure the HA setting by API.
    １．Executing the following API request which is for setting metadata value of "vmha" to "true" or "false" to the target instance.

    <API>
    Create or replace server metadata items

    <Sample API Request>

     curl -ik -X PUT ''${NOVA_URL}'/v2/'${OS_TENANT_ID}'/servers/'${SERVER_ID}'/metadata' \
 > -H "Accept: application/json" \
 > -H "Content-Type: application/json" \
 > -H "X-Auth-Token: ${TOKEN}" \
 > -d '{"metadata": {"vmha": "true"}}'
 HTTP/1.1 200 OK
 Server: nginx/1.8.1
 Date: Tue, 11 Apr 2017 00:31:13 GMT
 Content-Type: application/json
 Content-Length: 30
 Connection: keep-alive
 X-Compute-Request-Id: req-0c502e9f-ba55-40d6-8e85-296a3852a90a

{"metadata": {"vmha": "true"}}

    ※If configuring {"metadata": {}}, the HA setting will be enabled.
    ※For setting the HA setting to disabled, please configure {"metadata": {"vmha": "false"}}.

    ２．Customer can confirm the HA setting status by executing the following API to the target instance.

    <API>
    Show server metadata

    <Sample API Request>

     curl -ik -X GET ''${NOVA_URL}'/v2/'${OS_TENANT_ID}'/servers/'${SERVER_ID}'/metadata' \
 > -H "Accept: application/json" \
 > -H "Content-Type: application/json" \
 > -H "X-Auth-Token: ${TOKEN}"
 HTTP/1.1 200 OK
 Server: nginx/1.8.1
 Date: Tue, 11 Apr 2017 00:32:08 GMT
 Content-Type: application/json
 Content-Length: 30
 Connection: keep-alive
 X-Compute-Request-Id: req-76ca9f86-9717-42b9-904d-3df4ec595cf2

{"metadata": {"vmha": "true"}}

    Is this page helpful?

    Yes No
    Open in a new window
  • Windows instance faced bluescreen or freeze. What should I do?ECL2.0, Virtual Server / Operation

    Windows instance faced blue screen or freeze.

    Windows Server 2012R2 official images may cause a suddenly blue screen or freeze.
    The workaround is to update the network driver, storage driver, and memory balloon driver.
    There are two ways to update the software: using the Internet (Workaround 1) and not using the Internet (Workaround 2). Please check the following steps for each option.

    Workaround 1. Update on the Internet available instances

    Note: This workaround requires the Internet connection for your instance.

    1. Download a virtio-win-0.1.208 image to the instance

    Download a virtio-win-0.1.208 image from here for the instance for which you want to update the virtio driver.

    2. Mount the ISO file

    Mount the ISO file you downloaded.

    3. Update network drivers

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Device Manager" in the left pane.

    Expand "Network adapters" in the center pane.
    Verify that "Red Hat VirtIO Ethernet Adapter" is displayed. (If you are using multiple logical networks, the adapter for the number of logical networks are displayed.)

    Right click on the displayed adapter and select "Properties".

    Select "Driver" tab in the displayed window.

    Confirm that the Driver Version is "63.74.104.14100" or lower, and press "Update Driver..." in the same window.

    The Windows Driver Update Wizard opens.
    Click on "Browse my computer for driver software".

    A dialog box appears to select the directory where the new driver software is stored.
    Click "Browse..." to select the drive on which you mounted the ISO file, click "OK", and then click "Next".

    When the pop-up "Would you like to install this device software?" appears, click "Install".

    Then, when you see "Windows has successfully updated your device software", press "Close".

    You are automatically returned to the window where you checked the version before updating the driver.
    Make sure that the version is "63.85.104.20800", and press "Close".

    If the driver versions do not change, please apply the update to all Network Adapters, then "6. Eject the ISO (DVD drive)", and reboot the instance and try the update again.

    If you are using multiple logical networks, update the remaining Red Hat VirtIO Ethernet Adapters to version "63.85.104.20800" as well.

    4. Update storage drivers

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Device Manager" in the left pane, and expand "Network adapters" in the center pane.
    Verify that the Red Hat VirtIO SCSI contoller is displayed. (If you are using multiple disks, the adapter for the number of disks are displayed.)

    Right click on the displayed adapter and select "Properties".
    Check the version in "Driver" tab of the window.

    Follow the same procedure for updating the network driver to the Red Hat VirtIO SCSI contoller, verify that it is upgraded to "62.85.104.20800".

    If you have multiple disks, update the remaining Red Hat VirtIO SCSI contoller to version "62.85.104.20800" as well.

    5. Update memory balloon drivers

    Note: If you are using the official image "WindowsServer-2012R2_Standard_64_include-license_virtual-server_20", please contact us for more details.

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Device Manager" in the left pane, and expand "System Devices" in the center pane.
    Verify that the VirtIO Balloon Driver is displayed.

    Right click on the displayed adapter and select "Properties".
    Check the version in "Driver" tab of the window.

    Follow the same procedure for updating the network driver to the VirtIO Balloon Driver, verify that it is upgraded to "62.85.104.20800".

    6. Eject the ISO (DVD drive)

    Eject the ISO (DVD drive).

    7. Reboot the instance

    Reboot the WindowsServer instance.

    Workaround 2. Update on the Internet unreachable instances

    Note: With this workaround, it is possible to update virtio drivers even if your instance does not have the Internet connection. However, since the procedure includes the creation of a temporary instance and volume, a fee will be charged.

    1. Create a temporary volume with a virtio-win-0.1.208 image

    Create a 15GB temporary volume and attach it to a temporary instance (created from an official WindowsServer 2012R2 image) with the Internet connection.

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Disk Management" in the left pane.

    Right click on "Disk 1" and select "Online".

    Right click on "Disk 1" and select "Initialize Disk".

    Select MBR format and click "OK".

    Right click on unallocated area of "Disk 1" and select "New Simple Volume...".

    Follow the instructions in the Wizard to set up the volume.
    In the following example, the disk is formatted with NTFS and used as drive D.

    When the volume is available as drive D, download a virtio-win-0.1.208 image from here and save it in the drive.

    Shutdown the temporary instance and detach the temporary volume.

    2. Import the virtio-win-0.1.208 image from the temporary volume

    Attach the temporary volume to the instance for which you want to update the virtio drivers.

    In "Server Manager", click "Tools" and select "Computer Management".
    Press "Disk Management" in the left pane.
    Right click on the disk of the temporary volume and select "Online".

    When the volume is available, mount the virtio-win-0.1.208 image.

    3. Update virtio drivers

    Follow the same procedure as Workaround 1 to update the virtio drivers.

    4. Detach the temporary volume

    Eject the ISO (DVD drive) you mounted in "2. Import the virtio-win-0.1.208 image from the temporary volume".
    In "Server Manager", click "Tools" and select "Computer Management".
    Press "Disk Management" in the left pane.
    Right click on the disk of the temporary volume and select "Offline".
    Shutoff the instance and detach the temporary volume.

    5. Start the instance

    Start the WindowsServer instance.

    Is this page helpful?

    Yes No
    Open in a new window
  • System clock has been changed when shutdown & launch or reboot instances.ECL2.0, Virtual Server

    System clock on Windows Server is reset and changed to Coordinated Universal Time (UTC)when shutdown&launch or reboot instances.

    After Windows OS is booted, System clock is synchronized to NTP server and recovered to time which is set before shutdown&launch or reboot.

    We recommend that you set UTC for your Windows instances, however, you can conduct the following workaround if you would like to avoid it.

    # When Windows does not synchronize with a NTP server, the system clock may show an irregular date after Windows restarts.
    In this case, this system clock will return to a regular date by stopping and starting the instance once.
    After that, the regular date will be kept even if you restart Windows.

    Workaround

    1. Open Command Prompt Window
    2. Execute the following command for setting RealTimeIsUniversal registry key

    reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f

    3. Execute the following command for confirmation of the above setting

    reg query "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /s

    , and confirm whether the following message is outputted as execution result.

    RealTimeIsUniversal    REG_DWORD    0x1

    Is this page helpful?

    Yes No
    Open in a new window

Support Information

Enterprise Cloud 2.0

Enterprise Cloud 1.0

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.

▲