** Attachment added: source guest logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725328/+files/source.log.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** Attachment added: Source Libvirtd logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725330/+files/source_libvirtd.logs
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** Attachment added: Destination Libvirtd logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725331/+files/destination_libvirtd.logs
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** Attachment added: Destination guest logs
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725329/+files/dest.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
Il 04/07/2013 23:07, Peter Lieven ha scritto:
Am 04.07.2013 um 14:37 schrieb Paolo Bonzini pbonz...@redhat.com:
Il 03/07/2013 23:23, Peter Lieven ha scritto:
BDC is not used. I had an implementation that sent multiple descriptors
out, but
at least for my storage the maximum unmap counts
[CCing Vadim and Yan]
On Thu, Jul 04, 2013 at 07:00:49AM +, Libaiqing wrote:
Hi asias,
1 Window can not boot from vhost-scsi device;
2 A non-bootable vhost-scsi device can not be driven by windows guest.(I
used the driver virtio-win-0.1-59 version.)
Do you have any
Il 05/07/2013 05:26, Liu Ping Fan ha scritto:
Currently, unrealized is triggered in device_unparent(). But
unrealized normally involves the reclaim of resource occupied by
DeviceState. To obey the idiom that reclaiming resource when
refcnt reach zero, move it on the path of object_finalize().
The device MIGHT map or anchor the blocks after the unmap but it may
only do so if the blocks that become mapped are all zero.
So I think you can safely assume that if lbprz==1 then it will always
read back as zero no matter what happens internally in the target.
Either the block becomes
The destination VM's log says:
qemu: warning: error while loading state section id 1
This indicates that either there was an error on the destination while
loading state or the migration stream got out of sync.
Please check that QEMU on source and destination are identical. If you
are
Il 04/07/2013 22:09, Paolo Bonzini ha scritto:
Il 04/07/2013 19:17, Andreas Färber ha scritto:
Also if at some point you try to use, e.g., q35 rather than i440fx
machine, it might have EHCI by default and the snippet would be
instantiating a duplicate one. I.e., the three levels of dependency
Thanks, I ll work on this and update it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1192499
Title:
virsh migration copy-storage-all fails with Unable to read from
monitor: Connection reset
- Messaggio originale -
Da: Fabio Fantoni fabio.fant...@m2r.biz
A: Paolo Bonzini pbonz...@redhat.com
Cc: Andreas Färber afaer...@suse.de, Stefano Stabellini
stefano.stabell...@eu.citrix.com,
xen-de...@lists.xensource.com, Wei Liu wei.l...@citrix.com, Ian
Campbell
On Wed, Jul 03, 2013 at 04:34:15PM +0200, Paolo Bonzini wrote:
@@ -146,23 +159,20 @@ static inline int is_bit_set(BlockDriverState *bs,
int64_t bitnum)
static int coroutine_fn cow_co_is_allocated(BlockDriverState *bs,
int64_t sector_num, int nb_sectors, int *num_same)
{
+
On Wed, Jul 03, 2013 at 04:34:20PM +0200, Paolo Bonzini wrote:
diff --git a/qemu-img.c b/qemu-img.c
index f8c97d3..857e2ca 100644
--- a/qemu-img.c
+++ b/qemu-img.c
@@ -2073,6 +2073,10 @@ static int img_rebase(int argc, char **argv)
/* If the cluster is allocated, we don't
On 4 July 2013 21:40, Richard Henderson r...@twiddle.net wrote:
There are several hosts with only a div insn. Remainder is computed
manually from the quotient and inputs. We can do this generically.
Signed-off-by: Richard Henderson r...@twiddle.net
Reviewed-by: Peter Maydell
Il 05/07/2013 11:02, Paolo Bonzini ha scritto:
- Messaggio originale -
Da: Fabio Fantoni fabio.fant...@m2r.biz
A: Paolo Bonzini pbonz...@redhat.com
Cc: Andreas Färber afaer...@suse.de, Stefano Stabellini
stefano.stabell...@eu.citrix.com,
xen-de...@lists.xensource.com, Wei Liu
On 4 July 2013 21:40, Richard Henderson r...@twiddle.net wrote:
We can now detect and use divide instructions at runtime, rather than
having to restrict their availability to compile-time.
Signed-off-by: Richard Henderson r...@twiddle.net
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
On 4 July 2013 21:40, Richard Henderson r...@twiddle.net wrote:
As it really controls the availability of a thumb interworking
instruction on armv5t.
Signed-off-by: Richard Henderson r...@twiddle.net
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
-- PMM
On 4 July 2013 21:40, Richard Henderson r...@twiddle.net wrote:
GCC 4.8 defines a handy __ARM_ARCH symbol that we can use, which
will make us nicely forward compatible with ARMv8 AArch32.
Signed-off-by: Richard Henderson r...@twiddle.net
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
--
On 4 July 2013 21:40, Richard Henderson r...@twiddle.net wrote:
With this we can generate armv7 insns even when the OS compiles for a
lower common denominator. The macros are arranged so that when we do
compile for a given ISA, all of the runtime checks for that ISA are
optimized away.
Thanks Alex! Currently I'm trying to enable Wayland in Tizen Emulator. Tizen
Emulator is a clone of QEMU. Tizen can run in it as guest OS. It seems like
that spice does not fit this requirement.
Hi, I don't known if it's really a problem from qemu or tizen emulator.
Wayland is running on your
Il 05/07/2013 11:27, Fabio Fantoni ha scritto:
What is the best parameters for adding usb2 controller, those who had
already done?
About usb1 controller implementation parameter in xen is only with -usb,
is correct or need something better?
-usb is USB 1.0 on pc and USB 2.0 on q35.
The
Il 05/07/2013 11:19, Stefan Hajnoczi ha scritto:
/* If the cluster is allocated, we don't need to take action */
ret = bdrv_is_allocated(bs, sector, n, n);
+if (ret 0) {
+error_report(error while reading from file);
+
On 04.07.2013 11:14, poma wrote:
On 03.07.2013 13:43, Daniel P. Berrange wrote:
On Tue, Jul 02, 2013 at 01:25:21PM +0200, poma wrote:
Hello people,
libvirtd (libvirt) 1.0.5.2
virsh 1.0.5.2
virt-manager 0.10.0
Host:
Linux localhost 3.9.8-300.fc19.x86_64 #1 SMP Thu Jun 27 19:24:23 UTC
Hi Asias,
Windows driver should be able to support as many logical units and targets
as reported by QEMU. In case of VIRTIO_SCSI_S_BAD_TARGET it will just propagate
the relevant SRB error code to the port driver.
In any case, I will try reproducing this problem on my system.
Best,
Vadim.
-
On 28 June 2013 08:01, Rob Landley r...@landley.net wrote:
Now that the next kernel's about to come out, I'm trying to get my arm
versatile image to work under qemu 1.5.0. The old kernel doesn't work, and
the current vanilla kernel doesn't work. This change broke it.
Nope. Current vanilla is
Since 80ccf93b we flush the block device during close. The
bdrv_drain_all() call should come before bdrv_flush() to ensure guest
write requests have completed. Otherwise we may miss pending writes
when flushing.
Call bdrv_drain_all() again for safety as the final step after
bdrv_flush(). This
From: Fam Zheng f...@redhat.com
Depending on the subformat, has_zero_init queries underlying storage for
flat extent. If it has a flat extent and its underlying storage doesn't
have zero init, return 0. Otherwise return 1.
Aligns the operator assignments.
Signed-off-by: Fam Zheng
The following changes since commit ab8bf29078e0ab8347e2ff8b4e5542f7a0c751cf:
Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2013-07-03
08:37:00 -0500)
are available in the git repository at:
git://github.com/stefanha/qemu.git block
for you to fetch changes up to
From: Fam Zheng f...@redhat.com
CURL driver requests partial data from server on guest IO req. For HTTP
and HTTPS, it uses Range: *** in requests, and this will not work if
server not accepting range. This patch does this check when open.
* Removed curl_size_cb, which is not used: On one hand
for spice (qxl) video card, a kms driver in currently in developement
http://lists.freedesktop.org/archives/dri-devel/2013-March/035714.html
update : This has been released in kernel 3.10.
- Mail original -
De: Alexandre DERUMIER aderum...@odiso.com
À: Max A Yu max.a...@intel.com
Cc:
** This bug is no longer a duplicate of bug 1033727
USB passthrough doesn't work anymore with qemu-kvm 1.1.1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096
Title:
USB Passthrough not
With this patch dump-guest-memory on s390 produces an ELF formatted,
crash-readable dump.
In order to implement this, the arch-specific part of dump-guest-memory
was added:
target-s390x/arch_dump.c contains the whole set of function for writing
Elf note sections of all types for s390x.
If bdrv_flush_all() returns an error, there is an inconsistency in the
view of an image file between the source and the destination host.
Completing the migration would lead to corruption. Better abort
migration in this case.
Kevin Wolf (3):
block: Add return value for bdrv_flush_all()
cpus:
If flushing the block devices fails, return an error. The VM is stopped
anyway.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
cpus.c | 20 +---
include/sysemu/sysemu.h | 4 ++--
stubs/vm-stop.c | 2 +-
3 files changed, 16 insertions(+), 10 deletions(-)
bdrv_flush() can fail, and bdrv_flush_all() should return an error as
well if this happens for a block device. It returns the first error
return now, but still at least tries to flush the remaining devices even
in error cases.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block.c
If bdrv_flush_all() returns an error, there is an inconsistency in the
view of an image file between the source and the destination host.
Completing the migration would lead to corruption. Better abort
migration in this case.
To reproduce this case, try the following (ensures that there is
I don't recall saying there was a duplicate of this bug? I merely
objected to #1033727 being marked a duplicate.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096
Title:
USB Passthrough not
While the Calxeda Midway part is actually a bit more than a Highbank
with A15s, for QEMU's purposes this view is sufficient.
So refactor the Highbank initialization to allow a very similar
machine and add the necessary changes to support the new machine
called midway.
This is based on work by Rob
To allow the modelling of machines similar to Calxeda Highbank,
introduce a parameter to the init function and call it from a
wrapper. This allows to tweak the definition for individual machines
later on.
Signed-off-by: Andre Przywara andre.przyw...@calxeda.com
---
hw/arm/highbank.c | 29
The Calxeda ECX-2000 chip (aka. Midway) is model-wise quite similar
to the Highbank. The most prominent difference is the Cortex-A15 CPU
core in it, together with the associated core peripherals.
Add a new ARM machine type called midway.
Move the L2 cache controller device into the Highbank
[PATCH] Target-ppc : Enhance the CPU node labels for the guest
device tree for pseries.
In absence of a -CPU parameter in the qemu command line, the nodes of
KVM-enabled guest device tree look like this :
/proc/device-tree/cpus/HOST@0/...
/proc/device-tree/cpus/HOST@4/...
This patch replaces
host_alarm_handler() may be invoked as a signal handler. Previously we
did more processing in the signal handler and therefore needed
signal-safe timer code.
Today host_alarm_handler() just marks the alarm timer as expired/pending
and notifies the main loop using qemu_notify_event().
Therefore
This series makes the following functions thread-safe:
qemu_mod_timer_ns()
qemu_mod_timer()
qemu_del_timer()
qemu_timer_pending()
The following were already thread-safe:
qemu_free_timer()
qemu_new_timer()
qemu_timer_expired()
Now it is possible to use QEMUTimer outside the QEMU
This patch makes QEMUClock-active_timers list iteration thread-safe. With
additional patches, this will allow threads to use timers without holding the
QEMU global mutex.
The qemu_next_alarm_deadline() function was restructured to reduce code
duplication, which would have gotten worse due to the
Il 05/07/2013 14:03, Kevin Wolf ha scritto:
If flushing the block devices fails, return an error. The VM is stopped
anyway.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
cpus.c | 20 +---
include/sysemu/sysemu.h | 4 ++--
stubs/vm-stop.c | 2 +-
When a timer's expiration time is changed we may need to rearm the alarm
timer. Rearming is necessary when the nearest deadline changes.
This patch introduces the qemu_alarm_timer-timer_modified boolean and a
lock to protect it. It moves rearming the alarm timer from inside
qemu_mod_timer_ns()
Il 05/07/2013 14:39, Stefan Hajnoczi ha scritto:
This patch makes QEMUClock-active_timers list iteration thread-safe. With
additional patches, this will allow threads to use timers without holding the
QEMU global mutex.
The qemu_next_alarm_deadline() function was restructured to reduce code
On Wed, Jun 26, 2013 at 05:46:11PM +0800, liu ping fan wrote:
On Tue, Jun 25, 2013 at 5:40 PM, Kevin Wolf kw...@redhat.com wrote:
Am 25.06.2013 um 19:26 hat Liu Ping Fan geschrieben:
BH will be used outside big lock, so introduce lock to protect
between the writers, ie, bh's adders and
The a15mpcore device claims that its default value for num-irq
is the number of interrupts used by the A15MP in the vexpress-a15
board. However that chip has 128 external interrupts, not 64.
Since there is only one A15 based model in QEMU currently, we
can fix this by simply changing the default
Il 05/07/2013 15:46, Stefan Hajnoczi ha scritto:
On Wed, Jun 26, 2013 at 05:46:11PM +0800, liu ping fan wrote:
On Tue, Jun 25, 2013 at 5:40 PM, Kevin Wolf kw...@redhat.com wrote:
Am 25.06.2013 um 19:26 hat Liu Ping Fan geschrieben:
BH will be used outside big lock, so introduce lock to protect
This patch adds the optional file entry to the query-block output.
The value is a json-object representing the information about the
underlying file or device (when present).
Signed-off-by: Federico Simoncelli fsimo...@redhat.com
---
block/qapi.c |7 +++
qapi-schema.json
On 7/4/13 8:54 , Paolo Bonzini pbonz...@redhat.com wrote:
Il 03/07/2013 18:19, Tomoki Sekiyama ha scritto:
On 7/3/13 11:58 , Paolo Bonzini pbonz...@redhat.com wrote:
Il 03/07/2013 17:49, Tomoki Sekiyama ha scritto:
-return ga_install_service(path, log_filepath,
It seems to be unused since several years (commit
be995c27640a82c7056b6f53d02ec823570114e5 in 2006).
Signed-off-by: Stefan Weil s...@weilnetz.de
---
exec.c |1 -
include/exec/cpu-all.h |1 -
2 files changed, 2 deletions(-)
diff --git a/exec.c b/exec.c
index
With this I mean the bugreport, not the feature requested.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/764252
Title:
wishlist: kirkwood support
Status in QEMU:
New
Bug description:
This is
This was added in 2011, is there a plan to integrate support for
kirkwood?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/764252
Title:
wishlist: kirkwood support
Status in QEMU:
New
Bug
On 2013-07-05 14:39, Stefan Hajnoczi wrote:
host_alarm_handler() may be invoked as a signal handler. Previously we
did more processing in the signal handler and therefore needed
signal-safe timer code.
Signal handlers run in the context of the signal processing thread, i.e.
the iothread so
On Thu, Jul 04, 2013 at 05:53:08PM +0800, Wanlong Gao wrote:
From: Bandan Das b...@redhat.com
This allows us to use the cpus property multiple times
to specify multiple cpu (ranges) to the -numa option :
-numa node,cpus=1,cpus=2,cpus=4
or
-numa node,cpus=1-3,cpus=5
Note that after
On 2013-07-05 14:39, Stefan Hajnoczi wrote:
This series makes the following functions thread-safe:
qemu_mod_timer_ns()
qemu_mod_timer()
qemu_del_timer()
qemu_timer_pending()
The following were already thread-safe:
qemu_free_timer()
qemu_new_timer()
qemu_timer_expired()
If somebody wants to write and submit code I will review it. I am not
aware of anybody who is working on kirkwood emulation support or with
plans to do so.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Thu, Jul 04, 2013 at 05:53:07PM +0800, Wanlong Gao wrote:
[...]
Bandan Das (1):
NUMA: Support multiple CPU ranges on -numa option
Wanlong Gao (9):
NUMA: Add numa_info structure to contain numa nodes info
NUMA: Add Linux libnuma detection
NUMA: parse guest numa nodes memory
On Thu, Jul 04, 2013 at 05:53:17PM +0800, Wanlong Gao wrote:
Show host memory policy of nodes in the info numa monitor command.
After this patch, the monitor command info numa will show the
information like following if the host numa support is enabled:
(qemu) info numa
2 nodes
On Thu, Jul 04, 2013 at 05:53:09PM +0800, Wanlong Gao wrote:
Add the numa_info structure to contain the numa nodes memory,
VCPUs information and the future added numa nodes host memory
policies.
Signed-off-by: Andre Przywara andre.przyw...@amd.com
Signed-off-by: Wanlong Gao
Am 05.07.2013 21:32, schrieb Eduardo Habkost:
On Thu, Jul 04, 2013 at 05:53:09PM +0800, Wanlong Gao wrote:
Add the numa_info structure to contain the numa nodes memory,
VCPUs information and the future added numa nodes host memory
policies.
Signed-off-by: Andre Przywara
The help message contains single quotes which got lost in the output.
Fix also a typo and use two instead of three lines.
Signed-off-by: Stefan Weil s...@weilnetz.de
---
po/Makefile |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/po/Makefile b/po/Makefile
index
These patches are included:
[PATCH 1/4] po/Makefile: Fix and improve help message
[PATCH 2/4] po/Makefile: Fix *.mo generation for out-of-tree builds
[PATCH 3/4] po/Makefile: Fix generation of messages.po
[PATCH 4/4] po/Makefile: Use macro quiet-command for nice looking
Regards
Stefan W.
* Tell xgettext that we use UTF-8 encoding (this is currently optional).
* Set charset=UTF-8 in messages.po. This avoids warnings from msgmerge:
warning: Charset CHARSET is not a portable encoding name.
* Use filename relative to root directory (ui/gtk.c instead of ../ui/gtk.c
or
Commit f84756554e32d97db3aa949db1dd58c7eea62375 added a wildcard search
for *.po files. This search found no files for out of tree builds, so
those builds no longer created and installed *.mo files.
Signed-off-by: Stefan Weil s...@weilnetz.de
---
po/Makefile | 19 +++
1 file
Suppress also the ... done message from msgmerge.
Signed-off-by: Stefan Weil s...@weilnetz.de
---
po/Makefile |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/po/Makefile b/po/Makefile
index a6ab482..705166e 100644
--- a/po/Makefile
+++ b/po/Makefile
@@ -5,6 +5,7
On Thu, Jul 04, 2013 at 01:52:46PM +0100, Stefano Stabellini wrote:
On Thu, 4 Jul 2013, Paul Durrant wrote:
Introduces a new Xen PV PCI device which will act as a binding point for
PV drivers for Xen.
The device has parameterized vendor-id, device-id and revision to allow to
be configured
Public bug reported:
Host Gentoo linux 32bit
Guest Windows XP SP3
qemu 1.4.2 and
qemu fresh get clone and build 2013-07-04 (version1.5.50)
qemu command line
qemu-system-i386 -enable-kvm localtime -m 2047 -boot d
/archive3/qemu/WindowsXP.img -net nic,model=rtl8139 -net user -usb
-device
Hello everyone,
Inspired by a complaint from Scott about information getting lost
amongst qemu-devel mails, and spawning a qemu-announce mailing list
being out of my powers, I have started a simple Wiki page:
http://wiki.qemu.org/DeveloperNews
The idea is to have a brief summary of decisions
Hi Andreas,
On Tue, Jul 2, 2013 at 6:18 PM, Andreas Färber afaer...@suse.de wrote:
Hi Jia,
Am 02.07.2013 11:29, schrieb Jia Liu:
On Tue, Jul 2, 2013 at 5:11 PM, Dongxue Zhang elta@gmail.com
mailto:elta@gmail.com wrote:
Make target-openrisc running OK by add typename in
Am 05.07.2013 19:07, schrieb Stefan Weil:
It seems to be unused since several years (commit
be995c27640a82c7056b6f53d02ec823570114e5 in 2006).
Signed-off-by: Stefan Weil s...@weilnetz.de
Confirmed unused,
Reviewed-by: Andreas Färber afaer...@suse.de
Andreas
--
SUSE LINUX Products GmbH,
Am 03.07.2013 00:54, schrieb Andreas Färber:
Choose CPUState rather than PowerPCCPU since doing a CPU() cast on the
macro argument would hide type mismatches.
Signed-off-by: Andreas Färber afaer...@suse.de
---
target-ppc/mmu-hash32.c | 4 ++--
target-ppc/mmu-hash64.c | 4 ++--
Am 03.07.2013 20:42, schrieb Andreas Färber:
Hello,
As a follow-up to my CPUState part 11 series changing log_cpu_state[_mask]()
argument to CPUState, these patches propagate X86CPU argument where possible.
This is in response to rth asking about type/placement of variables.
[...]
Andreas
When forwarding a segmentation fault into the guest process, we were passing
the host's address directly into the guest process's signal descriptor.
That obviously confused the guest process, since it didn't know what to make
of the (usually 32-bit truncated) address. Passing in h2g(address)
Howdy,
It's been a while since I've tried to run wine in QEMU's i386
linux-user target, so I figured I'd give it a go again.
Obviously I've hit a bunch of obstacles, some of which were old,
some of which we only introduced recently.
However, with this patch set I am able to successfully run
When we create a new thread, there is no reason to reset it. I'm fairly sure
the code has mostly been left in there because nobody understood why it was
there in the first place.
Remove the reset. A new thread's kernel sided state should be identical to
the old one's.
Signed-off-by: Alexander
The epoll emulation uses data structures without packing them, so the
compiler might choose to add padding inside.
This patch makes the most offending one (target_epoll_event) a packed
structure to make sure we don't pad it by accident. ARM would pad it,
so declare the padding mandatory for ARM
The i386 target is now able to properly handle NPTL. Enable it.
Signed-off-by: Alexander Graf ag...@suse.de
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 0e0adde..61f2770 100755
--- a/configure
+++ b/configure
@@ -4156,6
When we get a segmentation fault we check whether the fault was a write. If
it was a write, it might be a fault because we tried to modify a code region.
This logic does not work on ARM hosts, because they don't evaluate whether a
segementation fault is due to a write. Instead they always declare
The page_unprotect() function is running everything locked. Before every
potential exit path of the function mmap_unlock() gets called to make sure
we don't leak the lock.
However, the function calls tb_invalidate_phys_page() which again can
exit a signal through longjmp, leaving our
While looking for cmsg entries, we want to compare guest pointers to see
whether we're at the end of the passed in array.
However, what we really do is we compare our in-use host pointer with the
to-be-the-end guest pointer. This comparison is obviously bogus.
Change the comparison to compare
Most kernels these days have protection code in place to forbid user space
to access low memory. The barrier varies between architectures though.
For this purpose we have the guest base option that allows us to offset
guest visible memory from host memory, so that the guest process thinks
it can
We can easily set the TLS on i386. Add code to do so.
Signed-off-by: Alexander Graf ag...@suse.de
---
linux-user/i386/target_cpu.h | 12 ++--
linux-user/syscall.c |2 +-
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/linux-user/i386/target_cpu.h
Am 01.07.2013 19:14, schrieb Richard Henderson:
On 06/29/2013 01:01 PM, Andreas Färber wrote:
Since commit cb446ecab714b2444a270be209e0533bcd2ee534 (kvm: Change
cpu_synchronize_state() argument to CPUState), one was no longer
accessing CPUArchState, the other was just checking existence.
Am 01.07.2013 22:19, schrieb Richard Henderson:
Which allows removing env from DisasContext.
Signed-off-by: Richard Henderson r...@twiddle.net
Reviewed-by: Andreas Färber afaer...@suse.de
I notice that implver is only ever assigned in CPUs' instance_init, so a
candidate for moving to
This patch adds tests for sync modes top and none.
Signed-off-by: Ian Main im...@redhat.com
---
tests/qemu-iotests/055| 67 ---
tests/qemu-iotests/055.out| 4 +--
tests/qemu-iotests/group | 2 +-
tests/qemu-iotests/iotests.py | 5
This patch adds sync-modes to the drive-backup interface and
implements the FULL, NONE and TOP modes of synchronization.
FULL performs as before copying the entire contents of the drive
while preserving the point-in-time using CoW.
NONE only copies new writes to the target drive.
TOP copies
This patch adds sync modes on top of the work that Stefan Hajnoczi has done.
These patches apply on kevin/block with
'[PATCH] block: add drive_backup HMP command' also applied.
Hopefully all is in order as this is my first QEMU patch. Many thanks to
Stephan and Fam Zheng for their help.
V2:
On Fri, Jul 05, 2013 at 06:35:26PM -0700, Ian Main wrote:
This patch adds sync modes on top of the work that Stefan Hajnoczi has done.
These patches apply on kevin/block with
'[PATCH] block: add drive_backup HMP command' also applied.
Hopefully all is in order as this is my first QEMU
Am 01.07.2013 22:19, schrieb Richard Henderson:
As discussed in the QOM thread.
Thanks, applying to qom-cpu-next to rebase qom-cpu-11:
https://github.com/afaerber/qemu-cpu/commits/qom-cpu-next
Andreas
Richard Henderson (2):
target-alpha: Copy singlestep_enabled to DisasContext
94 matches
Mail list logo
