[Qemu-devel] [Bug 1392504] Re: libvirt not relabeling devices on USB Passthrough

Actually I was talking about just libvirt. cmment #23 (and 24) suggests that the problem is libvirt not re-labeling the devices, so i'm wondering whether 1.2.12 fixes it. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.l

[Qemu-devel] [PATCH] replaced get_ticks_per_sec() with constant

This replaces all calls to get_ticks_per_sec() with NSEC_PER_SEC defined in /include/qemu/timer.h Signed-off-by: Emil Condrea --- audio/audio.c | 2 +- audio/noaudio.c| 4 ++-- audio/spiceaudio.c | 2 +- audio/wavaudio.c | 2 +- backends/baum.c

Re: [Qemu-devel] [Qemu-discuss] error - Guest has not initialized the display yet.

On 26/03/15 21:00, Paolo Bonzini wrote: > On 26/03/2015 21:55, Peter Maydell wrote: >> I feel like we're recapitulating history here -- is >> c3c1bb99d undoing the fix that a87f39543a made for when we >> tried this a year ago in 360e607, or is there something >> more subtle going on ? > > It's mo

Re: [Qemu-devel] ppc vga output breakage since commit c3c1bb99

On 28/03/15 19:04, BALATON Zoltan wrote: > Hello, > > Commit c3c1bb99d1c11978d9ce94d1bdcf0705378c1459 (exec: Respect > as_tranlsate_internal length clamp) seems to break vga output with > qemu-system-ppc on x86_64 host. Since this commit, the output window > does not get to the OpenBIOS console b

Re: [Qemu-devel] [PATCH 10/22] ram_addr: tweaks to xen_modified_memory

On Thu, 26 Mar 2015, Paolo Bonzini wrote: > Invoke xen_modified_memory from cpu_physical_memory_set_dirty_range_nocode; > it is akin to DIRTY_MEMORY_MIGRATION, so set it together with that bitmap. > The remaining call from invalidate_and_set_dirty's "else" branch will go > away soon. > > Second, f

[Qemu-devel] ppc vga output breakage since commit c3c1bb99

