fixing quint...@redhat.com email.
--
Jean-Sébastien Frerot
jsfre...@egliseespoir.com
2014-12-19 8:15 GMT-05:00 Frerot, Jean-Sébastien
:
>
> Hi, I've been using kvm for some time now using live migration as well
> with ceph backend. Recently I started running into an issue with only one
> of my
This patch sets the GPIO controller interrupt number to 47,not 43 (and the
Device tree agrees).
Signed-off-by: Amit Singh Tomar
---
hw/ppc/e500.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/ppc/e500.c b/hw/ppc/e500.c index 2832fc0..2cd69a9 100644
--- a/hw/ppc/e500
On Fri, Dec 19, 2014 at 01:18:24PM +, Stefan Hajnoczi wrote:
> From: "Michael S. Tsirkin"
>
> Some guests seem to set BM for e1000 after
> enabling RX.
> If packets arrive in the window, device is wedged.
> Probably works by luck on real hardware, work around
> this by making can_receive depe
Markus Armbruster writes:
> = Introduction =
>
> BDSes can be opened in various ways. Some of them don't provide for
> user configuration. Some of them should.
>
> Example: -drive format=qcow2,file=foo.qcow2 where foo.qcow2 has a raw
> backing file foo.raw. This creates the the following tree
Use build_append_namestring() instead of build_append_nameseg()
So user won't have to care whether name is NameSeg, NamePath or
NameString.
See for refernce ACPI 5.0: 20.2.2 Name Objects Encoding
Signed-off-by: Igor Mammedov
---
v3:
assert on wrong Segcount earlier and extend condition to
seg
On 19 December 2014 at 14:12, Mark Cave-Ayland
wrote:
> I now have something that nearly works in that I can issue a "savevm"
> followed by a "loadvm" in the monitor and be able to resume where I left
> off - but only in OpenBIOS. If I boot into an OS and try this then it
> doesn't work and the co
On 19/12/2014 14:15, Frerot, Jean-Sébastien wrote:
> Hi, I've been using kvm for some time now using live migration as well
> with ceph backend. Recently I started running into an issue with only
> one of my VM, which happens to be a windows server (2012). When I
> migrate this particular VM it s
Thanks for the info, how should I debug this then? Cause I can't live
migrate my windows VM now.
--
Jean-Sébastien Frerot
jsfre...@egliseespoir.com
2014-12-19 9:40 GMT-05:00 Paolo Bonzini :
>
>
>
> On 19/12/2014 14:15, Frerot, Jean-Sébastien wrote:
> > Hi, I've been using kvm for some time now u
re-adding right email: quint...@redhat.com
--
Jean-Sébastien Frerot
jsfre...@egliseespoir.com
2014-12-19 9:41 GMT-05:00 Frerot, Jean-Sébastien
:
>
> Thanks for the info, how should I debug this then? Cause I can't live
> migrate my windows VM now.
>
>
> --
> Jean-Sébastien Frerot
> jsfre...@egl
Reviewed-by: Claudio Fontana
On 19.12.2014 15:27, Igor Mammedov wrote:
> Use build_append_namestring() instead of build_append_nameseg()
> So user won't have to care whether name is NameSeg, NamePath or
> NameString.
>
> See for refernce ACPI 5.0: 20.2.2 Name Objects Encoding
>
> Signed-off-by:
Am 26.11.2014 um 17:20 hat Max Reitz geschrieben:
> Cover letter of v1:
>
> Sometimes, qemu does not have a filename to work with (it then generates
> a JSON filename), so it does not know which directory to use for a
> backing file specified by a relative filename.
>
> In this case, qemu should
On 12/15/2014 05:05 AM, Roy Vardi wrote:
> From: Roy Vardi
>
> Add 'persistent' boolean flag to -net tap option.
> When set to off - tap interface will be released on shutdown
> When set to on\not specified - tap interface will remain
>
> Running with -net tap,persistent=off will
= Introduction =
Kevin asked for all the ways you can reopen BDSes with different options
or flags. This memo only covers all the ways you can reopen, but it
doesn't attempt to fully analyze how options or flags change in each
case.
This is a systematic review of all the ways you can reopen BDSe
On 19/12/14 14:29, Peter Maydell wrote:
> On 19 December 2014 at 14:12, Mark Cave-Ayland
> wrote:
>> I now have something that nearly works in that I can issue a "savevm"
>> followed by a "loadvm" in the monitor and be able to resume where I left
>> off - but only in OpenBIOS. If I boot into an O
Filter out the "main loop: WARNING: I/O thread spun for..." warning from
qemu output (it hardly matters for code specifically testing I/O).
Furthermore, use _filter_qemu in all the custom functions which run
qemu.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/067 | 3 ++-
tests/qemu
Am 19.12.2014 um 17:17 hat Max Reitz geschrieben:
> Filter out the "main loop: WARNING: I/O thread spun for..." warning from
> qemu output (it hardly matters for code specifically testing I/O).
>
> Furthermore, use _filter_qemu in all the custom functions which run
> qemu.
>
> Signed-off-by: Max
On Fri, Dec 19, 2014 at 12:22:30PM +0100, Paolo Bonzini wrote:
> On 19/12/2014 03:41, Eduardo Habkost wrote:
> > +object_property_set_int(OBJECT(cpu), CPU(cpu)->cpu_index, "apic-id",
> > +&error);
> > +if (error) {
> > +goto out;
> > +}
> > +
>
> Sho
From: Fam Zheng
Using /tmp, which is usually mounted as tmpfs, the quick group can be
quicker.
On my laptop (Lenovo T430s with Fedora 20), this reduces the time from
50s to 30s.
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests-quick.sh | 2 +-
From: Paolo Bonzini
AioContext can be accessed recursively, in fact that's what we do with
aio_poll. Marking the GSource as recursive avoids that GLib blocks it
and unblocks it around every call to aio_dispatch, which is a pretty
expensive operation.
Signed-off-by: Paolo Bonzini
Signed-off-by:
The following changes since commit dfa9c2a0f4d0a0c8b2c1449ecdbb1297427e1560:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging
(2014-12-15 16:43:42 +)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch
From: Paolo Bonzini
This saves about 15% of the clock cycles spent on allocation. Using the
slice allocator does not add a visible improvement; allocation is faster
than malloc, while freeing seems to be slower.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
async.c | 10 ++--
From: Fam Zheng
Signed-off-by: Fam Zheng
Signed-off-by: Kevin Wolf
---
tests/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/Makefile b/tests/Makefile
index 16f0e4c..f430b18 100644
--- a/tests/Makefile
+++ b/tests/Makefile
@@ -463,7 +463,7 @@ check-qapi-schem
From: Paolo Bonzini
Most reads do not go past the end of the file, and they can use the
input QEMUIOVector instead of creating one. This removes the
qemu_iovec_* functions from the profile.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
block.c | 12 +---
1 file changed,
From: Max Reitz
Sometimes, qemu does not have a filename to work with, so it does not
know which directory to use for a backing file specified by a relative
filename. Add a test which tests that qemu exits with an appropriate
error message.
Additionally, add a test for qemu-img create with a bac
From: Fam Zheng
For the purpose of allowing running quick group on tmpfs.
Signed-off-by: Fam Zheng
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/group | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group
index a4742c6..0809
From: Max Reitz
Relative backing filenames are always relative to the backed image's
directory; the same applies to image creation. Therefore, if the backing
file has to be opened for determining its size (in case the size has not
been explicitly specified) its filename should be interpreted rela
From: Max Reitz
When a vmdk image is created with a backing file, it is opened to check
whether it is indeed a vmdk file by letting qemu probe it. When doing
so, the backing filename is relative to the image's base directory so it
should be interpreted accordingly.
Signed-off-by: Max Reitz
Revi
From: Max Reitz
CODING_STYLE states the following about braces around blocks:
> The opening brace is on the line that contains the control flow
> statement that introduces the new block; [...]
This is obviously impossible with multi-line conditions. Therefore,
CODING_STYLE does not make any cle
From: Max Reitz
Filter out the "main loop: WARNING: I/O thread spun for..." warning from
qemu output (it hardly matters for code specifically testing I/O).
Furthermore, use _filter_qemu in all the custom functions which run
qemu.
Signed-off-by: Max Reitz
Signed-off-by: Kevin Wolf
---
tests/q
From: Fam Zheng
Signed-off-by: Fam Zheng
Reviewed-by: Eric Blake
Reviewed-by: Max Reitz
Reviewed-by: Markus Armbruster
Message-id: 1418899027-8445-2-git-send-email-f...@redhat.com
Signed-off-by: Max Reitz
---
qapi-schema.json | 6 ++
1 file changed, 6 insertions(+)
diff --git a/qapi-sc
From: Max Reitz
When using a relative backing file name, qemu needs to know the
directory of the top image file. For JSON filenames, such a directory
cannot be easily determined (e.g. how do you determine the directory of
a qcow2 BDS directly on top of a quorum BDS?). Therefore, do not allow
rela
From: Max Reitz
Introduce bdrv_get_full_backing_filename_from_filename(), a function
which takes the name of the backed file and a potentially relative
backing filename to produce the full (absolute) backing filename.
Use this function from bdrv_get_full_backing_filename().
Signed-off-by: Max R
From: Fam Zheng
Similar to drive-backup, but this command uses a device id as target
instead of creating/opening an image file.
Also add blocker on target bs, since the target is also a named device
now.
Add check and report error for bs == target which became possible but is
an illegal case wi
From: Fam Zheng
This applies cases on drive-backup on blockdev-backup, except cases with
target format and mode.
Also add a case to check source == target.
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
Reviewed-by: Markus Armbruster
Message-id: 1418899027-8445-5-git-send-email-f...@redhat.
From: Vladimir Sementsov-Ogievskiy
Mirror and migration use dirty bitmaps for their purposes, and since
commit [block: per caller dirty bitmap] they use their own bitmaps, not
the global one. But they use old functions bdrv_set_dirty and
bdrv_reset_dirty, which change all dirty bitmaps.
Named di
On 19 December 2014 at 16:15, Mark Cave-Ayland
wrote:
> It looks like after restoring the CPU state with loadvm env->htab_base
> is still at 0x0 rather than its pre-migration value of 0x7e00.
Odd -- there is code that is at least trying to do that:
machine.c calls ppc_store_sdr1() which shoul
From: Fam Zheng
Signed-off-by: Fam Zheng
Reviewed-by: John Snow
Reviewed-by: Max Reitz
Reviewed-by: Markus Armbruster
Message-id: 1418899027-8445-4-git-send-email-f...@redhat.com
Signed-off-by: Max Reitz
---
blockdev.c | 79
qap
From: Fam Zheng
Signed-off-by: Fam Zheng
Reviewed-by: Eric Blake
Message-id: 1418694024-26498-1-git-send-email-f...@redhat.com
Signed-off-by: Max Reitz
---
qapi/block-core.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
inde
On 19/12/14 16:35, Peter Maydell wrote:
> On 19 December 2014 at 16:15, Mark Cave-Ayland
> wrote:
>> It looks like after restoring the CPU state with loadvm env->htab_base
>> is still at 0x0 rather than its pre-migration value of 0x7e00.
>
> Odd -- there is code that is at least trying to do
The following changes since commit b574f602680d41c4cf4a9c106e3e2244bed01cdd:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20141216-1' into
staging (2014-12-17 19:22:42 +)
are available in the git repository at:
https://github.com/otubo/qemu.git tags/pull-seccom
From: Paul Moore
The "memory-backend-ram" QOM object utilizes the mbind(2) syscall to
set the policy for a memory range. Add the syscall to the seccomp
sandbox whitelist.
Signed-off-by: Paul Moore
Tested-by: Eduardo Habkost
Reviewed-by: Eduardo Habkost
Acked-by: Eduardo Otubo
---
qemu-secc
Error message was misleading people to install wrong version of
libseccomp.
Signed-off-by: Eduardo Otubo
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index cae588c..7539645 100755
--- a/configure
+++ b/configure
@@ -1830,7 +1830,7 @@ if
On 12/19/2014 06:25 AM, Amos Kong wrote:
> Passing some invalid fds in QEMU commandline, the fds don't exist.
> QEMU will get error "TUNGETIFF ioctl() failed: Bad file descriptor",
> and coredump in setting queues.
>
> This patch checked return value of first operate to fd, QEMU will
> report erro
writes:
> From: Gonglei
>
> First, we can downsize vl.c, make it simpler by
> little and little. Second, I can maintain those code
> and make some improvement.
Any patch moving code from vl.c to a better place can't be all bad :)
[...]
> diff --git a/include/hw/hw.h b/include/hw/hw.h
> index 3
Hello Ben, I just submitted a pull request to fix the issue you
reported:
http://lists.gnu.org/archive/html/qemu-devel/2014-12/msg03134.html
Thanks again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bu
On 19.12.14 17:51, Mark Cave-Ayland wrote:
> On 19/12/14 16:35, Peter Maydell wrote:
>
>> On 19 December 2014 at 16:15, Mark Cave-Ayland
>> wrote:
>>> It looks like after restoring the CPU state with loadvm env->htab_base
>>> is still at 0x0 rather than its pre-migration value of 0x7e00.
>>
writes:
> From: Gonglei
>
> We can use it for checking when we change traditional
> boot order dynamically and propagate error message
> to the monitor.
In case you need to respin for some other reason: consider replacing "We
can use it" by something like "Will be useful", to make it clearer th
writes:
> From: Gonglei
>
> We can use it for checking when we change traditional
> boot order dynamically and propagate error message
> to the monitor.
>
> Signed-off-by: Gonglei
I was about to write that this patch isn't an improvement, but then I
read PATCH 4, and now I understand what you'
writes:
> From: Gonglei
>
> We can use it for checking when we change traditional
> boot order dynamically and propagate error message
> to the monitor.
> For x86 architecture, we pass &local_err to set_boot_dev()
> when vm startup in pc_coms_init().
>
> Cc: Michael S. Tsirkin
> Cc: Alexander G
writes:
> From: Gonglei
>
> Changes of v2:
> Thanks to Peter's report and suggestion.
> - fix 'make check' complaint.
> - fix inapposite using &error_abort in patch 5.
>
> Because of Peter's review comments in a pull request, I start a new
> round review about this patch series v2. Please rev
* Frerot, Jean-S?bastien (jsfre...@egliseespoir.com) wrote:
> Thanks for the info, how should I debug this then? Cause I can't live
> migrate my windows VM now.
Are the host clocks on the servers synchronised with ntp? Having a clock
mismatch with migration really confuses stuff (especially windo
On 19/12/2014 18:16, Alexander Graf wrote:
>
>
> On 19.12.14 17:51, Mark Cave-Ayland wrote:
>> On 19/12/14 16:35, Peter Maydell wrote:
>>
>>> On 19 December 2014 at 16:15, Mark Cave-Ayland
>>> wrote:
It looks like after restoring the CPU state with loadvm env->htab_base
is still at 0
On 19.12.14 15:20, Amit Tomar wrote:
> This patch sets the GPIO controller interrupt number to 47,not 43 (and the
> Device tree agrees).
>
>
> Signed-off-by: Amit Singh Tomar
Thanks, applied to ppc-next with modified commit message. Let's try to
improve the patch description next time ;).
On 12/19/2014 11:34 AM, Alex Zuepke wrote:
Now using psw_read() to retrieve the status bits correctly.
Signed-off-by: Alex Zuepke
---
target-tricore/translate.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/target-tricore/translate.c b/target-t
On 19.12.14 18:29, Paolo Bonzini wrote:
>
>
> On 19/12/2014 18:16, Alexander Graf wrote:
>>
>>
>> On 19.12.14 17:51, Mark Cave-Ayland wrote:
>>> On 19/12/14 16:35, Peter Maydell wrote:
>>>
On 19 December 2014 at 16:15, Mark Cave-Ayland
wrote:
> It looks like after restoring the C
On 12/19/2014 06:04 AM, Markus Armbruster wrote:
> Gerd Hoffmann writes:
>
>> Add new query vnc qmp command, for the lack of better ideas just name it
>> "query-vnc2". Changes over query-vnc:
>>
>> * It returns a list of vnc servers, so multiple vnc server instances
>>are covered.
>> * Eac
yes it is.
[jsfrerot@compute02 ~]$ ntpq -pn
remote refid st t when poll reach delay offset
jitter
==
+208.80.96.70142.3.100.2 2 u 148 1024 377 19.6890.037
1.219
*192.95.25.79213
Markus Armbruster writes:
> Conscious design decision: Backend (BB) and node (BDS) names share a
> common name space.
>
> Enables a convenience feature: when a command needs a node, we accept
> either kind of name, and a backend name is resolved to its root node.
>
> Should not be confused with a
On 12/19/2014 02:04 AM, Gerd Hoffmann wrote:
> Add websockets bool to VncBasicInfo, report websocket server sockets,
> flag websocket client connections.
>
> Signed-off-by: Gerd Hoffmann
> ---
> qapi-schema.json | 5 -
> ui/vnc.c | 15 ---
> 2 files changed, 16 insertion
Public bug reported:
using latest qemu 2.2.0 64bit for windows host (installed from
qemu-w64-setup-20141210.exe obtained from http://qemu.weilnetz.de/w64/
),OpenVPN 2.6.3-I601 64bit tap adapter named tap01 and calling qemu
using the following.
qemu-system-x86_64.exe -m 512 -net nic -net tap,ifnam
On 12/17/2014 10:17 AM, Bastian Koppelmann wrote:
> +tcg_gen_andi_tl(regs[r1], regs[r1], ~0xull);
> +tcg_gen_or_tl(regs[r1], regs[r1], tmp);
This is store_reg32_i64.
But just reminds me that I've got patches for 8 missing insns
outstanding since September 2013, that got stalled on
same behaviour observed with qemu 2.2.0 32bit version for windows host
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1404278
Title:
tap connections not working on windows host
Status in QEMU:
Ne
On 2014/12/20 1:27, Markus Armbruster wrote:
> I don't understand why you move declarations to sysemu.h, and I had a
> few remarks here and there. But I couldn't see anything wrong, so:
>
My thought is just moving the code related boot order to a unified place. :(
> Series
> Reviewed-by: Marku
On 2014/12/20 1:17, Markus Armbruster wrote:
> writes:
>
>> From: Gonglei
>>
>> We can use it for checking when we change traditional
>> boot order dynamically and propagate error message
>> to the monitor.
>
> In case you need to respin for some other reason: consider replacing "We
> can use
On 2014/12/20 1:24, Markus Armbruster wrote:
> writes:
>
>> From: Gonglei
>>
>> We can use it for checking when we change traditional
>> boot order dynamically and propagate error message
>> to the monitor.
>> For x86 architecture, we pass &local_err to set_boot_dev()
>> when vm startup in pc_c
From: Gonglei
It will be useful for checking when we change traditional
boot order dynamically and propagate error message
to the monitor.
Signed-off-by: Gonglei
Reviewed-by: Markus Armbruster
---
bootdevice.c| 14 ++
include/sysemu/sysemu.h | 2 +-
monitor.c
From: Gonglei
Changes of v3:
As Markus's suggestion, thanks.
- respin commit message of patch 2, 3, 5
- remove error_free() before exit().
- add 'R-by' tag for this patch series.
Changes of v2:
Thanks to Peter's report and suggestion.
- fix 'make check' complaint.
- fix inapposite using &
From: Gonglei
First, we can downsize vl.c, make it simpler by
little and little. Second, I can maintain those code
and make some improvement.
Cc: Jan Kiszka
Signed-off-by: Gonglei
Reviewed-by: Markus Armbruster
---
bootdevice.c| 62
From: Gonglei
It will be useful for checking when we change traditional
boot order dynamically and propagate error message
to the monitor.
For x86 architecture, we pass &local_err to set_boot_dev()
when vm startup in pc_coms_init().
Cc: Michael S. Tsirkin
Cc: Alexander Graf
Cc: Blue Swirl
Cc:
From: Gonglei
Signed-off-by: Gonglei
Reviewed-by: Markus Armbruster
---
bootdevice.c | 8
1 file changed, 8 insertions(+)
diff --git a/bootdevice.c b/bootdevice.c
index 7f07507..9de34ba 100644
--- a/bootdevice.c
+++ b/bootdevice.c
@@ -49,12 +49,20 @@ void qemu_register_boot_set(QEMUB
From: Gonglei
It will be useful for checking when we change traditional
boot order dynamically and propagate error message
to the monitor.
Signed-off-by: Gonglei
Reviewed-by: Markus Armbruster
---
bootdevice.c| 10 +-
include/sysemu/sysemu.h | 2 +-
vl.c
101 - 171 of 171 matches
Mail list logo
