similar to: how to detect if qemu supports live disk snapshot

Hi, All The vm can't start when using numa based on centos 6.5(kernel: kernel-2.6.32-431.17.1.el6.x86_64, qemu-kvm: qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64). My numa setting in vm xml is the following: -------------------- <numatune> <memory mode='strict' nodeset='1'/> </numatune> -------------------- When 'nodeset' sets '0', the

Hi, I tried to run domsuspend command on my PowerPC board but failed. # virsh dompmsuspend sdk --target mem error: Domain sdk could not be suspended error: argument unsupported: QEMU guest agent is not configured It seemed that support suspend-to-mem only from capabilities. # virsh capabilities <capabilities> <host>

I am using libvirt 0.10.2.2 and qemu-kvm 1.2.2 (qemu-kvm 1.2.0 + qemu 1.2.2 applied on top plus a number of stability patches). Having issue where my VMs fail to start with the following message: kvm_init_vcpu failed: Cannot allocate memory Following the instructions at http://libvirt.org/formatdomain.html#elementsNUMATuning I've added the following to my VCPU configuration: <vcpu

I hope this question isn't considered too off topic for this list, I am trying to reach the libvirt-sandbox developers, but I could not find a libvirt-sandbox specific mailing list, and it seemed to me that libvirt-sandbox was a part of libvirt itself. I am trying to port libvirt-sandbox to run on a CentOS 6.5 system. This wasn't too hard but, I had to do the following: I have used the

On Tue, Jun 19, 2018 at 12:12:30PM +0100, Richard W.M. Jones wrote: > On Tue, Jun 19, 2018 at 11:43:38AM +0100, Daniel P. Berrangé wrote: > > I'd encourage apps to check the capabilities XML to see what > > machine types are available. > > One issue is we don't always have access to the target hypervisor. > > For example in the Glance case we have to write

Tried to migrate a few VMs from existing system to an older host that we threw in the rack to facilitate some server reshuffling. Migration complained about lack of capabilities (which I expected its an older server) but when I looked at what I should throw into the xml file I got a core2duo when it should have been at least Penryn or something (Xeon E5345) Of course the VMs work fine with

On Mon, May 22, 2017 at 05:03:21PM -0700, W Kern wrote: >Tried to migrate a few VMs from existing system to an older host that we >threw in the rack to facilitate some server reshuffling. > >Migration complained about lack of capabilities (which I expected its an >older server) but when I looked at what I should throw into the xml file >I got a core2duo when it should have been

On Sun, Jun 8, 2008 at 3:28 PM, James Harper <james.harper@bendigoit.com.au> wrote: > I''ve just uploaded 0.9.8 to http://www.meadowcourt.org/downloads > > As a reminder, the wiki page is > http://wiki.xensource.com/xenwiki/XenWindowsGplPv > > This release fixes a bug which could be hit under high disk load (high > number of outstanding requests with fragmented

Test libvirt-users-request@redhat.com schrieb: >Send libvirt-users mailing list submissions to > libvirt-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users >or, via email, send a message with subject or body 'help' to > libvirt-users-request@redhat.com > >You can reach the

On Tue, Jun 19, 2018 at 11:43:38AM +0100, Daniel P. Berrangé wrote: > I'd encourage apps to check the capabilities XML to see what > machine types are available. One issue is we don't always have access to the target hypervisor. For example in the Glance case we have to write something which will be picked up by Nova much later: > > + "hw_machine_type", >

I am using a debian 9 guest, hosted on a ESXi platform with nested virtualisation enabled. On this debian 9 guest when I run libguesfs-test-tool, it fails with an error: "qemu-system-x86_64: /build/qemu-DqynNa/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed." Instead when I use a wrapper script and hook it with the env

Hi all, I have been trying to find out cpu topology using libvirt. When I do 'virsh capabilites', I find this inside <topology> tag: <topology>       <cells num='1'>         <cell id='0'>           <memory unit='KiB'>3908488</memory>           <cpus num='4'>             <cpu id='0' socket_id='0'

On Tue, Sep 17, 2013 at 05:41:12PM +0800, Peeyush Gupta wrote: > Hi all, > > I have been trying to find out cpu topology using libvirt. When > I do 'virsh capabilites', I find this inside <topology> tag: > > > <topology> >       <cells num='1'> >         <cell id='0'> >           <memory

... to be more precise in naming, and also to match Linux. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2009-07-10.orig/xen/arch/ia64/linux-xen/perfmon.c 2009-05-27 13:54:05.000000000 +0200 +++ 2009-07-10/xen/arch/ia64/linux-xen/perfmon.c 2009-07-15 10:02:08.000000000 +0200 @@ -7313,7 +7313,7 @@ xenpfm_context_create(XEN_GUEST_HANDLE(p goto out; /* XXX fmt */ -

On Tue, Jun 19, 2018 at 11:37:46AM +0100, Richard W.M. Jones wrote: > QEMU for x86 supports two machine types, "pc" (emulating the ancient > Intel i440FX chipset originally used by the Pentium Pro), and "q35" > (https://wiki.qemu.org/Features/Q35). > > Currently virt-v2v does not set any machine type, so libvirt or the > target hypervisor will choose some

Hi all, What are the differences between pc and q35?? By default, virt-manager+libvirt setups kvm guest machine as a pc-i440fx-rhel7.1.0. [hicheck at ckvm015 ~]$ /usr/libexec/qemu-kvm -machine ? Supported machines are: pc RHEL 7.1.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.1.0) pc-i440fx-rhel7.1.0 RHEL 7.1.0 PC (i440FX + PIIX, 1996) (default) pc-i440fx-rhel7.0.0

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. Newer versions of libvirt and QEMU will probably switch over to defaulting

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. The latest advice from the QEMU and libvirt communities is not to rely on

On Thursday, 19 July 2018 15:51:04 CEST Tomáš Golembiovský wrote: > Add oVirt specific elemnt to OVF. It represents the combination of > machine type (i440fx/q35) and firmware (BIOS/UEFI). Other than adding a new element in the OVF, this also enables the conversion of UEFI guests to oVirt. It is tested? Does it require other changes? I'd split the addition of <BiosType> to the

Hello I have recently had to reinstall Centos 7.5 to on host computer. I have not be able to set-up qemu to support the q35 chip set. I have several virtual machines that require q35. This is not my first install, I have configured libvirt on many machines in the past, it just worked, it has not required any manual configuration. [root at sj aadmin]# /usr/libexec/qemu-kvm -machine help