Re: [Qemu-devel] fstrim and cache=none

Il 04/06/2013 03:02, Dusty Mabe ha scritto: > On Mon, Jun 3, 2013 at 5:39 PM, Dusty Mabe wrote: >> >> It is possible that I was mistaken. Now when I switch back to >> cache=none I am still able to execute trim operations. I'll >> investigate a little more into my exact steps that I took and see if

Re: [Qemu-devel] VM can not boot after commit 235e898

Il 04/06/2013 05:47, Dunrong Huang ha scritto: > > QEMU command: > ~/usr/bin/qemu-system-x86_64 -enable-kvm -m 1024 debian-append.img > > git bisect tells that the following commit causes this bug: > > commit 235e8982ad393e5611cb892df54881c872eea9e1 > Author: Jordan Justen

Re: [Qemu-devel] [PATCH v2 1/2] net: introduce MAC_TABLE_CHANGED event

On Fri, May 31, 2013 at 11:02:54AM +0800, Amos Kong wrote: > On Fri, May 31, 2013 at 08:35:28AM +0800, Amos Kong wrote: > > On Thu, May 30, 2013 at 04:54:41PM +0300, Michael S. Tsirkin wrote: > > > On Tue, May 28, 2013 at 08:25:56AM -0400, Luiz Capitulino wrote: > > > > > > > 2. Can you actually

Re: [Qemu-devel] VM can not boot after commit 235e898

Fixed in 651eb0f4? On Mon, Jun 3, 2013 at 8:47 PM, Dunrong Huang wrote: > > QEMU command: > ~/usr/bin/qemu-system-x86_64 -enable-kvm -m 1024 debian-append.img > > git bisect tells that the following commit causes this bug: > > commit 235e8982ad393e5611cb892df54881c872eea9e1 > Author: Jordan Juste

Re: [Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

On Mon, Jun 03, 2013 at 03:20:48PM -0500, Anthony Liguori wrote: > Paolo Bonzini writes: > > > Il 03/06/2013 19:49, Anthony Liguori ha scritto: > >> Peter Wu writes: > >> > >>> Hi, > >>> > >>> With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e), > >>> `qemu-system-x86_64 -ena

Re: [Qemu-devel] [PATCH] target-i386: cpu: fix potential buffer overrun in get_register_name_32()

Reviewed-by: liguang 在 2013-06-03一的 18:23 +0200，Igor Mammedov写道： > spotted by Coverity, > x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing > x86_reg_info_32[CPU_NB_REGS32] will be one element off array. Yes, it will. > > Signed-off-by: Igor Mammedov > --- > target-i386/cpu.c |

Re: [Qemu-devel] [PATCH] target-i386: cpu: fix potential buffer overrun in get_register_name_32()

On 06/03/2013 11:23 AM, Igor Mammedov wrote: > spotted by Coverity, > x86_reg_info_32[] is CPU_NB_REGS32 elements long, so accessing > x86_reg_info_32[CPU_NB_REGS32] will be one element off array. > > Signed-off-by: Igor Mammedov > --- > target-i386/cpu.c |2 +- > 1 files changed, 1 insertio

[Qemu-devel] [PATCH V2] net: tap: fix NULL dereference when passing invalid parameters to tap

This patch forbid the following invalid parameters to tap: 1) fd and vhostfds were specified but vhostfd were not specified 2) vhostfds were specified but fds were not specified 3) fds and vhostfd were specified For 1 and 2, net_init_tap_one() will still pass NULL as vhostfdname to monitor_handle

Re: [Qemu-devel] [PATCH] net: tap: fix NULL dereference when passing both fd and vhostfds to tap

On 06/03/2013 06:48 PM, Laszlo Ersek wrote: > comments below > > On 06/03/13 11:04, Jason Wang wrote: >> This is because vhostfdname were passed as NULL to net_init_tap_one() when >> vhostfd were not specified, but net_init_tap_one() will still pass it to >> monitor_handle_fd_param() when tap->has_

Re: [Qemu-devel] [PATCH RFC 00/13] qemu: generate acpi tables for the guest

On Mon, Jun 3, 2013 at 4:12 PM, Anthony Liguori wrote: > Jordan Justen writes: >> I mentioned in the other thread that perhaps QEMU could also consider >> making the ACPI code available under some 'appropriate' license, which >> would allow firmware writers to leverage the code directly if desire

Re: [Qemu-devel] [PATCH] qemu-doc, help: update options/keys for GTK/SDL

03.06.2013 14:54, Peter Wu wrote: > The GTK display type has been introduced in 1.5, replacing SDL as default. > Some > options only work with SDL and not GTK. This patch tries to address them. > > The `-display` option is updated with the new `gtk` option. > > The `-alt-grab` and `-ctrl-alt` op

[Qemu-devel] Re: Boot guest OS on many nodes?

On Monday, June 3, 2013 7:54:31 PM CDT, Steven.G wrote: Thanks very much, On Sunday, June 2, 2013 9:37:55 PM CDT, Steven.G wrote: ... If I change the QEMU codes to adapt this using some mechanism like RPC to communicate within nodes, and register CPUs and Mems to the seabios when booting th

[Qemu-devel] VM can not boot after commit 235e898

QEMU command: ~/usr/bin/qemu-system-x86_64 -enable-kvm -m 1024 debian-append.img git bisect tells that the following commit causes this bug: commit 235e8982ad393e5611cb892df54881c872eea9e1 Author: Jordan Justen Date: Wed May 29 01:27:26 2013 -0700 kvm: support using KVM_MEM_READONLY flag

Re: [Qemu-devel] [PATCH trivial] acpi: actually require either data= or file= for -acpitable

03.06.2013 22:19, Laszlo Ersek wrote: > On 06/03/13 14:42, Michael Tokarev wrote: [] >> This function has another error -- if the file specified >> (either for data= or file=) can't be read, it happily >> continues instead of erroring out. _That_ is the bug >> I tried to hunt but catched something

Re: [Qemu-devel] [PATCH v5 4/4] Add qtest support for i.MX I2C device emulation.

Hi Peter, On Tue, Jun 4, 2013 at 1:21 AM, Peter Maydell wrote: > On 8 May 2013 09:28, Jean-Christophe DUBOIS wrote: >> This is using a ds1338 RTC chip on the i2c bus. This RTC >> chip is not present on the real board. > > Ideally this should work by the test driver passing > a "-device ds1338,so

[Qemu-devel] [Bug 1187121] Re: segfault with -vga vmware and -display gtk

** Changed in: qemu (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1187121 Title: segfault with -vga vmware and -display gtk Status in QEMU: Confirmed

Re: [Qemu-devel] fstrim and cache=none

On Mon, Jun 3, 2013 at 5:39 PM, Dusty Mabe wrote: > > It is possible that I was mistaken. Now when I switch back to > cache=none I am still able to execute trim operations. I'll > investigate a little more into my exact steps that I took and see if I > can come up with a reproducer for the issue I

Re: [Qemu-devel] Boot guest OS on many nodes?

Thanks very much, On Sunday, June 2, 2013 9:37:55 PM CDT, Steven.G wrote: Dear all, I've a scene, I have many host nodes with linux kernels, and I want to boot one guest OS on all these nodes use QEMU/KVM. In order that I can use all the physical CPUs and Mems distributed on these linux nodes,

Re: [Qemu-devel] gtk UI doesn't correctly byte swap 32-bit framebuffer on qemu-system-ppc little-endian host

Mark Cave-Ayland writes: > Hi all, > > I've just been testing some more OpenBIOS images with the new gtk UI and > found that if you specify a 32-bit depth framebuffer on qemu-system-ppc > running on a little-endian host then the RGB -> BGR byteswap doesn't > take place. > > Good: > ./qemu-syst

Re: [Qemu-devel] [PATCH RFC 00/13] qemu: generate acpi tables for the guest

Jordan Justen writes: > On Tue, May 14, 2013 at 6:34 AM, Anthony Liguori > wrote: >> "Michael S. Tsirkin" writes: >> >>> On Mon, May 13, 2013 at 03:38:51PM -0500, Anthony Liguori wrote: I don't think it's a good idea to move BIOS functionality in QEMU. >>> >>> Just to clarify: generating

[Qemu-devel] gtk UI doesn't correctly byte swap 32-bit framebuffer on qemu-system-ppc little-endian host

Hi all, I've just been testing some more OpenBIOS images with the new gtk UI and found that if you specify a 32-bit depth framebuffer on qemu-system-ppc running on a little-endian host then the RGB -> BGR byteswap doesn't take place. Good: ./qemu-system-ppc -g 1024x768x32 -vnc :1 ./qemu-syst

Re: [Qemu-devel] [PATCH RFC 00/13] qemu: generate acpi tables for the guest

On Tue, May 14, 2013 at 6:34 AM, Anthony Liguori wrote: > "Michael S. Tsirkin" writes: > >> On Mon, May 13, 2013 at 03:38:51PM -0500, Anthony Liguori wrote: >>> I don't think it's a good idea to move BIOS functionality in QEMU. >> >> Just to clarify: generating ACPI tables is not BIOS >> function

[Qemu-devel] [Bug 1187121] [NEW] segfault with -vga vmware and -display gtk

Public bug reported: When some guest is run with -vga vmware -display gtk, qemu segfaults after certain guest gui operations. ./x86_64-softmmu/qemu-system-x86_64 -cdrom ubuntu-10.04.4-desktop-i386.iso -vga vmware -enable-kvm (-enable-kvm just to speed things up, it does not depend on kvm). (Ubu

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

On 06/03/2013 05:58 PM, Benoît Canet wrote: When the PF does an FLR the hardware go back to its default state, the SR-IOV configuration is gone and the VFs disappears from the bus. Then the restore state function of the kernel reset code would bring the SR-IOV PF configuration back. Ok, now you

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

> >When the PF does an FLR the hardware go back to its default state, the SR-IOV > >configuration is gone and the VFs disappears from the bus. > >Then the restore state function of the kernel reset code would bring the > >SR-IOV > >PF configuration back. > > > Ok, now you're a bit mis-led here. >

Re: [Qemu-devel] [PATCH 0/3] Remove legacy sysfw code

You seem to have a much better handle than I do on machine migration and backward compatibility issues within QEMU. One difference we'll see from this series is that... With QEMU 1.2, an error would always be generated with: qemu-system-x86_64 -M pc-1.2 -enable-kvm -pflash flash.bin Whereas in Q

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

On 06/03/2013 05:27 PM, Benoît Canet wrote: I was asking this because the PF driver should reset the PF while the VF are used by VFIO/QEMU when the PF doesn't respond anymore. What your VF does while your PF is being reset is PF (& VF) dependent. A 'good design' would not impact the VF operati

Re: [Qemu-devel] fstrim and cache=none

Paolo, It is possible that I was mistaken. Now when I switch back to cache=none I am still able to execute trim operations. I'll investigate a little more into my exact steps that I took and see if I can come up with a reproducer for the issue I observed. Thanks, Dusty

Re: [Qemu-devel] [GIT PULL] Xen fixes and cleanups 20130603

On 3 June 2013 22:13, Anthony Liguori wrote: > Peter was kind enough to put up this page: > > http://wiki.qemu.org/Contribute/SubmitAPullRequest That just has the stuff that I could think of off the top of my head in half an hour or so, so other people should feel free to add/edit items. thanks

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

> >I was asking this because the PF driver should reset the PF while the VF are > >used by VFIO/QEMU when the PF doesn't respond anymore. > > > What your VF does while your PF is being reset is PF (& VF) dependent. > A 'good design' would not impact the VF operation, other than to stall it > until

[Qemu-devel] [PATCH v2] gtk: don't use g_object_unref on GdkCursor

It's not a GObject. Cc: Gerd Hoffman Reported-by: Michael Tokarev Signed-off-by: Anthony Liguori --- v1 -> v2 - Fix summary to agree with code (Peter) --- ui/gtk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ui/gtk.c b/ui/gtk.c index 8dc9041..3bc2842 100644 --- a/ui/gt

Re: [Qemu-devel] [GIT PULL] Xen fixes and cleanups 20130603

Stefano Stabellini writes: > On Mon, 3 Jun 2013, Anthony Liguori wrote: >> Stefano Stabellini writes: >> >> > On Mon, 3 Jun 2013, Anthony Liguori wrote: >> >> Stefano Stabellini writes: >> >> >> >> > Anthony, >> >> > please pull the following changes since commit >> >> > 6a4e17711442849bf2cc7

Re: [Qemu-devel] [PATCH] gtk: don't use g_object_ref on GdkCursor

Peter Maydell writes: > On 3 June 2013 21:39, Anthony Liguori wrote: >> It's not a GObject. >> >> Cc: Gerd Hoffman >> Reported-by: Michael Tokarev >> Signed-off-by: Anthony Liguori >> --- >> ui/gtk.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/ui/gtk.c b/ui/gt

Re: [Qemu-devel] [PATCH 1/3] sysfw: remove read-only pc_sysfw_flash_vs_rom_bug_compatible

Il 03/06/2013 22:36, Jordan Justen ha scritto: > On Mon, Jun 3, 2013 at 8:19 AM, Paolo Bonzini wrote: >> The variable is not written anymore. >> >> Signed-off-by: Paolo Bonzini >> --- >> hw/block/pc_sysfw.c | 26 +- >> 1 file changed, 1 insertion(+), 25 deletions(-) >> >>

Re: [Qemu-devel] [PATCH 3/3] pc_sysfw: do not make it a device anymore

Il 03/06/2013 22:46, Jordan Justen ha scritto: > Could you separate out the isapc_ram_fw part? It seems like a viable > separate change, and a better way to handle that situation. I don't think this change is useful enough without the rest. The real cleanup comes from differentiating BIOS vs. fla

Re: [Qemu-devel] [PATCH 2/3] pc_sysfw: remove the rom_only property

Il 03/06/2013 22:50, Jordan Justen ha scritto: > On Mon, Jun 3, 2013 at 8:19 AM, Paolo Bonzini wrote: >> > With the new semantics of pc_sysfw (no -pflash implies "old-style" ROM >> > setup, >> > -pflash implies "new-style" ROM setup), there is no need anymore for a >> > compat >> > property. Ol

Re: [Qemu-devel] [GIT PULL] Xen fixes and cleanups 20130603

On Mon, 3 Jun 2013, Anthony Liguori wrote: > Stefano Stabellini writes: > > > On Mon, 3 Jun 2013, Anthony Liguori wrote: > >> Stefano Stabellini writes: > >> > >> > Anthony, > >> > please pull the following changes since commit > >> > 6a4e17711442849bf2cc731ccddef5a2a2d92d29:

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

On 06/03/2013 03:29 PM, Benoît Canet wrote: to a guest will the consequences of a PF FLR be handled fine by QEMU and the guest ? the reset occurs long before the device is passed to the guest. I was asking this because the PF driver should reset the PF while the VF are used by VFIO/QEMU when

Re: [Qemu-devel] [PATCH] gtk: don't use g_object_ref on GdkCursor

On 3 June 2013 21:39, Anthony Liguori wrote: > It's not a GObject. > > Cc: Gerd Hoffman > Reported-by: Michael Tokarev > Signed-off-by: Anthony Liguori > --- > ui/gtk.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/ui/gtk.c b/ui/gtk.c > index 8dc9041..3bc2842 100644

Re: [Qemu-devel] [PATCH 2/3] pc_sysfw: remove the rom_only property

On Mon, Jun 3, 2013 at 8:19 AM, Paolo Bonzini wrote: > With the new semantics of pc_sysfw (no -pflash implies "old-style" ROM setup, > -pflash implies "new-style" ROM setup), there is no need anymore for a compat > property. Old machines simply will never use -pflash, and thus will always > use o

Re: [Qemu-devel] [GIT PULL] Xen fixes and cleanups 20130603

Stefano Stabellini writes: > On Mon, 3 Jun 2013, Anthony Liguori wrote: >> Stefano Stabellini writes: >> >> > Anthony, >> > please pull the following changes since commit >> > 6a4e17711442849bf2cc731ccddef5a2a2d92d29: >> > >> >

Re: [Qemu-devel] [PATCH v3] qemu-char: don't issue CHR_EVENT_OPEN in a BH

Michael Roth writes: > When CHR_EVENT_OPENED was initially added, it was CHR_EVENT_RESET, > and it was issued as a bottom-half: > > 86e94dea5b740dad65446c857f6959eae43e0ba6 > > Which we basically used to print out a greeting/prompt for the > monitor. > > AFAICT the only reason this was ever done

Re: [Qemu-devel] [PATCH 3/3] pc_sysfw: do not make it a device anymore

Could you separate out the isapc_ram_fw part? It seems like a viable separate change, and a better way to handle that situation. -Jordan On Mon, Jun 3, 2013 at 8:19 AM, Paolo Bonzini wrote: > Move the code to hw/i386, the sole remaining property is available > as !pci_enabled. > > Signed-off-by:

[Qemu-devel] [PATCH] gtk: don't use g_object_ref on GdkCursor

It's not a GObject. Cc: Gerd Hoffman Reported-by: Michael Tokarev Signed-off-by: Anthony Liguori --- ui/gtk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ui/gtk.c b/ui/gtk.c index 8dc9041..3bc2842 100644 --- a/ui/gtk.c +++ b/ui/gtk.c @@ -377,7 +377,7 @@ static void gd_c

[Qemu-devel] [PATCH] gtk: don't resize window when enabling scaling

Signed-off-by: Anthony Liguori --- ui/gtk.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ui/gtk.c b/ui/gtk.c index 52c3f95..8dc9041 100644 --- a/ui/gtk.c +++ b/ui/gtk.c @@ -885,9 +885,11 @@ static void gd_menu_zoom_fit(GtkMenuItem *item, void *opaque) s->free_s

Re: [Qemu-devel] [PATCH 1/3] sysfw: remove read-only pc_sysfw_flash_vs_rom_bug_compatible

On Mon, Jun 3, 2013 at 8:19 AM, Paolo Bonzini wrote: > The variable is not written anymore. > > Signed-off-by: Paolo Bonzini > --- > hw/block/pc_sysfw.c | 26 +- > 1 file changed, 1 insertion(+), 25 deletions(-) > > diff --git a/hw/block/pc_sysfw.c b/hw/block/pc_sysfw.c >

Re: [Qemu-devel] [GIT PULL] Xen fixes and cleanups 20130603

On Mon, 3 Jun 2013, Anthony Liguori wrote: > Stefano Stabellini writes: > > > Anthony, > > please pull the following changes since commit > > 6a4e17711442849bf2cc731ccddef5a2a2d92d29: > > > >

[Qemu-devel] [PATCH v3] qemu-char: don't issue CHR_EVENT_OPEN in a BH

When CHR_EVENT_OPENED was initially added, it was CHR_EVENT_RESET, and it was issued as a bottom-half: 86e94dea5b740dad65446c857f6959eae43e0ba6 Which we basically used to print out a greeting/prompt for the monitor. AFAICT the only reason this was ever done in a BH was because in some cases we'd

Re: [Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

Paolo Bonzini writes: > Il 03/06/2013 19:49, Anthony Liguori ha scritto: >> Peter Wu writes: >> >>> Hi, >>> >>> With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e), >>> `qemu-system-x86_64 -enable-kvm` fails to run with the following error: >>> >>> kvm_set_phys_mem: error

Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

On Mon, 3 Jun 2013 15:05:03 -0500 mdroth wrote: > On Mon, Jun 03, 2013 at 03:54:48PM -0400, Luiz Capitulino wrote: > > On Mon, 03 Jun 2013 21:13:30 +0200 > > Paolo Bonzini wrote: > > > > > Il 03/06/2013 19:17, Luiz Capitulino ha scritto: > > > > This entry doesn't reflect reality for a few year

Re: [Qemu-devel] [PATCH 0/2] Fix NBD hostname parsing issues

Il 03/06/2013 17:54, Ján Tomko ha scritto: > Fix parsing of NBD URIs with IPv6 addresses, broken by v1.4.0-736-gf17c90b > and fix parsing of NBD filenames with hostnames starting with a digit (fixed > by the same commit, but only for NBD URIs): > https://lists.gnu.org/archive/html/qemu-devel/2013-0

Re: [Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

Il 03/06/2013 19:49, Anthony Liguori ha scritto: > Peter Wu writes: > >> Hi, >> >> With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e), >> `qemu-system-x86_64 -enable-kvm` fails to run with the following error: >> >> kvm_set_phys_mem: error unregistering overlapping slot: I

Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

On Mon, Jun 03, 2013 at 03:54:48PM -0400, Luiz Capitulino wrote: > On Mon, 03 Jun 2013 21:13:30 +0200 > Paolo Bonzini wrote: > > > Il 03/06/2013 19:17, Luiz Capitulino ha scritto: > > > This entry doesn't reflect reality for a few years now. This commit > > > splits it into Human Monitor (HMP), Q

[Qemu-devel] OS crash while attempting to boot a 1TB guest.

Hello, For guest sizes >= 1TB RAM the guest OS is unable to boot up (please see attached GIF file for the Oops message). Wonder if this is a bug/regression in qemu/seabios or does one have to enable/disable something else in the qemu command line (pl. see below) ? Thanks Vinod Host and G

Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

On Mon, 03 Jun 2013 21:13:30 +0200 Paolo Bonzini wrote: > Il 03/06/2013 19:17, Luiz Capitulino ha scritto: > > This entry doesn't reflect reality for a few years now. This commit > > splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped > > as a maintainer. > > > > This is what we

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

> >to a guest will the consequences of a PF FLR be handled fine by QEMU and the > >guest ? > > > the reset occurs long before the device is passed to the guest. I was asking this because the PF driver should reset the PF while the VF are used by VFIO/QEMU when the PF doesn't respond anymore. > Th

Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

Il 03/06/2013 19:17, Luiz Capitulino ha scritto: > This entry doesn't reflect reality for a few years now. This commit > splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped > as a maintainer. > > This is what we have been for the last few years. Also, it's going > to help me to off

[Qemu-devel] [PULL 18/24] sd/sdhci.c: Fix bdata_read DPRINT message

From: Peter Crosthwaite This message was printing out the data in decimal only, which is not very friendly to the debugging developer. Add hex variant in parenthesis to make it consistent with other similar messages in this module. Signed-off-by: Peter Crosthwaite Reviewed-by: Igor Mitsyanko R

[Qemu-devel] [PULL 01/24] xilinx_spips: seperate SPI and QSPI as two classes

From: Peter Crosthwaite Make SPI and QSPI different classes. QSPIPS is setup as a child of SPIPS. Only QSPI has the LQSPI functionality, so move all that to the child class. Signed-off-by: Peter Crosthwaite Reviewed-by: Peter Maydell Reviewed-by: Edgar E. Iglesias Message-id: 2cdd0cadb5ba77c

Re: [Qemu-devel] VFIO and scheduled SR-IOV cards

On Mon, 2013-06-03 at 14:34 -0400, Don Dutile wrote: > On 06/03/2013 02:02 PM, Alex Williamson wrote: > > On Mon, 2013-06-03 at 18:33 +0200, Benoît Canet wrote: > >> Hello, > >> > >> I plan to write a PF driver for an SR-IOV card and make the VFs work with > >> QEMU's > >> VFIO passthrough so I am

Re: [Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

Peter Wu writes: > Hi, > > With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e), > `qemu-system-x86_64 -enable-kvm` fails to run with the following error: > > kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument > > After this message, qemu aborts. Revert

Re: [Qemu-devel] [PATCH 0/2] MAINTAINERS: QMP: entry update and new maintainers

Luiz Capitulino writes: > Hi, > > This is an small update on QMP/HMP/QAPI mainternership. Please, check > individual patches for details. Acked-by: Anthony Liguori Regards, Anthony Liguori > > Luiz Capitulino (2): > MAINTAINERS: new maintainers for qapi-schema.json > MAINTAINERS: split M

Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough

On 06/01/2013 08:13 AM, Benoît Canet wrote: Hello, I may have soon the PF driver of an SR-IOV card to code and make work with QEMU/KVM so I have the following questions. In an AMD64 setup where QEMU use VFIO to passthrough the VFs of an SR-IOV card to a guest will the consequences of a PF FLR

Re: [Qemu-devel] VFIO and scheduled SR-IOV cards

On 06/03/2013 02:02 PM, Alex Williamson wrote: On Mon, 2013-06-03 at 18:33 +0200, Benoît Canet wrote: Hello, I plan to write a PF driver for an SR-IOV card and make the VFs work with QEMU's VFIO passthrough so I am asking the following design question before trying to write and push code. Afte

Re: [Qemu-devel] [GIT PULL] Xen fixes and cleanups 20130603

Stefano Stabellini writes: > Anthony, > please pull the following changes since commit > 6a4e17711442849bf2cc731ccddef5a2a2d92d29: > > >

[Qemu-devel] [PULL 11/24] xilinx_spips: Fix striping behaviour

From: Peter Crosthwaite The QSPI controller was using byte-wide stripes when striping across the two flashes in dual parallel mode. The real hardware however uses individual bit striping. QEMU misbehaves in the (corner) case where data is written/read in dual-parallel mode and read/written back i

Re: [Qemu-devel] [PATCH trivial] acpi: actually require either data= or file= for -acpitable

On 06/03/13 14:42, Michael Tokarev wrote: > 03.06.2013 16:34, Eric Blake wrote: >> On 06/03/2013 03:20 AM, Michael Tokarev wrote: >>> Initially the code ensured that we have exactly one of data= or file= >>> option for -acpitable. But after some transformations, the condition >>> becomes >>> >>>

[Qemu-devel] Re: Boot guest OS on many nodes?

On Sunday, June 2, 2013 9:37:55 PM CDT, Steven.G wrote: Dear all, I've a scene, I have many host nodes with linux kernels, and I want to boot one guest OS on all these nodes use QEMU/KVM. In order that I can use all the physical CPUs and Mems distributed on these linux nodes, and the Guest looks

Re: [Qemu-devel] [PATCH] target-i386: Fix aflag logic for CODE64 and the 0x67 prefix

Applied. Thanks. Regards, Anthony Liguori

[Qemu-devel] [PULL 20/24] sd/sd.c: Fix "inquiry" ACMD41

From: Peter Crosthwaite QEMU models two (of the three) ACMD41 has two modes, "inquiry" and "first". The selection logic for which of the two is incorrect - it compares != 0 for the entire argument value rather than only bits 23:0 as per the spec. Fix. Signed-off-by: Peter Crosthwaite Message-id

Re: [Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

On Monday 03 June 2013 10:35:28 Jordan Justen wrote: > This should be fixed by Xiao's "fix double free the memslot in > kvm_set_phys_mem" patch. Confirmed, with this one-liner patch the bug is gone. > On Mon, Jun 3, 2013 at 10:23 AM, Peter Wu wrote: > > Hi, > > > > With the current git source (f

Re: [Qemu-devel] VFIO and scheduled SR-IOV cards

On Mon, 2013-06-03 at 18:33 +0200, Benoît Canet wrote: > Hello, > > I plan to write a PF driver for an SR-IOV card and make the VFs work with > QEMU's > VFIO passthrough so I am asking the following design question before trying to > write and push code. > > After SR-IOV being enabled on this ha

[Qemu-devel] [PULL 07/24] xilinx_spips: Add automatic start support

From: Peter Crosthwaite SPI has a mode where it automatically starts based on tx fifo occupancy. Implemented. Signed-off-by: Peter Crosthwaite Reviewed-by: Peter Maydell Reviewed-by: Edgar E. Iglesias Message-id: f4e9accb5de87b526fff6ed937f63278db76533b.1369117359.git.peter.crosthwa...@xilin

[Qemu-devel] [PULL 02/24] xilinx_spips: Make interrupts clear on read

From: Peter Crosthwaite By default these interrupts are clear on read. Signed-off-by: Peter Crosthwaite Reviewed-by: Peter Maydell Reviewed-by: Edgar E. Iglesias Message-id: 999ff0091ed3cc3969a431bf55c00ef934cecc8e.1369117359.git.peter.crosthwa...@xilinx.com Signed-off-by: Peter Maydell ---

[Qemu-devel] [PULL 22/24] hw/arm/exynos4210.c: convert chipid_and_omr to an mmio region

From: Igor Mitsyanko Exynos SoC was misusing memory_region_init_ram_ptr(): this interface can safely be used only for memory regions which size is a multiple of target page size. Change chipid_and_omr memory to an mmio region to fix this. Signed-off-by: Igor Mitsyanko Message-id: 1368199981-452

[Qemu-devel] [PULL 08/24] xilinx_spips: Implement automatic CS

From: Peter Crosthwaite Implement the automatic CS control feature. If the MANUAL_CS bit is cleared then the chip select stay de-asserted as long as the tx FIFO is empty. Signed-off-by: Peter Crosthwaite Reviewed-by: Peter Maydell Reviewed-by: Edgar E. Iglesias Message-id: 1d67383adc42761af7

[Qemu-devel] [PULL 17/24] sd/sdhci: Fix Buffer Write Ready interrupt

From: Peter Crosthwaite This interrupt is not risen after the last block is written to sd. It is mutually exclusive with the end of transfer conditions. Fix. Signed-off-by: Peter Crosthwaite Reviewed-by: Igor Mitsyanko Message-id: 7ca9fd3e03ce1bec94aff08f607c15a0ec3d3371.1369370934.git.peter.

[Qemu-devel] [PATCH v2] qemu-char: don't issue CHR_EVENT_OPEN in a BH

When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, and it was issued as a bottom-half: 86e94dea5b740dad65446c857f6959eae43e0ba6 Which we basically used to print out a greeting/prompt for the monitor. AFAICT the only reason this was ever done in a BH was because in some cases we'd m

[Qemu-devel] [PULL 21/24] i.MX: split GPT and EPIT timer implementation

From: Jean-Christophe DUBOIS There is no common code between these 2 timer implementation. So it is better to split them. Signed-off-by: Jean-Christophe DUBOIS Message-id: 1368990197-19694-1-git-send-email-...@tribudubois.net Signed-off-by: Peter Maydell --- hw/timer/Makefile.objs |3 +-

[Qemu-devel] [PULL 04/24] xilinx_spips: Add verbose LQSPI debug output

From: Peter Crosthwaite You really need this is you want to track a guest banging on LQSPI. Signed-off-by: Peter Crosthwaite Reviewed-by: Peter Maydell Reviewed-by: Edgar E. Iglesias Message-id: 26e508da4af11058d37daa777064c9e5c2a69abb.1369117359.git.peter.crosthwa...@xilinx.com Signed-off-b

[Qemu-devel] [PULL 05/24] xilinx_spips: Fix QSPI FIFO size

From: Peter Crosthwaite QSPI has a bigger FIFO than the regular SPI controller. Differentiate between the two with correct FIFO sizes for each. This is the first piece of class data for SPIPS, so this patch sees the creation of the XilinxSPIPSClass definition and assoicated QOM constructs. Sign

Re: [Qemu-devel] [GIT PULL] Trivial patches for 2013-06-01

Pulled. Thanks. Regards, Anthony Liguori

Re: [Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

This should be fixed by Xiao's "fix double free the memslot in kvm_set_phys_mem" patch. On Mon, Jun 3, 2013 at 10:23 AM, Peter Wu wrote: > Hi, > > With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e), > `qemu-system-x86_64 -enable-kvm` fails to run with the following error: > >

Re: [Qemu-devel] [PATCH 0/2] MAINTAINERS: QMP: entry update and new maintainers

On Mon, 03 Jun 2013 11:27:51 -0600 Eric Blake wrote: > On 06/03/2013 11:17 AM, Luiz Capitulino wrote: > > Hi, > > > > This is an small update on QMP/HMP/QAPI mainternership. Please, check > > individual patches for details. > > > > Luiz Capitulino (2): > > MAINTAINERS: new maintainers for qap

[Qemu-devel] [PULL 00/24] arm-devs queue

Hi; here's the latest arm-devs pullreq. I had a lot of cc'd mail to wade through putting this together so I wouldn't be surprised if I missed a patch somewhere; if so please ping the relevant patch. Please pull. thanks -- PMM The following changes since commit 8b779b368b3b45d5ed3160173499eeafee4

Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

On Mon, 03 Jun 2013 11:24:58 -0600 Eric Blake wrote: > On 06/03/2013 11:17 AM, Luiz Capitulino wrote: > > This entry doesn't reflect reality for a few years now. This commit > > splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped > > as a maintainer. > > > > This is what we have

Re: [Qemu-devel] [PATCH 0/2] MAINTAINERS: QMP: entry update and new maintainers

On 06/03/2013 11:17 AM, Luiz Capitulino wrote: > Hi, > > This is an small update on QMP/HMP/QAPI mainternership. Please, check > individual patches for details. > > Luiz Capitulino (2): > MAINTAINERS: new maintainers for qapi-schema.json > MAINTAINERS: split Monitor (QMP/HMP) entry Series: R

Re: [Qemu-devel] [PATCH v2] qemu-char: don't issue CHR_EVENT_OPEN in a BH

On Mon, Jun 03, 2013 at 12:17:00PM -0500, Anthony Liguori wrote: > Michael Roth writes: > > > When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, > > and it was issued as a bottom-half: > > > > 86e94dea5b740dad65446c857f6959eae43e0ba6 > > > > Which we basically used to print out a gr

[Qemu-devel] [PULL 03/24] xilinx_spips: Inhibit interrupts in LQSPI mode

From: Peter Crosthwaite The real hardware does not produce interrupts in LQSPI mode. Inhibit generation of interrupts when the LQ_MODE bit is set. Signed-off-by: Peter Crosthwaite Reviewed-by: Peter Maydell Reviewed-by: Edgar E. Iglesias Message-id: dff794a06872009ea7e5733ce6adcff94d18bbd0.1

Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

On 06/03/2013 11:17 AM, Luiz Capitulino wrote: > This entry doesn't reflect reality for a few years now. This commit > splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped > as a maintainer. > > This is what we have been for the last few years. Also, it's going > to help me to offlo

[Qemu-devel] QEMU aborts since "kvm: support using KVM_MEM_READONLY flag for regions"

Hi, With the current git source (f10acc8b38d65a66ffa0588a036489d7fa6a593e), `qemu-system-x86_64 -enable-kvm` fails to run with the following error: kvm_set_phys_mem: error unregistering overlapping slot: Invalid argument After this message, qemu aborts. Reverting the following commit on top

Re: [Qemu-devel] [PATCH v5 09/11] blockdev: add DriveBackup transaction

On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote: > This patch adds a transactional version of the drive-backup QMP command. > It allows atomic snapshots of multiple drives along with automatic > cleanup if there is a failure to start one of the backup jobs. > > Note that QMP events are emitted for b

[Qemu-devel] [PATCH 2/2] MAINTAINERS: split Monitor (QMP/HMP) entry

This entry doesn't reflect reality for a few years now. This commit splits it into Human Monitor (HMP), QAPI and QMP. Markus is dropped as a maintainer. This is what we have been for the last few years. Also, it's going to help me to offload some of this work to someone else in the near future. S

[Qemu-devel] [Bug 1186935] Re: [1.5] QEMU monitor gets overlapped by GTK menu bar

gtk 3.8.2 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1186935 Title: [1.5] QEMU monitor gets overlapped by GTK menu bar Status in QEMU: New Bug description: The QEMU minitor gets partially

Re: [Qemu-devel] [PATCH 0/2] configure: improve handling of target lists

On 20 May 2013 16:16, Peter Maydell wrote: > These patches clean up configure's handling of the list of known > targets. Firstly we autogenerate the default list based on the > set of default-config files; this reduces by 1 the number of > places that need editing when a new target is added to QEM

Re: [Qemu-devel] [PATCH v2] qemu-char: don't issue CHR_EVENT_OPEN in a BH

Michael Roth writes: > When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, > and it was issued as a bottom-half: > > 86e94dea5b740dad65446c857f6959eae43e0ba6 > > Which we basically used to print out a greeting/prompt for the > monitor. > > AFAICT the only reason this was ever done in

[Qemu-devel] [PATCH 0/2] MAINTAINERS: QMP: entry update and new maintainers

Hi, This is an small update on QMP/HMP/QAPI mainternership. Please, check individual patches for details. Luiz Capitulino (2): MAINTAINERS: new maintainers for qapi-schema.json MAINTAINERS: split Monitor (QMP/HMP) entry MAINTAINERS | 24 ++-- 1 file changed, 22 insertion

[Qemu-devel] [PATCH 1/2] MAINTAINERS: new maintainers for qapi-schema.json

I'm facing two problems lately wrt QMP patch review: increasingly lack of bandwidth and lack of background in so many different areas that are getting new QMP commands almost every week. In order to help me mitigate this problem, I'm adding Eric and Markus (besides me) as maintainers of the qapi-s

Re: [Qemu-devel] [PATCH v5 05/11] blockdev: use bdrv_getlength() in qmp_drive_mirror()

On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote: > Use bdrv_getlength() for its byte units and error return instead of > bdrv_get_geometry(). > > Reported-by: Kevin Wolf > Signed-off-by: Stefan Hajnoczi > --- > blockdev.c | 10 +++--- > 1 file changed, 7 insertions(+), 3 deletions(-) Reviewe

Re: [Qemu-devel] [PATCH v5 04/11] blockdev: drop redundant proto_drv check

On 05/30/2013 06:34 AM, Stefan Hajnoczi wrote: > It is not necessary to check that we can find a protocol block driver > since we create or open the image file. This produces the error that we > need anyway. > > Besides, the QERR_INVALID_BLOCK_FORMAT is inappropriate since the > protocol is incor

  1   2   3   >