Hello, Commit c3c1bb99d1c11978d9ce94d1bdcf0705378c1459 (exec: Respect as_tranlsate_internal length clamp) seems to break vga output with qemu-system-ppc on x86_64 host. Since this commit, the output window does not get to the OpenBIOS console but stays black. (Easy to reproduce by just starti

Re: [Qemu-devel] [PATCH 02/22] acpi-build: remove dependency from ram_addr.h

On Thu, Mar 26, 2015 at 06:38:20PM +0100, Paolo Bonzini wrote: > ram_addr_t is an internal interface, everyone should go through > MemoryRegion. Clean it up by making rom_add_blob return a > MemoryRegion* and using the new qemu_ram_resize infrastructure. > > Cc: Michael S. Tsirkin > Signed-off-b

Re: [Qemu-devel] [PATCH 01/22] memory: add memory_region_ram_resize

On Thu, Mar 26, 2015 at 06:38:19PM +0100, Paolo Bonzini wrote: > This is a simple MemoryRegion wrapper for qemu_ram_resize. > > Cc: Michael S. Tsirkin > Signed-off-by: Paolo Bonzini > --- > include/exec/memory.h | 12 > memory.c | 7 +++ > 2 files changed, 19 inse

Re: [Qemu-devel] [PATCH 05/22] memory: return bitmap from memory_region_is_logging

On Thu, Mar 26, 2015 at 06:38:23PM +0100, Paolo Bonzini wrote: > For now it only returns (1 << DIRTY_MEMORY_VGA) or 0, but this > will change soon so adjust the callers. > > Listeners check for "any bit except migration", which is handled > via the global start/stop listener callbacks. This in pr

Re: [Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

Am 28.03.2015 um 17:07 schrieb Waldemar Brodkorb: Fixes following problem, when trying to boot linux: qemu: hardware error: mcf_intc_write: Bad write offset 28 CPU #0: D0 = 00ff A0 = 402ea5dc F0 = ( 0) D1 = 0004 A1 = 402ea5e0 F1 = (

[Qemu-devel] [RFC] acpi: add reset register to fadt

Some operating systems such as FreeBSD and Mac OSX need the reset_register section of the FADT filled to know which port to write to for a system reset. What is the right way to set the reset_val and the reset addr in this case? --- hw/i386/acpi-build.c | 5 + hw/i386/acpi-defs.h | 2 ++ 2 f

[Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

Fixes following problem, when trying to boot linux: qemu: hardware error: mcf_intc_write: Bad write offset 28 CPU #0: D0 = 00ff A0 = 402ea5dc F0 = ( 0) D1 = 0004 A1 = 402ea5e0 F1 = ( 0) D2 = 0040 A2 = 40040752 F2 = 0

Re: [Qemu-devel] [PATCH v5 17/45] Add wrappers and handlers for sending/receiving the postcopy-ram migration messages.

On 27/03/2015 11:48, Dr. David Alan Gilbert wrote: > > So, I like the idea of one message per action in principle - but only > > if that action really is well-defined without reference to what > > operations come before and after it. If there are hidden dependencies > > about what actions have t

Re: [Qemu-devel] [PATCH v5 17/45] Add wrappers and handlers for sending/receiving the postcopy-ram migration messages.

On 27/03/2015 05:13, David Gibson wrote: >> It's a state variable tested and changed by at least two threads >> and it's got to go through a correct sequence of states. So >> generally you're doing a 'I expect to be in now change to >> ' so the exchange works well for that. > > So.. in

Re: [Qemu-devel] [PATCH v5 17/45] Add wrappers and handlers for sending/receiving the postcopy-ram migration messages.

On 25/02/2015 17:51, Dr. David Alan Gilbert (git) wrote: > +PostcopyState postcopy_state_get(MigrationIncomingState *mis) > +{ > +return atomic_fetch_add(&mis->postcopy_state, 0); > +} > + > +/* Set the state and return the old state */ > +PostcopyState postcopy_state_set(MigrationIncomingSt

Re: [Qemu-devel] [PATCH v5 11/45] Return path: Send responses from destination to source

On 10/03/2015 06:47, David Gibson wrote: >> > +void migrate_send_rp_message(MigrationIncomingState *mis, >> > + enum mig_rpcomm_cmd cmd, >> > + uint16_t len, uint8_t *data) > Using (void *) for data would avoid casts in a bunch of the caller

Re: [Qemu-devel] [PATCH v5 10/45] Return path: Control commands

On 25/02/2015 17:51, Dr. David Alan Gilbert (git) wrote: > > Add two src->dest commands: >* OPEN_RETURN_PATH - To request that the destination open the return path >* SEND_PING - Request an acknowledge from the destination It's just PING, not SEND_PING. Paolo

Re: [Qemu-devel] [PATCH v5 08/45] Return path: socket_writev_buffer: Block even on non-blocking fd's

On 25/02/2015 17:51, Dr. David Alan Gilbert (git) wrote: > +if (err != EAGAIN) { if (err != EAGAIN && err != EWOULDBLOCK) Paolo

Re: [Qemu-devel] [Qemu-discuss] error - Guest has not initialized the display yet.

On Mar 26, 2015, at 4:31 PM, Mark Cave-Ayland wrote: > On 25/03/15 23:52, Programmingkid wrote: > > (Added Peter C as CC) > >> On Mar 25, 2015, at 6:20 PM, qemu-discuss-requ...@nongnu.org >> wrote: >> QEMU window opens up, but I am getting this err

Re: [Qemu-devel] [PATCH 3/3] arm: semihosting: Wire up A64 HLT 0xf000

Hi Peter, On Fri, Mar 27, 2015 at 12:40 PM, Peter Maydell wrote: > On 27 March 2015 at 16:22, Christopher Covington > wrote: >> In AArch64, Angel semihosting uses HLT instructions with a special >> immediate value, 0xf000. Use a new exception type EXCP_SEMI for this, >> since I'm not aware of pl

Re: [Qemu-devel] [Migration Bug? ] Occasionally, the content of VM's memory is inconsistent between Source and Destination of migration

On 2015/3/27 18:18, Dr. David Alan Gilbert wrote: * zhanghailiang (zhang.zhanghaili...@huawei.com) wrote: On 2015/3/26 11:52, Li Zhijian wrote: On 03/26/2015 11:12 AM, Wen Congyang wrote: On 03/25/2015 05:50 PM, Juan Quintela wrote: zhanghailiang wrote: Hi all, We found that, sometimes, th

Re: [Qemu-devel] [PATCH v2] microblaze: fix memory leak

On 2015/3/28 15:31, Edgar E. Iglesias wrote: > On 28/03/2015 12:38 pm, "Gonglei" wrote: >> >> Hi, >> >>Ping again... Can this patch be a raw stuff for rc2 ? > > Looks good to me, thanks. > > Reviewed-by: Edgar E. Iglesias > Thanks :) > Can this go through -trivial? > It's ok, but I don't

Re: [Qemu-devel] [PATCH v2] microblaze: fix memory leak

On 28/03/2015 12:38 pm, "Gonglei" wrote: > > Hi, > >Ping again... Can this patch be a raw stuff for rc2 ? Looks good to me, thanks. Reviewed-by: Edgar E. Iglesias Can this go through -trivial? Cheers, Edgar > > Regards, > Gonglei > > On 2015/3/17 15:15, Gonglei wrote: > > On 2015/3/5 11