maybe it is easier to use cron
Marcos
Em Terça-feira, 21 de Fevereiro de 2017 15:28, Aleksei
escreveu:
It doesn't seem to be implemented in libvirt's XML. You can still try and
hack it though:
It will mark this domain "tainted" in libvirt's log.
--Regards, Alek
It doesn't seem to be implemented in libvirt's XML.
You can still try and hack it though:
It will mark this domain "tainted" in libvirt's log.
/--Regards, Aleksei/
*From:* Matt Xtlm
*Sent:* Tuesday, February
Hi there,
is there a way to set a guest to start with a specific date and time. (e.g.
when guest boots, starting guest time should always be
(2017-02-05T12:00:00)).
I've tried something like this in my kvm domain:
However, i can't insert a specific date and time statement (
[Starting to move to the development list.]
Milan Zamazal writes:
> Jiri Denemark writes:
>
>> On Fri, Feb 17, 2017 at 12:38:24 +0100, Milan Zamazal wrote:
>>>
>>> There are basically two problems:
>>>
>>> - When the job completion callback is called, I need to distinguish what
>>> kind of
I don't know whether this is a bug
because I have tried a lot of method to soluted this problem
but I alway failed
at last I have to upgrade our os version
发件人: abhishek jain [mailto:abhish_j...@yahoo.com]
发送时间: 2017年2月21日 21:33
收件人: 王李明; libvirt-users@redhat.com
主题: Re: 答复: [libvirt-users
I can only use RHEL6.
Is it a bug in libvirt ??
RegardsAbhishek
From: 王李明
To: 'abhishek jain' ; libvirt-users@redhat.com
Sent: Tuesday, 21 February 2017 11:54 AM
Subject: 答复: [libvirt-users] Virsh command hanging
#yiv0252501574 #yiv0252501574 -- _filtered #yiv0252501574
{font-famil
On Tue, Feb 21, 2017 at 10:32:08AM +0100, Gionatan Danti wrote:
> On 17/02/2017 19:50, Jiri Denemark wrote:
[...]
> > This looks like a bug in libvirt. The code doesn't check whether an
> > affected disk is going to be migrated (--copy-storage-all) or accessed
> > on the shared storage.
> >
> >
On 17/02/2017 19:50, Jiri Denemark wrote:
Yeah storage migration should be safe regardless of the cache mode used.
Very good news, thanks. Let me be paranoid: is it *surely* safe?
This looks like a bug in libvirt. The code doesn't check whether an
affected disk is going to be migrated (--c
