search for: rootdevic

From: Pino Toscano <ptoscano at redhat.com> Complementary fix of commit 2d25872df3619a3077006ad0f91c029602db6780. On SLES 11 SP4 with kdump enabled mkinitrd calls mkdumprd which calls mkinitrd, but mkdumprd doesn't have any clue of the root device. Call mkinitrd with rootdev environment variable to tell them all what device to use as root. Tested-By: C?dric Bosdonnat <cbosdonnat at

This is happening on anything other than plain vanilla Dell servers. One R730, with dual Tesla cards, one R420, with a fibre card for a RAID device, it never switches root. All these systems have Xeons, not AMD CPUs. We've had this with every one of the 327 kernels. In addition, it seems to happen also with the 229.20.1; the 229.14.1 has no such problem. >From the rdsosreport: starting

Hi, I'm writing some R code that requires a massive amount of looping and would ideally like to write it so that it avoid the use of "for" loop ... however I'm having some trouble. Very briefly, the basic idea is to implement a binary partitioning algorithm to determine the optimal cutpoint based on deviance measures obtained from likelihood estiamtes. This is in the

On Thu, 18 Feb 2016, m.roth at 5-cent.us wrote: > This is happening on anything other than plain vanilla Dell servers. One > R730, with dual Tesla cards, one R420, with a fibre card for a RAID > device, it never switches root. All these systems have Xeons, not AMD > CPUs. > > We've had this with every one of the 327 kernels. In addition, it seems to > happen also with the

Paul Heinlein wrote: > On Thu, 18 Feb 2016, m.roth at 5-cent.us wrote: > >> This is happening on anything other than plain vanilla Dell servers. One >> R730, with dual Tesla cards, one R420, with a fibre card for a RAID >> device, it never switches root. All these systems have Xeons, not AMD >> CPUs. >> >> We've had this with every one of the 327

The ‘vmware-uninstall-tools.pl’ script tries to rebuild the initrd. On SUSE, if kdump initrd has been enabled, this hangs because the ‘mkdumprd’ doesn't know what root device to use. Fix that by setting the ‘rootdev’ environment variable. --- v2v/convert_linux.ml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index

Hello All, Hardware: HP ML570 2G Ram Dual 2.8G procs Compaq 5300 Smart Array Controller Software: Centos 4.1 I yum-med a server last week and rebooted it. When it came up, it stopped. Looking at the console, I got: ---snip Setting Hostname: OK Checking root filesystem: /dev/cciss/c0d0p10 is mounted, e2fsck cannot continue, aborting failed *** an error occurred during the file system check

Hi to all. I''m installed XEN3.1 correctly but I''m some problem to start it. XEN start but I received this message: VFS: Cannot open root device "hda5" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) This is strange because my grub is configured like this:

Create the fedora-btrfs.img as an empty file. The only place this is used explicitly is tests/mountable/ test-mountable-inspect.sh, but that test already skips if !btrfs. Also this is used via guests-all-good.xml, but the script that creates this XML skips the file if it has zero size. --- test-data/phony-guests/make-fedora-img.pl | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2

[PATCH 1/7] mount: Add mount_vfs_nochroot This is significantly reworked from before. umount is gone as discussed, and variable motion is minimised. [PATCH 2/7] btrfs: Update btrfs_subvolume_list to take Already provisionally ACKed. Previous comment was that cleanup could be tidier. I looked into creating a new cleanup function for fs_buf, but it isn't possible (or simple, anyway) in this

Hi, this patch series attempt to uninstall VMware tools on all the Linux guests, and reduce the uninstallation time needed in some cases: - v2v tries to workaround the slowest part of the tarball-installed VMware tools - v2v uninstalls the open source VMware tools (open-vm-tools) Thanks, Pino Toscano (2): v2v: linux: remove open-vm-tools packages v2v: linux: try to trick

This series fixes inspection in the case that fstab contains references to md devices. I've made a few changes since the previous posting, which I've summarised below. [PATCH 1/8] build: Create an MD variant of the dummy Fedora image I've double checked that no timestamp is required in the Makefile. The script will not run a second time to build fedora-md2.img. [PATCH 2/8] build:

When installing the VMware tools from tarball, the installation script rebuilds the initramdisk of all the available kernels to inject the missing kernel drivers; in the end, the information on which kernels were changed is recorded in the internal "database" of the installation answers. When uninstalling the VMware tools, the uninstallation script reads the saved answers, and in the

I''d like to experiment with storing the boot archive on a compact flash that emulates an IDE hard disk, but then have the root pool on a 4-disk raidz set. (I''m using OpenSolaris) Anyone have suggestions on how to go about this? Will I need to set rootdev in /etc/system to tell the kernel the root device is different from the boot dev? Then what about "update-archive"

The attached patch breaks out the /dev/root device node creation from do_mounts, placing it in it's own utility (called mkrootdev). This is worthwhile, as certain setups will need the device node there to run fstype and load a proper module (or other things). No, it does not currently configure raid devices.... I didn't know if that made sense in there or not.... Let me know what you

Hi All, Could anybody tell me the creating of pv domain on nas. I mean to say that root file sytem should be at nas location. Useful links will be most welcome. Thanks, Trilok _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Patch v2 was here: https://www.redhat.com/archives/libguestfs/2019-April/thread.html#00114 There's no change here except that I've rebased it against the latest master branch and retested. There was a comment by Pino (https://www.redhat.com/archives/libguestfs/2019-April/msg00117.html) which isn't incorporated into this patch. Rich.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. I am trying to move the root volume from an existing svm mirror to a zfs root. The machine is a Sun V880 (SPARC) running nv_96, with OBP version 4.22.34 which is AFAICT the latest. The svm mirror was constructed as follows / d4 m 18GB d14 d14 s 35GB c1t0d0s0 d24 s 35GB c1t1d0s0 swap d3

Extend existing support for netdevice receive queue sysfs attributes to permit a device-specific attribute group. Initial use case for this support will be to allow the virtio-net device to export per-receive queue mergeable receive buffer size. Signed-off-by: Michael Dalton <mwdalton at google.com> --- include/linux/netdevice.h | 40 ++++++++++++++++++++++++++++++++++++---- net/core/dev.c

Extend existing support for netdevice receive queue sysfs attributes to permit a device-specific attribute group. Initial use case for this support will be to allow the virtio-net device to export per-receive queue mergeable receive buffer size. Signed-off-by: Michael Dalton <mwdalton at google.com> --- v3->v4: Simplify by removing loop in get_netdev_rx_queue_index.