similar to: New to Linux and Wine, need to know a few things

This is irritating: I've got a server I just upgraded to 5.4, then rebooted, only to discover that it just *sits* there at the grub boot menu. I looked at grub.conf, and uncommented hiddenmenu (which should have been done long ago). It *still* sits there when I reboot. Any clues, folks? mark grub.conf: #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz

I have one SATA drive with windows xp installed. I added a second SATA drive to install CentOS on. During the install, both drives are listed. If I use the auto-partition feature and deselect the drive with windows on it, only selecting the new drive, I get an error message that it could not create the partitions. The same thing happened a few months ago and I manually setup to partitions.

# grub.conf generated by anaconda I recently tried installing xen on another machine and I''m getting the "CPU0 is toast rebooting in 5 seconds" message. Reading through past postings, I was hopeful setting the dom0_mem=128M would solve the problem. Unfortunately, it didn''t make a difference. I haven''t fooled with anything on this system -- just a fresh FC4

I recently installed CentOS 5.1 on a DL71 ASI notebook. After my yum update the timeout parameter in /boot/grub/grub.conf file has no effect. It sits at the grub screen forever unless I press the enter key to select a kernel, at which point it will boot. Any help or suggestions to fix this would be much appreciated CentOS release 5.2 (Final) Kernel 2.6.18-92.1.18.el5 on an i686 # grub.conf

Dumb thought: I don't remember how, other than from a grub menu, but I'm pretty sure there's a way to default boot into a grub shell. Once there, you can see, using file completion, the drives, and where your initrd is. mark

Hi my friends, I am running into a problem with my NIC. [root@xxxx ~]# ifup eth0 Error for wireless request "Set Encode" (8B2A) : SET failed on device eth0 ; No such device. SIOCGIFFLAGS: No such device Failed to bring up eth0. eth0 is not a wireless device. Below are some information about my host: [root@xxxx ~]# lspci |grep -i ether 00:04.0 Ethernet controller: Intel Corporation

On Wed, May 25, 2011 at 12:41 AM, JAMES BOND 123 007 <james123007@gmail.com> wrote: > Hi , > I saw your thread post at > http://web.archiveorange.com/archive/v/ZvO4jnaavtTfcyqnHoRX > , about problems with XEN 4.0 installation. > I have the same problem and my machine is similar to yours( HP Proliant > DL380G6, 4GB-RAM) This question is better asked on the xen-users list.

Hello..I am not very proficient in Linux kernel stuffs although I know my basics. I have a question and all suggestions/solutions will be highly appreciated... I got to know that RHEL 5 has inbuilt Xen Support...So I tried to install a RHEL 5.0 Server on my P4 machine. On top of it I tried to install Xen specific RPMs and some other RPMs needed by Xen. The additinal RPMs added after base

Hey list, I recently started working with kickstart. It is awesome! I really had no idea how easy it would be to use. I do have one strange issue, that's really not that important, but that I'd like to figure out. I like to watch all the kernel boot messages go by in text mode by default, and when I've set up a box in the past, I've modified grub's menu.lst file to remove

I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg | more do not show the pci=nomsi. How can this be? there are no strange characters after quiet and before pci=nomsi. It was edited with vi. What can I do to get this parameter in my kernel boot line. Jerry ----------------- default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS

Hey, I ran a yum update and it installed a new kernel. ?? ... ?? Installed: ??? kernel.x86_64 0:2.6.32-71.29.1.el6? kernel-devel.x86_64 0:2.6.32-71.29.1.el6 but it did not modify the grub.conf file. ? #boot=/dev/sda ? default=0 ? timeout=5 ? splashimage=(hd0,0)/grub/splash.xpm.gz ? hiddenmenu ? title CentOS (2.6.32-71.el6.x86_64) ?? ?????? root (hd0,0) ?? ?????? kernel

Hi all, I compiled and installed Xen 3.2 source on FC8. Compilation and installation completed with no errors. However when I try to load Xen I get an error: Kernel panic - Attempted to kill init !!! This is my grub configuration: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means

Hi all, Recently I build XEN 4.1 (from the xen.org) on centIOS 5.5 (kernel 2.6.38.4). After changing the grub file and rebooting the machine, I am continuously getting out of memory error. The content of my grub file: default=0 timeout=5 serial --unit=0 --speed=115200 terminal --timeout=10 console serial splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.38.4) root

Hello list, I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem. I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work. After setting up grub like this,

Hi: Any hints/pointers welcome. I am very new to Xen, I have a AMD "AMD Athlon(tm) 64 X2 Dual Core Processor 4000+" based system on which I am running X86_64 Fedora Core 8. I have installed Xen-3.1 on it, but I can''t get Xen to boot. It seems unable to find the root volume, the kernel panics and reboots immediately so I can''t capture or write down anything and I

Hi all, I've installed CentOS 4.4 in a box which previously had dual boot (XP SP2 and Ubuntu) I can run CentOS without problem but I can't boot XP SP2. When I try it the system simply hangs... [root at seth ~]# fdisk -l Disco /dev/hdb: 40.0 GB, 40020664320 bytes 255 cabezas, 63 sectores/pista, 4865 cilindros Unidades = cilindros de 16065 * 512 = 8225280 bytes Disposit. Boot Start

There was a discussion here several days ago that was precipitated by my decision to manually install the new kernel before YUMming the upgrade to CentOS 4.2. The upgrade went south but I recovered by doing a fresh install and a bunch of copying from backups. All's well EXCEPT that I'm back in the same "box", thanks to anaconda. I set out to upgrade kernels this morning:

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz

Hello List, I am testing a XCP1 CentOS 5 paravirt vm with CloudLinux. http://cloudlinux.com/ CloudLinux is a great product for shared hosting and I was evaluation same on a paravirt guest. I found a strange thing in XCP. CloudLinux provides xen kernel for DomUs and after installing the CloudLinux in a DomU it actually got 32 cpus inside. I had assigned only 2 vCPU to that DomU. To confirm this I

Hello List, I am testing a XCP1 CentOS 5 paravirt vm with CloudLinux. http://cloudlinux.com/ CloudLinux is a great product for shared hosting and I was evaluation same on a paravirt guest. I found a strange thing in XCP. CloudLinux provides xen kernel for DomUs and after installing the CloudLinux in a DomU it actually got 32 cpus inside. I had assigned only 2 vCPU to that DomU. To confirm this I