similar to: dom0 startproblem

I''m a newbie. :) I followed the steps written by Jerone Young: http://sourceforge.net/mailarchive/message.php?msg_id=10562241 but i found an error at the 17th step: 17. mkinitrd /boot/initrd-2.6.10-xen0.img 2.6.10-xen0 it said:"No module ata_piix found for kernel 2.6.10-xen0, aborting." so I commented the line of "module /boot/initrd-2.6.10-xen0.img" in the

Our newly build xen kernel does not boot. The error message is : Invalid or unsupported executable format. I have build xen from the xen-2.0.4 source (make world, make install) on a debian sarge system. I have not changed any of the kernel configurations, I did make an initrd image. The entry in my menu.lst is : title Debian GNU/Linux, kernel 2.6.10-xen0 root (hd0,0) #

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 have the following message while trying to boot xenlinux: ----------------------------------------------------- >Kernel Panic : Syncing no init found try passing init= option to kernel ------------------------------------------------------ My grub.conf is ------------------------------------------------------- title Xen 2.0 / XenLinux 2.6- 1th test root (hd0,1) kernel

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 installed 2.0.5 binary release of Xen in my FC3 , and below is my grub.conf ---- part of grub.conf -- title Fedora Core (2.6.10-1.766_FC3) root (hd0,7) kernel /vmlinuz-2.6.10-1.766_FC3 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.10-1.766_FC3.img title Xen 2.0 / XenLinux 2.6.10 root (hd0,7) kernel /boot/xen.gz dom0_mem=131072 module

Hi all, A number of people have posted to the Xen lists recently wanting to network-boot Xen on machines whose NICs are not supported by GRUB. I''ve been writing a module for PXELINUX that will allow it to boot Xen directly over the network on PXE-enabled machines, without relying on any hacks (mbootpack, &c.), or needing to write/port any device drivers. I have a version of it

Hi. I am trying to install xen 2.0.5 and am having problems getting the xen kernel to boot. It seems to come up, recognize the PCI bus info, the CPU, memory, and such, and then halts when it gets to trying to mount NFS. It then asks for a boot floppy. My guess is that it is not finding the / partition. The actual kernel panic string, I don''t have because the screen blanks so

Hi! I''m trying to run w83627hf_wdt.ko watchdog driver in domain 0 (xenlinux 2.6.10-xen0), but the driver doesn''t seem to work (the machine reboots all the time after the watchdog-timeout set in BIOS). Is there something that could prevent the driver from accessing the watchdog-hardware (io-ports/registers) ? The watchdog-driver is very simple, and you can find it in

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

Hi,   I am trying to build dom0 iso. I have following in my isolinux.cfg file. I see error: "Invalid or corrupt image file".   --- default 1 prompt 1 timeout 300 display menu.txt label 1   kernel boot/vmlinuz.vm   append boot/xen.gz  ramdisk_size=131072 initrd=boot/ramdisk.gz root=/dev/ram0 ---   The image I check is valid. xen.gz is actually xen-3.4.2.gz: xen.gz: gzip compressed data,

If this has already been done, please forgive me. However, if not, I''d like to submit this as a mechanism for generating a bootable grub2 stanza for hypervisors. As the /etc/grub.d/* files rely on defaults in /etc/default/grub, I added the following Xen specific variable: GRUB_CMDLINE_XEN_DEFAULT="console=com1 115200,8n1 dom0_mem=512M dom0_max_vcpus=1 dom0_vcpus_pin=true

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

I am currently using a Dell PowerEdge server R610 with Xen 4.0 installed and the 2.6.31.13 pvops kernel. I am accessing the server console using the iDRAC KVM feature of the dell management console. Does anyone know how to configure the console option in the grub menu so that all the boot messages can be seen on the mgmt console? Currently I can view only the Xen bootup messages if I dont specify

Hi all- I''m using Ubuntu 12.04 and compiled unstable on revision 25605:9950f2dc2ee6, the compilation completed cleanly and I issued sudo make install. I modified the grub entry for Xen 4.1 as follows: menuentry ''Ubuntu GNU/Linux, with Xen 4.2-unstable and Linux 3.2.19'' --class ubuntu --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2

    Question: can dom0 in Xen4.0 be rebooted (from domU or from within dom0) anytime without loosing anything ? If so, please provide details. If not, does Xen.org have this in roadmap ? The closest posting I found (old one) is: http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00885.html The option is parameter as below (but this grub conf) noreboot Debugging Requests that

Odd question I know. I am looking for source for as recent a kernel as possible running the old style xenlinux/xenified kernel (i.e. capable of running the xen3.3.x hypervisor). Any ideas where I can get this - preferably in git form? I think Stefano Stabellini had something that worked up to 2.6.36 (from memory). And yes, we would all prefer all our customers moved to xen4 but this is difficult

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