similar to: [PATCH node] fix mount_live again

use /dev/loop0 only when it really contains LiveCD ISO. mount_live should fail silently when LiveCD ISO is not available, which is the case on boot from HostVG/Root. Resolves: rhbz#508425 --- scripts/ovirt-functions | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) mode change 100755 => 100644 scripts/ovirt-functions diff --git a/scripts/ovirt-functions b/scripts/ovirt-functions

This completes the switch to ext3 backed root partitions. /boot is now contained on each Root/RootBackup partition. On install grub is updated to read and boot from the correct partition as well. --- scripts/ovirt-config-boot | 29 ++++++++++++------------ scripts/ovirt-config-storage | 47 +++++++++++---------------------------- scripts/ovirt-config-uninstall | 5 +---

Putting these out for feedback and comments. These will eventually support the new newt/python based ui for installation/configuration storage.py functions will be moved under a class for better data portability before final version --- scripts/ovirtfunctions.py | 672 +++++++++++++++++++++++++++++++++++++++++++++ scripts/storage.py | 451 ++++++++++++++++++++++++++++++ 2 files

This patch includes feedback from apevec to remain backward compatible with the previous karg, ovirt_local_boot.

This patch allows the node to be upgraded without destroying any configuration. The new kernel argument, ovirt_upgrade, will boot cause the node to install the upgraded image, then reboot. Resolves: rhbz#527217 Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-early | 14 +++++++------- scripts/ovirt-firstboot | 22 +++++++++++++---------

Resending the refactored patch: I realized after I emailed it that it referenced the wrong bugzilla.

Added a new function, "ask_yes_or_no", to ovirt-functions. It contains a default prompt if none is provided. Changed all prompts that ask for yes, no and/or abort to use this new method. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-boot-wrapper | 8 ++--- scripts/ovirt-config-collectd | 39 +++++++++++++++-----------

I'm looking for feedback on this first patch. The node has been pushed towards a more generic boot process. With this patch the node can now boot up and execute a few specifically-named scripts that reside in /etc/node.d/ at key points during the startup. After this goes upstream, the next step will be to define in more detail the remote interfaces for the "managed" runtime

This patch obsoletes the previous, renaming the karg to ssh_pwauth.

This patch obsoletes the previous one with feedback from pmyers at redhat.com.

This patch supercedes the previous one by moving the functionality for relocating files into the make system.

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]

Following is one grub entry menuentry "Ubuntu, Linux 2.6.32.27" { insmod ntfs set root=''(hd0,2)'' search --no-floppy --fs-uuid --set 96f65c80f65c6313 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) linux /boot/vmlinuz-2.6.32.27 root=/dev/sda2 loop=/ubuntu/disks/root.disk ro quiet splash initrd

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

Hi! I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here''s exactly what I''ve done: $ dd if=/dev/zero of=raid1_0.img bs=1M count=500 $ dd if=/dev/zero of=raid1_1.img bs=1M count=500 $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img $ losetup /dev/loop0 raid1_0.img $ losetup /dev/loop1 raid1_1.img $ mount -t

hi there i try to setup OCFS2 with loop device /dev/loop0 i've 4 servers running SLES10 SP2. internal ip's: 192.168.55.1, .2, .3 and .6 my cluster.conf: -------------------------------------------- node: ip_port = 7777 ip_address = 192.168.55.1 number = 0 name = www cluster = cawww node: ip_port = 7777 ip_address = 192.168.55.2

Thanks: Steven Rosenberg --- v2v/windows_virtio.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/windows_virtio.ml b/v2v/windows_virtio.ml index 59b0bf493..56c7a6757 100644 --- a/v2v/windows_virtio.ml +++ b/v2v/windows_virtio.ml @@ -338,7 +338,7 @@ and copy_from_virtio_win g inspect srcdir destdir filter missing = ) paths ) ) - else if is_regular_file

I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all

Hi all. I''ve got a domU that exists in a sparse file image, I''d like to now use this on a physical partition (loopback performance issues). Is there an a easy way to do this ? Thanks Stuart _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

When adding orphans to an inode''s root, we start a transaction for that root that when ended in several places such as for example extent-tree.c:btrfs_remove_block_group(), inode.c:btrfs_unlink() and inode.c:btrfs_evict_node(), doesn''t result in a commit, that is, inode.c:btrfs_orphan_commit_root() doesn''t get called (via transaction.c:commit_fs_roots()). The respective