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.

Environment

Situation

Resolution

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 workon your DomU, check /etc/inittab. The file should have a similarline. If the line does not exist and it is SLES 10 SP1 or later,you may add it. For other Linux distributions, please check withthe vendor.

method 1: simple configuration file
This method is recommended forDomU's that are unmanaged.

1. Shutdown the DomU
2. Go to /etc/xen/vm and locate theconfiguration file
3. Backup the configruation file
4. Open the file for editing
5. Locate the "extra" line
6. Replace the line with
   extra="console=xvc0"
7. Save and close the file
8. Test the configuration

ExampleConfiguration:


method 2: method 1 plus importing
This method is for managed DomU'sthat have not been altered by management tools like "virt-manager",YaST or "virt-manager"

1. Follow method 1
2. Import the change
   xm new -fNAME_OF_DOMU

method 3:for modified managed domains
This method is not recommended unless you have modified a manageddomain, as it involves exporting the configration from the Xenstore 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).
   
   (linux
   (kernel )
   (args 'TERM=XTERM xencons=tty')
   (device_model /usr/lib/xen/bin/qemu-dm)
   
5. Change it to
   
   (linux
   (kernel )
   (args 'console=xvc0')
   (device_model /usr/lib/xen/bin/qemu-dm)
6. Save and close the file
7. Import the changes
   xm new -FSLES10