similar to: Is RAMDISK required for domU boot?

Hello, i will describe my approach 1) I have downloaded Centos5-64bit xen image from jailtime.org 2) I have created own swap image with 512MB file size 3) I have used same as dom0 kernel 2.6.18-53.1.19.el5xen 4) I have mounted my image file and copied /lib/modules/2.6.18-53.1.19.el5xen 5) I have created custom ramdisk for domU with mkinitrd --with=xennet --preload=xenblk

Maybe this question is a little stupid, but please help me. I am a newbie to Xen. When I tried to create a new domain "domain 1", I followed the Yan-Ching CHU''s guide on :installing quick file systems for new domains in Xen 1.2". But when I do "xc_dom_create.py -Dvmid=1", Xen seems to start to boot with some normal bootup information, but right after several

I am having an issue getting a DomU to boot properly. There is never any indication of a stop error or kernel panic, it simply hangs after "Starting crond [ OK ]" and never continues. I''ve included my mkinitrd and output from xm create... please help! ##### XENBUS errors ##### XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050

Ok So I''ve been able to successfully create a CentOS5 virt-install on xen using LVM created partitions. But have many problems trying to install 4.4 (It does not work with virt-install hence you have to try another method). I Created a name, name-tmp, name-swap, name-root paritions. I did mke2fs and mkswap no problem everything is good. I went on further to mount the name-tmp and

Hello, I am getting kernel panic while trying to xm create a domU. Xen version 3.0 Linux kernel 2.6.12.6 Grub entry for dom0: title Xen 3.0 / XenLinux 2.6 kernel /boot/xen- 3.0.gz console=vga module /boot/vmlinuz-2.6-xen0 root=LABEL=/ ro console=tty0 module /boot/initrd-2.6.12.6-xen0.img For domU, my xm file contains: kernel = "/boot/vmlinuz-2.6.12.6-xenU "

Hello, Maybe someone can help me.... I have a guest XEN image that ran well until today. I use an LVM partition to host the guest and today on Dom0 I added another LVM to be available to this domU. This were all the commands I issued : On hypervisor lvcreate -n lintra02data -L 30G rootvg vi /etc/xen/lintra02 and add volume to file like this : disk = [

Hello everyone, I''m quite a newbie with Xen and I''m currently having an issue. I run Xen 4 on Debian Squeeze x64 and I''m trying to build an OpenFiler DomU from the Xen domU filesystem tarbal they provide (See http://www.openfiler.com/community/download/). I downloaded the tarball and run ''tar xzpvf /root/soft/openfiler-2.3-x86_64.tar.gz'' to extract

more /etc/xen/scalix2 kernel="/boot/vmlinuz-2.6.18-8.1.6.el5xen" memory = 512 name = "hating-xen" vif = [''ip = "10.0.1.150", bridge=xenbr0''] disk = [ ''/dev/XEN/scalixroot,sda1,w'', ''/dev/XEN/scalixvar,sda3,w'', ''/dev/XEN/scalixswap,sda2,w'' ] It

?Not sure if this actually made it to the list the first time.? Here is the SERIAL output (bottom of message after your questions).? Googling the error indicates it's something people ran into a few years back but was supposedly fixed.? Any ideas? I can verify that if I REMOVE the second CPU, it boots into Xen kernel no problem.? The CPU itself doesn't matter, as I can swap either

Hi all- I''m hoping someone can help me with this problem with Xen under CentOS 5.1 (RHEL 5.1) I''m having... This is the Xen package that comes stock with the distribution, I didn''t compile it from source. I can boot Domain0 and the hypervisor just fine. I''m trying to bring up a Xen guest VM and it crashes on boot, with this error: # xm create -c tcga1

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

Hello, I have a problem with a 2.5.62 kernel and ramdisk. I am using isolinux to create a cd that loads some of its partition in ramdisk. The script involves mounting a ramdisk (e2fs) on /fake/ramdisk, copying part of the cd to that mount point, unmounting it, and remounting it on /fake/needwrite. The problem is that, although the content of /fake/needwrite gets correctly copied, the content of

Hi everyone! I came across a problem when I used xm create to create a domainU on my machine. I installed xen-3.0.4 on my computer, running Fedora 6, kernel version is 2.6.18-1.2798.fc. I want to install a Fedora 6 on xen, so I write the following config file, named fc6.cfg kernel = "/boot/vmlinuz-2.6.16.33-xenU" memory = 128 name = "fedora.fc6" dhcp = "dhcp" disk =

This patch (against unstable) makes sure that the skel/etc/init.d/rcS file is executable before building the final ramdisk image. This should fix the problem some people are having with their ramdisk builds. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com _______________________________________________ Xen-devel mailing list

Hello! I'd like to load a ramdisk with syslinux, but from another disk. And I've found this in the syslinux faq: "An initrd is loaded from a DOS file if the option "initrd=filename" (where filename is the filename of the initrd image; the file must be located in the root directory on the boot floppy)"

Way are not a ramdisk included with the images from jailtime.org That seems this is needed _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I'm having loads of problems with recordings, as in crappy audio quality and lost pieces of the recordings. I've been searching for a solution and the solutions i find on the interwebs include a ramdisk, for local recording, or another machine, handling the recording. I guess the ramdisk would be the "easy" solution and the external machine would be little harder to set up. I do

I'm supporting a number of consumer devices (e.g. small NAS devices) in Debian. They typically don't export the serial console and don't have any other output devices. We perform the installation via SSH on such devices and start SSH automatically when the system boots so people can login. This works pretty well but sometimes a device stops to boot for no good reason. This is

On Centos 4.x 32 I want to create like a 64Mbyte ramdisk. Is there a problem putting 30k to 80k empty files on a ramdisk? Is there a simple howto on creating a ramdisk that anyone knows of off the top of there head? Matt