Citrix XenServer How to Force Shutdown Virtual Machines

Sometimes you just can’t get a VM to shutdown, it maybe an issue with XenTools or sun spots. Here is a list of commands that will help you get that damn thing shutdown.

1. Disable High Availability (HA) so you don’t run into issues
2. Log into the Xenserver host that is running your VM with issues via ssh or console via XenCenter
3. Run the following command to list VMs and their UUIDs
   xe vm-list
4. First you can try just the normal shutdown command with force
   xe vm-shutdown uuid=<UUID from step 3> force=true
5. If that just hangs, use CONTROL+C to kill it off and try to reset the power state.  The force is required on this command
   xe vm-reset-powerstate  uuid=<UUID from step 3> force=true
6. If the VM is still not shutdown, we may need to destroy the domain
7. Run this command to get the domain id of the VM.  It is the number in the first row of output
   list_domains
8. Now run this command using the domain ID from the output of step 7
   /opt/xensource/debug/xenops destroy_domain –domid <DOMID from step 7>

$20 Promotional code released!

https://www.netdedi.com/index.php?/cart/17--lang-ssd_vps-/
$20 Promotional code released!
Try our most popular plan VPS.
CODE: 637SH8DZKU851UN

How to Add Additional Physical NICs to XenServer

Instructions

Complete the following procedure to get the NIC to show in XenCenter:

1. From the XenServer Command Line Interface (CLI), issue the following command:
   xe pif-list
2. Press Enter.
   Note: If you have more than one XenServer in the pool, you must issue the xe host-list command to list all the XenServer hosts and write down the Universally Unique Identifier (UUID) of the host that you added the new NIC, then issue command xe pif-list host-uuid=[uuid of the XenServer host]
3. The preceding command lists all the physical NICs of that XenServer. If you do not see the additional NIC, you must scan for new physical interface(s) on a XenServer and issue this command:
   xe pif-scan host-uuid=[uuid of the XenServer host]
4. Press Enter.
5. Use xe pif-list again and you can see the new NIC.
6. If you see the device of the new NIC with similar to this __tmp206888048,  you must remove it and introduce so it can recognize in the correct way such as ethX.
   xe pif-forget uuid=[uuid of __tmp206888048 that you want to forget]
   xe pif-list,  you won’t see __tmp206888048 anymore.
7. Introduce the additional physical NIC to the XenServer so it can recognize it from the XenCenter.
   ifconfig –a
8. Press Enter.
   Similar to the following output is generated:

   ifconfig:
   __tmp206888048 Link encap:Ethernet HWaddr 00:15:17:6B:6A:31
   UP BROADCAST MULTICAST MTU:1500 Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) 

   Note: The __tmp206888048 is still there with the MAC address 00:15:17:6B:6A:31. You must write down the MAC address 00:15:17:6B:6A:31 so later, you can introduce that MAC address for the next available NIC device such as ethX.
9. Now you can introduce the new physical NIC(s) to the XenServer. xe pif-introduce host-uuid=[uuid of the XenServer host] device=[machine-readable name of the interface (for example, eth3)] mac=00:15:17:6B:6A:31
10. Press Enter. The command returns a UUID, for example: 83750d2d-dd36-787c-da1c-951d7afc2cf0
11. Plug that new UUID 83750d2d-dd36-787c-da1c-951d7afc2cf0
    xe pif-plug uuid=83750d2d-dd36-787c-da1c-951d7afc2cf0
    xe pif-list to see the new PIF
12. Open XenCenter and the new physical NIC(s) are displayed           http://support.citrix.com/article/CTX121615

NETDEDI Cloud Server

• Data center locations:
  • South Korea, Hong Kong, North America
• Details:
  • Cloud platform: XCP
  • Hypervisor: Xen
  • Storage type: Central SAN
  • Minimum period: Hourly
  • Purchasing model: Server, storage and bandwidth purchased separately
  • Phone support: Yes
  • Online pricing & immediate signup: Yes
  • Free trial: Yes [1 week]
• Features:
  • High Availability: Yes
  • Scalable instances: Yes
  • Guaranteed CPU minimum: No
• Extra functionality:
  • Integrated backup/snapshot: Yes
  • Integrated load balancing: Yes
  • Integrated firewall: Yes
  • API: Yes
• Operative systems:
  • Windows support: Yes
  • Linux support: Yes
  • Custom OS support: Yes

In addition to cloud servers, CDN (Content Delivery Network) services are also offered. To read more about the cloud servers from Renet, please visit their website or check out the other tabs on this page. httts://www.netdedi.com

Monitoring Cloudstack-Zenoss 4.2.5

1. System Requirement.    OS: CentOS 64-bit 6.x (recommended)   Hardware Requirements: Up to 1000 Devices Deployment Size Memory CPU Storage   1 to 250 devices   4GB   2 cores   1x300GB, 10K RPM drive or SSD  250 to 500 devices  8GB  4 cores  1x300GB, 10K RPM drive or SSD  500 to 1000 devices  16GB  8 cores  1x300GB, 15K RPM drive or SSD Auto-deploy Installation Note: Updated for 4.2.5 The simplest way to install Zenoss Core 4.2 on a newly-deployed RHEL/CentOS 64-bit 5/6 system is to use our auto-deploy script, which downloads all required files for you. To use the script, first set up a new server running one of our supported operating systems. Then, as root, run the following commands: # wget https://github.com/zenoss/core-autodeploy/tarball/4.2.5 -O auto.tar.gz # tar xvf auto.tar.gz # cd zenoss-core-autodeploy-* Now, you have the option of editing zenpack_actions.txt, which defines all ZenPacks that will be installed by default (all Core ZenPacks). If you would like to avoid installing certain ZenPacks, then remove the corresponding lines from this file and save it. Now you are ready to install Zenoss Core 4.2.5: # ./core-autodeploy.sh

Start A Xen Server VM that Gives "VDI Not Available"

Recently,Xenserver was working abnormally.
During the reboot, the following messages are displayed and
Cold reboot was necessary.  After the cold reboot, some VMs are not started normally.

 File "/opt/xensource/sm/resetvdis.py", line 155, in ?
    reset_vdi(session, vdi_uuid, force)
  File "/opt/xensource/sm/resetvdis.py", line 56, in reset_vdi
    vdi_ref = session.xenapi.VDI.get_by_uuid(vdi_uuid)
  File "/usr/lib/python2.4/site-packages/XenAPI.py", line 245, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.4/site-packages/XenAPI.py", line 149, in xenapi_request
    result = _parse_result(getattr(self, methodname)(*full_params))
  File "/usr/lib/python2.4/site-packages/XenAPI.py", line 219, in _parse_result
    raise Failure(result['ErrorDescription'])
XenAPI.Failure: ['UUID_INVALID', 'VDI', '--force']



Furthermore, we also received the following error message when we tried to boot the server from the Xev Servers host's console:

[root@xenserver-102-90 log]# xe vm-start vm=vm-name
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=VDI 29ee8765-5556-42e1-a53e-362435f03d38 locked], 

 

To fix this issue , I followed the steps listed below   

1.

[root@]# xe vdi-forget uuid=29ee8765-5556-42e1-a53e-362435f03d38
2.
[root@}# xe vdi-list uuid=29ee8765-5556-42e1-a53e-362435f03d38
uuid ( RO)                : 29ee8765-5556-42e1-a53e-362435f03d38
          name-label ( RW): name
    name-description ( RW): name
             sr-uuid ( RO): dc7d9c04-bc32-cf68-d0c9-954a32257c55
        virtual-size ( RO): 322223484
            sharable ( RO): false
           read-only ( RO): false
3.
[root@]# xe vdi-param-set uuid=29ee8765-5556-42e1-a53e-362435f03d38 name-label=new-name
4.
[root@]# xe vdi-list uuid=29ee8765-5556-42e1-a53e-362435f03d38
uuid ( RO)                : 29ee8765-5556-42e1-a53e-362435f03d38
          name-label ( RW): new-name
    name-description ( RW): new-name
             sr-uuid ( RO): dc7d9c04-bc32-cf68-d0c9-954a32257c55
        virtual-size ( RO): 322122547200
            sharable ( RO): false
           read-only ( RO): false
5. On the VMs storage tab, select “Attach” and proceed to select the VDI on the SR.

P2V with XenServer

IBM 3250 M2 with 2003 Server to Virtual Machine.

Tools : Xenconverter 2.4
XenServer : 6.0

Migration Steps.

1. Run XenConverter
2. Modified the Disk Storage.
3. Select XenServer and type credential
4. Execute the Convert directly to XenServer.

If you want to Convert Windows 2012 R2 physical machine to Virtual Machine,
You need to use, XenConverter 2.5 x64 with XenServer 6.0.