similar to: Root-NFS: No NFS server available, giving up.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List, So I managed to get Xen 3.0.1 compiled and installed, but the machine failed to boot from the Xen kernel. The server's physically located at a Co-lo, so I'm having to rely on somebody on the other end to tell me what it's doing and saying. When I try to boot the -xen0 kernel, the screen fills up with Segmentation Faults and

Hello, I''ve got a problem to get a serial output on grub, xen, linux-xen0 and getty. The serial works fine with grub, xen and linux-xen0, but I''m unable to start a console, where I''m able to login. I dont''t get any output. If I change only the getty from ttyS0 to ttyS1 than I''m able to login.. At the attachment you can see what I see through a serial,

Good evening all, I''ve all but finished installing Xen 2.0.5, XenLinux 2.6.10 and Debian GNU/Linux 3.0r4 into /boot on a colo box currently (and temporarily) running CentOS. I''ve chrooted into the debian install (chroot /boot /bin/bash) and was able to set everything up, install requisite packages, install xen, etc. Now I''m at the last step and I''ve run into

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 #

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: grave Justification: renders package unusable When xend starts: [2006-05-22 22:07:18 xend] INFO (SrvDaemon:278) Xend Daemon started [2006-05-22 22:07:18 xend] INFO (SrvDaemon:282) Xend changeset: Thu Apr 27 09:58 :50 2006 +0100 . [2006-05-22 22:07:18 xend] ERROR (SrvDaemon:292) Exception starting xend ((111,

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

Preamble: dom0: Xen 3.0.4 running on Ubuntu 6.06 x86_64. domU: Xen 3.0.4 or 3.1.0 kernel booting from host pygrub. File backed. ------------- I am having this strange problem getting pygrub to load consistently. When I start a domU, I sometimes get this. Error: Boot loader didn''t return any data! ... and nothing else. When I look in the xend-debug.log log, I see this.

# Error facing :------ kernel panic - : not syncying , VFS : Unable to mount root fs on un-known block (3,5) ------------------------------------------------------------------------------------------------------ # Machine and kernel architecture:----------- Default Working installed kernel - vmlinux-2.6.5-7.97 Xen dom0 kernel - vmlinuz-2.6.12.6-xen0

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) #

Hi all, I am very interested in Xen and want to make some tests. However my problems as below: I built Xen on top of centOS from source according to user manual. To customize the set of kernels, I add KERNELS ?= linux-2.6-xen0 linux-2.6-xenU to the top-level in Makefile. And I updated grub.conf: title Xen 3.4.2 / XenLinux 2.6.18 root (hd0,0) kernel /xen-3.4.2.gz

I am unable to boot Dom0 on my IBM eServer BladeCenter HS20, type 8843, EMT64 blades. I have read reports that Dom0 boots on Opteron boxes, but on my EMT64 blades, it does not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1

Note: I''m familiar with gentoo distribution, but not with xen. A time has come, I desided, I need several xen virtual guests on my box (mostly because I want some personal web-applications installed on different environment that my desctop machine and desire to have ''playground'' for web-development attempts) What I have done 1) installed recent gentoo-sources (2.6.39),

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

I''m running xen 3.0.1 on the 2.6.12-26mdkxen0 mandriva kernel. (x86_64) When I set the serial line using the following configuration, my serial output is truncated as show in http://pastebin.ca/259403 title xen kernel (hd0,0)/xen.gz com1=115200n8 console=com1 xencons=serial module (hd0,0)/vmlinuz-2.6.12-26mdkxen0 root=/dev/sda2 module (hd0,0)/initrd-2.6.12-26mdkxen0.img The system is

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, 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

Hi everyone, I''m getting the following boot error, when installing xen-unstable on a dual opteron 246 machine, with a Tyan 2881 Motherboard, 4GB RAM, SATA Drive and ReiserFS filesystem. The machine is a Fedora Core 4. I installed the i386 FC4 on the dual opteron, I didn''t want the 64bit yet. All my binaries are 32bit and I''m compiling it all with 32bit too. After

> I'm getting crazy about ztdummy. I have to replicate a PBX where ztdummy > is working fine but for some reason I cannot. > The two machines have the same kernel, motherboard, the same gcc version > and the same zaptel 1.4.8. On the second machine zaptel compiles without > errors and ztdummy.ko is generated but when I modprobe it I get the > following error in messages: >

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

This is a really long email...my apologies. Hardware platform: Dell Poweredge 1855 (blade), Dual Xeon 2.8 GHz; 12 MB RAM; PERC 4/IM; mirrored 73 GB U320 SCSI; qLogic 2312 PCI Fibre Channel HBAs. OS: (currently) CentOS 4.3, gcc 3.4.5 Software: Xen 3.0.2-2 Attempting to boot off local SCSI RAID (mirror)...not the SAN. I am more of a Solaris person, so forgive me if I don''t know all