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.
Pressing enter a few times gradually fixes it.
I do
On Tue, Apr 1, 2014 at 3:09 PM, 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
Public bug reported:
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)
which works fine(
When hotplug an memdev that was previously plugged and unplugged,
RAMBlock idstr is not cleared and triggers an assert error in
qemu_ram_set_idstr(). This series fixes it.
Hu Tao (2):
exec: introduce qemu_ram_unset_idstr() to unset RAMBlock idstr
unset RAMBlock idstr when unregister MemoryRegi
Signed-off-by: Hu Tao
---
exec.c| 26 +-
include/exec/cpu-common.h | 1 +
2 files changed, 22 insertions(+), 5 deletions(-)
diff --git a/exec.c b/exec.c
index 91513c6..cbf7923 100644
--- a/exec.c
+++ b/exec.c
@@ -1202,17 +1202,24 @@ static void qemu_r
Signed-off-by: Hu Tao
---
savevm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/savevm.c b/savevm.c
index 22123be..6f4b1a5 100644
--- a/savevm.c
+++ b/savevm.c
@@ -1208,7 +1208,7 @@ void vmstate_register_ram(MemoryRegion *mr, DeviceState
*dev)
void vmstate_unregister_ra
Hi
I am booting an OpenIndiana image on qemu by using the -smp 4 option. I
seem to be running into this known bug
http://docs.oracle.com/cd/E19253-01/820-5245/ggmsj/index.html
Can someone tell me how can i go about doing workaround 2 on qemu??
Workaround 3,4 are not an option for me. I already tr
On 01/04/14 16:47, Christian Borntraeger wrote:
> We want to configure several things in KVM that go beyond what
> ENABLE_CAP (we need payload) or ONE_REG (we need it for the VM
> and we need to do more complex actions) can provide. Instead of
> adding several s390 specific ioctls, lets provide a c
It's looking good so far, after a few migrations (it takes a while to test
because I'm waiting at least 5 hours between migrations). I'll be happier
once I've done a couple of weeks of this without any failures!
Does anyone have any hints how to debug this thing? :(
I've tried to put hanged gue
Hi,
> > >
> > Actually I move the judge in function assigned_dev_register_msix_mmio.
> > Because assigned_dev_register_msix_mmio do not address the return value,
> > if dev->msix_table is null, this will result a segfault. Right?
>
> I see the confusion, there is a bug there but I think it should
On 02/04/14 10:39, Alexander Graf wrote:
>
> On 02.04.14 10:31, Christian Borntraeger wrote:
>> On 01/04/14 16:47, Christian Borntraeger wrote:
>>> We want to configure several things in KVM that go beyond what
>>> ENABLE_CAP (we need payload) or ONE_REG (we need it for the VM
>>> and we need to d
From: ChenLiang
The cache_insert don't check whether the page has been in the cache.
Signed-off-by: ChenLiang
Signed-off-by: Gonglei
---
page_cache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/page_cache.c b/page_cache.c
index c78157b..78f7590 100644
--- a/page_cache.
> Subject: Re: [Qemu-devel] [PATCH v4 5/8] XBZRLE: optimize XBZRLE to
> decrease the cache misses
>
> I've got a world with just patches 1..5 on that's seeing corruptions, but
> I've not seen where the problem is. So far the world with 1..4 on hasn't
> hit those corruption, but maybe I need to te
* Marcin Gibu??a (m.gib...@beyond.pl) wrote:
> >It's looking good so far, after a few migrations (it takes a while to test
> >because I'm waiting at least 5 hours between migrations). I'll be happier
> >once I've done a couple of weeks of this without any failures!
>
> Does anyone have any hints h
Can you give:
1) A backtrace from the guest
thread apply all bt full
in gdb
You mean from gdb attached to hanged guest? I'll try to get it. From
what I remember it looks rather "normal" - busy executing guest code.
2) What's the earliest/newest qemu versions you've seen thi
* Marcin Gibu??a (m.gib...@beyond.pl) wrote:
> >Can you give:
> > 1) A backtrace from the guest
> > thread apply all bt full
> > in gdb
>
> You mean from gdb attached to hanged guest? I'll try to get it. From
> what I remember it looks rather "normal" - busy executing guest
> code.
ye
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 Graf
---
hw/intc/openpic_kvm.c | 10 ++
1 file changed,
于 2014/3/28 16:21, Markus Armbruster 写道:
> Eric Blake writes:
>
>> On 03/27/2014 02:03 AM, Wenchao Xia wrote:
>>> This file holds some functions that do not need to be generated.
>>>
>>> Signed-off-by: Wenchao Xia
>>> ---
>>> include/qapi/qmp-event.h | 27 +
>>> qapi/Makefil
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
> When a link change occurs on a backend (like tap), we currently do
> not propage such change to the nic. As a result, when someone turns
> off a link on a tap device, for instance, then a guest doesn't see
> that change and continues
On 02.04.2014 11:39, Dr. David Alan Gilbert wrote:
* Marcin Gibu??a (m.gib...@beyond.pl) wrote:
Can you give:
1) A backtrace from the guest
thread apply all bt full
in gdb
You mean from gdb attached to hanged guest? I'll try to get it. From
what I remember it looks rather "norma
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin wrote:
> On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
>> When a link change occurs on a backend (like tap), we currently do
>> not propage such change to the nic. As a result, when someone turns
>> off a link on a tap device, for
Am 02.04.2014 10:54, schrieb Alexander Graf:
>
> On 24.03.14 15:25, Andreas Färber wrote:
>> Am 23.03.2014 10:28, schrieb Prasad Joshi:
>>> Signed-off-by: Prasad Joshi
>>> ---
>>> hw/intc/openpic_kvm.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> Thanks for spotting this, appli
On Wed, Apr 02, 2014 at 01:46:14PM +0300, Yan Vugenfirer wrote:
>
> On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin wrote:
>
> > On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
> >> When a link change occurs on a backend (like tap), we currently do
> >> not propage such change to
Il 01/04/2014 18:24, Laszlo Ersek ha scritto:
On 04/01/14 17:01, 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
linux-image-3.2.0-4-amd64 version 3.2.54-2 and a
> Am 02.04.2014 um 12:53 schrieb Andreas Färber :
>
> Am 02.04.2014 10:54, schrieb Alexander Graf:
>>
>> On 24.03.14 15:25, Andreas Färber wrote:
>>> Am 23.03.2014 10:28, schrieb Prasad Joshi:
Signed-off-by: Prasad Joshi
---
hw/intc/openpic_kvm.c | 2 +-
1 file changed, 1
** Also affects: qemu-kvm
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285708
On Wed, Apr 2, 2014 at 3:10 AM, Peter Maydell wrote:
> On 25 March 2014 03:34, Joel Fernandes wrote:
>> Loading kernel at offset 0x1 works only for zImage, but not for Image,
>> because the kernel expect the start of decompressed kernel (.head.text) to be
>> at an address that's a distance th
On Sat, Mar 29, 2014 at 2:10 AM, Peter Maydell wrote:
> The AArch64 usermode 'any' CPU type was accidentally specified
> with the ARM_FEATURE_THUMB2EE bit set. This is incorrect since
> ARMv8 removes Thumb2EE completely. Since we never implemented
> Thumb2EE anyway having the feature bit set was f
At Tue, 01 Apr 2014 16:34:15 -0400,
Cole Robinson wrote:
>
> On 02/13/2014 06:15 AM, Takashi Iwai wrote:
> > Hi,
> >
> > this is a series of patches to fix / improve the behavior of Gtk UI
> > in the relative pointer tracking mode. Most people didn't notice
> > the bug likely because it doesn't
On Mon, Mar 31, 2014 at 7:37 PM, Andreas Färber wrote:
> CPU address spaces touching load and store helpers as well as the
> movement of (almost) all fields from CPU_COMMON to CPUState have led to
> a noticeable increase of CPU() usage in "hot" paths for both TCG and KVM.
>
> While CPU()'s OBJECT_
Hi,
this is the renewed patch series, just rebased the previous ones on
top of the current git tree. Below is the original description:
***
Hi,
this is a series of patches to fix / improve the behavior of Gtk UI
in the relative pointer tracking mode. Most people didn't notice
the bug likely
I simply like it better, you don't? :)
Signed-off-by: Takashi Iwai
---
ui/gtk.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/ui/gtk.c b/ui/gtk.c
index 9b8df1224fdb..ffaf91ea453a 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -141,6 +141,7 @@ typedef struct GtkDisplayState
G
It's pretty annoying that the pointer reappears at a random place once
after grabbing and ungrabbing the input. Better to restore to the
original position where the pointer was grabbed.
Reference: https://bugzilla.novell.com/show_bug.cgi?id=849587
Signed-off-by: Takashi Iwai
---
ui/gtk.c | 16 +
The GDK motion-notify-event isn't generated when the pointer goes out
of the target window even if the pointer is grabbed, which essentially
means to lose the pointer tracking in gtk-ui.
Meanwhile the generic "event" signal is sent when the pointer is
grabbed, so we can use this and pick the motio
The relative pointer tracking mode was still buggy even after the
previous fix of the motion-notify-event since the events are filtered
out when the pointer moves outside the drawing window due to the
boundary check for the absolute mode.
This patch fixes the issue by moving the unnecessary bounda
On Wed, Apr 02, 2014 at 12:35:26AM +0200, Laszlo Ersek wrote:
> On 04/02/14 00:00, Kevin O'Connor wrote:
> > On Tue, Apr 01, 2014 at 11:44:12PM +0200, Laszlo Ersek wrote:
> >> Right now, OVMF can accept individual fields, or table-at-a-time blobs,
> >> via fw_cfg.
> >>
> >> The internal interface (
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".
Signed-off-by: Paolo Bonzini
---
block/iscsi.c | 3 ++-
1 file changed, 2 insertions(+), 1 del
On 2 April 2014 13:11, Peter Crosthwaite wrote:
> Like others, I have been carrying this change locally. Good to see it up!
Why are you all booting raw Images anyway (just out of curiosity)? All my
test cases boot either a zImage or a uImage, or occasionally a full SD card
image, or I'd have noti
Il 01/04/2014 23:19, Hervé Poussineau ha scritto:
Signed-off-by: Hervé Poussineau
---
hw/ppc/prep.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/hw/ppc/prep.c b/hw/ppc/prep.c
index 035b5b2..dfe4a5c 100644
--- a/hw/ppc/prep.c
+++ b/hw/ppc/prep.c
@@ -346,9 +346,6 @@ static void ppc_p
On Wed, Apr 2, 2014 at 10:47 PM, Peter Maydell wrote:
> On 2 April 2014 13:11, Peter Crosthwaite wrote:
>> Like others, I have been carrying this change locally. Good to see it up!
>
> Why are you all booting raw Images anyway (just out of curiosity)? All my
> test cases boot either a zImage or a
Non-block SCSI devices do not support flushing, but we may still send
them requests via bdrv_flush_all. Just ignore them.
Signed-off-by: Paolo Bonzini
---
block/iscsi.c | 4
1 file changed, 4 insertions(+)
diff --git a/block/iscsi.c b/block/iscsi.c
index 0d15b4d..00316af 100644
--- a/bloc
On 04/02/2014 04:51 AM, Michael S. Tsirkin wrote:
> On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
>> When a link change occurs on a backend (like tap), we currently do
>> not propage such change to the nic. As a result, when someone turns
>> off a link on a tap device, for instanc
On 04/02/2014 08:32 AM, Takashi Iwai wrote:
> The GDK motion-notify-event isn't generated when the pointer goes out
> of the target window even if the pointer is grabbed, which essentially
> means to lose the pointer tracking in gtk-ui.
>
> Meanwhile the generic "event" signal is sent when the poi
On 04/02/2014 08:32 AM, Takashi Iwai wrote:
> The relative pointer tracking mode was still buggy even after the
> previous fix of the motion-notify-event since the events are filtered
> out when the pointer moves outside the drawing window due to the
> boundary check for the absolute mode.
>
> Thi
On 04/02/2014 08:32 AM, Takashi Iwai wrote:
> It's pretty annoying that the pointer reappears at a random place once
> after grabbing and ungrabbing the input. Better to restore to the
> original position where the pointer was grabbed.
>
> Reference: https://bugzilla.novell.com/show_bug.cgi?id=84
On 04/02/2014 08:32 AM, Takashi Iwai wrote:
> I simply like it better, you don't? :)
>
In fact, relative mouse mode is a pain without this feature, you need to
manually initiate a grab with ctrl+alt+g before mouse movement will even work.
Compare to our sdl front end, or virt-viewer, vinagre, vir
On 04/02/14 13:13, Fabio Fantoni wrote:
> Il 01/04/2014 18:24, Laszlo Ersek ha scritto:
>> On 04/01/14 17:01, 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 pa
On 04/02/14 14:38, Gabriel L. Somlo wrote:
> On Wed, Apr 02, 2014 at 12:35:26AM +0200, Laszlo Ersek wrote:
>> On 04/02/14 00:00, Kevin O'Connor wrote:
>>> On Tue, Apr 01, 2014 at 11:44:12PM +0200, Laszlo Ersek wrote:
Right now, OVMF can accept individual fields, or table-at-a-time blobs,
At Wed, 02 Apr 2014 09:28:54 -0400,
Cole Robinson wrote:
>
> On 04/02/2014 08:32 AM, Takashi Iwai wrote:
> > I simply like it better, you don't? :)
> >
>
> In fact, relative mouse mode is a pain without this feature, you need to
> manually initiate a grab with ctrl+alt+g before mouse movement wi
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.
Signed-off-by: Paolo Bonzini
---
block/iscsi.c | 12 +++
Am 02.04.2014 14:48, schrieb Paolo Bonzini:
> Il 01/04/2014 23:19, Hervé Poussineau ha scritto:
>> Signed-off-by: Hervé Poussineau
>>
>> ---
>> hw/ppc/prep.c |3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/hw/ppc/prep.c b/hw/ppc/prep.c
>> index 035b5b2..dfe4a5c 100644
>> --- a/hw
On 04/02/2014 09:42 AM, Takashi Iwai wrote:
> At Wed, 02 Apr 2014 09:28:54 -0400,
> Cole Robinson wrote:
>>
>> On 04/02/2014 08:32 AM, Takashi Iwai wrote:
>>> I simply like it better, you don't? :)
>>>
>>
>> In fact, relative mouse mode is a pain without this feature, you need to
>> manually initia
I am using octeon linux as guest operating system with mips64. I want to
use SMP support. When i use '-smp 2' it display following error:
*Number of SMP cpus requested (2), exceeds max cpus supported by machine
`octeon' (1)*
Does QEMU support SMP for mips64?
Regards
--
Maryyam Muhammad Din
Al-Kha
On 02.04.14 10:31, Christian Borntraeger wrote:
On 01/04/14 16:47, Christian Borntraeger wrote:
We want to configure several things in KVM that go beyond what
ENABLE_CAP (we need payload) or ONE_REG (we need it for the VM
and we need to do more complex actions) can provide. Instead of
adding se
On 24.03.14 15:25, Andreas Färber wrote:
Am 23.03.2014 10:28, schrieb Prasad Joshi:
Signed-off-by: Prasad Joshi
---
hw/intc/openpic_kvm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for spotting this, applied to ppc-next (w/ typo fix in subject):
https://github.com/afaerbe
FreeBSD 10.0-RELEASE has bswap16() etc. macros defined in sys/endian.h,
which leads to a conflict with our static inline definitions.
Force using the system version of the macros.
Signed-off-by: Andreas Färber
---
On 9.0-RELEASE I did not have this issue, so unsure if some version check
is nee
Signed-off-by: Jun Li
This patch can make sure the data still existing after shrinking. And only
discard the unused (guest) clusters. If shrinking to the size which stored
data, It will return an error and will not do any change.
As this patch can support shrinking, so changed the func name of
Signed-off-by: Jun Li
This patch can make sure the data still existing after shrinking. And only
discard the unused (guest) clusters. If shrinking to the size which stored
data, It will return an error and will not do any change.
As this patch can support shrinking, so changed the func name of
Signed-off-by: Jun Li
This patch can make sure the data still existing after shrinking. And only
discard the unused (guest) clusters. If shrinking to the size which stored
data, It will return an error and will not do any change.
As this patch can support shrinking, so changed the func name of
Signed-off-by: Jun Li
This patch can make sure the data still existing after shrinking. And only
discard the unused (guest) clusters. If shrinking to the size which stored
data, It will return an error and will not do any change.
As this patch can support shrinking, so changed the func name of
Signed-off-by: Jun Li
This patch can make sure the data still existing after shrinking. And only
discard the unused (guest) clusters. If shrinking to the size which stored
data, It will return an error and will not do any change.
As this patch can support shrinking, so changed the func name of
On 11 March 2014 12:13, Dr. David Alan Gilbert wrote:
> Except pthread_setname_np is not portable and was previously
> ifdef'd _GNU_SOURCE anyway, and the parameters on other OSs
> maybe different (freebsd has got a 3rd parameter for no
> apparent reason).
No, glibc's arguments are identical to
On 01/04/14 17:48, Markus Armbruster wrote:
Heinz Graalfs writes:
Hi Kevin,
doing a
virsh detach-device ...
ends up in the following QEMU monitor commands:
1. device_del ...
2. drive_del ...
qmp_device_del() performs the device unplug path.
In case of a block device do_drive_del() t
Il 02/04/2014 15:31, Laszlo Ersek ha scritto:
On 04/02/14 13:13, Fabio Fantoni wrote:
Il 01/04/2014 18:24, Laszlo Ersek ha scritto:
On 04/01/14 17:01, Fabio Fantoni wrote:
Today I tried latest qemu 2.0 compiled from git (commit
63678e17cf399ff81b93417fe7bee8d6ef6b6b1b) on this dom0:
Debian 7 (
IRQ are lowered when ievent bit is cleared, so irq_pulse makes no sense
here...
Signed-off-by: Fabien Chouteau
---
hw/net/fsl_etsec/rings.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/net/fsl_etsec/rings.c b/hw/net/fsl_etsec/rings.c
index e36cfbe..d4a494f 100644
---
On 02.04.2014, at 16:49, Fabien Chouteau wrote:
> IRQ are lowered when ievent bit is cleared, so irq_pulse makes no sense
> here...
>
> Signed-off-by: Fabien Chouteau
Thanks, applied to ppc-next. Given that the wiring with boards is still missing
I don't think this is a critical 2.0 fix.
A
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
>
> On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin wrote:
>
>> On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
>>> When a link change occurs on a backend (like tap), we currently do
>>> not propage such change to the nic. As a result
On 04/02/2014 04:52 PM, Alexander Graf wrote:
>
> On 02.04.2014, at 16:49, Fabien Chouteau wrote:
>
>> IRQ are lowered when ievent bit is cleared, so irq_pulse makes no sense
>> here...
>>
>> Signed-off-by: Fabien Chouteau
>
> Thanks, applied to ppc-next.
Thanks Alex,
> Given that the wiring
Note that it launches two instances to as sharing memory is the purpose
of Nahanni/ivshmem.
Cc: Cam Macdonell
Signed-off-by: Andreas Färber
---
This test demonstrates a use case of running two QEMU instances in qtest.
However, similar to mst's proposed KVM acpi-test, it fails on systems
with
On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
> On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
> >
> > On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin wrote:
> >
> >> On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
> >>> When a link change occurs on a backend (like
On Mi, 2014-04-02 at 09:28 -0400, Cole Robinson wrote:
> On 04/02/2014 08:32 AM, Takashi Iwai wrote:
> > I simply like it better, you don't? :)
> >
>
> In fact, relative mouse mode is a pain without this feature, you need to
> manually initiate a grab with ctrl+alt+g before mouse movement will ev
[On 04/02/2014 08:47 AM, Peter Maydell wrote:
> On 2 April 2014 13:11, Peter Crosthwaite wrote:
>> Like others, I have been carrying this change locally. Good to see it up!
>
> Why are you all booting raw Images anyway (just out of curiosity)? All my
> test cases boot either a zImage or a uImage,
Hi,
> > From the conversation so far, it seems to me that:
> >
> > - type 0 is best left to the BIOS (user overrides via
> > command line at their own risk)
I think it was a bad idea to allow overriding type0 fields in the first
place. It also isn't used in practice. I don't think
Am 02.04.2014 17:06, schrieb Michael S. Tsirkin:
> On Wed, Apr 02, 2014 at 04:57:48PM +0200, Andreas Färber wrote:
>> Note that it launches two instances to as sharing memory is the purpose
>> of Nahanni/ivshmem.
>>
>> Cc: Cam Macdonell
>> Signed-off-by: Andreas Färber
>> ---
>> This test demons
Without this, we need to initiate a manual grab with ctrl+alt+g just
to get a usable mouse.
Signed-off-by: Cole Robinson
---
Gerd, Takashi, I think this should do what we want.
ui/gtk.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/ui/gtk.c b/ui/gtk.c
index 9b8df12..ebaade2 10064
Hi,
> If qemu gives OVMF a complete, concatenated dump of all tables, I'll
> have to split that up into individual tables, and install those one by one.
I feel like I should have a look at how coreboot handles this for an
additional data point ...
cheers,
Gerd
On Wed, Apr 02, 2014 at 04:57:48PM +0200, Andreas Färber wrote:
> Note that it launches two instances to as sharing memory is the purpose
> of Nahanni/ivshmem.
>
> Cc: Cam Macdonell
> Signed-off-by: Andreas Färber
> ---
> This test demonstrates a use case of running two QEMU instances in qtest.
Signed-off-by: Lluís Vilanova
---
tests/qapi-schema/test-qapi.py |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/qapi-schema/test-qapi.py b/tests/qapi-schema/test-qapi.py
index b3d1e1d..ac6da13 100644
--- a/tests/qapi-schema/test-qapi.py
+++ b/tests/qapi-schema/te
Signed-off-by: Lluís Vilanova
---
Makefile | 24 ++--
tests/Makefile | 20
2 files changed, 34 insertions(+), 10 deletions(-)
diff --git a/Makefile b/Makefile
index ec74039..84345ee 100644
--- a/Makefile
+++ b/Makefile
@@ -237,23 +237,35 @@ qapi
On Wed, Apr 02, 2014 at 05:07:09PM +0200, Andreas Färber wrote:
> Am 02.04.2014 17:06, schrieb Michael S. Tsirkin:
> > On Wed, Apr 02, 2014 at 04:57:48PM +0200, Andreas Färber wrote:
> >> Note that it launches two instances to as sharing memory is the purpose
> >> of Nahanni/ivshmem.
> >>
> >> Cc:
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 ioeventfd for TCG, no.
Paolo
Signed-off-by: Lluís Vilanova
---
docs/qapi-code-gen.txt | 11 +
scripts/qapi.py| 66 +++-
tests/Makefile |5 ++
tests/qapi-schema/include-after-err.err|1
tests/qapi-schema/in
On Mi, 2014-04-02 at 14:32 +0200, Takashi Iwai wrote:
> +static gboolean gd_event(GtkWidget *widget, GdkEvent *event, void
> *opaque)
> +{
> +if (event->type == GDK_MOTION_NOTIFY)
> +return gd_motion_event(widget, &event->motion, opaque);
> +return FALSE;
> +}
Fails checkpatch:
WA
Use an explicit input file on the command-line instead of reading from standard
input
Signed-off-by: Lluís Vilanova
---
Makefile | 12 ++--
docs/qapi-code-gen.txt |4 ++--
scripts/qapi-commands.py
On Mi, 2014-04-02 at 11:07 -0400, Cole Robinson wrote:
> +if (button->button == 1 &&
> +button->type == GDK_BUTTON_PRESS &&
> +!gd_is_grab_active(s) &&
> +!qemu_input_is_absolute()) {
> +
> gtk_check_menu_item_set_active(GTK_CHECK_MENU_ITEM(s->grab_item),
> +
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 &&
> > +!gd_is_grab_active(s) &&
> > +!qemu_input_is_absolute()) {
> > +
> > gtk_che
Adds an include primitive to the syntax of QAPI schema files, allowing these to
be modularized into multiple per-topic files in the future.
Signed-off-by: Lluís Vilanova
---
Changes in v8:
* Do not show absolute paths in error messages.
Changes in v7:
* Add tests for relative path inclusion.
On 04/02/2014 11:03 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
>> On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
>>>
>>> On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin wrote:
>>>
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
At Wed, 02 Apr 2014 17:17:54 +0200,
Gerd Hoffmann wrote:
>
> On Mi, 2014-04-02 at 14:32 +0200, Takashi Iwai wrote:
> > +static gboolean gd_event(GtkWidget *widget, GdkEvent *event, void
> > *opaque)
> > +{
> > +if (event->type == GDK_MOTION_NOTIFY)
> > +return gd_motion_event(widget, &
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> The datasheet is clear that the frame length written to the DATA
> register is actually stored in the TX FIFO; this means we don't
> need to keep both tx_frame_len and tx_fifo_len state separately.
>
> Signed-off-by: Peter Maydell
> Reviewed-by:
On Wed, Apr 02, 2014 at 11:25:32AM -0400, Vlad Yasevich wrote:
> On 04/02/2014 11:03 AM, Michael S. Tsirkin wrote:
> > On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
> >> On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
> >>>
> >>> On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin wrote
The subsection already exists in one well-known enterprise Linux
distribution, but for some strange reason the fields were swapped
when forward-porting the patch to upstream.
Limit headaches for said enterprise Linux distributor when the
time will come to rebase their version of QEMU.
Signed-off-
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> Packet transmission for the stellaris ethernet controller can be triggered
> in one of two ways:
> * by setting a threshold value in the THR register; when the FIFO
>fill level reaches the threshold, the h/w starts transmitting.
>Software
On Wed, Apr 02, 2014 at 05:33:02PM +0200, Paolo Bonzini wrote:
> The subsection already exists in one well-known enterprise Linux
> distribution, but for some strange reason the fields were swapped
> when forward-porting the patch to upstream.
>
> Limit headaches for said enterprise Linux distribu
* Ed Maste (ema...@freebsd.org) wrote:
> On 11 March 2014 12:13, Dr. David Alan Gilbert wrote:
>
> > Except pthread_setname_np is not portable and was previously
> > ifdef'd _GNU_SOURCE anyway, and the parameters on other OSs
> > maybe different (freebsd has got a 3rd parameter for no
> > apparen
On 04/02/2014 11:29 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 02, 2014 at 11:25:32AM -0400, Vlad Yasevich wrote:
>> On 04/02/2014 11:03 AM, Michael S. Tsirkin wrote:
>>> On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
>
> O
On Wed, 2014-04-02 at 08:50 +, Gonglei (Arei) wrote:
> Hi,
> > > >
> > > Actually I move the judge in function assigned_dev_register_msix_mmio.
> > > Because assigned_dev_register_msix_mmio do not address the return value,
> > > if dev->msix_table is null, this will result a segfault. Right?
>
On 2 April 2014 16:33, Paolo Bonzini wrote:
> The subsection already exists in one well-known enterprise Linux
> distribution, but for some strange reason the fields were swapped
> when forward-porting the patch to upstream.
>
> Limit headaches for said enterprise Linux distributor when the
> time
Il 02/04/2014 17:42, Peter Maydell ha scritto:
On 2 April 2014 16:33, Paolo Bonzini wrote:
The subsection already exists in one well-known enterprise Linux
distribution, but for some strange reason the fields were swapped
when forward-porting the patch to upstream.
Limit headaches for said ent
Hello,
I was using the qemu command line option:
-name foo,process=foo
in order to get a nice process naming on my linux box.
and so I could do
$ ps axco pid,command | grep 'foo'
4242 foo
I switched to a config file with:
[name]
guest = "foo"
process = "foo"
but now the previous `ps` comman
1 - 100 of 144 matches
Mail list logo
