<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1x64</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Well, take it over to CentOS-virt, attach the config of the guest and I'm sure someone will spot the problem.<BR>
<BR>
-Ross<BR>
<BR>
<BR>
----- Original Message -----<BR>
From: centos-bounces@centos.org <centos-bounces@centos.org><BR>
To: CentOS mailing list <centos@centos.org><BR>
Sent: Fri Feb 29 08:48:42 2008<BR>
Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1x64<BR>
<BR>
Ross S. W. Walker wrote:<BR>
><BR>
> Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0.<BR>
><BR>
> Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities.<BR>
><BR>
> -Ross<BR>
><BR>
><BR>
> ----- Original Message -----<BR>
> From: centos-bounces@centos.org <centos-bounces@centos.org><BR>
> To: CentOS mailing list <centos@centos.org><BR>
> Sent: Fri Feb 29 04:46:42 2008<BR>
> Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on<BR>
> CentOS5.1 x64<BR>
><BR>
> Rudi Ahlers wrote:<BR>
> > Hi all<BR>
> ><BR>
> > This is the first time I try and get Xen working, and want to install<BR>
> > a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server.<BR>
> ><BR>
> > Trying to get the first one to install is rather trivial, and I keep<BR>
> > on running into errors. At fist I wanted to install it fro the cdrom,<BR>
> > so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could<BR>
> > choose my language, but then got an error saying I don't have the<BR>
> > right driver for the cdrom install. Odd.<BR>
> ><BR>
> > So, I copied the whole CD to my intranet server, to try a HTTP<BR>
> > installation, which got much further, but fails as soon as it starts<BR>
> > copying the files to the xvda partition.<BR>
> ><BR>
> > Here's what I've done:<BR>
> > virt-install -p<BR>
> > --location=<A HREF="http://intranet/kickstart/centos/5.1/32/os/i386">http://intranet/kickstart/centos/5.1/32/os/i386</A> --ram=512<BR>
> > --file=/vm/vm03.img --name=vm03<BR>
> ><BR>
> > Probing for video card: Unable to probe<BR>
> > No video hardware found, assuming headless<BR>
> > Graphical installation not available... Starting text mode.<BR>
> > Welcome to CentOS<BR>
> ><BR>
> > +------------------+ Package Installation +------------------+<BR>
> > | |<BR>
> > | Name : libXt-1.0.2-3.1.fc6-i386 |<BR>
> > | Size : 359k |<BR>
> > | Summary: X.Org X11 libXt runtime library |<BR>
> > | |<BR>
> > | |<BR>
> > | Status: |<BR>
> > | |<BR>
> > | 53% |<BR>
> > | |<BR>
> > | Packages Bytes Time |<BR>
> > | Total : 349 564M 0:02:30 |<BR>
> > | Completed: 123 200M 0:00:53 |<BR>
> > | Remaining: 226 364M 0:01:37 |<BR>
> > | |<BR>
> > | 35% <BR>
> > Guest installation complete... restarting guest.<BR>
> > libvir: Xen Daemon error : POST operation failed: (xend.err "Error<BR>
> > creating domain: Boot loader didn't return any data!")<BR>
> > exception was: virDomainCreate() failed POST operation failed:<BR>
> > (xend.err "Error creating domain: Boot loader didn't return any data!")<BR>
> > Domain installation may not have been<BR>
> > successful. If it was, you can restart your domain<BR>
> > by running 'virsh start vm03'; otherwise, pleasels | <F12> next<BR>
> > screen<BR>
> > restart your installation.<BR>
> > [root@gimbli ~]# virsh start vm03<BR>
> > libvir: Xen Daemon error : POST operation failed: (xend.err "Error<BR>
> > creating domain: Boot loader didn't return any data!")<BR>
> > error: Failed to start domain vm03<BR>
> ><BR>
> ><BR>
> ><BR>
> > /var/log/messages got filled with the following messages:<BR>
> ><BR>
> > stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0<BR>
> > tclass=capability<BR>
> > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc:<BR>
> > denied { sys_resource } for pid=2445 comm="xenstored" capability=24<BR>
> > scontext=system_u:system_r:xenstored_t:s0<BR>
> > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability<BR>
> > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc:<BR>
> > denied { sys_resource } for pid=2445 comm="xenstored" capability=24<BR>
> > scontext=system_u:system_r:xenstored_t:s0<BR>
> > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability<BR>
> > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc:<BR>
> > denied { sys_resource } for pid=2445 comm="xenstored" capability=24<BR>
> > scontext=system_u:system_r:xenstored_t:s0<BR>
> > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability<BR>
> > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc:<BR>
> > denied { sys_resource } for pid=2445 comm="xenstored" capability=24<BR>
> > scontext=system_u:system_r:xenstored_t:s0<BR>
> > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability<BR>
> ><BR>
> ><BR>
> ><BR>
> > What am I doing wrong?<BR>
> ><BR>
><BR>
> as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU<BR>
> on a 64bit dom0 is not supported and known to crash<BR>
><BR>
><BR>
> _______________________________________________<BR>
><BR>
<BR>
<BR>
Ok, so what do I do if I want to have a 64bit Host XEN & 32guest's? I'd<BR>
prefer to use CentOS for this purpose, if possible<BR>
<BR>
--<BR>
<BR>
Kind Regards<BR>
Rudi Ahlers<BR>
CEO, SoftDux<BR>
<BR>
Web: <A HREF="http://www.SoftDux.com">http://www.SoftDux.com</A><BR>
Check out my technical blog, <A HREF="http://blog.softdux.com">http://blog.softdux.com</A> for Linux or other technical stuff, or visit <A HREF="http://www.WebHostingTalk.co.za">http://www.WebHostingTalk.co.za</A> for Web Hosting stugg<BR>
<BR>
_______________________________________________<BR>
CentOS mailing list<BR>
CentOS@centos.org<BR>
<A HREF="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</A><BR>
</FONT>
</P>
<P></P>
<HR WIDTH="100%">
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.
</BODY>
</HTML>