similar to: [GIT PULL v8 0/6] save/restore on Xen

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

flight 12357 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12357/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-oldkern 2 host-install(2) broken REGR. vs. 11890 build-i386 2 host-install(2) broken REGR. vs. 11890

flight 10413 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10413/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 3 host-install(3) broken test-amd64-i386-win 8 guest-saverestore fail REGR. vs. 10201 test-i386-i386-win 8 guest-saverestore fail REGR. vs. 10201

This series extends QMP introspection to cover deprecation. Additionally, new option -compat lets you configure what to do when deprecated interfaces get used. This is intended for testing users of the management interfaces. It is experimental. -compat deprecated-input=<in-policy> configures what to do when deprecated input is received. Available policies: * accept: Accept deprecated

Hi On Tue, Mar 17, 2020 at 12:55 PM Markus Armbruster <armbru@redhat.com> wrote: > > This series extends QMP introspection to cover deprecation. > Additionally, new option -compat lets you configure what to do when > deprecated interfaces get used. This is intended for testing users of > the management interfaces. It is experimental. > > -compat

This series extends QMP introspection to cover deprecation. Additionally, new option -compat lets you configure what to do when deprecated interfaces get used. This is intended for testing users of the management interfaces. It is experimental. -compat deprecated-input=<in-policy> configures what to do when deprecated input is received. Available policies: * accept: Accept deprecated

New option -compat lets you configure what to do when deprecated interfaces get used. This is intended for testing users of the management interfaces. It is experimental. -compat deprecated-input=<in-policy> configures what to do when deprecated input is received. Available policies: * accept: Accept deprecated commands and arguments (default) * reject: Reject them * crash: Crash

This moves the xen_modified_memory call from cpu_physical_memory_map to cpu_physical_memory_unmap because the memory could be migrated before the device model have written to it. But because we need to know the guest address and to avoid rewriting a new function, the call is moved to qemu_invalidate_entry. So this later has to new parameters, the length of the mapping and if it was a write.

I assume this commit message was supposed to be "Enable VGA acceleration for VTI" right? We''re not actually accelerating CGA right? Regards, Anthony Liguori Xen patchbot-unstable wrote: > # HG changeset patch > # User kaf24@firebug.cl.cam.ac.uk > # Node ID e67432187b88ee60433779ad0f004b532ed378c8 > # Parent 639ad22eb7c80ac21c3958747b879892680bdaba >

flight 2041 xen-unstable real http://www.chiark.greenend.org.uk/~xensrcts/logs/2041/ Regressions :-( tests which did not succeed: test-amd64-amd64-pair 12 guest-migrate/src_host/dst_host fail never pass test-amd64-amd64-pv 8 guest-saverestore fail like 2017 test-amd64-amd64-win 6 guest-saverestore fail REGR. vs. 2017 test-amd64-amd64-xl

Am 18.02.2012 09:24, schrieb Blue Swirl: > On Wed, Feb 8, 2012 at 17:06, Roger Pau Monne <roger.pau@entel.upc.edu> wrote: >> libm is used in cutils.c, but the library was not specified >> when linking some binaries, throwing the following error: >> >> cutils.o: In function `strtosz_suffix_unit': >> /home/royger/xen-clean/tools/qemu-xen-dir/cutils.c:354:

flight 14916 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/14916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 15 guest-stop fail REGR. vs. 14856 test-amd64-i386-xl 14 guest-localmigrate/x10 fail REGR. vs. 14856 test-amd64-i386-xend-winxpsp3 7

Keir Fraser wrote: > On 11 Jan 2006, at 01:54, Yu, Ke wrote: > >> The vmx domain still blocks in my environment. HV complains it can >> not find E820 table and HVM INFO page. After fixing them with the >> following patch, HV does not complain any thing. But the vmx domain >> just silently blocks. Would you please take a look? Thanks > > I think the problem

System: CentOS Linux release 6.0 (final) Kernel: 2.6.32-71.23.1.el6.x86_64 KVM: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2) Libvirt: ibvirtd (libvirt) 0.8.1 Hi everyone, I only recently subscribed to this list and hope you can shed some light on the following error. I created a VM on my Centos 6 KVM machine, used a qcow2 image and wanted to create a snapshot via 'virsh

Greetings, Currently, as I understand PV memory allocation, the Guest''s pfn -> mfn physmap will get populated on-demand as the guest uses more an more of its memory reservation. Is it possible to also make this go in the reverse direction? For example: let''s say we have a guest that is mostly idle and has a great deal of free memory and we decide to balloon down the domain.

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm'

Hi David, thanks for the added input! I'm taking the liberty to snip a few paragraphs to trim this email down a bit. On Thu, Feb 8, 2018 at 1:07 PM, David Hildenbrand <david@redhat.com> wrote: >> Just to give an example, >> https://www.redhat.com/en/blog/inception-how-usable-are-nested-kvm-guests >> from just last September talks explicitly about how "guests can

Attempting to take snapshots of VM using virsh with the following command, # virsh -c qemu:///system snapshot-create CentOS6-x86-001 Results in the following error, error: internal error unable to execute QEMU command 'savevm': The command savevm has not been found The VM's virtual disks are qcow2. Below is the XML file for this vm ------------ <domain type='kvm'

flight 5503 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5503/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-xl-credit2 14 guest-localmigrate/x10 fail pass in 5502 test-amd64-xcpkern-i386-xl 14 guest-localmigrate/x10 fail pass in 5502 Tests which did not succeed, but are not blocking,

On Thu, Feb 8, 2018 at 2:47 PM, David Hildenbrand <david@redhat.com> wrote: >> Again, I'm somewhat struggling to understand this vs. live migration — >> but it's entirely possible that I'm sorely lacking in my knowledge of >> kernel and CPU internals. > > (savevm/loadvm is also called "migration to file") > > When we migrate to a file, it