This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 434] Error: Error creating domain: (0, 'Error')

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 434] Error: Error creating domain: (0, 'Error')
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 07 Dec 2005 15:47:52 +0000
Delivery-date: Wed, 07 Dec 2005 15:48:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From hikenboot@xxxxxxxxx  2005-12-07 15:47 -------
I am inserting my reply to the xen users list for people with a similar issue.
But your help with the distinguishing the logs was a great asset in determining
the source of the problem...at least what i beleive the source of the problem
is. Please read bellow and correct me if I am wrong!

Greetings and Happy Holiday Season:

I filed an open issue with Fedora installer and rpm because of the same error. I
was suggested to look in the xend-debug.log for detailed logs on the problem.

This is enabled in

nano /etc/xen/xend-config.sxp

by adding the following lines

(logfile /var/log/xend.log.debug)
(loglevel DEBUG)
then removing the logs
rm -f /var/log/xend.log
rm -f /var/log/xend.log.debug
rm -f /var/log/xend-debug.log
then issuing
touch /var/log/xend.log
touch /var/log/xend.log.debug
touch /var/log/xend-debug.log
(note this starts your logs with a clean slate with nothing in them)
and then
issuing the command  /usr/sbin/xend restart (so it uses the newly created logs)

When this is done more details show up on the problem

However after looking ove the suggested logs I believe the root of the problem
is that
the install script and the .tar files now available DO NOT PROVIDE a domU kernel
the existing domU kernels in the existing domain are actually part of xen 2.6 or
2.7 --whatever the last version was named.

When the 3.0 kernel was just issued it no longer works with older domU kernels
and one was not provided with the script to replace it with that is generic.

Correct me if I am wrong but the procedure for creating a new domU kernel would
be somthing as follows:


(NOTE: I might be wrong since no source is provided--therefor recompiling
wouldnt be possible with the rpm therfor one couldnt enable the proper front
end/or backend whatever drivers--cant remember which the domU's require)

Then again as I mention later on it might be simple as
copy dom0 kernel to  a name like kernel-domU and placing it in domU's boot
directory....creating a initrd image doing a modprobe -a in domU after it starts
and creating proper config file for it....not in that order of course!

Please note that the procedure will have to vary slightly since the name of the
kernel is ...domU kernel I think this can be taken care of with
EXTRAVERSION=3.1.1-domU but not sure havent tried it yet
make DESTDIR=$BUILD_ROOT install  may have to be setup so it installs it into
/boot where it will then have to be copied into the domU image by
mount -o loop /path/to/image/file/image.file /mnt/fedora
cd /mnt/fedora
rpm -Uvh -root /path/to/image/file/mnt/fedora/  NewDomUKernel-3.1.1-domU

Its complicated and would be easier if they provided a prebuilt domU kernel. Im
not sure but the dom0 kernel may be generic enough to use as domU kernel just by
renaming it ---this is dependant upon if its compiled with both the backend and
frontend drivers but am not sure.

Perhaps if someone wants to start a wiki on doing this we can all contribute to 


Steven Anderson

Thats the summary of what I believe the error to be!

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>