On Wed, Oct 26, 2016 at 5:04 PM, Martin Kletzander wrote:
> Or have you possibly edited the on-disk saved state of libvirt some time
> back instead of using virsh edit? =)
That could have been it, but no, we have this all automated and never
touch the on-disk xml after a
On Wed, Oct 26, 2016 at 04:40:12PM +0200, Ruben Kerkhof wrote:
On Thu, Oct 20, 2016 at 7:53 PM, Martin Kletzander wrote:
On Thu, Oct 20, 2016 at 11:26:09AM +0200, Ruben Kerkhof wrote:
Hi all,
virsh(1) has this to say about virsh shutdown:
"The exact behavior of a domain
On Thu, Oct 20, 2016 at 7:53 PM, Martin Kletzander wrote:
> On Thu, Oct 20, 2016 at 11:26:09AM +0200, Ruben Kerkhof wrote:
>>
>> Hi all,
>>
>> virsh(1) has this to say about virsh shutdown:
>> "The exact behavior of a domain when it shuts down is set by the
>> on_shutdown
On Thu, Oct 20, 2016 at 11:26:09AM +0200, Ruben Kerkhof wrote:
Hi all,
virsh(1) has this to say about virsh shutdown:
"The exact behavior of a domain when it shuts down is set by the
on_shutdown parameter in the domain's XML definition."
on_shutdown isn't documented in
Hi all,
virsh(1) has this to say about virsh shutdown:
"The exact behavior of a domain when it shuts down is set by the
on_shutdown parameter in the domain's XML definition."
on_shutdown isn't documented in https://libvirt.org/formatdomain.html
Is the virsh(1) manpage wrong?
Kind regards,
Hi all:
Suppose we have a guest domain which is pvops, for example, rhel6.4.
Steps to produce the problem:
1 start the guest by virDomainCreate()
2 the API returns before the guest domain fully available, which
>means,
>>> the disks, network interfaces
Zhangbo (Oscar) wrote:
> Hi all:
> Suppose we have a guest domain which is pvops, for example, rhel6.4.
>
> Steps to produce the problem:
> 1 start the guest by virDomainCreate()
> 2 the API returns before the guest domain fully available, which means,
> the disks, network
Hi all:
Suppose we have a guest domain which is pvops, for example, rhel6.4.
Steps to produce the problem:
1 start the guest by virDomainCreate()
2 the API returns before the guest domain fully available, which means, the
disks, network interfaces and some import services are
On 23.03.2015 10:31, zhang bo wrote:
The problem we encountered is:
1) use qemu-agent to shutdown a domain.
2) libvirt will block in qemuAgentShutdown(), if the domain itself got
stucked when it powers-off.
It's the *guest domain*'s fault that it stucks when shutdown. However, we
could
, if they find this problem, let them
manually DESTROY the domain.
or
3) let SHUTDOWN timeout in libvirt when the guest domain got stucked.
Looking forward to your reply, thanks in advance.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On 09.09.2014 18:25, Steven Wilson wrote:
We recently ran into libvirt lxc shutdown failing because of mount
namespaces not being available:
# virsh -c lxc:/// start test01
Domain test01 started
# virsh -c lxc:/// list
IdName State
On Wed, Sep 10, 2014 at 10:35:04AM +0200, Michal Privoznik wrote:
On 09.09.2014 18:25, Steven Wilson wrote:
We recently ran into libvirt lxc shutdown failing because of mount
namespaces not being available:
# virsh -c lxc:/// start test01
Domain test01 started
# virsh -c lxc:/// list
We recently ran into libvirt lxc shutdown failing because of mount namespaces
not being available:
# virsh -c lxc:/// start test01
Domain test01 started
# virsh -c lxc:/// list
IdName State
9336 test01
host: centos-6.5
kernel: 3.13.2-4.el6.x86_64
guest: fedora20
since libvirt-1.2.2 i can not shutdown this domain. works fine with
libvirt-1.2.1
# virsh shutdown fedora2
error: Failed to shutdown domain fedora2
error: Mount namespaces are not available on this platform: Function
not implemented
Resending this as there was no feedback overall and at least
the first change fixes the following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=746007
---
The issue is easy to observe when using virt-manager as a frontend.
Its main window seems to open connections for the up/down main
display
The issue is easy to observe when using virt-manager as a frontend.
Its main window seems to open connections for the up/down main
display once and then only repeats DomainGetInfo on the same
connection to check whether the instance is up or shut down.
The initial open on the connection sets the
it make any sense to enhance the output of list/domstate , for
example to
show something like this when libvirt issues a shutdown to a running
domain
Id Name State
--
3 FC15-2 running (shutdown in progress)
Or something like this when
domstate domain') does not provide
any way of
knowing if
- a domain is being shutdown
or
- a domain has a pending shutdown request (like in the example above).
Would it make any sense to enhance the output of list/domstate , for
example to
show something like this when libvirt issues
-Original Message-
From: Wen Congyang [mailto:we...@cn.fujitsu.com]
Sent: Thursday, September 15, 2011 6:22 PM
To: Christian Benvenuti (benve)
Cc: Libvirt
Subject: Re: [libvirt] domain shutdown requests
At 09/16/2011 05:10 AM, Christian Benvenuti (benve) Write:
When you shutdown
At 09/16/2011 09:36 AM, Christian Benvenuti (benve) Write:
-Original Message-
From: Wen Congyang [mailto:we...@cn.fujitsu.com]
Sent: Thursday, September 15, 2011 6:22 PM
To: Christian Benvenuti (benve)
Cc: Libvirt
Subject: Re: [libvirt] domain shutdown requests
At 09/16/2011 05:10
-Original Message-
From: Wen Congyang [mailto:we...@cn.fujitsu.com]
Sent: Thursday, September 15, 2011 6:42 PM
To: Christian Benvenuti (benve)
Cc: Libvirt
Subject: Re: [libvirt] domain shutdown requests
At 09/16/2011 09:36 AM, Christian Benvenuti (benve) Write:
-Original
not provide
any way of
knowing if
- a domain is being shutdown
or
- a domain has a pending shutdown request (like in the example above).
Would it make any sense to enhance the output of list/domstate , for
example to
show something like this when libvirt issues a shutdown to a running
domain
Id
On Wed, Apr 13, 2011 at 11:26:03AM -0600, Eric Blake wrote:
On 04/13/2011 12:56 AM, Zvi Dubitzky wrote:
Hi
For some reason recent libvirt code (0.8.3 and even before) the 'virsh
shutdown domain ' is not effective .
It issues an ok message by the domians remains in a runnning state .
Hi
For some reason recent libvirt code (0.8.3 and even before) the 'virsh
shutdown domain ' is not effective .
It issues an ok message by the domians remains in a runnning state . Only
th e destroy works fine.
Any idea ?
Zvi Dubitzky
Email:d...@il.ibm.com
--
libvir-list mailing list
On 04/13/2011 12:56 AM, Zvi Dubitzky wrote:
Hi
For some reason recent libvirt code (0.8.3 and even before) the 'virsh
shutdown domain ' is not effective .
It issues an ok message by the domians remains in a runnning state . Only
th e destroy works fine.
Any idea ?
'virsh shutdown' is
Am Mittwoch 10 November 2010 16:19:41 schrieb Guido Günther:
On Wed, Nov 10, 2010 at 10:35:40AM +0200, Avi Kivity wrote:
On 11/10/2010 10:01 AM, Hermann Himmelbauer wrote:
Hi,
I manage my KVM machines via libvirt and wonder if there are any init.d
scripts for automatically starting up and
On 11/10/2010 10:01 AM, Hermann Himmelbauer wrote:
Hi,
I manage my KVM machines via libvirt and wonder if there are any init.d
scripts for automatically starting up and shutting down virtual machines
during boot/shutdown of the host?
Writing this for myself seems to be not that simple, as when
于 2010年11月10日 16:35, Avi Kivity 写道:
On 11/10/2010 10:01 AM, Hermann Himmelbauer wrote:
Hi,
I manage my KVM machines via libvirt and wonder if there are any init.d
scripts for automatically starting up and shutting down virtual machines
during boot/shutdown of the host?
Writing this for myself
On Wed, Nov 10, 2010 at 10:35:40AM +0200, Avi Kivity wrote:
On 11/10/2010 10:01 AM, Hermann Himmelbauer wrote:
Hi,
I manage my KVM machines via libvirt and wonder if there are any init.d
scripts for automatically starting up and shutting down virtual machines
during boot/shutdown of the host?
this, if you shutdown guest only if one of:
- current runlevel is 0 (halt) or 6 (reboot). You can get current
runlevel by running:
runlevel | cut -d -f2
- if service libvirt shutdown is called, which is not very systematic,
but can work well
Just please do not create a new
On Tue, 2009-01-13 at 15:00 -0500, Sir Woody Hackswell wrote:
Here is a small patch for libvirtd init and sysconfig script. Before
killing libvirtd, we virsh shutdown any running domains. We also have
a maximum time limit for shutdown (300 sec default), just in case the
VM will not shut
On Tue, Jan 13, 2009 at 03:00:17PM -0500, Sir Woody Hackswell wrote:
Here is a small patch for libvirtd init and sysconfig script. Before
killing libvirtd, we virsh shutdown any running domains. We also have
a maximum time limit for shutdown (300 sec default), just in case the
VM will not
On Wed, Jan 14, 2009 at 5:58 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Jan 13, 2009 at 03:00:17PM -0500, Sir Woody Hackswell wrote:
It is desirable to stop things when the machine is shutting down.
If we put this functionality in the stop() function of the initscript
we
+done
+
killproc $PROCESS
RETVAL=$?
echo
--- /etc/sysconfig/libvirtd.orig2009-01-13 19:56:09.0 -0500
+++ /etc/sysconfig/libvirtd 2009-01-13 19:41:27.0 -0500
@@ -8,4 +8,7 @@
# Override Kerberos service keytab for SASL/GSSAPI
#KRB5_KTNAME=/etc/libvirt
On Tue, Aug 19, 2008 at 10:26:33PM +0200, Stefan de Konink wrote:
I would really like to know how I can make a defined domain *gone* after
shutdown :) (instead of it still be defined, after shutdown)
virsh undefine?
Rich.
--
Richard Jones, Emerging Technologies, Red Hat
On Wed, Aug 20, 2008 at 02:31:52PM +0100, Richard W.M. Jones wrote:
On Tue, Aug 19, 2008 at 10:26:33PM +0200, Stefan de Konink wrote:
I would really like to know how I can make a defined domain *gone* after
shutdown :) (instead of it still be defined, after shutdown)
[...]
Oh right, so am
On Wed, Aug 20, 2008 at 02:34:22PM +0100, Richard W.M. Jones wrote:
On Wed, Aug 20, 2008 at 02:31:52PM +0100, Richard W.M. Jones wrote:
On Tue, Aug 19, 2008 at 10:26:33PM +0200, Stefan de Konink wrote:
I would really like to know how I can make a defined domain *gone* after
shutdown :)
Hi,
I would really like to know how I can make a defined domain *gone* after
shutdown :) (instead of it still be defined, after shutdown)
Stefan
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Hello Daniel,
Am Dienstag, 15. Juli 2008 21:17:04 schrieb Daniel P. Berrange:
On Sat, Jul 12, 2008 at 10:25:01PM +0200, Matthias Pfafferodt wrote:
Hello,
there is the possibility to autostart a (qemu/kvm) domain. If libvirtd is
stopped this domain is killed and the filesystem is in a
39 matches
Mail list logo