The test driver and qemu driver share the same code in
virDomainGetMessages(), so extract it to a function.
Signed-off-by: Luke Yue
---
src/conf/domain_conf.c | 53
src/conf/domain_conf.h | 5
src/libvirt_private.syms | 1 +
In order to test the virDomainGetMessages for test driver, we need to
check some taints or deprecations, so introduce testDomainObjCheckTaint
for checking taints.
As we introduced testDomainObjCheckTaint for test driver, the `dominfo`
command in virshtest will now print tainting messages, so add
Signed-off-by: Luke Yue
---
src/test/test_driver.c | 53 ++
1 file changed, 53 insertions(+)
diff --git a/src/test/test_driver.c b/src/test/test_driver.c
index ef0ddab54d..35742fcde3 100644
--- a/src/test/test_driver.c
+++ b/src/test/test_driver.c
@@
v3:
- Squash tests commit
- Extract the same code in test driver and qemu driver to a function
Luke Yue (3):
test_driver: Implement virDomainGetMessages
test_driver: Introduce testDomainObjCheckTaint
conf: domain: Introduce and use virDomainObjGetMessages()
src/conf/domain_conf.c | 53
Sorry for the inconvenience.
Tested-by: Liu Yiding
Thanks,
Liu
On 6/29/21 9:08 PM, Andrea Bolognani wrote:
> On Tue, Jun 29, 2021 at 02:54:24AM +, liuyd.f...@fujitsu.com wrote:
>> That works for me. Thanks.
>>
>> Tested-by: liuyd.f...@fujitsu.com
> Glad to hear that! Can you please provide
Add function to build the the json structure to configure a PTY in
cloud-hypervisor. The configuration only supports a single serial or
console device.
Signed-off-by: William Douglas
---
src/ch/ch_monitor.c | 59 +
1 file changed, 59 insertions(+)
With all the rest of the enablement work out of the way, add the final
call for the cloud-hypervisor driver to handle domainOpenConsole.
Signed-off-by: William Douglas
---
src/ch/ch_driver.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/ch/ch_driver.c b/src/ch/ch_driver.c
index
Add the handler function to find and open the console character
device that will be used by the console API.
Signed-off-by: William Douglas
---
src/ch/ch_driver.c | 77 ++
1 file changed, 77 insertions(+)
diff --git a/src/ch/ch_driver.c
Call into the PTY json builder for configured serial and console
devices though the devices themselves still aren't allowed in
configuration.
Signed-off-by: William Douglas
---
src/ch/ch_monitor.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/ch/ch_monitor.c b/src/ch/ch_monitor.c
Add functionality to allow libvirt console to connect to the
cloud-hypervisor created PTY associated with a VM. This will need to
be run once the VM is created by cloud-hypervisor.
Signed-off-by: William Douglas
---
src/ch/ch_process.c | 64 +
1 file
Now that virCHMonitorGet is capable of handling data returned by the
cloud-hypervisor API, make use of this via virCHMonitorGetInfo to call
into the vm.info endpoint.
Signed-off-by: William Douglas
---
src/ch/ch_monitor.c | 15 +++
src/ch/ch_monitor.h | 3 +++
2 files changed, 18
The virCHMonitorGet function needed to be able to return data from the
hypervisor. This functionality is needed in order for the driver to
support PTY enablement and getting details about the VM state.
Signed-off-by: William Douglas
---
src/ch/ch_monitor.c | 37
Add call to update the domain with console path information from
cloud-hypervisor as part of the last stages of initializing the
domain.
Signed-off-by: William Douglas
---
src/ch/ch_process.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/ch/ch_process.c b/src/ch/ch_process.c
index
With the console and serial device handling fully functional, allow
the required device types to be specified in the domain
configuration.
Signed-off-by: William Douglas
---
src/ch/ch_domain.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/ch/ch_domain.c
This series enables console support in the cloud-hypervisor driver.
Cloud-hypervisor only supports a single console or serial device at a
time, hence the checks to ensure the domain configuration is only
passing one or the other.
I wasn't sure if the controller device should have some additonal
The virCHMonitorGet function wasn't in use and was declared as
non-static (though not in a header file). This function isn't going to
be used outside of the monitor though so remove the initial
declaration and define the function to be static.
Future work should adjust this function to allow
On Tue, Jun 29, 2021 at 03:33:26PM +0200, Peter Krempa wrote:
> On Mon, Jun 28, 2021 at 16:55:34 +0200, Tomáš Golembiovský wrote:
> > Hi,
> >
> > I have a few questions regarding this to get better understanding on how
> > this should be handled by management apps.
> >
> > On Fri, Jun 04, 2021
On Mon, Jun 28, 2021 at 16:55:34 +0200, Tomáš Golembiovský wrote:
> Hi,
>
> I have a few questions regarding this to get better understanding on how
> this should be handled by management apps.
>
> On Fri, Jun 04, 2021 at 02:08:40PM +0200, Peter Krempa wrote:
> > Disk serials are truncated
On Tue, Jun 29, 2021 at 02:54:24AM +, liuyd.f...@fujitsu.com wrote:
> That works for me. Thanks.
>
> Tested-by: liuyd.f...@fujitsu.com
Glad to hear that! Can you please provide a full Tested-by tag in the
expected format
Tested-by: FirstName LastName
so that it's suitable for inclusion
On 6/28/21 11:18 AM, zhangjl02 wrote:
> From: zhangjl02
>
> Tell whether a port definition is an ovs managed virtual port
> ---
> src/qemu/qemu_domain.c | 13 +
> src/qemu/qemu_domain.h | 3 +++
> 2 files changed, 16 insertions(+)
>
> diff --git a/src/qemu/qemu_domain.c
On 6/28/21 11:18 AM, zhangjl02 wrote:
> From: zhangjl02
>
> Return 0 directly if the port is ovs managed. When the ovs port is set
> noqueue, qos config on this port will not work.
> ---
> src/qemu/qemu_domain.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/qemu/qemu_domain.c
On 6/28/21 11:18 AM, zhangjl02 wrote:
> From: zhangjl02
>
> When qos is set or delete, we have to check if the port is an ovs managed
> port. If true, call the virNetDevOpenvswitchInterfaceSetQos function when qos
> is set, and call the virNetDevOpenvswitchInterfaceClearQos function when
> the
On 6/28/21 11:18 AM, zhangjl02 wrote:
> From: zhangjl02
>
> Introduce qos setting and cleaning method. Use ovs command to set qos
> parameters on specific interface of qemu virtual machine.
>
> When an ovs port is created, we add 'ifname' to external-ids. When setting
> qos on an ovs port,
On Tue, Jun 29, 2021 at 10:05:17AM +0200, Erik Skultety wrote:
> ...
>
> > > +Example guest definition without launchSecurity
> > > +===
> > > +
> > > +Minimal domain XML for a protected virtualization guest using the
> > > +``iommu='on'`` setting for
On Mon, Jun 28, 2021 at 11:36:45PM +0800, Luke Yue wrote:
And I have another question, as it's freeze for 7.5.0, should I change
the version number in comments to 7.6.0 in the new patches? Thanks!
Yep, it won't make 7.5.0 now. Thanks.
signature.asc
Description: PGP signature
On 6/25/21 12:11 PM, Pavel Hrdina wrote:
@@ -158,8 +163,42 @@ allocated 2K entries. A commonly used value for swiotlb is
262144.
Example guest definition
-Minimal domain XML for a protected virtualization guest, essentially
-it's mostly about the ``iommu``
On 6/25/21 10:51 AM, Pavel Hrdina wrote:
On Tue, Jun 22, 2021 at 03:10:46PM +0200, Boris Fiuczynski wrote:
Adding virDomainSecDef for general launch security data
and moving virDomainSEVDef as an element for SEV data.
Signed-off-by: Boris Fiuczynski
---
src/conf/domain_conf.c | 127
...
> > +Example guest definition without launchSecurity
> > +===
> > +
> > +Minimal domain XML for a protected virtualization guest using the
> > +``iommu='on'`` setting for each virtio device.
>
> I don't know how s390-pv works but for example with
I have just tagged v7.5.0-rc2 in the repository and pushed signed
tarballs and source RPMs to https://libvirt.org/sources/
Please give the release candidate some testing and in case you find a
serious issue which should have a fix in the upcoming release, feel
free to reply to this thread to make
29 matches
Mail list logo
