Re: [libvirt] [PATCH 0/9] rpc: make client streams multi-thread safer

On 08.02.2019 19:19, Michal Privoznik wrote: > On 2/7/19 1:58 PM, Nikolay Shirokovskiy wrote: >> Nikolay Shirokovskiy (9): >>    rpc: fix race on stream abort/finish and server side abort >>    rpc: use single function to send stream messages >>    rpc: remove unused virNetClientSendNoReply >>   

Re: [libvirt] [PATCH 0/4] bhyve: model PCI ISA bridge

On 2/10/19 10:08 AM, Roman Bogorodskiy wrote: This adds modeling of the pci-isa bridge device for bhyve to make it possible to assign specific PCI address for instead of the default PCI slot 0. I tried to keep the existing behaviour, i.e. the isa-bridge controller is automatically added to domai

[libvirt] [PATCH 1/4] conf: add 'isa-bridge' PCI controller model

Introduce 'isa-bridge' PCI controller model that looks this way in domain XML: ... ... Currently, this is needed by the bhyve driver to allow choosing a specific PCI address for that. In bhyve, this controller is used to attach serial ports and a boot ROM. Signed-off-by: Roman Bog

[libvirt] [PATCH 4/4] news: document bhyve isa-bridge changes

Signed-off-by: Roman Bogorodskiy --- docs/news.xml | 10 ++ 1 file changed, 10 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index 8d6d58ae6a..e0c9c3590f 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -59,6 +59,16 @@ of the network's bridge element.

[libvirt] [PATCH 2/4] bhyve: model PCI ISA bridge

bhyve(8) uses PCI ISA bridge to attach serial ports and a boot ROM. In the libvirt driver a PCI slot 1 was always reserved for that, and if a domain used serial ports or a boot ROM, then it would be added to the command line. However, some guests require the ISA bridge to have PCI slot other than

[libvirt] [PATCH 3/4] docs: bhyve: document isa-bridge addressing

Document ability to specify LCP PCI-ISA bridge PCI address. Signed-off-by: Roman Bogorodskiy --- docs/drvbhyve.html.in | 22 ++ 1 file changed, 22 insertions(+) diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in index 2e9cf5551b..18bfb94b48 100644 --- a/docs/drvbhyve

[libvirt] [PATCH 0/4] bhyve: model PCI ISA bridge

This adds modeling of the pci-isa bridge device for bhyve to make it possible to assign specific PCI address for instead of the default PCI slot 0. I tried to keep the existing behaviour, i.e. the isa-bridge controller is automatically added to domain if it uses serial or video devices, or boot RO

[libvirt] [PATCH v2 3/3] news: document bhyve msrs feature

Describe bhyve's ignoring unknown MSRs writes feature introduced by commit 525918ac5c. Signed-off-by: Roman Bogorodskiy --- docs/news.xml | 10 ++ 1 file changed, 10 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index 8d6d58ae6a..cb23b63143 100644 --- a/docs/news.xml +++ b/do

[libvirt] [PATCH v2 2/3] bhyve: implement ignore unknown MSRs feature

Implement the MSRs ignore unknown reads and writes feature that's specified using: ... ... in the domain XML. In bhyve, it's just passing '-w' command line argument to the bhyve(8) executable. Signed-off-by: Roman Bogorodskiy --- docs/drvbhyve.html.in

[libvirt] [PATCH v2 0/3] bhyve: implement MSRs ignore unknown writes feature

Changes from v1: * Replaced with Roman Bogorodskiy (3): conf: introduce 'msrs' feature bhyve: implement ignore unknown MSRs feature news: document bhyve msrs feature docs/drvbhyve.html.in | 22 +++ docs/formatdomain.html.in | 1 +

[libvirt] [PATCH v2 1/3] conf: introduce 'msrs' feature

Introduce the 'msrs' feature element that controls Model Specific Registers related behaviour. At this moment it allows only single tunable attribute "unknown": Which tells hypervisor to ignore accesses to unimplemented Model Specific Registers. The only user of that for now is going to be the