I updated the kernels on host and guests.
1 VM didn't start up with this error
.. failed : Using config file "/xen/travelsuite.cfg". WARNING:root:Unknown directive root WARNING:root:Unknown directive kernel
WARNING:root:Unknown directive initrd Traceback (most recent call last): File "/usr/bin/pygrub", line 684, in ? data = fs.open_file(chosencfg["kernel"]).read()
IOError: [Errno 2] No such file or directory No handlers could be found for logger "xend"
Error: Boot loader didn't return any data!
Usage: xm create [options] [vars]
Create a domain based on . Options: -h, --help
Print this help. --help_config
Print the available configuration variables (vars) for the configuration script. -q, --quiet
Search path for configuration scripts. The value of PATH is a colon-separated directory list.
-f=FILE, --defconfig=FILE Use the given Python configuration script.
The configuration script is loaded after arguments have been processed.
Each command-line option sets a configuration variable named after its long option name, and these variables are placed in the environment of the script before it is loaded.
Variables for options that may be repeated have list values.
Other variables can be set using VAR=VAL on the command line.
After the script is loaded, option values that were not set on the command line are replaced by the values set in the script. -F=FILE, --config=FILE
Domain configuration to use (SXP).
SXP is the underlying configuration format used by Xen.
SXP configurations can be hand-written or generated from Python configuration scripts, using the -n (dryrun) option to print the configuration.
-n, --dryrun Dry run - prints the resulting configuration in SXP but does not create the domain.
-p, --paused Leave the domain paused after it is created.
-c, --console_autoconnect Connect to the console after the domain is created.
I then changed the Boot method from PYgrub to Host kernel and got this error
failed : Disk check failed : fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006)
Superblock last mount time is in the future. Fix? yes
Superblock last write time is in the future. Fix? yes Pass
1: Checking inodes, blocks, and sizes Pass
2: Checking directory structure Pass
3: Checking directory connectivity Pass
4: Checking reference counts Pass
5: Checking group summary information /xen/domain.img:
***** FILE SYSTEM WAS MODIFIED ***** /xen/domain.img: 73983/3639264 files (1.9% non-contiguous), 557751/7417856 blocks
I then went into the /xen/domain.cfg and changed the bottom 2 lines
vfb = ['type=vnc,vncunused=1,vncpasswd=PASSWORD,vnclisten=0.0.0.0'] bootloader = "/usr/bin/pygrub"
kernel = "/xen/vmlinuz-vm2-xenU" ramdisk = "/xen/initrd.vm2.xenU.img" root = "/dev/sda1 ro"
now it runs again
there seems to be unwanted issues with PYgrub ..
Submitted by JamieCameron on Thu, 11/11/2010 - 17:58 Comment #1
That is very odd .. it looks from the first error that the
kerneloptions in the Xen .cfg file are not recognized!
Did Xen get upgraded on the host system too?
it was kernel updates on host and guests...I switched to using the host kernel and now it runs.
I get this error back if I change bootmethod to PYgrub again.
Submitted by JamieCameron on Thu, 11/11/2010 - 18:48 Comment #3
Which exact Xen version are you running on the host system?
host : sv02.domain.org
release : 2.6.18-194.26.1.el5xen
version : #1 SMP Tue Nov 9 13:35:30 EST 2010
machine : x86_64
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2000
hw_caps : bfebfbff:20100800:00000000:00000140:040ce33d:00000000:00000001
total_memory : 8190
free_memory : 1
node_to_cpu : node0:0-3
xen_major : 3
xen_minor : 1
xen_extra : .2-194.26.1.el5
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
cc_compile_by : mockbuild
cc_compile_domain : centos.org
cc_compile_date : Tue Nov 9 12:45:24 EST 2010
xend_config_format : 2
Submitted by JamieCameron on Fri, 11/12/2010 - 12:53 Comment #5
That looks fine .. I assume you are just using the Xen RPMs provided by CentOS?
To debug this further, I'd need to login to your Cloudmin master system and see what is going wrong in PyGrub mode..
yes Im using defaults provided by CentOS
Ill dig up your emailaddress and send you the credentials..
Submitted by JamieCameron on Fri, 11/12/2010 - 14:46 Comment #7
My email is email@example.com
yes i had it in my addressbook, mail send :)