It implies only debu for qemu-img operations.
To make the log configuration persistent, you will need to edit the file
/etc/vdsm/logger.conf :
1 . Insert qemu at the end of the list in the loggers entry
[loggers]
keys=root,vds,storage,virt,ovirt_hosted_engine_ha,ovirt_hosted_engine_ha_config,IOPr
On Wed, Jun 28, 2017 at 1:14 PM, Fred Rolland wrote:
>
> Hi,
>
> Yes, the /etc/vdsm/logger.conf contains log level settings for most of the
> operations, but not all.
>
> You can use vdsm-client to enable logging :
>
> vdsm-client Host setLogLevel level=DEBUG name=QemuImg
>
>
>
Thanks.
The vdsm-
On Wed, Jun 28, 2017 at 8:48 AM, Fred Rolland wrote:
> Hi,
>
> The qemu operation progress is parsed [1] and is printed on debug level in
> Vdsm log [2].
>
Where should I see this information: vdsm.log ?
It seems I see nothing. Could it depend on settings in
/etc/vdsm/logger.conf ?
Which part
Hi,
The qemu operation progress is parsed [1] and is printed on debug level in
Vdsm log [2].
In the UI, a progress indication of the operation is available on the disks
status for the "Move Disk" operation.
Currently only for this operation.
Regards,
Fred
[1]
https://github.com/oVirt/vdsm/blob
On Tue, Jun 27, 2017 at 3:09 PM, InterNetX - Juergen Gotteswinter <
j...@internetx.com> wrote:
>
> > >
> > > Suppose I have one 500Gb thin provisioned disk
> > > Why can I indirectly see that the actual size is 300Gb only in
> Snapshots
> > > tab --> Disks of its VM ?
> >
> > i
> >
> > Suppose I have one 500Gb thin provisioned disk
> > Why can I indirectly see that the actual size is 300Gb only in Snapshots
> > tab --> Disks of its VM ?
>
> if you are using live storage migration, ovirt creates a qcow/lvm
> snapshot of the vm block device. but fo
On Tue, Jun 27, 2017 at 1:37 PM, InterNetX - Juergen Gotteswinter <
j...@internetx.com> wrote:
>
>
> Am 27.06.2017 um 11:27 schrieb Gianluca Cecchi:
> > Hello,
> > I have a storage domain that I have to empty, moving its disks to
> > another storage domain,
> >
> > Both source and target domains a
On Tue, Jun 27, 2017 at 12:37 PM, InterNetX - Juergen Gotteswinter <
j...@internetx.com> wrote:
>
>
> Am 27.06.2017 um 11:27 schrieb Gianluca Cecchi:
> > Hello,
> > I have a storage domain that I have to empty, moving its disks to
> > another storage domain,
> >
> > Both source and target domains
Am 27.06.2017 um 11:27 schrieb Gianluca Cecchi:
> Hello,
> I have a storage domain that I have to empty, moving its disks to
> another storage domain,
>
> Both source and target domains are iSCSI
> What is the behavior in case of preallocated and thin provisioned disk?
> Are they preserved with
9 matches
Mail list logo
