[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Getting frustrated with Xen


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Art Fore <art.fore@xxxxxxxxx>
  • Date: Mon, 30 Oct 2006 07:18:53 +0800
  • Delivery-date: Sun, 29 Oct 2006 15:17:57 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:reply-to:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=nKrBu/4HKdA677riBrFhmDKqklcSmCSVVLxmavFPIxaGFZ9dxyOIR/MquaDgkuh00nF45iW8TJK2EV8pD+CL4flTRl86iEaw+WfVrH6GpkWcTpKKPF50Wj7eEl2frunlTRt9HvoGzp1t3j9A7viGgW1WIrJdSUxrnrOqfaIirQQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Finally got the zen kernel compiled. the README file is wrong. I also
needed to install bin86, dev86, and glibc -32bit.

Doing a /sbin/mkinitrd -m "aacraid sd_mod scsi_mod" -k
"vmlinuz-2.6.16.29-xen" -i "initrd-xen-3.0.3" 

results in kernel panic on boot

Doing /sbin/mkinitrd -k "vmlinuz-2.6.16.29-xen" -i "initrd-xen-3.0.3" 

Allows me to boot into xen.

Running xm create suse.hvm (for the img file from the Live CD) gets
unrecognized boot device.

running depmod -v 2.6.16.29-xen results in almost every *.ko needs
something.

Notice there are symsets and symtypes for the other kernels, but only
exeuteables xen-syms-3.0.3-0 and vmlinux-syms-2.6/16/29-xen for the xen
kernel. Why is this? could this be the problem with depmod?

I do not think this kernel has ever been compiled for Athlon 64 X2 AMD2
socket. Otherwise, the README file would not be so wrong.

Art


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.