XEN: "x0" re-spawning too fast message in DomU console

This document (7000048) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 10 Service Pack 2
SUSE Linux Enterprise Server 10 Service Pack 1


SLES 10 SP1 and other some other Linux distributions may have the following errors.

In /var/log/messages:
init: Id "x0" respawning too fast: disabled for 5 minutes

In /var/log/messages:
Apr 13 17:02:43 bhoward5 agetty[8511]: /dev/xvc0: No such file or directory
Apr 13 17:02:53 bhoward5 agetty[8927]: /dev/xvc0: No such file or directory
Apr 13 17:03:03 bhoward5 agetty[8929]: /dev/xvc0: No such file or directory

On the console:
init: Id "x0" respawning too fast: disabled for 5 minutes


Between SLES 10 and SLES 10 SP1, the version of Xen changed. In 3.04. A new console device, /dev/xvc0 was introduced to handle the console. This error is typically seen on DomU's which support "xvc0" but have been configured with legacy options.

match compatibility
To see if this method will work on your DomU, check /etc/inittab. The file should have a similar line. If the line does not exist and it is SLES 10 SP1 or later, you may add it. For other Linux distributions, please check with the vendor.
x0:12345:respawn:/sbin/agetty -L 9600 xvc0 xterm

method 1: simple configuration file
This method is recommended for DomU's that are unmanaged.
  1. Shutdown the DomU
  2. Go to /etc/xen/vm and locate the configuration file
  3. Backup the configruation file
  4. Open the file for editing
  5. Locate the "extra" line
  6. Replace the line with
  7. Save and close the file
  8. Test the configuration

Example Configuration:
disk=[ 'file:/var/lib/xen/images/bh7-oes/disk0,xvda,w', ]
vif=[ 'mac=00:16:3e:89:c2:f2', ]

method 2: method 1 plus importing
This method is for managed DomU's that have not been altered by management tools like "virt-manager", YaST or "virt-manager"
  1. Follow method 1
  2. Import the change
    xm new -f NAME_OF_DOMU
method 3: for modified managed domains
This method is not recommended unless you have modified a managed domain, as it involves exporting the configration from the Xen store and then editing the Python manually.
  1. Export the configuration
    xm list -l SLES10 > SLES10.py
  2. Backup the exported configuration file
  3. Open the file for editing
  4. Locate the following (or similiar).
    (kernel )
    (args 'TERM=XTERM xencons=tty')
    (device_model /usr/lib/xen/bin/qemu-dm)
  5. Change it to
    (kernel )
    (args 'console=xvc0')
    (device_model /usr/lib/xen/bin/qemu-dm)
  6. Save and close the file
  7. Import the changes
    xm new -F SLES10


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7000048
  • Creation Date: 13-Apr-2008
  • Modified Date:14-Mar-2021
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center