Hiya,
I found a couple of corner cases where signal handling fails in QEMU
linux-user support. Signal handling here being just a symptom -
actual problems are in TB / page management.
Here are a couple of simple tests
(https://github.com/andreiw/andreiw-wip/tree/master/qemu/tests). The
test:
1)
At Wed, 02 Apr 2014 16:18:15 -0400,
Cole Robinson wrote:
On 04/02/2014 11:25 AM, Takashi Iwai wrote:
At Wed, 02 Apr 2014 17:19:51 +0200,
Gerd Hoffmann wrote:
On Mi, 2014-04-02 at 11:07 -0400, Cole Robinson wrote:
+if (button-button == 1
+button-type == GDK_BUTTON_PRESS
Change over to my proper Xilinx email. s/petalogix.com/xilinx.com.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
MAINTAINERS | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7d17f83..39c8c66 100644
---
Looks good, I'll get this to linux-user que once QEMU 2.0 is released.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
Status in QEMU:
Can any one tell me, what's the address range used by PCI emulation in QEMU
and whether this emulation supports 64 bit addresses?
Moreover, is PCIE emulation in QEMU used by any architecture?
Andreas script worked for me. Thank you.
But i seem to be running into an issue with when i set multiple cores.
(-smp cores=4). Multiple CPUs works fine (-smp 4)
During boot i get these messages:
NOTICE: System detected 4 cpus, but only 1 cpu(s) were enabled during boot
NOTICE: Use boot-ncpus
That patch will copy the whole of the target executable into a temporary file
without changing any of it -- the fake_open mechanism is really intended for
cases where we need to return modified results. Wouldn't it be easier to just
have something in do_open() that said:
if
(I got the bracket placement wrong there so as you can tell the code is
untested :-))
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
** Summary changed:
- Windows guest freezes after exiting an 3D application on guest.
+ Windows guest freezes while using USB passthrough.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1301047
Yes, it works. Here is updated patch.
** Patch added: qemu.patch
https://bugs.launchpad.net/qemu/+bug/1299190/+attachment/4062345/+files/qemu.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Some nits:
The (CPUArchState *) cast isn't necessary
We should use exec_path, not ts-bprm-argv[0] (the guest argv[0] isn't
necessarily the executable path)
We don't want to call path() here -- exec_path is a host path, and only guest
filename paths need to go through path().
Looking a little
Il 02/04/2014 18:03, Anthony PERARD ha scritto:
On Wed, Apr 02, 2014 at 01:13:31PM +0200, Fabio Fantoni wrote:
- if you posted qemu's backtrace at the sigsegv.
I tried to use gdb following this old post:
https://lists.gnu.org/archive/html/qemu-devel/2011-12/msg02575.html
but with same changes:
** Description changed:
I have the following issue with my Windows 8.1 guest. (Technical stuff
is at the bottom):
I have vfio-binded my graphics card(NVIDIA GTX670) and is passing it through
to the guest.
I run heavy 3D applications such as games(Guild Wars 2, Diablo 3, DOTA etc)
Il 02/04/2014 18:05, Anthony PERARD ha scritto:
On Tue, Apr 01, 2014 at 05:01:18PM +0200, Fabio Fantoni wrote:
Today I tried latest qemu 2.0 compiled from git (commit
63678e17cf399ff81b93417fe7bee8d6ef6b6b1b) on this dom0:
Debian 7 (Wheezy) 64 bit with kernel from package
On 03/07/2014 03:18 AM, Andreas Färber wrote:
Am 06.03.2014 04:11, schrieb Alexey Kardashevskiy:
Previously libvirt required the first/default PCI bus to have name pci.
Since QEMU can support multiple buses now, libvirt wants pci.0 now.
This removes custom busname and lets QEMU make up
On Thu, 2014-04-03 at 10:15 +0200, Fabio Fantoni wrote:
Seems that do segfault when I connect to vnc or spice, in the test of
this backtrace after connect to vnc, spice and other things of my
patches are disabled, so do not think it is a problem caused by my patches.
The last spice patch of
On Wed, Apr 02, 2014 at 04:57:48PM +0200, Andreas Färber wrote:
+int main(int argc, char **argv)
+{
+QTestState *s1, *s2;
+char *cmd;
+int ret;
+
+g_test_init(argc, argv, NULL);
+qtest_add_func(/ivshmem/nop, nop);
+
+cmd = g_strdup_printf(-device
Hi all,
As we know, when hot-add a device, we don't know whether the device is
present in VM from outside(like libvirt).
However, unplugging device, when complete remove the device, Qemu will generate
a Monitor event,QEVENT_DEVICE_DELETED.
Libvirt can receive the event and do something.
On 04/03/14 03:57, Gabriel L. Somlo wrote:
On Wed, Apr 02, 2014 at 01:01:28PM -0400, Gabriel L. Somlo wrote:
Speaking of, I *thought* I had a vague idea of how all this stuff fits
together, but it turns out I don't... There's
- OVMF
Joon Pang chickenj...@gmail.com writes:
Hello there
Could you delete e-mail at the mailing list?
You need to send your unsubscribe message to
qemu-devel-requ...@nongnu.org or use the link provided:
To subscribe or unsubscribe via the World Wide Web, visit
2014-03-25 15:15 GMT+08:00 Chunyan Liu cy...@suse.com:
2014-03-24 23:00 GMT+08:00 Leandro Dorileo l...@dorileo.org:
Hi Chunyan,
On Mon, Mar 24, 2014 at 11:02:14AM +0800, Chunyan Liu wrote:
2014-03-21 20:31 GMT+08:00 Leandro Dorileo l...@dorileo.org:
On Fri, Mar 21, 2014 at
Reviewed-by: Eric Blake ebl...@redhat.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
util/qemu-option.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/util/qemu-option.c b/util/qemu-option.c
index 9d898af..e6d10bc 100644
---
This patch series is to replace QEMUOptionParameter with QemuOpts, so that only
one Qemu Option structure is kept in QEMU code.
---
Changes to v23:
* Improve conversion functions, make .assigned info not lost.
* Update qcow2.c amend_option, keep checking 'assigned'.
* Improve
In later patch, qemu_opt_get_del functions will be added, they will
first get the option value, then call qemu_opt_del to remove the option
from opt list. To prepare for that purpose, move qemu_opt_del ahead first.
Reviewed-by: Eric Blake ebl...@redhat.com
Signed-off-by: Chunyan Liu
For later merge .create_opts of drv and proto_drv in qemu-img commands.
Reviewed-by: Leandro Dorileo l...@dorileo.org
Signed-off-by: Chunyan Liu cy...@suse.com
---
Changes:
* some fixes for spelling and space
include/qemu/option.h | 5
util/qemu-option.c| 65
Add def_value_str (default value) to QemuOptDesc, to replace function of the
default value in QEMUOptionParameter.
Improve qemu_opts_get_* functions: if find opt, return opt-str; otherwise,
if desc-def_value_str is set, return desc-def_value_str; otherwise, return
input defval.
Improve
Change qapi interfaces to output the newly added def_value_str when querying
command line options.
Reviewed-by: Eric Blake ebl...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
qapi-schema.json | 6 +-
qmp-commands.hx| 2
qemu_opt_del() already assumes that all QemuOpt instances contain
malloc'd name and value; but it had to cast away const because
opts_start_struct() was doing its own thing and using static storage
instead. By using the correct type and malloced strings everywhere, the
usage of this struct
To simplify later using of qemu_opts_del, accept NULL input.
Reviewed-by: Eric Blake ebl...@redhat.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
util/qemu-option.c | 4
1 file changed, 4 insertions(+)
diff --git a/util/qemu-option.c b/util/qemu-option.c
index c9df671..c4c7545 100644
Add qemu_opt_get_del, qemu_opt_get_bool_del, qemu_opt_get_number_del and
qemu_opt_get_size_del to replace the same handling of QEMUOptionParamter
(get and delete).
Several drivers are coded to parse a known subset of options, then
remove them from the list before handing all remaining options to
Currently this function is not used anywhere. In later patches, it will
replace print_option_parameters. print_option_parameters uses printf,
to avoid print info changes after switching to QemuOpts, change
qemu_opts_print from fprintf stderr to printf to keep consistent.
Also to avoid print info
Add two temp conversion functions between QEMUOptionParameter to QemuOpts,
so that next patch can use it. It will simplify later patch for easier
review. And will be finally removed after all backend drivers switch to
QemuOpts.
Signed-off-by: Chunyan Liu cy...@suse.com
---
Changes:
* fix two
One extra change is to define QED_DEFAULT_CLUSTER_SIZE = 65536 instead
of 64 * 1024; because:
according to existing create_options, cluster size has default value =
QED_DEFAULT_CLUSTER_SIZE, after switching to create_opts, this has to be
stringized and set to .def_value_str. That is,
print_option_help takes QEMUOptionParameter as parameter, add
qemu_opts_print_help to take QemuOptsList as parameter for later
replace work.
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
Changes:
* check non-empty list
Reviewed-by: Eric Blake ebl...@redhat.com
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/gluster.c | 81 ++---
1 file changed, 42
vvfat shares create options of qcow driver. To avoid vvfat broken when
qcow driver changes from QEMUOptionParameter to QemuOpts, let it able
to handle both cases.
Signed-off-by: Chunyan Liu cy...@suse.com
---
Changes:
* Initialize opts and create_opts to NULL
block/vvfat.c | 19
Reviewed-by: Eric Blake ebl...@redhat.com
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/cow.c | 54 ++
1 file changed, 26
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/raw-posix.c | 59 +--
1 file changed, 27 insertions(+), 32 deletions(-)
diff --git
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/vpc.c | 62 +
1 file changed, 34 insertions(+), 28 deletions(-)
diff --git
Now only qemu_opts_append uses 'allocated' to indicate free memory.
For this function only, we can also let result list's (const char *)
members point to input list's members, only if the input list has
longer lifetime than result list. In current code, that is true.
So, we can remove the
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/ssh.c | 32 +++-
1 file changed, 15 insertions(+), 17 deletions(-)
diff --git a/block/ssh.c b/block/ssh.c
index
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/vdi.c | 73 +
1 file changed, 35 insertions(+), 38 deletions(-)
diff --git a/block/vdi.c b/block/vdi.c
index 820cd37..950cf46
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/raw_bsd.c | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/block/raw_bsd.c b/block/raw_bsd.c
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/vmdk.c | 123 ++-
1 file changed, 63 insertions(+), 60 deletions(-)
diff --git
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/raw-win32.c | 38 +++---
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/block/raw-win32.c
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/qcow.c | 72 ++--
1 file changed, 36 insertions(+), 36 deletions(-)
diff --git
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/sheepdog.c | 108 ---
1 file changed, 55 insertions(+), 53 deletions(-)
diff --git
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/vhdx.c | 99 +---
block/vhdx.h | 1 +
2 files changed, 48 insertions(+), 52
Now that all backend drivers are using QemuOpts, remove all
QEMUOptionParameter related codes.
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block.c | 85 ++---
block/cow.c | 4 +-
block/gluster.c
Il 03/04/2014 10:45, Ian Campbell ha scritto:
On Thu, 2014-04-03 at 10:15 +0200, Fabio Fantoni wrote:
Seems that do segfault when I connect to vnc or spice, in the test of
this backtrace after connect to vnc, spice and other things of my
patches are disabled, so do not think it is a problem
Ok, fixed.
** Patch added: qemu.patch
https://bugs.launchpad.net/qemu/+bug/1299190/+attachment/4062748/+files/qemu.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
Changes:
* Use qemu_opt_find to judge if the option is set explicitly, replace
.assinged check in QEMUOptionParameter
* In qcow2_amend_options, use qemu_opt_get instead of
Thanks. That version
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
Status in QEMU:
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/iscsi.c | 34 --
1 file changed, 16 insertions(+), 18 deletions(-)
diff --git a/block/iscsi.c
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu cy...@suse.com
---
block/rbd.c | 63 +
1 file changed, 30 insertions(+), 33 deletions(-)
diff --git
Change block layer to support both QemuOpts and QEMUOptionParameter.
After this patch, it will change backend drivers one by one. At the end,
QEMUOptionParameter will be removed and only QemuOpts is kept.
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
Signed-off-by: Chunyan Liu
Non-block SCSI devices do not support flushing, but we may still send
them requests via bdrv_flush_all. Just ignore them.
Reviewed-by: Peter Lieven p...@kamp.de
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
block/iscsi.c | 4
1 file changed, 4 insertions(+)
diff --git
Max WRITE SAME length is also used when the UNMAP bit is zero, so it
should be queried even if LBPWS=0. Same for the optimal transfer
length.
However, the write_zeroes_alignment only matters for UNMAP=1 so we
still restrict it to LBPWS=1.
Reviewed-by: Peter Lieven p...@kamp.de
Signed-off-by:
The following changes since commit 63678e17cf399ff81b93417fe7bee8d6ef6b6b1b:
configure: add option to disable -fstack-protector flags (2014-03-31 20:16:02
+0100)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for you to fetch changes up to
Il 03/04/2014 10:44, Alexey Kardashevskiy ha scritto:
Ufff. Does anyone know any workaround how to tell libvirt to use these
custom names? Since there is no pci (and there is pci.0), libvirt
cannot put any device onto default PCI bus and I do not see any way to
workaround it in XML, am I
This assertion is invalid, because get_sg_list can return an
empty sg-list even for commands that transfer no data (such
as SYNCHRONIZE CACHE).
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi/scsi-bus.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/scsi/scsi-bus.c
Some targets may return invalid field as the ASCQ from WRITE SAME
if they support the command only without the UNMAP field. Recognize
that, and return ENOTSUP just like for invalid operation code.
Reviewed-by: Peter Lieven p...@kamp.de
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
On 2 April 2014 16:53, Paolo Bonzini pbonz...@redhat.com wrote:
Il 01/04/2014 15:06, Eduardo Otubo ha scritto:
Not sure why it didn't get upstream yet.
Anthony, Peter, could you take a closer look at this?
Peter filters on for you to fetch changes up to and your git didn't
include it. :)
On Wed, Apr 02, 2014 at 05:15:59PM +0200, Paolo Bonzini wrote:
Il 02/04/2014 17:15, Michael S. Tsirkin ha scritto:
Yes and I think this someone was you actually.
Can something similar be done for this test?
I think ivshmem depends on ioeventfd, doesn't it? So short of
implementing
On Thu, Apr 03, 2014 at 05:02:56PM +0800, xiexiangyou wrote:
Hi all,
As we know, when hot-add a device, we don't know whether the device is
present in VM from outside(like libvirt).
However, unplugging device, when complete remove the device, Qemu will
generate a Monitor
On 04/02/14 00:09, Andy Lutomirski wrote:
Running:
./virtme-run --installed-kernel
from this virtme commit:
https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git/commit/?id=2b409a086d15b7a878c7d5204b1f44a6564a341f
results in a bunch of missing lines of text once bootup finishes.
Am 03.04.2014 13:16, schrieb Michael S. Tsirkin:
On Wed, Apr 02, 2014 at 05:15:59PM +0200, Paolo Bonzini wrote:
Il 02/04/2014 17:15, Michael S. Tsirkin ha scritto:
Yes and I think this someone was you actually.
Can something similar be done for this test?
I think ivshmem depends on
On 3 April 2014 07:31, Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
Change over to my proper Xilinx email. s/petalogix.com/xilinx.com.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
MAINTAINERS | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
- Original Message -
From: Fam Zheng f...@redhat.com
To: Jun Lee j...@redhat.com
Cc: kw...@redhat.com, stefa...@redhat.com, qemu-devel@nongnu.org
Sent: Wednesday, April 2, 2014 10:24:34 AM
Subject: Re: [Qemu-devel] [PATCH] qcow2: Patch for shrinking qcow2 disk image
On Tue, 04/01 10:06,
On Thu, Apr 03, 2014 at 12:02:35PM +0500, Ayaz Akram wrote:
Can any one tell me, what's the address range used by PCI emulation in QEMU
and
whether this emulation supports 64 bit addresses?
We'll support full 64 bit addresses starting 2.0.
However, note that most hardware (cpus and iommus
Am 03.04.2014 10:46, schrieb Stefan Hajnoczi:
On Wed, Apr 02, 2014 at 04:57:48PM +0200, Andreas Färber wrote:
+int main(int argc, char **argv)
+{
+QTestState *s1, *s2;
+char *cmd;
+int ret;
+
+g_test_init(argc, argv, NULL);
+qtest_add_func(/ivshmem/nop, nop);
+
+
On 2 April 2014 10:41, Alexander Graf ag...@suse.de wrote:
Commit 6f1834a2b exposed a bug in openpic_kvm where we don't filter
for memory events that only happen to the region we want to know
events about.
Add proper filtering, fixing the e500plat target with KVM.
Signed-off-by: Alexander
On 3 April 2014 12:12, Paolo Bonzini pbonz...@redhat.com wrote:
The following changes since commit 63678e17cf399ff81b93417fe7bee8d6ef6b6b1b:
configure: add option to disable -fstack-protector flags (2014-03-31
20:16:02 +0100)
are available in the git repository at:
On 04/03/2014 03:02 AM, xiexiangyou wrote:
Hi all,
As we know, when hot-add a device, we don't know whether the device is
present in VM from outside(like libvirt).
However, unplugging device, when complete remove the device, Qemu will
generate a Monitor event,QEVENT_DEVICE_DELETED.
On 01/04/14 15:25, Christian Borntraeger wrote:
On 01/04/14 10:33, Qiao Nuohan wrote:
Dumping guest memory is available to specify the dump format now. This patch
adds options '-z|-l|-s' to HMP command dump-guest-memory to specify dumping
in
kdump-compression format, with zlib/lzo/snappy
On 12.03.14 06:52, Alexey Kardashevskiy wrote:
This adds SPAPR VFIO IOMMU device in order to support DMA operations
for VFIO devices.
Sorry if this has been mentioned before, but why exactly do you need a
separate IOMMU for VFIO? Couldn't the existing IOMMU backend drive things?
Alex
The Monday 31 Mar 2014 à 15:39:19 (+0100), anton.iva...@kot-begemot.co.uk wrote
:
From: Anton Ivanov antiv...@cisco.com
This transport allows to connect a QEMU nic to a static Ethernet
over L2TPv3 tunnel. The transport supports all options present
in the Linux kernel implementation. It
The Monday 31 Mar 2014 à 15:39:19 (+0100), anton.iva...@kot-begemot.co.uk wrote
:
From: Anton Ivanov antiv...@cisco.com
This transport allows to connect a QEMU nic to a static Ethernet
over L2TPv3 tunnel. The transport supports all options present
in the Linux kernel implementation. It
On 04/03/2014 10:09 PM, Paolo Bonzini wrote:
Il 03/04/2014 10:44, Alexey Kardashevskiy ha scritto:
Ufff. Does anyone know any workaround how to tell libvirt to use these
custom names? Since there is no pci (and there is pci.0), libvirt
cannot put any device onto default PCI bus and I do not
From: Riku Voipio riku.voi...@linaro.org
The following changes since commit 63678e17cf399ff81b93417fe7bee8d6ef6b6b1b:
configure: add option to disable -fstack-protector flags (2014-03-31 20:16:02
+0100)
are available in the git repository at:
From: Petar Jovanovic petar.jovano...@imgtec.com
Flags NONBLOCK and CLOEXEC can have different values on the host and the
guest, so set correct host values before calling accept4().
This fixes several issues with accept4 system call and user-mode of QEMU.
Signed-off-by: Petar Jovanovic
On 03/04/14 13:20, Benoît Canet wrote:
The Monday 31 Mar 2014 à 15:39:19 (+0100), anton.iva...@kot-begemot.co.uk
wrote :
From: Anton Ivanov antiv...@cisco.com
This transport allows to connect a QEMU nic to a static Ethernet
over L2TPv3 tunnel. The transport supports all options present
in
On Thu, Apr 03, 2014 at 01:45:28PM +0200, Andreas Färber wrote:
Am 03.04.2014 10:46, schrieb Stefan Hajnoczi:
The name should be unique and we should clean up in both success and
failure (abort(3)) cases.
The recipe for unique filenames elsewhere is mkstemp(), which I was
planning to use
The first patch is in Paolo's kvm/next, others are new. They are independend
but may not apply if to change their order. Please comment. Thanks.
Alexey Kardashevskiy (4):
kvm: Add set_one_reg/get_one_reg helpers
spapr: Enable DABRX special register
KVM: PPC: Support POWER8 registers
On 03.04.14 15:14, Alexey Kardashevskiy wrote:
This advertises Data Address Breakpoint Register Extension (DABRX) to
the guest via hyperrtas list and enables it to migrate.
Do all CPUs we support (970 anyone) have DABRX support? Also who handles
this hcall in the TCG case? What about older
On Thu, Apr 03, 2014 at 11:42:31AM +0200, Laszlo Ersek wrote:
Unless you want to do OVMF development yourself (ie. as long as you'd
like to test only), you're best off with
(a) Gerd's packages:
http://www.kraxel.org/repos/
(b) If you use a Fedora host, you can also try a (recently
On Thu, Apr 03, 2014 at 01:23:08PM +0200, Andreas Färber wrote:
Am 03.04.2014 13:16, schrieb Michael S. Tsirkin:
On Wed, Apr 02, 2014 at 05:15:59PM +0200, Paolo Bonzini wrote:
Il 02/04/2014 17:15, Michael S. Tsirkin ha scritto:
Yes and I think this someone was you actually.
Can something
On 03.04.14 15:14, Alexey Kardashevskiy wrote:
This enabled KVM and migration support for a number of POWER8 registers:
* Program Prioirty Register (PPR)
Typo
* Sampled Instruction Address Register (SIAR)
* Sampled Data Address Register (SDAR)
* Vector Registers Save Register (VRSAVE)
This
This allows guests to have a different timebase origin from the host.
This is needed for migration, where a guest can migrate from one host
to another and the two hosts might have a different timebase origin.
However, the timebase seen by the guest must not go backwards, and
should go forwards
This enabled KVM and migration support for a number of POWER8 registers:
* Program Prioirty Register (PPR)
* Sampled Instruction Address Register (SIAR)
* Sampled Data Address Register (SDAR)
* Vector Registers Save Register (VRSAVE)
This enables save/restore of transactional state if MSR_TS is
If lazy refcounts are enabled for a backing file, committing to this
backing file may leave it in a dirty state even if the commit succeeds.
The reason is that the bdrv_flush() call in bdrv_commit() doesn't flush
refcount updates with lazy refcounts enabled, and qcow2_reopen_prepare()
doesn't take
On 04/04/2014 12:25 AM, Alexey Kardashevskiy wrote:
The change log is:
Isolate sc 1 detection logic
build: auto-detect ppc64 architecture
cas: increase hcall buffer size to accomodate 256 cpus
usb: change device tree naming
usb-core: adjust port numbers in set_address
This advertises Data Address Breakpoint Register Extension (DABRX) to
the guest via hyperrtas list and enables it to migrate.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
hw/ppc/spapr.c | 1 +
target-ppc/translate_init.c | 4
2 files changed, 5 insertions(+)
diff
This adds QEMU wrappers for KVM_SET_ONE_REG/KVM_GET_ONE_REG ioctls.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
---
Changes:
v3:
* changed comments
v2:
* added Doc Comments
* removed error_print
---
include/sysemu/kvm.h | 21 +
kvm-all.c| 18
If the user passes an unknown CPU name via the '-cpu' option, exit
with an error message rather than segfaulting.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/arm/highbank.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/hw/arm/highbank.c b/hw/arm/highbank.c
index
On 04/03/14 15:32, Gabriel L. Somlo wrote:
On Thu, Apr 03, 2014 at 11:42:31AM +0200, Laszlo Ersek wrote:
You don't see SMBIOS tables in the guest because you've built upstream
OVMF. As I said before, upstream OvmfPkg doesn't include my SMBIOS
patches. Both (a) and (b) do however.
Oh, OK.
This patchset fixes a couple of issues with A15 boards.
The first is a really obvious one -- running QEMU with
'-M midway -cpu bang' segfaults.
The second one is a problem with running an A15 board
model under KVM with -cpu host: since the 'host' CPU object
doesn't have a 'reset-cbar' QOM
For the machine models which can have a Cortex-A15 CPU (vexpress-a15 and
midway), silently continue if the CPU object has no reset-cbar property
rather than failing. This allows these boards to be used under KVM with
the -cpu host option, since the 'host' CPU object has no reset-cbar
property.
Using __DATE__ or __TIME__ in binary pkgs changes the checksum of
compiled binaries if they get rebuilt, even if there are no other
source changes. Replace the dynamic strings with some equally
informative static strings.
Signed-off-by: Olaf Hering o...@aepfle.de
---
Or remove both lines
Il 03/04/2014 15:47, Olaf Hering ha scritto:
Using __DATE__ or __TIME__ in binary pkgs changes the checksum of
compiled binaries if they get rebuilt, even if there are no other
source changes. Replace the dynamic strings with some equally
informative static strings.
Signed-off-by: Olaf Hering
1 - 100 of 237 matches
Mail list logo
