similar to: Boot problem: gave up waiting for root device

Hi I have a problem booting dom0 on Xen 3.1 under 2.6.18 kernel. At system start I obtain the next message: gave up waiting for root device. common problems: boot args (cat /proc/cmdline) check rootdelay= (did the system wait long enough?) check root= (did the system wait for the righ device?) missing modules (cat /proc/modules: ls /dev) /dev/sd* are not present in /dev dir and

After successful creation of the Xen kernel and entry into grub, whenever I try and boot into the Xen kernel I receive the following error: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat

Hello, someone used trixbox domU with xen? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, I compiled xen on ubuntu, but at the bot i got the kernel panic message. I enabled the support to ext4 fs. This is kernel panic error: EXT3-fs: unable to read superblock ETX4-fs (md0): unable to read superblock FAT: unable to read boot vector Kernel panic - not syncing: VFS: Unable to read superblock(9,8) My grub.cfg generated by update-grup: menuentry ''Ubuntu, with Linux

Hi Konrad, I just tried linux-3.4-rc0 (linus his tree, last commit f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your tree pulled on top of that: branch stable/for-ingo-3.4.v2 (required for dom0 to boot) branch stable/for-jens-3.4 branch stable/for-jens-3.4-bugfixes Hypervisor is xen-4.1.3-rc1-pre linux 3.3 vanilla works fine Booting dom0 goes fine, but

Hello again, I'm always not able to boot-up my CF-FileSystem. (It works with a 2.4.x Kernel!) See: http://syslinux.zytor.com/archives/2006-June/006942.html I dont't understand, why the kernel can't mount the root-fs on exit of "linuxrc". Before finising "linuxrc" I can work on it, start a "bash"-shell, do all sorts of linux-cmds on the root-fs...

Would it be possible to append the device syslinux booted from to /proc/cmdline? It would be nice to have a method of grepping /proc and /sys to locate the correct boot device for a LiveCD/USB instead of looking for it or manually appending it to the cfg file. I'm the creator of Parted Magic and people are starting to do odd things with it. They will boot the CD and have Parted Magic on a USB

Hi, I'm wondering when /proc/cmdline has "root=/dev/mtdblockX", name_to_dev_t_real will return __makedev(0,254) for root device's device number which is weired. I think we need to create the device on the fly from information in sysfs. Maybe I have mistaken something. Is there any clue? -- Regards, Shizheng -------------- next part -------------- An HTML attachment was

Hi all, i am having some problem with making blktap2 to work on ubuntu 12.04 can you please help me on this. Created PV guest ubuntu 12.04 64 bit on dom0 running Ubuntu 12.04 with initial configuration *[''file:/VM/vm-images/para-ubuntu.img,xvda,w''] * but after installing and booting vm,changed to blktap2 after installing its drivers on dom0 and made these changes to

Hello! I have testing new xen 4.1.0 with Debian Wheezy. I have an strange problem. When I try to boot the DomU with disks in local img works Ok: disk=[''file:/VMs/plantilla-squeeze-disk.img,xvda1,w'', ''file:/VMs/plantilla-squeeze-swap.img,xvda2,w''] but when I try to boot with the same disk offered with iSCSI: (open-iscsi, login, ...)

[quoted lines from Ady Ady]: > At this time, Syslinux by itself cannot boot files located on a > different filesystem volume. > Using chain.c32, you can load a boot sector (MBR or VBR) located on > another device. Since the list of files located in your boot stick did > not include chain.c32, my assumption (and not only mine, if you > carefully read some of the prior

Dear All, Can''t start system because kernel can''t load file systems to and get the next error: modprobe: can''t load module microcode (kernel/arch/x86/kernel/microcode.ko): No such device done. Begin: Running /scripts/init-premount ... Begin: Requesting microcode update using per-core interface ... done. done. Begin: Mounting root file system ... Begin: Running

This patch adds the ability to mount filesystems via an embedded fstab or via the kernel command line. When using the kernel command-line, the following format is required: 'kinit_mount=<fs_name>;<fs_dir>;<fs_type>;<fs_opts>' Multiple mount options can be specified; they are evaluated in the order they appear in the command-line. Signed-off-by: San Mehat <san

Hello, The attached l32or64.c implements a com32 module that boots two different kernels with different initrds depending on whether the cpu has long mode support or not. I stumbled upon two problems while developing it with current git version (last commit 595705ffad4f63cfeb84e9bb1243df03808c2fff). The first was that syslinux_boot_linux didn't work for me. Both the command line and initrd

Hello, I guess it possible distro specific issue but is it resolvable? I have one node(testing purpose) ganeti 2.0.1 cluster installed over Debian5 Lenny. Almost everything from distro repositories. Only ganeti 2.0.1 and ganeti-debootstrap are from sources. I have it successful run with vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686 from repositories. Both Dom0 and DomU are use the

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

--- init/init.c | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/init/init.c b/init/init.c index 473a5c5..a6279b8 100644 --- a/init/init.c +++ b/init/init.c @@ -101,13 +101,19 @@ main () char *root, *path; size_t len; int dax = 0; - uint64_t delay_ns = 250000; + uint64_t delay_ns; int virtio_message = 0; - struct timespec t; int major,

On Wed, Apr 19, 2017 at 10:57:28AM +0100, Richard W.M. Jones wrote: > + struct timespec t; > +#define NANOSLEEP(ns) do { \ > + t.tv_sec = delay_ns / 1000000000; \ > + t.tv_nsec = delay_ns % 1000000000; \ > + nanosleep (&t, NULL); \ > + } while(0) > + Defining 't' outside its context is a bit

I have a project that disk imaging from a cd using isolinux and a dialog gui system, but some users want to setup systems to run automatically. Some can download the development kit, and built an image with a modified script, but others don't have the skills or resources. I've come up with a system that seems to work with both the isolinux.cfg or menu.lst with grub4dos and I believe

On Mon, Jul 2, 2018 at 7:53 PM, Ulf Volmer <u.volmer at u-v.de> wrote: > On 02.07.2018 18:23, Thomas Schweikle wrote: > >> System boots into emergency mode because it does not find any of the >> logical volumes defined, because it does not enable the LVM volume >> group. >> >> Giving "lvm", then "vgchange -a y", followed by CTRL-D