Bug 474280

Summary:	error in commands for auto-starting a guest
Product:	Red Hat Enterprise Linux 5	Reporter:	gwikle
Component:	doc-Virtualization_Guide	Assignee:	Christopher Curran <ccurran>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Don Domingo <ddomingo>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.2	CC:	menthos
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-02 04:56:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description gwikle 2008-12-03 03:37:17 UTC

The commands recommended in the section titled, Automatically starting domains during the host system boot, seem to be wrong.

I'm 95% sure that in the auto directory you should make links to
the virtual guest _config_ files rather than the image files so the line
that creates the symbolic link should be:

  ln -s /etc/xen/example .

instead of,

  ln -s /var/lib/xen/images/example .

Also, according to the xen documentation this is a configuration for a service called xendomains so you probably should document how to start and stop the service as they do in the xen documentation (or maybe just refer the user to the xen documentation?)

Comment 1 Christian Rose 2008-12-03 10:22:34 UTC

I am 100% sure the example instructions in this section is wrong. After following the instructions in this section, I could not get automatic domain startup to work, and

  service xendomains status

showed garbage and errors (I guess the xendomains script did its best in order to try to interpret the domain image file I fed to it, as per the erroneous symlink instructions, as a domain config file, and then borked).

After a night's sleep, skimming the actual xendomains script and some googling I found out the correct instructions. After removing the erroneous symlink, and replacing it with

  cd /etc/xen/auto
  ln -s ../example .

then 'service xendomains status' would display the intended results.

Comment 2 Christopher Curran 2008-12-24 02:53:36 UTC

I will try to reproduce this. From an initial look that example may not work with SELinux. This may be a bug with other components as well.

Chris

Comment 3 Christopher Curran 2009-07-31 05:20:54 UTC

This has been fixed in the latest version.