search for: autodetected

Hi All, I'm currently trying to install centos 5.4 x86-64bit on a raid 1, so if one the 2 disks fails the server will still be available. i installed grub on /dev/sda using the advanced grub configuration option during the install. after the install is done i boot in linux rescue mode , chroot the filesystem and copy grub to both drives using: grub>root (hd0,0) grub>setup (hd0)

Hello all, I have 2 x 250GB sata disks (sda and sdb). # fdisk -l /dev/sda Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 14939 119997486 fd Linux raid autodetect /dev/sda2 14940 29878

In the guestfs_disk_create API we have traditionally allowed you to set backingfile without setting backingformat. The meaning of this is to let qemu autodetect the backing format when opening the overlay disk. However libvirt >= 6.0 refuses to even pass such disks to qemu (see https://bugzilla.redhat.com/show_bug.cgi?id=1798148). For this reason, move the autodetection earlier and make it

...2 image: base.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false # create overlay1.qcow2 via qemu-img; note how backing file format is autodetected ("-f qcow2" regards the overlay file itself) [root@singularity images]# qemu-img create -b /var/lib/libvirt/images/base.qcow2 overlay1.qcow2 -f qcow2 Formatting 'overlay1.qcow2', fmt=qcow2 size=8589934592 backing_file=/var/lib/libvirt/images/base.qcow2 cluster_size=65536 lazy_r...

...t intentional? Yes, I pushed it intentionally. Peter has a partial fix on the libvirt side, but it seems to me they are heading in the direction of requiring that the format of backing files in the chain being specified. Since our API specifies that a NULL backing format means the format will be autodetected (but not by what), I moved the detection to here. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many...

We're getting the below errors about once a day on a system we're trying to set up with RedHat 7.3. This has happened to multiple filesystems on multiple physical and logical disks (basically we've got 4 drives as 2 sets of RAID 1 arrays, details below). Until a week ago, this box was a high-volume IMAP server running RedHat 6.2 with uptimes in the 200-day range, so I don't

IMAP logins via fetchmail are failing on my mailserver root at grelber:/home/esr# tail -f /var/log/mail.err Nov 24 16:56:48 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/cathy Nov 24 16:56:48 grelber dovecot: IMAP(cathy): Fatal: Namespace initialization failed Nov 24 16:57:39 grelber dovecot: IMAP(cathy):

Ok, this patch replaces the old patch I sent, and it does a bit more. For one, it sorts the linked list of drivers based on the priority values, highest valued ones coming first. That allows the _find_default_driver_id code to stop looping (break) immediately when it finds a driver that works, because it already knows it's the working driver with the highest priority (what it normally

...I pushed it intentionally. Peter has a partial fix on the > libvirt side, but it seems to me they are heading in the direction of > requiring that the format of backing files in the chain being > specified. Since our API specifies that a NULL backing format means > the format will be autodetected (but not by what), I moved the > detection to here. One of the arguments was that using qemu-img to detect the format of an image was unsafe in any case, and thus libvirt does not use it (it has own parsing code). To sum up the situation: - if using qemu-img is safe (with more or less hardenin...

On Thursday, 6 February 2020 18:20:19 CET Richard W.M. Jones wrote: > In the guestfs_disk_create API we have traditionally allowed you to > set backingfile without setting backingformat. The meaning of this is > to let qemu autodetect the backing format when opening the overlay > disk. > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see >

...onally. Peter has a partial fix on the > > libvirt side, but it seems to me they are heading in the direction of > > requiring that the format of backing files in the chain being > > specified. Since our API specifies that a NULL backing format means > > the format will be autodetected (but not by what), I moved the > > detection to here. > > One of the arguments was that using qemu-img to detect the format of > an image was unsafe in any case, and thus libvirt does not use it > (it has own parsing code). > > To sum up the situation: > - if using qemu...

...partial fix on the > > > libvirt side, but it seems to me they are heading in the direction of > > > requiring that the format of backing files in the chain being > > > specified. Since our API specifies that a NULL backing format means > > > the format will be autodetected (but not by what), I moved the > > > detection to here. > > > > One of the arguments was that using qemu-img to detect the format of > > an image was unsafe in any case, and thus libvirt does not use it > > (it has own parsing code). > > > > To sum up...

Hello fellow CentOS'ers- I've got a system running CentOS 5.0. The motherboard has two onboard SATA ports with two drives attached. I installed the system on a RAID1 setup. However, I'd like to add a hotspare disk to the array. Since there are no additional SATA ports, I've installed an additional controller. After partitioning, the additional drive was easily and successfully

Hi, I'm currently experimenting with software RAID1 on a spare PC with two 40 GB hard disks. Normally, on a desktop PC with only one hard disk, I have a very simple partitioning scheme like this : /dev/hda1 80 MB /boot ext2 /dev/hda2 1 GB swap /dev/hda3 39 GB / ext3 Here's what I'd like to do. Partition a second hard disk (say, /dev/hdb) with three

Hi all, I have a dovecot v2.2.7 installation, and I would like dovecot to autocreate the Maildir mailbox when those mailboxes don't exist. Following the instructions at http://wiki2.dovecot.org/MailboxSettings have had no effect, the errors below are reported. As soon as I create the Maildir manually with maildirmake fetching mail starts working fine, so all of the messages about the

First let me say I am not a true expert, but I am experienced. If this machine you purchased was some name brand, you must be speaking about hardware raid, true? If this is true, it normally presents you with what looks like a standard drive (/dev/sda) for every 2 drives configured as raid-1. Also, most name brand servers give you a bootable machine day one. If you are using software raid,

I'm trying to setup a samba4 with openchange which uses postfix+dovecot+openldap on a ubuntu 12.04.2 system. I can send outgoing emails but incoming emails fail. I looked up the logs and I get: Mar 5 11:03:48 testerA dovecot: lda(sammy): Error: user sammy: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/var/mail Mar 5

https://bugzilla.samba.org/show_bug.cgi?id=6996 Summary: syncing backups - autodetect older variants already existing on receiver Product: rsync Version: 3.1.0 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

On Tue, Jun 27, 2017 at 07:42:20PM +0300, Pavel Butsykin wrote: > This feature allows you to use different image formats for the fixed > appliance. The raw format is used by default. I wonder if you're stil using this feature? Unfortunately because of a recent change in libvirt it is no longer possible to have a backing file where libvirt will autodetect the format. See: