On Mon, 2018-10-15 at 08:21 +0200, Kashyap Chamarthy wrote:
> On Sun, Oct 14, 2018 at 02:28:07PM +0200, Andrea Bolognani wrote:
> > If I had to guess, I would say the element of your guest
> > is probably pointing to a custom-built QEMU 2.11 binary rather than
> > the default one installed from RP
Peter Krempa writes:
> On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
>> Hi, when working on hot unplugs of various devices, I've found out that
>> hot unplugging device doesn't generate
>> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. also doesn't have an
>> alias, so it wouldn't be
On Mon, Oct 15, 2018 at 09:56:39 +0200, Milan Zamazal wrote:
> Peter Krempa writes:
>
> > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
> >> Hi, when working on hot unplugs of various devices, I've found out that
> >> hot unplugging device doesn't generate
> >> VIR_DOMAIN_EVENT_ID
On Mon, Oct 15, 2018 at 09:05:16AM +0200, Andrea Bolognani wrote:
[...]
> Interesting. What is the output of 'virsh capabilities'?
In attachment.
> More interesting still is the fact that the guest XML you shared
> looks like an *active* XML, ie. one taken from a running guest...
> Does that me
On Mon, 2018-10-15 at 11:46 +0200, Kashyap Chamarthy wrote:
> On Mon, Oct 15, 2018 at 09:05:16AM +0200, Andrea Bolognani wrote:
> > Interesting. What is the output of 'virsh capabilities'?
>
> In attachment.
Looks reasonable enough.
> > More interesting still is the fact that the guest XML you s
Peter Krempa writes:
> On Mon, Oct 15, 2018 at 09:56:39 +0200, Milan Zamazal wrote:
>> Peter Krempa writes:
>>
>
>> > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
>> >> Hi, when working on hot unplugs of various devices, I've found out that
>> >> hot unplugging device doesn't g
Hi,
i have a two node cluster with virtual guests as resources.
I'd like to snapshot the guests once in the night and thought i had a procedure.
But i realize that things in a cluster are a bit more complicated than expected
:-))
I will shutdown the guests to have a clean snapshot.
I can shutdow
Pacemaker always knows where its resources are running. Query it, stop the
domain, then use the queried location as the host to which to issue the
snapshot?
Cheers,
Peter
On Mon, 15 Oct 2018, 20:36 Lentes, Bernd, <
bernd.len...@helmholtz-muenchen.de> wrote:
> Hi,
>
> i have a two node cluster w
I snapshot my guests live with qemu-guest-agent. It works pretty much
flawlessly with qcow2, but even with raw I can almost always boot off of
a snapshot. I combine this with zfs and hourly snapshots and replication
and have a really usable backup and DR system that works with my guests,
both W
- Am 15. Okt 2018 um 21:47 schrieb Peter Crowther
peter.crowt...@melandra.com:
> Pacemaker always knows where its resources are running. Query it, stop the
> domain, then use the queried location as the host to which to issue the
> snapshot?
But can i be sure that the resource starts on th
10 matches
Mail list logo
