On 2014/11/10 15:50, Hannes Reinecke wrote:
> On 11/10/2014 08:39 AM, Gonglei wrote:
>> On 2014/11/10 15:02, Hannes Reinecke wrote:
>>
>>> On 11/09/2014 10:44 AM, Mark Cave-Ayland wrote:
On 07/11/14 12:22, Hannes Reinecke wrote:
> A linux guest will be issuing messages:
>
> [
On 11/10/2014 08:39 AM, Gonglei wrote:
> On 2014/11/10 15:02, Hannes Reinecke wrote:
>
>> On 11/09/2014 10:44 AM, Mark Cave-Ayland wrote:
>>> On 07/11/14 12:22, Hannes Reinecke wrote:
>>>
A linux guest will be issuing messages:
[ 32.124042] DC390: Deadlock in DataIn_0: DMA aborted
On 2014/11/10 15:02, Hannes Reinecke wrote:
> On 11/09/2014 10:44 AM, Mark Cave-Ayland wrote:
>> On 07/11/14 12:22, Hannes Reinecke wrote:
>>
>>> A linux guest will be issuing messages:
>>>
>>> [ 32.124042] DC390: Deadlock in DataIn_0: DMA aborted unfinished: 00
>>> bytes remain!!
>>> [ 3
> -Origin email-
> From: Peter Maydell
> Sent Time: Friday, November 7, 2014
> To: Kaiyuan
> Cc: QEMU Developers
> Subject: Re: [Qemu-devel] What "opaque" stand for?
>
> On 7 November 2014 14:42, Kaiyuan wrote:
> >
> > Hello, all
> >
> > I am reviewing source of Qemu. I can see parame
In bdrv_rw_co we report -EINVAL for nb_sectors > INT_MAX /
BDRV_SECTOR_SIZE, so a caller shouldn't exceed it.
Signed-off-by: Fam Zheng
---
block.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block.c b/block.c
index dacd881..5513379 100644
--- a/block.c
+++ b/block.c
@
On 11/09/2014 10:44 AM, Mark Cave-Ayland wrote:
> On 07/11/14 12:22, Hannes Reinecke wrote:
>
>> A linux guest will be issuing messages:
>>
>> [ 32.124042] DC390: Deadlock in DataIn_0: DMA aborted unfinished: 00
>> bytes remain!!
>> [ 32.126348] DC390: DataIn_0: DMA State: 0
>>
>> and the
On Fri, Oct 03, 2014 at 06:47:39PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Rework the migration thread to setup and start postcopy.
>
> Signed-off-by: Dr. David Alan Gilbert
> ---
> include/migration/migration.h | 3 +
> migration.c |
On Fri, Oct 03, 2014 at 06:47:42PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> On receiving MIG_RPCOMM_REQPAGES look up the address and
> queue the page.
>
> Signed-off-by: Dr. David Alan Gilbert
> ---
> arch_init.c | 52
>
On Fri, Oct 03, 2014 at 06:47:40PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
This could do with a bit more rationale in the commit message.
Also is there a reason not to fold this with the patch originally
marking the RAM as userfault? IIRC that one wasn't part
On Fri, Oct 03, 2014 at 06:47:41PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Add MIG_RPCOMM_REQPAGES command on Return path for the postcopy
> destination to request a page from the source.
>
> Signed-off-by: Dr. David Alan Gilbert
> ---
> include/migratio
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
This patch is used together with the patches in K
VT-d Posted-Interrupts(PI) is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
involvement when guest is running in non-root mode.
If VT-d PI is supported by KVM, we need to upd
On Mon, Nov 10, 2014 at 02:54:49PM +0900, SeokYeon Hwang wrote:
> Added 'assert(os_errno > 0)' in 'error_set_errno()'.
> Fixed errno since it passes wrong value to 'error_set_errno()'.
>
> Signed-off-by: SeokYeon Hwang
Reviewed-by: Amos Kong
> ---
> hw/pci/pcie.c | 2 +-
> util/error.c | 1 +
On 2014/11/9 2:47, MikeFrysinger wrote:
> the problem is this commit:
> http://git.qemu.org/?p=qemu.git;a=commit;h=b791c3b38c7969cb9f4acda8229e19fd865a1c08
>
> it's easy to reproduce -- plug in a USB flash drive and try to pass it
> through
>
What's your USB flash drive's version? USB1.1 or USB
> -Original Message-
> From: Markus Armbruster [mailto:arm...@redhat.com]
> Sent: Friday, November 07, 2014 4:41 PM
> To: Amos Kong
> Cc: SeokYeon Hwang; mre...@redhat.com; paolo.bonz...@gmail.com; qemu-
> de...@nongnu.org
> Subject: Re: [Qemu-devel] [PATCH v2] error: passing a negative val
Added 'assert(os_errno > 0)' in 'error_set_errno()'.
Fixed errno since it passes wrong value to 'error_set_errno()'.
Signed-off-by: SeokYeon Hwang
---
hw/pci/pcie.c | 2 +-
util/error.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
index 5845
Hi, all
bdrv_co_flush() will flush all cached data to persistent storage, and I'm
wondering whether guest sync() will eventually trigger bdrv_co_flush() be
called.
Intuitively, guest sync() should trigger bdrv_co_flush() in qemu. But simple
grep gave me a negative answer. So I'm wondering why
Hi, all
bdrv_co_flush() will flush all cached data to persistent storage, and I'm
wondering whether guest sync() will eventually trigger bdrv_co_flush() be
called.
Intuitively, guest sync() should trigger bdrv_co_flush() in qemu. But simple
grep gave me a negative answer. So I'm wondering why
Igor Mammedov wrote on 2014-05-23:
> if user starts QEMU with "-machine pc,accel=xen", then compat property
> in xenfv won't work and it would cause error:
> "Unsupported bus. Bus doesn't have property 'acpi-pcihp-bsel' set"
> when PCI device is added with -device on QEMU CLI.
>
> In case of Xen i
Hi Andreas
Thanks a lot for your patients. Because I'm a newer to this , I'll
follow your advices and pay much more attention to these details.
Besides ,I have replied to Thomas' question on my previous submission.
Thanks again for your help.
Best regards
Guo lei
Re: [Qemu-deve
Hi, all
bdrv_co_flush() will flush all cached data to persistent storage, and I'm
wondering whether guest sync() will eventually trigger bdrv_co_flush() be
called.
Intuitively, guest sync() should trigger bdrv_co_flush() in qemu. But simple
grep gave me a negative answer. So I'm wondering why
hello
Hi Laurent
This pagraph exactly is a cut&paste of the Motorola "Programmer's
reference manual".
I didn't mean to add it as commits to the patch.I just want to introduce this
instruction to the reviewer.
So don't worry about the copyrights.
Best Regards
Guo Lei
>
>
>
> > Le 7 novembr
Hi,
Is there a way for passing a parameter directly to a module (i.e. device driver
within QEMU), for example file path (when I am working at Full system
emulation)?
My goal is to have a device emulation which will be able to read a
configuration file that its name is provided in runtime.
Than
On 09/11/14 16:42, Peter Maydell wrote:
> On 9 November 2014 09:43, Mark Cave-Ayland
> wrote:
>> On 05/11/14 15:32, Peter Maydell wrote:
>>> Please make sure you update the changelog at
>>> http://wiki.qemu.org/ChangeLog/2.2 with any interesting/important
>>> new features that got added in this r
On 9 November 2014 09:43, Mark Cave-Ayland
wrote:
> On 05/11/14 15:32, Peter Maydell wrote:
>> Please make sure you update the changelog at
>> http://wiki.qemu.org/ChangeLog/2.2 with any interesting/important
>> new features that got added in this release.
>
> I don't have a wiki account, but I th
It isn't necessery to notify guest each time when one request
is completed, and it should be enough to just notify one time
for each running of virtio_scsi_iothread_handle_cmd().
This patch supresses about 30K/sec write on eventfd.
Signed-off-by: Ming Lei
---
hw/scsi/virtio-scsi-dataplane.c |
The size of each element should be sizeof(VirtIOSCSIVring *).
Signed-off-by: Ming Lei
---
hw/scsi/virtio-scsi-dataplane.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/scsi/virtio-scsi-dataplane.c b/hw/scsi/virtio-scsi-dataplane.c
index 855439e..8a7cd9f 100644
--- a/h
The 1st patch fixes an allocation problem.
The 2nd one supresses writing eventfd a lot(~30K/sec in my test).
Thanks,
Ming Lei
Thanks Todd - the recommended fix did work. Thanks Rob, I downloaded and
used your qemu-img binary, and it worked perfectly :-)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1354167
Title:
On VM re
At present, I use simplified sshd, ssh and scp (dropbear open source
program) to communicate with microblaze qemu successfully, and let gcc
'make check' have real effect. It is just testing (may run a week!!).
So we can say, the related environments construction based on qemu is
finished. This th
On 07/11/14 12:22, Hannes Reinecke wrote:
> A linux guest will be issuing messages:
>
> [ 32.124042] DC390: Deadlock in DataIn_0: DMA aborted unfinished: 00
> bytes remain!!
> [ 32.126348] DC390: DataIn_0: DMA State: 0
>
> and the HBA will fail to work properly.
> Reason is the emulatio
On 05/11/14 15:32, Peter Maydell wrote:
> Hi; I've just tagged v2.2.0-rc0 in master, so we're now officially
> in hardfreeze, and only accepting bug fixes from here onward.
> Mike Roth should have the rc0 tarballs out sometime later today.
>
> I've updated http://wiki.qemu.org/Planning/2.2 to lis
On 06/11/14 18:23, Artyom Tarasenko wrote:
>> Could you please explain it with some more details? I don't really know how
>> to do that (yet)...
>> We are really interested in such a support for Sparc64, so I think that it
>> would be for sun4u machines only.
>> Would the changes would be the same
34 matches
Mail list logo
