On Fri, Apr 24, 2020 at 4:35 PM Peter Crowther
wrote:
>
> On Fri, 24 Apr 2020 at 21:10, Mauricio Tavares wrote:
>>
>> Let's say I have libvirt
>>
>> [root@vmhost2 ~]# virsh version
>> [...]
>>
>> Running hypervisor: QEMU 2.12.0
>> [root@vmhost2 ~]#
>> [...]
>
> When I try to start the guest I
On Fri, 24 Apr 2020 at 21:10, Mauricio Tavares wrote:
> Let's say I have libvirt
>
> [root@vmhost2 ~]# virsh version
> [...]
Running hypervisor: QEMU 2.12.0
> [root@vmhost2 ~]#
> [...]
>
When I try to start the guest I get the following error message:
>
> [root@vmhost2 ~]# virsh start
Let's say I have libvirt
[root@vmhost2 ~]# virsh version
Compiled against library: libvirt 4.5.0
Using library: libvirt 4.5.0
Using API: QEMU 4.5.0
Running hypervisor: QEMU 2.12.0
[root@vmhost2 ~]#
running on centos 8 and then I have this card
[root@vmhost2 ~]# virsh nodedev-dumpxml
On 4/24/20 7:37 AM, Daniel P. Berrangé wrote:
On Fri, Apr 24, 2020 at 02:33:13PM +0200, Michal Privoznik wrote:
On 4/24/20 6:38 AM, Vincent Wu wrote:
The save format is fragile. At the beginning there is a header which
describes the file, then there is libvirt section (which contains the
On Fri, Apr 24, 2020 at 02:33:13PM +0200, Michal Privoznik wrote:
> On 4/24/20 6:38 AM, Vincent Wu wrote:
> >
>
> The save format is fragile. At the beginning there is a header which
> describes the file, then there is libvirt section (which contains the domain
> XML and a cookie) and then there
On 4/24/20 6:38 AM, Vincent Wu wrote:
>
The save format is fragile. At the beginning there is a header which
describes the file, then there is libvirt section (which contains the
domain XML and a cookie) and then there is QEMU section (where QEMU
saved the guest memory). Because of this, we
Hi administrator,
I am a cloud compute developer. I need some help from you about libvirt.
I have a work to modify a image file which is saved by virDomainSave()
or virDomainSaveFlags().So virDomainSaveImageGetXMLDesc() and
virDomainSaveImageDefineXML() are APIs I choosed to do.
