search for: elementscpu

The problem desribed here: https://bugzilla.redhat.com/show_bug.cgi?id=593266 Please update http://www.libvirt.org/formatdomain.html and describe NEW xml tags, like <serial>xxxx</serial> for hard drive and all cpu tags, other if any. -- Segmentation fault

...64 xen-4.8.1-2.fc26.x86_64 libvirt-3.2.1-1.fc26.x86_64 I can disable '3dnowprefetch' CPU feature in guest via 'xl' command, with adding `cpuid='host,3dnowprefetch=0'` into the CFG file. However, follow the instruction (https://libvirt.org/ formatdomain.html#elementsCPU), I added the following block into my XML file: ``` <cpu mode='host-passthrough' check='none'> <feature policy='disable' name='3dnowprefetch'/> </cpu> ``` Created the instance, seemed this feature was not being disabled in my guest. (I...

...libvirt-3.2.1-1.fc26.x86_64 > > I can disable '3dnowprefetch' CPU feature in guest via 'xl' command, with > adding `cpuid='host,3dnowprefetch=0'` into the CFG file. > > However, follow the instruction > (https://libvirt.org/formatdomain.html#elementsCPU > <https://libvirt.org/formatdomain.html#elementsCPU>), I added the following > block into my XML file: > > ``` > <cpu mode='host-passthrough' check='none'> > <feature policy='disable' name='3dnowprefetch'/> > <...

Hi, How do I enable aes for guest VM? Host CPU supports aes (cat /proc/cpuinfo has aes in its flags and virsh capabilities also displays aes as a feature). When I add <features> <aes/> </features> to the xml file, I am unable to create the VM. It complains with the below error: virsh create /tmp/tmp.xml error: Failed to create domain from /tmp/tmp.xml error: internal error:

Hello, I am migrating a suspended x86-64 guest (disk & state) across different x86-64 hosts with small differences in the available CPU instructions and when I try to resume the guest on the different host libvirt reports an error like this "CPU feature XXX not found" and fails. My question is, is there a way to limit the instructions that are used on the "origin" host

Could anyone tell me what is virConnectBaselineCPU exactly do. What could I do which this API. It's very nice to give me a simple example. -- Focus on: Network security,Scanner,NodeJS,JAVA,WWW Blog: http://www.nohouse.net

Hi, I?m testing to start a KVM-VM with different CPU settings and I get an weird error when I use the parameter: <cpu mode='host-model'> !! I have a AMD Opteron 4280 CPU, but in the VM, proc/cpuinfo shows me, that I?m using Intel core2duo cpu model T7700 and in the flag-line of proc/cpu the system is listing the svm-flag of AMD?!?! If I use <cpu

...one have masked their CPU flags with Libvirt?? It's because I have done so with Libvirt and Virsh compare / baseline. But when I boot the DomU I see the same flags as if I hadn't declare de <cpu> tag containing the features just as is described in: http://libvirt.org/formatdomain.html#elementsCPU I posted here my XML file definition: http://pastebin.com/ze5wvSZt I would be really grateful if someone shared your domain XML definition with me or tell me the syntax. I've been struggling for hours, just you know, following the documentation available but there is no functionality for me...

...); - } end_element (); + single_element_format ("vcpu", "%d", config->vcpus); if (config->cpu.vendor || config->cpu.model || config->cpu.sockets || config->cpu.cores || config->cpu.threads) { /* https://libvirt.org/formatdomain.html#elementsCPU */ start_element ("cpu") { attribute ("match", "minimum"); - if (config->cpu.vendor) { - start_element ("vendor") { - string (config->cpu.vendor); - } end_element (); - } + if (config-&gt...

...uct data_conn *data_conns, string_format ("%d", config->vcpus); } end_element (); + if (config->cpu.vendor || config->cpu.model || + config->cpu.sockets || config->cpu.cores || config->cpu.threads) { + /* https://libvirt.org/formatdomain.html#elementsCPU */ + start_element ("cpu") { + attribute ("match", "minimum"); + if (config->cpu.vendor) { + start_element ("vendor") { + string (config->cpu.vendor); + } end_element (); + } + if (config-&gt...

This is tangentially related to: https://bugzilla.redhat.com/show_bug.cgi?id=1372668 The problem in that bug is that we didn't pass the source CPU model (Sandybridge in that case) through to the target RHV hypervisor. So when the Windows guest booted on the target it gives an error about CPU hardware being disconnected (although it otherwise boots and works fine). This patch series

...andled by F<main.c>. + * CPU model is essentially impossible to get without using libvirt, + * but we cannot use libvirt for the reasons outlined in this message: + * https://www.redhat.com/archives/libvirt-users/2017-March/msg00071.html * - * See: L<https://libvirt.org/formatdomain.html#elementsCPU> + * Note that #vCPUs and amount of RAM is handled by F<main.c>. */ #include <config.h> @@ -40,15 +37,10 @@ #include <stdarg.h> #include <string.h> #include <errno.h> +#include <error.h> #include <libintl.h> -#ifdef HAVE_LIBVIRT -#include <...

v1 -> v2: - Support for passing topology through -o glance. - Support for passing topology through -o rhv. - Use bool for acpi/apic/pae struct fields in virt-p2v. - Write the xpath expression in error messages instead of file/line. - Fix more memory leaks in virt-p2v cpuid.c. - Passes make check & check-valgrind. There may be some other minor changes. I believe that everything

v1 was here: https://www.redhat.com/archives/libguestfs/2018-October/msg00047.html v2 was here: https://www.redhat.com/archives/libguestfs/2018-October/msg00051.html v3: - Back to using string/string_format and attribute/attribute_format. - Add both single_element and single_element_format. - Rebased and retested. Rich.

v1 was here: https://www.redhat.com/archives/libguestfs/2018-October/msg00047.html However it was broken in a few ways. First of all the documentation was broken because "/**" enhanced comments were not permitted on macros. This is fixed in the new 1/4 patch. Secondly we didn't use single_element() everywhere possible, which is fixed in the new 4/4 patch. Lastly I've

Now that virt-p2v has its own repository [1] and releases [2], it is time to remove it from libguestfs. [1] https://github.com/libguestfs/virt-p2v [2] http://download.libguestfs.org/virt-p2v/ Pino Toscano (2): Remove virt-p2v Remove remaining virt-p2v bits .gitignore | 4 - Makefile.am | 7 +- bash/Makefile.am