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

[Xen-users] Can't get a CentOS pv working on NetBSD dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Rob G <rob@xxxxxxxx>
  • Date: Sun, 23 May 2010 16:00:26 -0400
  • Delivery-date: Tue, 01 Jun 2010 09:24:13 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I've been working with this for several, several weeks now. I'm finding it fairly impossible to get a Linux (CentOS specifically is my test case) domu running as a pv, under a NetBSD dom0.

I'm running xen 3.3.2

I've tried several different kernels for CentOS. When using the Generic CentOS kernel, I get:

# xm create -c Rob1CentOSpv
/usr/pkg/lib/python2.6/site-packages/xen/util/acmpolicy.py:20: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
Using config file "./Rob1CentOSpv".
Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n')

Ok, .. The tutorial on CentOS's site claims to use the xen kernel/initrd images from their FTP.. here is the results:

--

# xm create -c Rob1CentOSpv
/usr/pkg/lib/python2.6/site-packages/xen/util/acmpolicy.py:20: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
Using config file "./Rob1CentOSpv".
# Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

--

The kernels installed via the CentOS kernels-xen package, the same result as above occurs.

I'm just quite confused, there is a large amount of resource out there, but not many let you know what specific Xen version such applies to, etc. I'm pretty much stuck with 3.3.2 for now with NetBSD and I'm fine with it.

I just don't know what kernel I should be using, and what method(s) I should be using to start it.

Here is my cfg file, the kickstart file mentioned is the same one in the CentOS pv tutorial: (http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU)

-----------------

#-kernels from kernels-xen package
kernel = '/home/rob/kernels/centos/vmlinuz-2.6.18-164.15.1.el5xen';
ramdisk = '/home/rob/kernels/centos/initrd-2.6.18-164.15.1.el5xen.img';

#-generic kernel
#kernel = '/home/rob/kernels/centos/vmlinuz-2.6.18-164.el5'
#ramdisk = '/home/rob/kernels/centos/initrd-2.6.18-164.el5.img'

#- installation kernels from ftp
#kernel = '/home/rob/kernels/centosx/vmlinuz'
#ramdisk = '/home/rob/kernels/centosx/initrd.img'

extra = "text ks=http://localhost/kickstart.cfg";
name = "centospv"
memory = "512"
disk = [ 'file:/home/rob/fileback/server1.img,xvda,w', ]
vif = [ 'bridge=xenbr0', ]
#vif = [ 'type=ioemu, bridge=bridge0, ip=208.100.63.199' ]
vcpus=1
on_reboot = 'destroy'
on_crash = 'destroy'


------------------
xm info for dom0:
host                   :
release                : 5.99.27
version : NetBSD 5.99.27 (XEN3_DOM0) #0: Tue Apr 20 21:04:16 CDT 2010 root@:/usr/objdir/sys/arch/amd64/compile/XEN3_DOM0
machine                : amd64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2000
hw_caps : bfebfbff:28100800:00000000:00000140:009ce3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 32758
free_memory            : 31287
node_to_cpu            : node0:0-7
node_to_memory         : node0:31287
xen_major              : 3
xen_minor              : 3
xen_extra              : .2
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_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler : gcc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120)
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Tue Apr 20 17:17:21 CDT 2010
xend_config_format     : 4


Thanks, Rob G


_______________________________________________
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®.