similar to: Compilation error in make tools - undefined reference to `x86_cpu_list''

Source: xen Version: 4.1.4-4 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value

This time make world on Ubuntu 10.04 gives following error gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .fsimage.so.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -I../../../tools/libfsimage/common/

I downloaded the "QEMU 0.8.2 CVS20070120 + patches snapshot January 20th 2007" and it was compiled ok for "ppc-softmmu" but failed in the "sparc-softmmu" with the message: ../dyngen -o op.h op.o dyngen: ret; restore; not found at end of op_ldstub_kernel can someone tell me what to do or where can I find a QEMU software running on solaris/sparc to lunch linux

Hi, I get the following error when running libvirtd on MacOS as root: $ sudo libvirtd 2019-07-11 00:12:33.379+0000: 123145573953536: info : libvirt version: 5.5.0 2019-07-11 00:12:33.379+0000: 123145573953536: warning : virProcessGetStartTime:1070 : Process start time of pid 49746 not available on this platform 2019-07-11 00:12:33.379+0000: 123145573953536: error : virSysinfoReadDMI:1172 :

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol

On Fri, Jan 24, 2014 at 04:49:24PM -0800, Tim Fall wrote: > Not that I know of, resource usage seems totally normal. Also, as I > mentioned, virt-install and virt-manager can both access and run vm's on > qmeu without any trouble. Ulimit is also unset. You can try a different qemu from upstream, which should diagnose whether this is a kernel problem or a qemu problem:

I gave this series a spin, along a custom QEMU, and `supermin` from Git, for my `libguestfs-test-tool` itself fails with: "Could not open option rom 'linuxboot_dma.bin': No such file or directory" How I went about: (1) Build QEMU with https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05891.html -- Add optionrom compatible with fw_cfg DMA version

Some general comments on using the patch: * For libguestfs I chose to add -compat deprecated-input=reject,deprecated-output=hide This is only enabled in developer builds of libguestfs when we are running qemu directly (not via libvirt). The patch for this is attached. * What's the point/difference in having reject vs crash? * I hope that by hiding deprecated QAPI fields we may

Hello to everyone. I'm trying to use qemu 5.1 with virt-manager and libvirt on my ARM chromebook (armhf 32 bit cpu) running with Devuan 4 as host o.s. By default it uses qemu and its dependencies,version 5.2. I remember that I can't use qemu 5.2,because it doesn't have any support for KVM as you can read here : https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg02074.html

On 14.05.20 13:10, David Hildenbrand wrote: > On 14.05.20 12:12, David Hildenbrand wrote: >> On 14.05.20 12:02, teawater wrote: >>> >>> >>>> 2020?5?14? 16:48?David Hildenbrand <david at redhat.com> ??? >>>> >>>> On 14.05.20 08:44, teawater wrote: >>>>> Hi David, >>>>> >>>>> I got a

Hi,all,i build qemu-kvm1.0.93 from source code on centos6.2 , # qemu-system-x86_64 --version QEMU emulator version 1.0.93 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard and the guestfish's version: # guestfish --version guestfish 1.7.17 but when i use the guestfish command to upload a file to a vm,it does not work , # guestfish --rw -i -d centosvm upload /test/ifcfg-eth0_centos

On 16.09.14 14:21, Richard W.M. Jones wrote: > On Tue, Sep 16, 2014 at 04:04:02PM +0300, Shahar Havivi wrote: > > Hi, > > > > I am trying to convert from esx server to local directory a VM names CSB, > > Its build from source 77b371b18b6a7ad37105a595931514f542a04396 > > > > When running: > > LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic

On 06/05/2017 10:46 AM, Martin Kletzander wrote: > On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >> I've upgraded from Fedora 20; probably missed a merge of rpmnew with >> existing .conf; permission problem, some other mistake along the way to >> Fedora 25. >> > > Yeah, probably some 'rpm -qV' (or whatever the command to verify all

Hyper-V SynIC (synthetic interrupt controller) device implementation. The implementation contains: * msr's support * irq routing setup * irq injection * irq ack callback registration * event/message pages changes tracking at Hyper-V exit * Hyper-V test device to test SynIC by kvm-unit-tests Andrey Smetanin (7): standard-headers/x86: add Hyper-V SynIC constants target-i386/kvm: Hyper-V

Hyper-V SynIC (synthetic interrupt controller) device implementation. The implementation contains: * msr's support * irq routing setup * irq injection * irq ack callback registration * event/message pages changes tracking at Hyper-V exit * Hyper-V test device to test SynIC by kvm-unit-tests Andrey Smetanin (7): standard-headers/x86: add Hyper-V SynIC constants target-i386/kvm: Hyper-V

On 06/06/2017 04:43 AM, Martin Kletzander wrote: > On Mon, Jun 05, 2017 at 07:52:58PM -0400, Michael C Cambria wrote: >> >> >> On 06/05/2017 10:46 AM, Martin Kletzander wrote: >>> On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >>>> I've upgraded from Fedora 20; probably missed a merge of rpmnew with >>>> existing .conf;

I'm running libvirt 1.0.1 and qemu 1.3. I see the following error of libvirtd startup: 2013-01-19 04:51:06.183+0000: 1459: error : virCommandWait:2287 : internal error Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ /usr/bin/kvm -help) unexpected exit status 1 This is indeed what the return code seems to be for that command. This this just a

On 17.05.2011, at 08:47, David Gibson wrote: > From: Alexey Kardashevskiy <aik at ozlabs.ru> > > The recently added pseries machine does not currently support PCI > emulation. For the (upcoming) kvm case, this is quite difficult to do > because the preferred HV mode for the host kernel does not allow MMIO > emulation (a hardware limitation). > > Therefore, to