similar to: Re: Can Xen boot a Linux OS already installed in a realpartition

I have the following kernels on my /boot: 2.6.18-128.1.6 2.6.18-92.1.18 2.6.18-92.1.22 I'm low on /boot space and need to remove the oldest version. It appears that I cannot use yum to remove since all of the versions are the same (only the release is different). I believe that I can use rpm to remove the old version, but I also need to remove them from the grub.conf. Any other

I've managed to install CentOS 5.1 on S5000PAL with fakeraid Intel Embedded Raid Technology II Raid1 (LSI chipset) with some help of kickstart declaration 'driverdisk --source=http://.../driver.img' Then I've had some problems with yum update - new kernel didn't know about megasr.ko. I've solved it with commands: cd /lib/modules/ cp 2.6.18-53.el5PAE/updates/megasr.ko

Dear All, I use a raid card on my Centos 5.4 server. Whenever I updated the kernel, I used to compile drivers of the card for the new kernel. I have done this many times in the past without any problem. But this time after installing the new kernel files given below, I can not compile the new driver anymore. kernel-headers-2.6.18-164.9.1.el5 kernel-PAE-devel-2.6.18-164.9.1.el5

I build a DomU kernel on RHEL AS5.1. But when I boot this Guest DomU with the kernel, it gives me error message: Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') Can someone give me any suggestion about this problem? Thank you! Joe _______________________________________________ Xen-users

Hello, We have installed RHEL 5.2 Server ( i386 image ) on a machine with 64GB of RAM. When booting the default PAE kernel ( 2.6.18-92.el5PAE ) that is shipped with RHEL 5.2 installation the OS detects 64GB of RAM. But when booting the Xen kernel ( 2.6.18-92.el5xen ) the OS detects only 14GB of the total amount of available RAM. Did anyone encounter this problem before ? Is it a normal

We apologize for multiple receipts. -------------------------------------------------------------------------------- Eighth Real-Time Linux Workshop October 12-15, 2006 Lanzhou University - SISE Tianshui South Road 222 Lanzhou, Gansu 730000

Why??? I was/am running kernel 2.6.18-128.1.6.el5 I did a yum update and watched 2.6.18-128.1.6.el5xen and 2.6.18-128.1.6.el5PAE being installed, with PAE listed first in my /boo/grub/menu.lst I also see: Installing: kmod-fuse i686 2.7.4-1.el5.rf rpmforge 26 k replacing dkms-fuse.noarch 2.7.4-1.nodist.rf kmod-fuse-PAE i686

Hi! I have install Centos 5.5 on HP ProLiant ML110 G6 with RAID-1 hardware active. (00:1f.2 RAID bus controller: Intel Corporation 5 Series/3400 Series Chipset SATA RAID Controller (rev 05)) I have follow this suggest:

Hi, Has anybody ever stumbled upon the need to replicate a live and in production server to a virtual machine? I''m trying to virtualize a bunch of servers but I can''t figure out how can I mirror the file system. I do not want to start from scratch with them. The whole idea is to transfer them to the virtual side as they currently are. Any advice is welcome. Thank you.

HVM = fully virtualized. The question is, why are you using fully virtualized domUs? Why not paravirtualized (PV)? >>> On 2008/06/16 at 16:07, Rudi Ahlers <Rudi@SoftDux.com> wrote: Itamar - IspBrasil wrote: > why you''re using hvm ? its slow > > > > Rudi Ahlers wrote: >> Hi all >> >> I''m running CentOS 5.1 x64 + Xen 3.0 & I

HI, I always get a grub prompt ,after I installed 2nd processor to the Server IBM x3610 At the grub prompt, I always have to issue below commands. Then, Server starts successfully. grub> root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub> kernel /vmlinuz-2.6.18-128.1.1.el5PAE [Linux-bzImage, setup=0x1e00, size=0x1bb714] grub> initrd

I've been going along not noticing things happening right under my nose. so imagine my surprise when I discovered last night that my Centos 5 box has installed multiple new kernels over the last few months, as updates come out, and IT IS NOT BOOTING THE NEWST ONE. grub.conf says to boot kernel 0, and 0 is the newest one. but the one it actually boots is 6 or 8 down the list (clearly I've

Hi, DomU is a Win2008 R2 64 When i install the GPLPV drivers the network latency goes from 15ms to random numbers up to 1200ms and eventually dies. If you run a ping from the DomU to another host the network stays alive but the high latency is still there. Further more if i try and uninstall the network driver i am unable to use the old one (realtek) as it cannot detect the device.

CENTOS 5.5 dahdi 1.4.3.0.1 uname -r 2.6.18-194.3.1.el5PAE [root at localhost dahdi-linux-2.3.0.1]# service dahdi start Loading DAHDI hardware modules: FATAL: Module dahdi not found. wct4xxp: FATAL: Module wct4xxp not found. [FAILED] wctc4xxp: FATAL: Module wctc4xxp not found.

Well, I seem to have developed a strange issue with the GPL PV drivers in Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some Windows XP HVM domUs. Most (12-15) of my Windows machines work just fine. Two of them, though, have started exhibiting a strange behavior with intermittent network connectivity. Basically, the network starts up and connects initially. After some

I downloaded the src rpm for CentOS 5 and tried to recompile it. It failed with the following message: + sh ./scripts/modsign/modsign.sh /var/tmp/kernel-2.6.18-8.el5-root /lib/modules/2.6.18-8.el5PAE/kernel/drivers/char/watchdog/pcwd_pci.ko CentOS gpg: WARNING: unsafe permissions on homedir `..' + mv -f

Hey, everyone, I''m having some issues with a Xen DomU right related to performance. We have an application that cross-compiles a Linux distribution from scratch for embedded systems. We''re attempting to run this application inside a Xen DomU (paravirtualized, modified guest kernel), and the performance is really bad. The culprit seems to be high I/O wait times related to the

Hey, everyone, I''m running Xen 3.2 (SLES10) and trying to get an OpenSolaris PV domU to run correctly. I''ve followed a couple of the instruction sets out on the Xen wiki and other folks blogs, but I''m running into an issue with the domU crashing. The OpenSolaris version is the latest development release - 5.11-0.128. The config looks like this:

When trying to use the GPL PV drivers with Windows 7 x64 (and testsigning turned on), I get a BSOD with a STOP 0x00000101 error. There''s also an error at the top that says "A clock interrupt was not received on a secondary processor within the allocated time interval." Is this STOP error related to the HPET or other timing adjustments for Xen? Any advice on things I should

This may be a better question for the Xen-Devel list, but I''ll start here... Does anyone know if there is any easy way to replace the gPXE ROM with a newer version in Xen? Also, anyone know if there are any plans to have some sort of option in the domU config file to specify a boot rom? Looks like qemu-dm has an "-option-rom" option - is there any way in Xen to make use of