Context: The baremetal host previously had QEMU 2.11. But I manually
downgraded the QEMU version (via `dnf downgrade qemu-system-x86`); now
it is at 2.10:
$ rpm -q qemu-system-x86
qemu-system-x86-2.10.2-1.fc27.x86_64
The guest is offline. Let's see (in a couple of ways) what machine typ
On Fri, Oct 12, 2018 at 4:50 AM Martin Kletzander
wrote:
> On Mon, Sep 17, 2018 at 02:17:39PM +0200, Fabian Deutsch wrote:
> >On Fri, Sep 14, 2018 at 6:55 PM David Vossel wrote:
> >> Any chance we can get the safety check removed for the next Libvirt
> >> release? Does there need to be an issue
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 identifiable in the corresponding callback.
Is this difference from other hotpluggable devices i
> - On Sep 7, 2018, at 9:26 PM, Eric Blake ebl...@redhat.com wrote:
>
>> On 09/07/2018 12:06 PM, Lentes, Bernd wrote:
>>> Hi,
>>>
>>> currently i'm following
>>> https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit. I 'm
>>> playing around with it and it seems to be quite
On Mon, Sep 17, 2018 at 02:17:39PM +0200, Fabian Deutsch wrote:
On Fri, Sep 14, 2018 at 6:55 PM David Vossel wrote:
Any chance we can get the safety check removed for the next Libvirt
release? Does there need to be an issue opened to track this?
Regardless of Martin's answer :): Please file
