hi i have installed xen 3.1 on rhel5 on IBM 3650 (32 bit). i tried to install rhel5 also as domU but i get an error while creating domU that Error: (2, '';Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32p not supported by xen kernel, sorry\n'') is there something missing about my configuration or as the error says my guest kernel is not supported by xen 3.1? And does anybody know which rhel5 kernel should i use and where can i find it? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Mehmet, Mehmet Can ÖNAL wrote:> i have installed xen 3.1 on rhel5 on IBM 3650 (32 bit). i tried to > install rhel5 also as domU but i get an error while creating domU that > > Error: (2, '';Invalid kernel'', ''xc_dom_compat_check: guest type > xen-3.0-x86_32p not supported by xen kernel, sorry\n'') > > is there something missing about my configuration or as the error says > my guest kernel is not supported by xen 3.1? And does anybody know > which rhel5 kernel should i use and where can i find it?it looks like you''re trying to boot a kernel that is not working with xen. I guess it''s not a HVM domU, so my second guess is, that the kernel you try to boot does not support PAE. you can check what kind of guest os you can boot with: xm info |grep xen_caps So, to resolve your problem, you either have to run your domU as a HVM machine, then you can use the rhel5 stock kernel (I think) or you have to get/build a PAE kernel. Greetz Age_M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Mehmet, Age_M wrote:> Hello Mehmet, > > Mehmet Can ÖNAL wrote: >> i have installed xen 3.1 on rhel5 on IBM 3650 (32 bit). i tried to >> install rhel5 also as domU but i get an error while creating domU that >> >> Error: (2, '';Invalid kernel'', ''xc_dom_compat_check: guest type >> xen-3.0-x86_32p not supported by xen kernel, sorry\n'') >> >> is there something missing about my configuration or as the error >> says my guest kernel is not supported by xen 3.1? And does anybody >> know which rhel5 kernel should i use and where can i find it? > it looks like you''re trying to boot a kernel that is not working with > xen. I guess it''s not a HVM domU, so my second guess is, that the > kernel you try to boot does not support PAE. > you can check what kind of guest os you can boot with: > > xm info |grep xen_caps > > So, to resolve your problem, you either have to run your domU as a HVM > machine, then you can use the rhel5 stock kernel (I think) or you have > to get/build a PAE kernel. >sorry I got it all wrong :-p it''s the other way round! Your Xen dom0 does not support domU-kernel with PAE support (you can see this at the little ''p'' -> ''guest type xen-3.0-x86_32p not supported''). So you need a non-PAE Kernel in domU. Greetz Age_M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Age_M wrote:> Hi Mehmet, > > Age_M wrote: >> Hello Mehmet, >> >> Mehmet Can ÖNAL wrote: >>> i have installed xen 3.1 on rhel5 on IBM 3650 (32 bit). i tried to >>> install rhel5 also as domU but i get an error while creating domU that >>> >>> Error: (2, '';Invalid kernel'', ''xc_dom_compat_check: guest type >>> xen-3.0-x86_32p not supported by xen kernel, sorry\n'') >>> >>> is there something missing about my configuration or as the error >>> says my guest kernel is not supported by xen 3.1? And does anybody >>> know which rhel5 kernel should i use and where can i find it? >> it looks like you''re trying to boot a kernel that is not working with >> xen. I guess it''s not a HVM domU, so my second guess is, that the >> kernel you try to boot does not support PAE. >> you can check what kind of guest os you can boot with: >> >> xm info |grep xen_caps >> >> So, to resolve your problem, you either have to run your domU as a >> HVM machine, then you can use the rhel5 stock kernel (I think) or you >> have to get/build a PAE kernel. >> > sorry I got it all wrong :-p it''s the other way round! Your Xen dom0 > does not support domU-kernel with PAE support (you can see this at the > little ''p'' -> ''guest type xen-3.0-x86_32p not supported''). So you need > a non-PAE Kernel in domU.This interpretation does not seem to be correct if you are using the kerne-xen shipped with RHEL5 distribution. RHEL kernel-xen is pae enabled only supports pae guests and you can''t run non-pae kernels on guests. If this is the case, can we have more details from your system? If you have compiled the dom0 kernel from upstream source, this may be correct and u need to re-compile it with pae support. --Sadique> > Greetz > Age_M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pls keep replies to the list. Can we see ur guest config file? --Sadique santhosh kumar wrote:> Hi Sadique, > > Can I have your help. > the problem is that i have centos 5.1 as the OS which has a default > xen-.3.0.3-25.el5. > when ever i try to install new guest(rhel5 or windows xp) it gives > following error: > > Kernel panic - not syncing: Attempted to kill init! > > i hav attached the config file. > > full out put is here. > > Using config file "/root/Desktop/xmexample/xm2". > Started domain Rhel5 > Linux version 2.6.18-8.el5xen (mockbuild@builder4.centos.org > <mailto:mockbuild@builder4.centos.org>) (gcc version 4.1.1 20070105 > (Red Hat 4.1.1-52)) #1 SMP Thu Mar 15 21:02:53 EDT 2007 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000020800000 (usable) > 0MB HIGHMEM available. > 520MB LOWMEM available. > NX (Execute Disable) protection: active > ACPI in unprivileged domain disabled > Built 1 zonelists. Total pages: 133120 > Kernel command line: root=/dev/sda ro > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c071b000 soft=c06fb000 > PID hash table entries: 4096 (order: 12, 16384 bytes) > Xen reported: 2094.748 MHz processor. > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Software IO TLB disabled > vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 > Memory: 510080k/532480k available (2017k kernel code, 13744k reserved, > 824k data, 172k init, 0k highmem) > Checking if this processor honours the WP bit even in supervisor > mode... Ok. > Calibrating delay using timer specific routine.. 5238.88 BogoMIPS > (lpj=10477768) > Security Framework v1.0.0 initialized > SELinux: Initializing. > SELinux: Starting in permissive mode > selinux_register_security: Registering secondary module capability > Capability LSM initialized as secondary > Mount-cache hash table entries: 512 > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 512K (64 bytes/line) > Checking ''hlt'' instruction... OK. > SMP alternatives: switching to UP code > Freeing SMP alternatives: 16k freed > Brought up 1 CPUs > checking if image is initramfs... it is > Freeing initrd memory: 3373k freed > Grant table initialized > NET: Registered protocol family 16 > ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06CAAA0 could > not acquire Mutex [2] [20060707] > Brought up 1 CPUs > PCI: setting up Xen PCI frontend stub > ACPI: Interpreter disabled. > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: System does not support PCI > PCI: System does not support PCI > NetLabel: Initializing > NetLabel: domain hash size = 128 > NetLabel: protocols = UNLABELED CIPSOv4 > NetLabel: unlabeled traffic allowed by default > NET: Registered protocol family 2 > IP route cache hash table entries: 32768 (order: 5, 131072 bytes) > TCP established hash table entries: 131072 (order: 8, 1048576 bytes) > TCP bind hash table entries: 65536 (order: 7, 524288 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com > <mailto:tigran@veritas.com>> > audit: initializing netlink socket (disabled) > audit(1210058158.840:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > SELinux: Registering netfilter hooks > Initializing Cryptographic API > ksign: Installing public key data > Loading keyring > - Added public key EE79A493AEE5EDC9 > - User ID: CentOS (Kernel Module GPG key) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > Console: switching to colour frame buffer device 100x37 > input: Xen Virtual Keyboard/Mouse as /class/input/input0 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > ide-floppy driver 0.99.newide > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > TCP bic registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/768 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 172k freed > Write protecting the kernel read-only data: 355k > USB Universal Host Controller Interface driver v3.0 > SCSI subsystem initialized > Kernel panic - not syncing: Attempted to kill init! > > can i even know the difference between sdx and hdx (x=a,b,c....) > > Thanks & Regards > san > >-- Red Hat Software Services (India) Pvt. Ltd. 6th Floor, East Wing Marisoft-III, Marigold Premises Kalyani Nagar, Pune, Maharashtra India, Pin-411014 Mobile +919890354236 Tel: +91 20 40057363 If you want things you''ve never had, you have to do things you''ve never done. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sadique Puthen wrote:> Age_M wrote: >> Hi Mehmet, >> >> Age_M wrote: >>> Hello Mehmet, >>> >>> Mehmet Can ÖNAL wrote: >>>> i have installed xen 3.1 on rhel5 on IBM 3650 (32 bit). i tried to >>>> install rhel5 also as domU but i get an error while creating domU that >>>> >>>> Error: (2, '';Invalid kernel'', ''xc_dom_compat_check: guest type >>>> xen-3.0-x86_32p not supported by xen kernel, sorry\n'') >>>> >>>> is there something missing about my configuration or as the error >>>> says my guest kernel is not supported by xen 3.1? And does anybody >>>> know which rhel5 kernel should i use and where can i find it? >>> it looks like you''re trying to boot a kernel that is not working >>> with xen. I guess it''s not a HVM domU, so my second guess is, that >>> the kernel you try to boot does not support PAE. >>> you can check what kind of guest os you can boot with: >>> >>> xm info |grep xen_caps >>> >>> So, to resolve your problem, you either have to run your domU as a >>> HVM machine, then you can use the rhel5 stock kernel (I think) or >>> you have to get/build a PAE kernel. >>> >> sorry I got it all wrong :-p it''s the other way round! Your Xen dom0 >> does not support domU-kernel with PAE support (you can see this at >> the little ''p'' -> ''guest type xen-3.0-x86_32p not supported''). So you >> need a non-PAE Kernel in domU. > > This interpretation does not seem to be correct if you are using the > kerne-xen shipped with RHEL5 distribution. RHEL kernel-xen is pae > enabled only supports pae guests and you can''t run non-pae kernels on > guests. If this is the case, can we have more details from your system?Well, there was little information to work with :-/ but doesn''t "guest type xen-3.0-x86_32p not supported" mean that you can only boot non-PAE kernels? Greetz Age_M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
first of all thanx for your answer. xm info | grep xen_caps command gives me an output xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 i have downloaded the kernel i tried to boot as domU from rhel site ( rhn.redhat.com) as kernel-xen-2xxxx that its description says that this kernel enables vm operations. does that mean it''s dom0 kernel? would you mind explaining your answer a bit more that i''m so new to these concept thanx a lot 2008/5/6 Age_M <Age_M@gmx.de>:> Hello Mehmet, > > > Mehmet Can ÖNAL wrote: > > > i have installed xen 3.1 on rhel5 on IBM 3650 (32 bit). i tried to > > install rhel5 also as domU but i get an error while creating domU that > > > > Error: (2, '';Invalid kernel'', ''xc_dom_compat_check: guest type > > xen-3.0-x86_32p not supported by xen kernel, sorry\n'') > > > > is there something missing about my configuration or as the error says > > my guest kernel is not supported by xen 3.1? And does anybody know which > > rhel5 kernel should i use and where can i find it? > > > it looks like you''re trying to boot a kernel that is not working with xen. > I guess it''s not a HVM domU, so my second guess is, that the kernel you try > to boot does not support PAE. > you can check what kind of guest os you can boot with: > > xm info |grep xen_caps > > So, to resolve your problem, you either have to run your domU as a HVM > machine, then you can use the rhel5 stock kernel (I think) or you have to > get/build a PAE kernel. > > > Greetz > Age_M > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
my host machine is IBM 3650 server
i installed rhel 5 as OS
i have installed xen 3.1 from binary tarball (i did not compile from source)
i downloaded kernel-xen-2.6.18-8.el5 from rhn.redhat.com and make initrd
with --preload=xennet and --preload=xenblk options
my configuration file is:
# -*- mode: python; -*-
#===========================================================================#
Example Python setup script for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
#
# This is a relatively advanced script that uses a parameter, vmid, to
control
# the settings. So this script can be used to start a set of domains by
# setting the vmid parameter on the ''xm create'' command line.
For example:
#
# xm create vmid=1
# xm create vmid=2
# xm create vmid=3
#
# The vmid is purely a script variable, and has no effect on the the domain
# id assigned to the new domain.
#===========================================================================
# Define script variables here.
# xm_vars is defined automatically, use xm_vars.var() to define a variable.
# This function checks that ''vmid'' has been given a valid
value.
# It is called automatically by ''xm create''.
def vmid_check(var, val):
val = int(val)
if val <= 0:
raise ValueError
return val
# Define the ''vmid'' variable so that ''xm
create'' knows about it.
xm_vars.var(''vmid'',
use="Virtual machine id. Integer greater than 0.",
check=vmid_check)
# Check the defined variables have valid values..
xm_vars.check()
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.18-8.el5xen"
# Optional ramdisk.
ramdisk = "/boot/initrd-xenEL5.img"
# The domain build function. Default is ''linux''.
#builder=''linux''
# Initial memory allocation (in megabytes) for the new domain.
#
# WARNING: Creating a domain with insufficient memory may cause out of
# memory errors. The domain needs enough memory to boot kernel
# and modules. Allocating less than 32MBs is not recommended.
memory = 2048
# A name for the new domain. All domains have to have different names,
# so we use the vmid to create a name.
name = "VM%d" % vmid
# 128-bit UUID for the domain. The default behavior is to generate a new
UUID
# on each call to ''xm create''.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
#cpus = "%s" % vmid # set based on vmid (mod number of CPUs)
# Number of Virtual CPUS to use, default is 1
#vcpus = 1
vcpus = 4 # make your domain a 4-way
#----------------------------------------------------------------------------
# Define network interfaces.
# By default, no network interfaces are configured. You may have one
created
# with sensible defaults using an empty vif clause:
#
# vif = [ '''' ]
#
# or optionally override backend, bridge, ip, mac, script, type, or vifname:
#
# vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ]
#
# or more than one interface may be configured:
#
# vif = [ '''', ''bridge=xenbr1'' ]
vif = [ '''' ]
#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
# This makes the disk device depend on the vmid - assuming
# that devices sda7, sda8 etc. exist. The device is exported
# to all domains as sda1.
# All domains get sda6 read-only (to use for /usr, see below).
disk = [ ''file:/root/VMDomain1/domu1root,sda1,w'' ]
#----------------------------------------------------------------------------
# Define frame buffer device.
#
# By default, no frame buffer device is configured.
#
# To create one using the SDL backend and sensible defaults:
#
# vfb = [ ''type=sdl'' ]
#
# This uses environment variables XAUTHORITY and DISPLAY. You
# can override that:
#
# vfb = [
''type=sdl,xauthority=/home/bozo/.Xauthority,display=:1'' ]
#
# To create one using the VNC backend and sensible defaults:
#
# vfb = [ ''type=vnc'' ]
#
# The backend listens on 127.0.0.1 port 5900+N by default, where N is
# the domain ID. You can override both address and N:
#
# vfb = [ ''type=vnc,vnclisten=127.0.0.1,vncdisplay=%d'' % vmid
]
#
# Or you can bind the first unused port above 5900:
#
# vfb = [ ''type=vnc,vnclisten=0.0.0.0,vnunused=1'' ]
#
# You can override the password:
#
# vfb = [ ''type=vnc,vncpasswd=MYPASSWD'' ]
#
# Empty password disables authentication. Defaults to the vncpasswd
# configured in xend-config.sxp.
#----------------------------------------------------------------------------
# Define to which TPM instance the user domain should communicate.
# The vtpm entry is of the form
''instance=INSTANCE,backend=DOM''
# where INSTANCE indicates the instance number of the TPM the VM
# should be talking to and DOM provides the domain where the backend
# is located.
# Note that no two virtual machines should try to connect to the same
# TPM instance. The handling of all TPM instances does require
# some management effort in so far that VM configration files (and thus
# a VM) should be associated with a TPM instance throughout the lifetime
# of the VM / VM configuration file. The instance number must be
# greater or equal to 1.
#vtpm = [''instance=%d,backend=0'' % (vmid) ]
#----------------------------------------------------------------------------
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the
domain''s
# IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP.
# You can use ''extra'' to set the runlevel and custom
environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
#netmask# Set default gateway.
#gateway# Set the hostname.
#hostname= "vm%d" % vmid
# Set root device.
root = "/dev/mapper/VolGroup00-LogVol00 ro"
# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = ''169.254.1.0''
# Root directory on the nfs server.
#nfs_root = ''/full/path/to/root/directory''
# Sets runlevel 4 and the device for /usr.
#extra = "4 VMID=%d usr=/dev/sda6" % vmid
#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits. There are three
''reasons''
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of
the
old
# one;
# "preserve", meaning that no clean-up is done until the
domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up,
but is
# renamed and a new domain started in its place.
#
# The default is
#
# on_poweroff = ''destroy''
# on_reboot = ''restart''
# on_crash = ''restart''
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = ''onreboot'' means on_poweroff =
''destroy''
# on_reboot = ''restart''
# on_crash = ''destroy''
#
# restart = ''always'' means on_poweroff =
''restart''
# on_reboot = ''restart''
# on_crash = ''restart''
#
# restart = ''never'' means on_poweroff =
''destroy''
# on_reboot = ''destroy''
# on_crash = ''destroy''
#on_poweroff = ''destroy''
#on_reboot = ''restart''
#on_crash = ''restart''
#===========================================================================
if you need more info just send a new post please
thanx again
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Mehmet, Mehmet Can ÖNAL wrote:> xm info | grep xen_caps command gives me an output > > xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >did you get any further with your problem? As Sadique allready mentioned, it could be, that I am interpreting things wrong. I would say that your Xen is not capable of booting PAE kernels. So you need to either get a non-PAE kernel for domU, or get/built a different Xen with PAE support. Maybe you could try to boot the dom0 kernel in your domU, which worked ok here on gentoo-linux.> i have downloaded the kernel i tried to boot as domU from rhel site > (rhn.redhat.com <http://rhn.redhat.com>) as kernel-xen-2xxxx that its > description says that this kernel enables vm operations. does that > mean it''s dom0 kernel?Uuhm, I don''t know :-/ I never worked with RedHat products? Maybe you could search for a non-PAE kernel @redhat.com?> > would you mind explaining your answer a bit more that i''m so new to > these concept >What do you want to know? What should I explain more? Greetz Age_M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Age_M wrote:> Hi Mehmet, > > Mehmet Can ÖNAL wrote: >> xm info | grep xen_caps command gives me an output >> >> xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >> > did you get any further with your problem? > As Sadique allready mentioned, it could be, that I am interpreting > things wrong. > I would say that your Xen is not capable of booting PAE kernels. So > you need to either get a non-PAE kernel for domU, or get/built a > different Xen with PAE support.Does your cpu support pae? what is the output of "cat /proc/cpuinfo | grep pae"? If you don''t have pae support for your cpu, you can''t use any RHEL or Centos xen kernels that come with the distribution. All that you can do is compile the dom0 and domu kernels from upstream source after truning off pae support and try to use that. --Sadique> Maybe you could try to boot the dom0 kernel in your domU, which worked > ok here on gentoo-linux. >> i have downloaded the kernel i tried to boot as domU from rhel site >> (rhn.redhat.com <http://rhn.redhat.com>) as kernel-xen-2xxxx that its >> description says that this kernel enables vm operations. does that >> mean it''s dom0 kernel? > Uuhm, I don''t know :-/ I never worked with RedHat products? Maybe you > could search for a non-PAE kernel @redhat.com? >> >> would you mind explaining your answer a bit more that i''m so new to >> these concept >> > What do you want to know? What should I explain more? > > Greetz Age_M > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
cat /proc/cpuinfo | grep pae command comes with flag lines and with "pae" in it. can i use my dom0 kernel with another initrd? 2008/5/7 Sadique Puthen <sputhenp@redhat.com>:> Age_M wrote: > > > Hi Mehmet, > > > > Mehmet Can ÖNAL wrote: > > > > > xm info | grep xen_caps command gives me an output > > > > > > xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 > > > > > > did you get any further with your problem? > > As Sadique allready mentioned, it could be, that I am interpreting > > things wrong. > > I would say that your Xen is not capable of booting PAE kernels. So you > > need to either get a non-PAE kernel for domU, or get/built a different Xen > > with PAE support. > > > > Does your cpu support pae? what is the output of "cat /proc/cpuinfo | grep > pae"? If you don''t have pae support for your cpu, you can''t use any RHEL or > Centos xen kernels that come with the distribution. All that you can do is > compile the dom0 and domu kernels from upstream source after truning off pae > support and try to use that. > > --Sadique > > Maybe you could try to boot the dom0 kernel in your domU, which worked ok > > here on gentoo-linux. > > > > > i have downloaded the kernel i tried to boot as domU from rhel site ( > > > rhn.redhat.com <http://rhn.redhat.com>) as kernel-xen-2xxxx that its > > > description says that this kernel enables vm operations. does that mean it''s > > > dom0 kernel? > > > > > Uuhm, I don''t know :-/ I never worked with RedHat products? Maybe you > > could search for a non-PAE kernel @redhat.com? > > > > > > > > would you mind explaining your answer a bit more that i''m so new to > > > these concept > > > > > > What do you want to know? What should I explain more? > > > > Greetz Age_M > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
when i use my dom0 kernel i get an error "volume group VolGroup00 not found" could not find filesystem ''/dev/root'' ........................ i searched this error in this group from that cases i make the initial ram disk with xenblk and xennet options but does not work? do you have any idea? 2008/5/7 Mehmet Can ÖNAL <mconalxen@gmail.com>:> cat /proc/cpuinfo | grep pae command comes with flag lines and with "pae" > in it. > > can i use my dom0 kernel with another initrd? > > 2008/5/7 Sadique Puthen <sputhenp@redhat.com>: > > Age_M wrote: > > > > > Hi Mehmet, > > > > > > Mehmet Can ÖNAL wrote: > > > > > > > xm info | grep xen_caps command gives me an output > > > > > > > > xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 > > > > > > > > did you get any further with your problem? > > > As Sadique allready mentioned, it could be, that I am interpreting > > > things wrong. > > > I would say that your Xen is not capable of booting PAE kernels. So > > > you need to either get a non-PAE kernel for domU, or get/built a different > > > Xen with PAE support. > > > > > > > Does your cpu support pae? what is the output of "cat /proc/cpuinfo | > > grep pae"? If you don''t have pae support for your cpu, you can''t use any > > RHEL or Centos xen kernels that come with the distribution. All that you can > > do is compile the dom0 and domu kernels from upstream source after truning > > off pae support and try to use that. > > > > --Sadique > > > > Maybe you could try to boot the dom0 kernel in your domU, which worked > > > ok here on gentoo-linux. > > > > > > > i have downloaded the kernel i tried to boot as domU from rhel site > > > > (rhn.redhat.com <http://rhn.redhat.com>) as kernel-xen-2xxxx that > > > > its description says that this kernel enables vm operations. does that mean > > > > it''s dom0 kernel? > > > > > > > Uuhm, I don''t know :-/ I never worked with RedHat products? Maybe you > > > could search for a non-PAE kernel @redhat.com? > > > > > > > > > > > would you mind explaining your answer a bit more that i''m so new to > > > > these concept > > > > > > > > What do you want to know? What should I explain more? > > > > > > Greetz Age_M > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users