similar to: [rjones@redhat.com: Re: Suggestions on building VM disks from scratch]

I use python-guestfs to mount windows image it have some problems .Here is my code: [root@mfsdata1 ~]# python Python 2.6.6 (r266:84292, Sep 11 2012, 08:34:23) [GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import os >>> sheepfs_dir="/tmp/sheepfs"

trace: >>> g.inspect_os() libguestfs: trace: inspect_os libguestfs: trace: umount_all libguestfs: trace: umount_all = 0 libguestfs: trace: list_devices libguestfs: trace: list_devices = ["/dev/vda"] libguestfs: trace: vfs_type "/dev/vda" libguestfs: trace: vfs_type = "" libguestfs: trace: mount_ro "/dev/vda" "/" libguestfs: trace:

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

> On 30.06.2016 19:41, Erwan Velu via Syslinux wrote: > > The exisiting label= option offer to boot on a gpt partition that have > > a particular label. > > The existing guuid= option offer to boot on a disk or partition with a > > particular label. > > > > This new option offer to boot the disk that have a partition which > > have a given label. >

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512

This may not be the best forum to ask, but it does seem to be one where it is as likely as anywhere that someone will have dealt with a similar problem. I need to define a procedure for last resort disaster recovery from an incremental file level backup of the root partition (and any others that are critical.) Now it is easy enough to create a raw virtual disk with dd, then to losetup and do a

This may not be the best forum to ask, but it does seem to be one where it is as likely as anywhere that someone will have dealt with a similar problem. I need to define a procedure for last resort disaster recovery from an incremental file level backup of the root partition (and any others that are critical.) Now it is easy enough to create a raw virtual disk with dd, then to losetup and do a

Greetings - I am going through some testing steps to expand a logical volume and the corresponding filesystem on a KVM guest and have run across a deficiency in my knowledge. I spent the afternoon yesterday googling for answers, but had have come up blank still. What I am trying to do is resize the file system to use the additional disk space that I added to the logical volume that the

Hi,everyone: As the subject says, why chinese characters are shown as '?' by using ls function? Did anyone encounter the same problem and does resolution exist? Looking forward to your reply. Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 3/5/2017 10:41 ??, Marcelo Roccasalva wrote: > Does the UUID of root filesystem in /etc/fstab match the actual UUID > as reported by blkid? And remove/etc/lvm/cache/.cache if it exists Thank you Marcelo for replying, The directory /etc/lvm/cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs"

Hi, Sorry for the long delay. It prints exactly the same: [ 3.792033] virtqueue elements = 128, max_segments = 126 (1 queues) [ 3.802191] vda: vda1 vda2 < vda5 > A little bit more about my setup (if it helps): It's a qemu-system-x86_64 kvm instance with 16 cores and 10G of RAM. I can reproduce the bug every time with mkfs.btrfs on a 10GB LVM volume (right after the reboot). I

Hi, Sorry for the long delay. It prints exactly the same: [ 3.792033] virtqueue elements = 128, max_segments = 126 (1 queues) [ 3.802191] vda: vda1 vda2 < vda5 > A little bit more about my setup (if it helps): It's a qemu-system-x86_64 kvm instance with 16 cores and 10G of RAM. I can reproduce the bug every time with mkfs.btrfs on a 10GB LVM volume (right after the reboot). I

On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were

On Fri, May 5, 2017 at 2:38 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 3:15 ??, Gianluca Cecchi wrote: > > ... >> grub2-install /dev/vda >> ... >> Was this one of the command you already tried? >> > > Yes, I have tried that multiple times, both from Troubleshooting Mode > (booting using CentOS 7 Installation CD) and from within the

-----Original Message----- From: Richard W.M. Jones [mailto:rjones@redhat.com] Sent: Tuesday, January 14, 2014 4:42 PM To: Исаев Виталий Анатольевич Cc: libguestfs@redhat.com Subject: Re: [Libguestfs] Libguestfs can't launch with one of the disk images in the RHEV cluster On Tue, Jan 14, 2014 at 08:07:43AM +0000, Исаев Виталий Анатольевич wrote: > [00072ms] /usr/libexec/qemu-kvm \

Fix for: https://bugzilla.redhat.com/show_bug.cgi?id=619793 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part

The exisiting label= option offer to boot on a gpt partition that have a particular label. The existing guuid= option offer to boot on a disk or partition with a particular label. This new option offer to boot the disk that have a partition which have a given label. The label is so just a way to detect a disk to boot. A typical use is for making an intelligent localboot like : label

Hi All, We've had a report[1] of the virt_blk driver causing a lot of spew because it's calling a sleeping function from an invalid context. The backtrace is below. This is with kernel v3.16-rc2-69-gd91d66e88ea9. The reporter is on CC and can give you relevant details. josh [1] https://bugzilla.redhat.com/show_bug.cgi?id=1113805 [drm] Initialized bochs-drm 1.0.0 20130925 for

Hi All, We've had a report[1] of the virt_blk driver causing a lot of spew because it's calling a sleeping function from an invalid context. The backtrace is below. This is with kernel v3.16-rc2-69-gd91d66e88ea9. The reporter is on CC and can give you relevant details. josh [1] https://bugzilla.redhat.com/show_bug.cgi?id=1113805 [drm] Initialized bochs-drm 1.0.0 20130925 for

On Fri, May 5, 2017 at 2:05 PM, Bernard Lheureux < bernard.lheureux at bbsoft4.org> wrote: > On 05/05/2017 12:57, Gianluca Cecchi wrote: > > grub-install /dev/vda2 didn't work ? > > As this is a CentOS 7.x system, I would say this, if you want to install it on MBR: grub2-install /dev/vda as detailed here: