similar to: Strange Fedora Booting problem: can not mount "LABEL=*"partitions

Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu

On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >Hello, > >I use libvirt 3.3.0 and qemu 2.9.0 > >My domain XML spec is the following: > ><domain type='qemu'> > <name>s390_generic</name> > <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> > <memory unit='KiB'>1048576</memory> >

2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: > 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >> On Fri, Oct 20, 2017 at 03:07:19PM +0300, Matwey V. Kornilov wrote: >>> >>> 2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>>> >>>> On Thu, Oct 19, 2017 at

https://bugzilla.samba.org/show_bug.cgi?id=9995 Summary: Rsync 3.1 dev : Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: dochitoai.vu at ladhyx.polytechnique.fr

Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu

I've put some thought into adding DB support to rsync (in a future release). This would allow it to maintain some extra information about files and be able to lookup information rapidly. This would support things like caching of checksum information, finding files to hard-link with, saving file attributes separately from the files (allowing non-root preservation of full file attributes as

mkfs.c: In function ‘is_ssd’: mkfs.c:1168:26: warning: ignoring return value of ‘blkid_devno_to_wholedisk’, declared with attribute warn_unused_result [-Wunused-result] blkid_devno_to_wholedisk(devno, wholedisk, sizeof(wholedisk), NULL); Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com> --- mkfs.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/mkfs.c

2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >> >> Hello, >> >> I use libvirt 3.3.0 and qemu 2.9.0 >> >> My domain XML spec is the following: >> >> <domain type='qemu'> >> <name>s390_generic</name> >>

2017-10-24 12:58 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >> >> 2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >>> >>> 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>>> >>>> On Fri, Oct 20, 2017

2017-10-25 17:28 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: > 2017-10-24 12:58 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >> On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >>> >>> 2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >>>> >>>> 2017-10-20 15:16

I agree. This line was removed during testing because it didn't make big sense (EFLAGS_CF, ebx, and ecx are checked after int 0x13). But it's better to leave it in code to make sure that BIOS conforms standards and clears CF flag on successful call. Adjusted patch is given below. Andy Alex Signed-off-by: Andy Alex <andy at r-tt.com> --- diff -uprN

At Tue, 29 May 2018 08:10:39 -0400 (EDT) CentOS mailing list <centos at centos.org> wrote: > > > At Mon, 28 May 2018 20:49:54 -0700 CentOS mailing list <centos at centos.org> wrote: > > > > > On 05/28/2018 06:20 PM, Robert Heller wrote: > > > The UUID in the BIOS is NOT VFAT volume. It is something completely > > > different. I have no

At Mon, 28 May 2018 20:49:54 -0700 CentOS mailing list <centos at centos.org> wrote: > > On 05/28/2018 06:20 PM, Robert Heller wrote: > > The UUID in the BIOS is NOT VFAT volume. It is something completely > > different. I have no clue what it is -- it does not correspond to anything I > > can find. > > > It should be the UUID of the partition, not of

From: Raphael S. Carvalho <raphael.scarv at gmail.com> MULTIFS SYNTAX: (hd[disk number]:[partition number])/path/to/file The meaning of this_fs was changed to improve the flexibility of the support. Now, this_fs means the file system being currently used. root_fs was created to save the context of the main file system (where ldlinux.sys lives in). get_fs_info is a function pointer that

DL register is not set to drive number when detecting EDD for drive, so detection may fail. Signed-off-by: Andy Alex<andy at r-tt.com> --- diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 +++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-20 12:15:08.000000000 +0400 @@ -337,7

On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >> 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>> On Fri, Oct 20, 2017 at 03:07:19PM +0300, Matwey V. Kornilov wrote: >>>> >>>> 2017-10-20 14:59 GMT+03:00 Martin Kletzander

Op 2014-02-20 om 13:23 schreef Andy Alex: > DL register is not set to drive number when detecting EDD for drive, so detection may fail. > > Signed-off-by: Andy Alex<andy at r-tt.com> > --- > diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c > --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 > +++

blkid_probe_get_wholedisk_devno() isn''t available in some older versions of libblkid. It was used to work around an old bug in blkid_devno_to_wholedisk(), but that has been fixed since 5cd0823 libblkid: fix blkid_devno_to_wholedisk(), present in util-linux 2.17 and beyond. If we happen to be missing that fix, the worst that happens is that we''d fail to detect that a device is

On Mon, 2015-06-15 at 21:41 -0500, Robert Nichols wrote: > Non-GPT partitions do not have a UUID. The _content_ (filesystem, > LVM physical volume, non-encrypted swap space, etc.) of such a > partition could have a UUID, but the partition itself does not. ON Centos 5, using GPARTED I created partitions for filing systems ext3 and ext4. 4 primary and unlimited (except by space) extended

Hi, Stephen and Jeff, Thanks. But the problem got debugged&fixed, the answer was post on fedora-list about 2 weeks ago. The problem is: the /etc/blkid.tab file works as an old unappropriate disk partitions cache for fsck|blkid commands when stystem image is installed to a different arch (scsi->ide) machine, the old cache will mislead fsck|blkid at the first run and only the first run,