XenServer虚拟机导出失败求助：Transfer VM启动后停滞于停止状态

I’ve dealt with quite a few cases like yours where the Transfer VM gets stuck in a "stopped" state during VM exports, so let’s walk through targeted troubleshooting steps to fix this:

• Verify the Transfer VM Template Integrity
  Even though you removed old templates, double-check the current one’s health. Run this command on your XenServer host via CLI:

  xe template-list name-label="XenCenter Transfer VM"
  

  If the template is missing, corrupted, or has invalid parameters, delete it with xe template-uninstall uuid=<template-uuid> and restart XenCenter—it’ll automatically re-download a fresh, valid template.

• Check Resource Availability
  The Transfer VM needs basic resources to spin up:

  • Storage: Ensure your host’s local/shared storage has enough free space. Use xe sr-list to view storage repository capacities; aim for at least 1GB of free space to avoid issues.
  • Memory: Confirm there’s enough idle memory for the Transfer VM. Run xe host-list params=memory-free—you’ll need a minimum of 512MB of free memory (1GB is safer for larger exports).

• Validate Network Configuration
  The Transfer VM relies on your host’s management network (or a dedicated export network) to operate:

  • Make sure the management network is active, connected, and has no misconfigured VLANs or IP conflicts.
  • If you’re using a custom export network, verify that the network allows VM instantiation and there are no firewall rules blocking traffic between the host and XenCenter.

• Dig into XenServer’s Backend Logs
  XenCenter’s generic "failed to export" message isn’t helpful—let’s pull detailed logs from the XenServer host:

  • Check /var/log/xensource.log for entries related to "Transfer VM" or "export"—this will show exactly why the VM failed to start (e.g., template load errors, storage access issues).
  • Also review /var/log/messages for hardware, storage, or network-related errors that might be interfering.

• Test Manual Transfer VM Creation
  If automatic creation fails, manually spin up a Transfer VM to isolate the issue:

  1. Get the template UUID:

     xe template-list name-label="XenCenter Transfer VM" --minimal
     

  2. Create a test VM from the template:

     xe vm-create template-uuid=<your-template-uuid> name-label="Test-Transfer-VM"
     

  3. Try starting it:

     xe vm-start vm="Test-Transfer-VM"
     

  If it fails, run xe vm-list params=power-state,status-code,status-detail to get specific error codes and details—this will pinpoint whether the problem is with the template, resources, or host configuration.

• Apply XenServer and XenCenter Updates
  XenServer 7.3 has known bugs related to Transfer VM operations. Install the latest available patches for XenServer 7.3, and update XenCenter to the version compatible with your patched XenServer. Many users have resolved this exact issue by applying official updates.

内容的提问来源于stack exchange，提问作者Andreas Rogge