similar to: kernel panic - Init problems

I am installing Xen on a remote server. I left the other kernels on the grub.conf and made xen the default to boot from. The box didn''t boot into Xen on reboot but I''m not sure why. Here is my Xen config file: # 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 that #

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

Hi, I''ve installed xen-2.0.5 from source on gentoo, but the xen dom0 kernel doesn''t find the root device: ############################# snip ###################################### Kernel panic: VFS: Unable to mount root fs on unknown-block (3,3) ############################# snap ###################################### grub.conf: ############################# snip

Hello All, I finally compiled xen 3.3.0 using make World, installed it but I cannot get it to Boot, I always get kernel panic, kernel not sync kind of errors, I suppose it''s some hard disk or partition issue, my setup is as follows. CentOS 5.2 x86_64 on a HP ML-115 Grub, menu.list Entries CentOS xen''s line title CentOS (2.6.18-92.1.22.el5xen) root

Hi, I recently compiled a Xen-4.0.1 and pv-ops Dom0 2.6.32.27 kernel from JF''s tree.Where my hypervisor could not boot and unfortunately the system is rebooting so frequently that I am not able to note down the error messages on a paper and pencil.So now I am planning to go for a non pv-ops Dom0.I am not clear as what should be the approach? I have been Googling it every now and then and

Hello, I''ve tried all the install directions, all the wiki howtos, etc, and haven''t been able to startup a Xen domain 0 properly. So far i''ve tried: - install from binary (2.6.11.12) - install from source (2.6.11.12) - aptitude install xen-system (2.6.11.12) and they all hang when trying to boot. Here''s my typical grub entry: title Debian

The Xen boot option ''ser_baud=<baud>'' has been removed from the unstable tree. If you were still using this obsolete option then the effect is that you will get no serial output when you boot Xen, which may lead you to believe that there is a more serious problem. To fix this you must move to the new boot option: ''com1=<baud>,8n1'' -- Keir

On 03/21/2017 07:48 AM, PJ Welsh wrote: > On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis > <ricardo at palmtx.com.ar <mailto:ricardo at palmtx.com.ar>> wrote: > > El Lunes 20/03/2017, PJ Welsh escribi?: > > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > > Thanks > > PJ > > Edit grub's entry

El Lunes 20/03/2017, PJ Welsh escribi?: > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it. > On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes <johnny at centos.org> wrote: > > On

I am using Xen 3.3 from source. My PV guest boots fine with the normal kernel and initrd options When I boot the guest with PV GRUB I only get: GNU GRUB version 0.97 (65536K lower / 0K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible

Hello, I have a big startproblem with the dom0 kernel. I use the latest stable xen with the 2.6.10 kernel. menu.lst: --- title Xen 2.05 / XenLinux 2.6.10 kernel /boot/xen.gz dom0_mem=512M noreboot module /boot/vmlinuz-2.6.10-xen0 root=/dev/sda1 ro console=tty0 --- Starterror: --- (XEN) Initial guest OS requires too much space (XEN) (8MB is greater than 0MB limit) --- System: I use an fresh

Hi, How do I map certain pci devices directly into a user domain? Has anybody done this? Any leads would be appreciated. thanks deepak _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

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

Background: This is a dual boot (Windows XP and CentOS 5.2 (32 bit) box. There were four (4) NTFS partitions. The C partition got full. I deleted the 4 NTFS partitions and did a clean install of Windows XP, into one (1) NTFS partition. I knew that I would need to install GRUB again and I did that, using the CentOS 5 Installation DVD. When I tried to boot into Linux, no joy. this is the GRUB error

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,

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

hi, i red several mails, but didn''t found a real solution. I want to install hylafax in DomU and i need access to /dev/ttyS1. I hide com2 in grub: title Xen 2.0 / XenLinux 2.6.11 kernel /boot/xen.gz dom0_mem=64000 physdev_dom0_hide=''(00:2f.8)'' max_loop=32 module /boot/xen-linux-2.6.11.12-xen0.xen.kernel root=/dev/hda2 ro i used the entries from dmesg: Serial:

Hi, This morning one of my servers (centos 4.5) refused to boot. The console shows a lopp message grub loading stage2... I've been able to boot from the install CD choosing the rescue option. I can chroot /mnt/sysimage with no problems and even started the services (network, mysql , httpd etc). How can I solve this? I've followed the manual (

Hi, I have a problem with compilation my own kernel with the xen-2.0-testing package. I use this packadge because there are drivers for the nforce2 nic called fordedeth. I do the following: wget xen-2.0-testing-src.tgz tar xvfz xen-2.0-testing-src.tgz cd xen-2.0-testing make world ( The first compilation show now errors and build all kernels. ) cd linux-2.6.11-xen0 make clean make ARCH=xen