On a Friday in 2023, Jiri Denemark wrote:
See patch 2/3 for details.
Jiri Denemark (3):
Clarify VIR_DOMAIN_EVENT_SUSPENDED_API_ERROR semantics
Introduce VIR_DOMAIN_PAUSED_API_ERROR
qemu_migration: Use VIR_DOMAIN_PAUSED_API_ERROR
include/libvirt/libvirt-domain.h | 3 ++-
src/conf/domain_conf.
See patch 2/3 for details.
Jiri Denemark (3):
Clarify VIR_DOMAIN_EVENT_SUSPENDED_API_ERROR semantics
Introduce VIR_DOMAIN_PAUSED_API_ERROR
qemu_migration: Use VIR_DOMAIN_PAUSED_API_ERROR
include/libvirt/libvirt-domain.h | 3 ++-
src/conf/domain_conf.c | 1 +
src/qemu/qemu_domai
Whiles working on Hyper-V patches I've posted yesterday I ran
domaincapstest occasionally and was puzzled for a moment that qemu-7.2.0
wasn't tested. Well it is, but it's harder to see immediately because
individual test cases are in 'random' order:
11) qemu_7.2.0.x86_64
Kristina Hanicova (3):
qemu_capabilities: Add QEMU_CAPS_INPUT_LINUX
conf: Parse/format XML input type 'linux'
qemu: Build command line for object input-linux
docs/formatdomain.rst | 30 +
docs/schemas/domaincommon.rng | 20 ++
src/conf/d
The publican theme is used by the libvirt-appdev-guide-python, so we
should test it.
Daniel P. Berrangé (3):
cfg: remove obsolete "release" config entry
gitlab: introduce CI jobs for building content
gitlab: add CONTRIBUTING.rst file to indicate use of merge requests
.gitlab-ci.yml
This introduces GitLab CI jobs for the Go bindings and indicates that
contributors should submit merge requests.
Daniel P. Berrangé (3):
Fix tests on Ubuntu 18.04 / Debian 9 with missing screenshot file
gitlab: introduce CI jobs testing git master & distro libvirt
gitlab: add CONTRIBUTING.rs
On Mon, Feb 25, 2019 at 12:42:58PM +0100, Erik Skultety wrote:
> On Mon, Feb 25, 2019 at 11:14:41AM +, Daniel P. Berrangé wrote:
> > On Mon, Feb 25, 2019 at 12:09:41PM +0100, Erik Skultety wrote:
> > > On Fri, Feb 22, 2019 at 04:43:25PM +, Daniel P. Berrangé wrote:
> > > > On Fri, Feb 22, 2
On Mon, Feb 25, 2019 at 11:14:41AM +, Daniel P. Berrangé wrote:
> On Mon, Feb 25, 2019 at 12:09:41PM +0100, Erik Skultety wrote:
> > On Fri, Feb 22, 2019 at 04:43:25PM +, Daniel P. Berrangé wrote:
> > > On Fri, Feb 22, 2019 at 04:32:27PM +0100, Erik Skultety wrote:
> > > > Unfortunately, in
On Mon, Feb 25, 2019 at 12:09:41PM +0100, Erik Skultety wrote:
> On Fri, Feb 22, 2019 at 04:43:25PM +, Daniel P. Berrangé wrote:
> > On Fri, Feb 22, 2019 at 04:32:27PM +0100, Erik Skultety wrote:
> > > Unfortunately, in order to support the new flags, the last patch
> > > introduces an
> > > A
On Fri, Feb 22, 2019 at 04:43:25PM +, Daniel P. Berrangé wrote:
> On Fri, Feb 22, 2019 at 04:32:27PM +0100, Erik Skultety wrote:
> > Unfortunately, in order to support the new flags, the last patch introduces
> > an
> > API breakage as the convention we use for the bindings is to also enforce
On Fri, Feb 22, 2019 at 10:54:10AM -0600, Eric Blake wrote:
> On 2/22/19 10:43 AM, Daniel P. Berrangé wrote:
> > On Fri, Feb 22, 2019 at 04:32:27PM +0100, Erik Skultety wrote:
> >> Unfortunately, in order to support the new flags, the last patch
> >> introduces an
> >> API breakage as the conventi
On 2/22/19 10:43 AM, Daniel P. Berrangé wrote:
> On Fri, Feb 22, 2019 at 04:32:27PM +0100, Erik Skultety wrote:
>> Unfortunately, in order to support the new flags, the last patch introduces
>> an
>> API breakage as the convention we use for the bindings is to also enforce
>> types
>> for flags.
On Fri, Feb 22, 2019 at 10:39:06AM -0600, Eric Blake wrote:
> On 2/22/19 9:32 AM, Erik Skultety wrote:
> > Unfortunately, in order to support the new flags, the last patch introduces
> > an
> > API breakage as the convention we use for the bindings is to also enforce
> > types
> > for flags.
>
>
On Fri, Feb 22, 2019 at 04:32:27PM +0100, Erik Skultety wrote:
> Unfortunately, in order to support the new flags, the last patch introduces an
> API breakage as the convention we use for the bindings is to also enforce
> types
> for flags.
Yes, unfortunately this need to break ABI is fallout res
On 2/22/19 9:32 AM, Erik Skultety wrote:
> Unfortunately, in order to support the new flags, the last patch introduces an
> API breakage as the convention we use for the bindings is to also enforce
> types
> for flags.
Oh bummer - I didn't realize that some of the other language bindings
are more
Unfortunately, in order to support the new flags, the last patch introduces an
API breakage as the convention we use for the bindings is to also enforce types
for flags.
Erik Skultety (3):
Introduce DomainSnapshotXMLFlags constant
Introduce DomainSaveImageXMLFlags constant
Enforce new flags
Pavel Hrdina (3):
util: Introduce virtDBusUtilTypedParams
util: Introduce virtDBusUtilGVariantToTypedParams
domain: Implement SetPerfEvents method
data/org.libvirt.Domain.xml | 6 +++
src/domain.c| 31
src/util.c | 89 ++
Andrea Bolognani (3):
jobs: Introduce variants
jobs: Tweak autotools-mingw-job template
jobs: Drop autotools-mingw-job
jobs/autotools.yaml| 94 --
jobs/defaults.yaml | 17 +
jobs/generic.yaml | 16
jobs/go
On 07/24/2017 02:33 PM, Pavel Hrdina wrote:
>> EXACTLY! This is why I started down this path... Of course I want far
>> too generic for some people's preferences by going with primaryKey and
>> secondaryKey type nomenclature, so I was forced by review to use
>> UUID/Name which are far less gene
On Mon, Jul 24, 2017 at 11:12:01AM -0400, John Ferlan wrote:
>
>
> On 07/24/2017 09:04 AM, Michal Privoznik wrote:
> > On 07/23/2017 11:33 PM, John Ferlan wrote:
> >>
> >>
> >> On 07/23/2017 04:46 PM, Michal Privoznik wrote:
> >>> On 07/23/2017 07:21 PM, Pavel Hrdina wrote:
> On Sun, Jul 23,
On 07/24/2017 09:04 AM, Michal Privoznik wrote:
> On 07/23/2017 11:33 PM, John Ferlan wrote:
>>
>>
>> On 07/23/2017 04:46 PM, Michal Privoznik wrote:
>>> On 07/23/2017 07:21 PM, Pavel Hrdina wrote:
On Sun, Jul 23, 2017 at 02:33:49PM +0200, Michal Privoznik wrote:
> On 07/23/2017 02:10 PM
On 07/23/2017 11:33 PM, John Ferlan wrote:
>
>
> On 07/23/2017 04:46 PM, Michal Privoznik wrote:
>> On 07/23/2017 07:21 PM, Pavel Hrdina wrote:
>>> On Sun, Jul 23, 2017 at 02:33:49PM +0200, Michal Privoznik wrote:
On 07/23/2017 02:10 PM, John Ferlan wrote:
>
>
> On 07/19/2017 10:
On Sun, Jul 23, 2017 at 10:46:15PM +0200, Michal Privoznik wrote:
> On 07/23/2017 07:21 PM, Pavel Hrdina wrote:
> > On Sun, Jul 23, 2017 at 02:33:49PM +0200, Michal Privoznik wrote:
> >> On 07/23/2017 02:10 PM, John Ferlan wrote:
> >>>
> >>>
> >>> On 07/19/2017 10:31 AM, Michal Privoznik wrote:
> >
On 07/23/2017 04:46 PM, Michal Privoznik wrote:
> On 07/23/2017 07:21 PM, Pavel Hrdina wrote:
>> On Sun, Jul 23, 2017 at 02:33:49PM +0200, Michal Privoznik wrote:
>>> On 07/23/2017 02:10 PM, John Ferlan wrote:
On 07/19/2017 10:31 AM, Michal Privoznik wrote:
> While this is not
On 07/23/2017 07:21 PM, Pavel Hrdina wrote:
> On Sun, Jul 23, 2017 at 02:33:49PM +0200, Michal Privoznik wrote:
>> On 07/23/2017 02:10 PM, John Ferlan wrote:
>>>
>>>
>>> On 07/19/2017 10:31 AM, Michal Privoznik wrote:
While this is not that critical (hash tables have O(1) time complexity for
>
On Sun, Jul 23, 2017 at 02:33:49PM +0200, Michal Privoznik wrote:
> On 07/23/2017 02:10 PM, John Ferlan wrote:
> >
> >
> > On 07/19/2017 10:31 AM, Michal Privoznik wrote:
> >> While this is not that critical (hash tables have O(1) time complexity for
> >> lookups), it lays down path towards makin
On 07/23/2017 02:10 PM, John Ferlan wrote:
>
>
> On 07/19/2017 10:31 AM, Michal Privoznik wrote:
>> While this is not that critical (hash tables have O(1) time complexity for
>> lookups), it lays down path towards making virDomainObj using RW locks
>> instead
>> of mutexes. Still, in my limited
On 07/19/2017 10:31 AM, Michal Privoznik wrote:
> While this is not that critical (hash tables have O(1) time complexity for
> lookups), it lays down path towards making virDomainObj using RW locks instead
> of mutexes. Still, in my limited testing this showed slight improvement.
>
> Michal Priv
While this is not that critical (hash tables have O(1) time complexity for
lookups), it lays down path towards making virDomainObj using RW locks instead
of mutexes. Still, in my limited testing this showed slight improvement.
Michal Privoznik (3):
virthread: Introduce virRWLockInitPreferWriter
Hi, everyone.
Please take a look at pull backup API and its qemu implementation. There is no
any
documentation inside yet so I put it here.
Backup is described in xml like next:
, , elements and 'present' attribute are optional. The
export address is bare mini
On 19.08.2016 13:54, Michal Privoznik wrote:
>
Ping.
Michal
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
This series is implementing support for something, that is not merged yet to
qemu. Therefore I won't push it until qemu side patch (which is in queue as
qemu is preparing for 2.7 release) is in [1]. However, review is welcome!
1: http://lists.nongnu.org/archive/html/qemu-devel/2016-08/msg02029.htm
On 09/17/2015 04:46 AM, Shivangi Dhir wrote:
> These patches solve a BiteSizedTask - Introduce new virtType enum item[0]
>
> [0]
> http://wiki.libvirt.org/page/BiteSizedTasks#Introduce_new_virtType_enum_item
>
> Shivangi Dhir (3):
> conf: Add new VIR_DOMAIN_VIRT_NONE enum
> qemu: Make virt
On 09/23/2015 12:51 AM, Shivangi Dhir wrote:
[...]
>
> Thanks alot for your feedback.
> Should I modify and resend the patches after making the changes
> suggested above, if there are no other issues ?
>
>
I should be able to jiggle your patches - I'll work on those tomorrow
(for me).
I a
Hi,
On Tue, Sep 22, 2015 at 6:53 PM, Daniel P. Berrange
wrote:
>
> On Tue, Sep 22, 2015 at 07:50:41AM -0400, John Ferlan wrote:
> >
> >
> > On 09/17/2015 04:46 AM, Shivangi Dhir wrote:
> > > These patches solve a BiteSizedTask - Introduce new virtType enum
item[0]
> > >
> > > [0]
http://wiki.libv
On Tue, Sep 22, 2015 at 07:50:41AM -0400, John Ferlan wrote:
>
>
> On 09/17/2015 04:46 AM, Shivangi Dhir wrote:
> > These patches solve a BiteSizedTask - Introduce new virtType enum item[0]
> >
> > [0]
> > http://wiki.libvirt.org/page/BiteSizedTasks#Introduce_new_virtType_enum_item
> >
> > Shi
On 09/17/2015 04:46 AM, Shivangi Dhir wrote:
> These patches solve a BiteSizedTask - Introduce new virtType enum item[0]
>
> [0]
> http://wiki.libvirt.org/page/BiteSizedTasks#Introduce_new_virtType_enum_item
>
> Shivangi Dhir (3):
> conf: Add new VIR_DOMAIN_VIRT_NONE enum
> qemu: Make virt
These patches solve a BiteSizedTask - Introduce new virtType enum item[0]
[0] http://wiki.libvirt.org/page/BiteSizedTasks#Introduce_new_virtType_enum_item
Shivangi Dhir (3):
conf: Add new VIR_DOMAIN_VIRT_NONE enum
qemu: Make virtType of type virDomainVirtType
conf: Change the description of
The specification is here:
http://www.dmtf.org/sites/default/files/standards/documents/DSP0134_3.0.0.pdf
The first two patches rework the code a bit, and the last one adds something
useful.
Michal Privoznik (3):
virSysinfoDef: Exempt BIOS variables
virSysinfoDef: Exempt SYSTEM variables
vi
Well, here's an alternative approach to my question here [1].
1: https://www.redhat.com/archives/libvir-list/2015-February/msg00369.html
Michal Privoznik (3):
virQEMUCapsCacheLookupCopy: Pass machine type
virQEMUCapsCacheLookupCopy: Filter qemuCaps based on machineType
qemuCaps: Disable mem
On 08/25/2014 08:22 PM, Ján Tomko wrote:
> Introduce virDomainOpenGraphicsFD which returns a socket fd
> created by the daemon, unlike virDomainOpenGraphics, where
> it's created by client.
>
> This should be usable by virt-viewer under SELinux, but
> I was not able to verify that yet.
I have now
Introduce virDomainOpenGraphicsFD which returns a socket fd
created by the daemon, unlike virDomainOpenGraphics, where
it's created by client.
This should be usable by virt-viewer under SELinux, but
I was not able to verify that yet.
Ján Tomko (3):
Introduce virDomainOpenGraphicsFD API
Add RP
This is counterpart for virDomainPMSuspendForDuration API which
we have already in. It allows user to wake up guest from S3 state.
Michal Privoznik (3):
Introduce virDomainPMWakeup API
virsh: Expose virDomainPMWakeup
qemu: Implement virDomainPMWakeup API
include/libvirt/libvirt.h.in |2
This series introduces a new (fake) flag for the qemu binary. The flag
QEMUD_CMD_FLAG_PCI_MULTIBUS is used to mark an architecture to be able to
have multiple PCI-busses. When executing qemu, -device should take either a
bus-string like "pci" or "pci.0". Where the latter can be used to select the
a
44 matches
Mail list logo
