I have a working solution now. I try the Xen tools available with the
Fedora Core 4 without any update:
kernel-xen0-2.6.11-1.1369_FC4.i686.rpm
kernel-xenU-2.6.11-1.1369_FC4.i686.rpm
xen-2-20050522.i386.rpm
and now it is working even with memory like 768 MB for the VM. If it
help, here is my grub config:
title Fedora Core (2.6.11-1.1369_FC4xen0)
root (hd0,0)
kernel /boot/xen.gz dom0_mem=1572864
module /boot/vmlinuz-2.6.11-1.1369_FC4xen0 ro root=LABEL=/
module /boot/initrd-2.6.11-1.1369_FC4xen0.img
I also disabled TLS by doing:
mv /lib/tls /lib/tls.disabled
this was no the problem but I have done it.
Daniel Lacroix
Le mercredi 07 décembre 2005 à 14:39 +0100, Daniel Lacroix a écrit :
> Le mercredi 07 décembre 2005 à 18:49 +0530, Dakshina Dasari a écrit :
> > hi,
> > I was also facing the issue .
> >
> > I updated my Core kernel to kernel 2.6.14-1.1644 FC4 and was able to
> > create a domain without any more errors .
>
>
> The latest Xen kernel I found for Fedora Core 4 is 2.6.13-1.1532_FC4.
> Where have you found the 2.6.14-1.1644 kernel for Xen ? Have compiled
> it ?
>
> I have used the kernel advised here:
> http://www.fedoraproject.org/wiki/FedoraXenQuickstart
> for Xen and XenU and it work but only for small memory XenU system. I
> really don't know were to found a good pair of working kernels.
>
> Daniel
>
> > Also latest Xen kernels like FC4-1532 seem to be giving errors like
> > Not enough memory allocated for Domain-0 .
>
> > Regards,
> > Dakshina
> >
> >
> >
> >
> >
> >
> >
> > Robert Mortimer wrote:
> > >
> > > -----Original Message-----
> > > From: Robert Mortimer [mailto:rmortimer@xxxxxxxxxxxxxxxxxxxxxxxx]
> > > Sent: 07 December 2005 11:49
> > > To: Dakshina.Dasari@xxxxxxx
> > >
> > >
> > >>>>I have referred the steps given at the following link.
> > >>>>http://www.fedoraproject.org/wiki/FedoraXenQuickstart
> > >>>>
> > >>>>
> > >>>>I was able to get the Xen host OS up and minimal Xen base
> > >>>>operating system for XenU into an image file.
> > >>>>But the domain is crashing immediately after it is created .
> > >>>>after using
> > >>>>xm create -c <config_file>
> > >
> > >
> > > Hi, I seem to be having similar issues. I used the new Xen 3.0 installer
> > > script to produce an FC3 dom0. It was great and all is up and running
> > >
> > > [root@xen xen]# /usr/sbin/xm list
> > > Name ID Mem(MiB) VCPUs State Time(s)
> > > Domain-0 0 681 1 r----- 42.6
> > >
> > > I then moved to the http://www.fedoraproject.org/wiki/FedoraXenQuickstart
> > > Generated a file and formatted it as instructed for the guest
> > > Mounted it and added the required file system entries
> > > Downloaded the FC4 guest kernel - yum -y install kernel-xenU.i686
> > > Amended my config file for the correct guest kernel
> > > Tried to start my domain and the log said
> > >
> > > ERROR: Will only load images built for Xen v3.0
> > > ERROR: Actually saw:
> > > 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=no,LOADER
> > > =generic'
> > > ERROR: Error constructing guest OS
> > > Traceback (most recent call last):
> > > File
> > > "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/server/SrvDomainDir
> > > .py", line 77, in op_create
> > > File
> > > "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/XendDomain.py",
> > > line 226, in domain_create
> > > File
> > > "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/XendDomainInfo.py",
> > > line 181, in create
> > > File
> > > "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/XendDomainInfo.py",
> > > line 1184, in initDomain
> > > File "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/image.py",
> > > line 115, in createImage
> > > File "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/image.py",
> > > line 134, in createDomain
> > > File "/var/tmp/xen-3.0.0-2.1_fc4-root/usr/lib/python/xen/xend/image.py",
> > > line 183, in buildDomain
> > > error: (0, 'Error')
> > >
> > >>From the first line I assume that this is a version problem
> > > Can I get an FC4 guest kernel from elsewhere (i.e. the Xen site) or do I
> > > have to compile my own?
> > >
> > >
> > >
> > >>>>The log files xend.log and xend-debug.log files are not very
> > >>>>intuitive abt the cause .
> > >>>>
> > >>>>Help appreciated.
> > >>>> --Dakshina
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>_______________________________________________
> > >>>>Xen-users mailing list
> > >>>>Xen-users@xxxxxxxxxxxxxxxxxxx
> > >>>>http://lists.xensource.com/xen-users
> > >>>>
> > >>
> > >>--
> > >>---------------------------------
> > >>Dakshina Dasari
> > >>SunMC Team
> > >>Sun Microsystems India Pvt. Ltd
> > >>Tel: +91 80 5692-7596 (Work)
> > >> x27596 (SWAN)
> > >>Email: dakshina.dasari@xxxxxxx
> > >>---------------------------------
> > >>
> > >>_______________________________________________
> > >>Xen-users mailing list
> > >>Xen-users@xxxxxxxxxxxxxxxxxxx
> > >>http://lists.xensource.com/xen-users
> > >>
> > >
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> >
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
signature.asc
Description: This is a digitally signed message part
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home