Hello!
> FWIW virt-manager 1.2.0 (just released) will do the following when creating a
> new VM:
>
> - aarch64 + kvm : -cpu host
> - aarch64 + tcg : -cpu cortex-a57
> - arm32 + kvm : -cpu host
> - arm32 + tcg : defer to qemu
>
> Though if you explicitly request 'hypervisor default' then we won'
On Mon, May 04, 2015 at 11:27:36AM +0200, Paolo Bonzini wrote:
>
>
> On 04/05/2015 05:18, Edgar E. Iglesias wrote:
> > From: "Edgar E. Iglesias"
> >
> > Signed-off-by: Edgar E. Iglesias
> > ---
> > hw/core/ptimer.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git
On 05/07/2015 05:21 PM, Nikunj A Dadhania wrote:
Each hardware instance has a platform unique location code. The OF
device tree that describes a part of a hardware entity must include
the “ibm,loc-code” property with a value that represents the location
code for that hardware entity.
Populate i
On Fri, May 8, 2015 at 12:14 AM, Pavel Fedin wrote:
> Hello!
>
>> FWIW virt-manager 1.2.0 (just released) will do the following when creating a
>> new VM:
>>
>> - aarch64 + kvm : -cpu host
>> - aarch64 + tcg : -cpu cortex-a57
>> - arm32 + kvm : -cpu host
>> - arm32 + tcg : defer to qemu
>>
>> Tho
Paolo Bonzini wrote:
> On 07/05/2015 18:46, Juan Quintela wrote:
>> static CompressParam *comp_param;
>> static QemuThread *compress_threads;
>> +/* comp_done_cond is used to wake up the migration thread when
>> + * one of the compression threads has finished the compression.
>> + * comp_done_lo
On 08/05/2015 08:45, Markus Armbruster wrote:
>> Luckily, most common error values are more or less universal: in
>> particular, of all errno values <= 34 (up to ERANGE), they are all
>> the same on supported platforms except for 11 (which is EAGAIN on
>> Windows and Linux, but EDEADLK on Darwin
On 2015/5/8 0:09, Peter Maydell wrote:
> On 7 May 2015 at 10:29, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> Expose the needed device information to the table generation
>> insfrastructure and register a machine_init_done notify to
>
> "infrastructure".
>
>> call virt_acpi_build().
>>
>> Ad
This is an alternative version of:
https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00945.html. Code
merged with
original "virt" implementation.
I decided to stick to different machine name instead of adding an option
because of
compatibility with libvirt. In order to make use of a new
On 08/05/2015 09:14, Pavel Fedin wrote:
> Hello!
>
>> FWIW virt-manager 1.2.0 (just released) will do the following when creating a
>> new VM:
>>
>> - aarch64 + kvm : -cpu host
>> - aarch64 + tcg : -cpu cortex-a57
>> - arm32 + kvm : -cpu host
>> - arm32 + tcg : defer to qemu
>>
>> Though if you
On Tue, May 05, 2015 at 04:23:56PM +0100, Dr. David Alan Gilbert wrote:
> * Stefan Hajnoczi (stefa...@redhat.com) wrote:
> > On Fri, Apr 24, 2015 at 11:36:35AM +0200, Paolo Bonzini wrote:
> > >
> > >
> > > On 24/04/2015 11:38, Wen Congyang wrote:
> > > >> >
> > > >> > That can be done with drive
Hello!
> Ignoring legacy, the ideal naming scheme would be:
>
> qemu-system-arm
> aarch64-linux-user
> aarch32-linux-user
You know, i rethought. Actually, the question concerns only "virt" machine,
because for other real machines the CPU should be the same as on real HW, and
this is no quest
On Thu, May 07, 2015 at 02:43:43PM +0100, Stefan Hajnoczi wrote:
> On Wed, May 06, 2015 at 07:23:32PM +0800, Fam Zheng wrote:
> > Reported by Paolo.
> >
> > Unlike the iohandler in main loop, iothreads currently process the event
> > notifier used as virtio-blk ioeventfd in all nested aio_poll. Th
On Fri 24 Apr 2015 03:04:06 PM CEST, Kevin Wolf wrote:
>> >> I think it would be nice to have a way to free unused cache
>> >> entries after a while.
>> >
>> > Do you think mmap plus a periodic timer would work?
>> >
>> > I'm hesitant about changes like this because they make QEMU more
>> > compl
The following changes since commit f8340b360b9bc29d48716ba8aca79df2b9544979:
hw/ptimer: Do not artificially limit timers when using icount (2015-05-08
17:15:23 +1000)
are available in the git repository at:
git://github.com/cohuck/qemu tags/s390x-20150508
for you to fetch changes up to
We used to avoid enabling event_idx for virtio-blk devices via
s390-virtio, but we now have a workaround in place for guests trying
to use the device before setting DRIVER_OK. Therefore, let's add
DEFINE_VIRTIO_COMMON_FEATURES to the base device so all devices get
those common features - and make s
From: Christian Borntraeger
Feature updates are not a synchronuous operation for the legacy
s390-virtio transport. This transport syncs the guest feature bits
(those from finalize) on the set_status hypercall. Before that qemu
thinks that features are zero, which means QEMU will misbehave, e.g.
i
From: Jens Freimann
KVM_S390_INT uses only two parameter fields. This is not
enough to pass all required information for certain interrupts.
A new ioctl KVM_S390_IRQ is available which allows us to
inject all local interrupts as defined in the Principles of
Operation. It takes a struct kvm_s390_
From: Christian Borntraeger
The old s390-virtio transport clears the vring used/avail indices in
the shared area on reset. When we enabled event_idx for virtio-blk, we
noticed that this is not enough: We also need to clear the published
used/avail event indices, or reboot will fail.
Signed-off-b
virtio-ccw has an odd sequence of realizing devices: first the
device-specific relization (net, block, ...), then the generic
realization. It feels less odd to have the generic realization
callback trigger the device-specific realization instead (and this
also matches what virtio-pci does).
One th
From: Jens Freimann
This patch adds support to migrate vcpu interrupts.
We use ioctl KVM_S390_GET_IRQ_STATE and _SET_IRQ_STATE
to get/set the complete interrupt state for a vcpu.
Reviewed-by: David Hildenbrand
Signed-off-by: Jens Freimann
Signed-off-by: Cornelia Huck
---
target-s390x/cpu-qom
Let's move operations that are only valid after the backend has been
realized to a ->device_plugged callback, just as virtio-pci does.
Also reorder setting up the host feature bits to the sequence used
by virtio-pci.
While we're at it, also add a ->device_unplugged callback to stop
ioeventfd, just
Block replication is a very important feature which is used for
continuous checkpoints(for example: COLO).
Usage:
Please refer to docs/block-replication.txt
You can get the patch here:
https://github.com/wencongyang/qemu-colo/commits/block-replication-v4
You can get the patch with the other COLO
From: David Hildenbrand
Let's move the floating point registers into a seperate subsection and
bump up the version id. This cleans up the current vmstate and will
allow for a future extension with vector registers in a compatible way.
This patch is based on a patch from Eric Farman.
Reviewed-by
Usage:
-drive file=xxx,id=Y, \
-drive
file=,id=X,backing_reference.drive_id=Y,backing_reference.hidden-disk.*
It will create such backing chain:
{virtio-blk dev 'Y'}
{virtio-blk dev 'X'}
|
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
docs/block-replication.txt | 179 +
1 file changed, 179 insertions(+)
create mode 100644 docs/block-replication.txt
diff --git a/docs/b
In some cases, we want to connect/disconnect the remote target when
we need, not in bdrv_open()/bdrv_close().
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block.c | 24
include/block/block.h | 3 +++
include
When opening BDS, we need to create backup jobs for
image-fleecing.
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Cc: Jeff Cody
---
block/Makefile.objs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/Makefile.objs b/block/Makefile.ob
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
blockdev.c| 8
include/block/block.h | 1 +
qemu-options.hx | 4
3 files changed, 13 insertions(+)
diff --git a/blockdev.c b/blockdev.c
index 5eaf77e..6839c8f 100644
--- a/blockd
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block.c | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/block.c b/block.c
index 49d472f..8fa4f05 100644
--- a/block.c
+++ b/block.c
@@ -1051,6 +1051,20 @@ out:
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Cc: Luiz Capitulino
Cc: Michael Roth
Reviewed-by: Paolo Bonzini
---
block.c | 40
include/block/block.h | 5 +
include/block/block_int.h | 14 ++
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/block.c b/block.c
index 35e1a95..15d21da 100644
--- a/block.c
+++ b/block.c
@@ -1204,6 +1204,14 @@ static int
bdrv_open_backing_reference_fil
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block/nbd.c | 65 -
1 file changed, 47 insertions(+), 18 deletions(-)
diff --git a/block/nbd.c b/block/nbd.c
index 2176186..0624232 100644
--- a/block
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Cc: Jeff Cody
---
block/backup.c | 13 +
blockjob.c | 10 ++
include/block/blockjob.h | 12
3 files changed, 35 insertions(+)
diff --git a/block/backup.c b/
If the child is not ready, read/write/getlength/flush will
return -errno. It is not critical error, and can be ignored:
1. read/write:
Just not report the error event.
2. getlength:
just ignore it. If all children's getlength return -errno,
and be ignored, return -EIO.
3. flush:
Just ig
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block.c | 12
1 file changed, 12 insertions(+)
diff --git a/block.c b/block.c
index 54d5b29..a442b5f 100644
--- a/block.c
+++ b/block.c
@@ -4219,6 +4219,10 @@ void bdrv_start_replication(BlockDrive
The secondary qemu starts later than the primary qemu, so we
cannot connect to nbd server in bdrv_open(). Introduce a new
open flags to control it.
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block/nbd.c | 10 ++
1 file changed, 6 insertions(+),
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block/quorum.c | 78 ++
1 file changed, 78 insertions(+)
diff --git a/block/quorum.c b/block/quorum.c
index f91ef75..e3c2e46 100644
--- a/block/quorum.c
+
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
---
block/Makefile.objs | 1 +
block/replication.c | 512
2 files changed, 513 insertions(+)
create mode 100644 block/replication.c
diff --git a/block/Makefil
On Fri, 17 Apr 2015 09:52:37 +0200
Cornelia Huck wrote:
> From: Xu Wang
>
> A new sysbus device for diag288 watchdog, it monitors the kvm guest
> status, and take corresponding actions when it detects that the guest
> is not responding.
>
> Signed-off-by: Xu Wang
> Reviewed-by: David Hildenbr
On Thu, May 07, 2015 at 11:40:50PM +0530, Amit Shah wrote:
> On (Thu) 07 May 2015 [13:45:26], Peter Maydell wrote:
> > On 7 May 2015 at 12:50, Juan Quintela wrote:
> > >
> > >
> > > Hi again
> > >
> > > For v2
> > >
> > > - fix 32bit compilation (as said, compiling for 64bit linux, 64bit
> > > w
Paolo Bonzini writes:
> On 08/05/2015 08:45, Markus Armbruster wrote:
>>> Luckily, most common error values are more or less universal: in
>>> particular, of all errno values <= 34 (up to ERANGE), they are all
>>> the same on supported platforms except for 11 (which is EAGAIN on
>>> Windows and L
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> On Tue, May 05, 2015 at 04:23:56PM +0100, Dr. David Alan Gilbert wrote:
> > * Stefan Hajnoczi (stefa...@redhat.com) wrote:
> > > On Fri, Apr 24, 2015 at 11:36:35AM +0200, Paolo Bonzini wrote:
> > > >
> > > >
> > > > On 24/04/2015 11:38, Wen Congyan
Looking at the output of "qemu-system-xxx -help", you easily get
the impression that "-net" is the preferred way instead of "-netdev"
to specify host network interface, since the "-net" option is
omnipresent but the "-netdev" option is only listed as a one-liner
at the end. This is ugly since "-net
Am 08.05.2015 um 10:42 hat Stefan Hajnoczi geschrieben:
> On Tue, May 05, 2015 at 04:23:56PM +0100, Dr. David Alan Gilbert wrote:
> > * Stefan Hajnoczi (stefa...@redhat.com) wrote:
> > > On Fri, Apr 24, 2015 at 11:36:35AM +0200, Paolo Bonzini wrote:
> > > >
> > > >
> > > > On 24/04/2015 11:38, We
On 08/05/2015 11:32, Markus Armbruster wrote:
+/* NBD errors are based on errno numbers, so there is a 1:1 mapping,
+ * but only a limited set of errno values is specified in the protocol.
+ * Everything else is squashed to EINVAL.
+ */
>>>
>>> Is the protocol defined anywhere
Am 08.05.2015 um 11:00 hat Alberto Garcia geschrieben:
> On Fri 24 Apr 2015 03:04:06 PM CEST, Kevin Wolf wrote:
>
> >> >> I think it would be nice to have a way to free unused cache
> >> >> entries after a while.
> >> >
> >> > Do you think mmap plus a periodic timer would work?
> >> >
> >> > I'm
Hi Peter,
On 2015/5/8 0:34, Peter Maydell wrote:
> Hi. I've had a look through these patches now, and sent some mails
> for a couple of specific issues. For the rest, this is what I'd
> like to see for me to pull this in to target-arm:
>
Thanks for your review comments.
> (1) acks or reviewed-b
Right now, NBD includes potentially platform-specific error values in
the wire protocol.
Luckily, most common error values are more or less universal: in
particular, of all errno values <= 34 (up to ERANGE), they are all the
same on supported platforms except for 11 (which is EAGAIN on Windows and
This patch changes the way cpu_index is handed out to newly created
CPUs by tracking the allocted CPUs in a bitmap. More information and
the need for this patch is described in patch 2/3 of this series. These
generic changes are needed to support CPU hot plug/unplug on PowerPC.
cpu_index is alloca
Add an Error argument to cpu_exec_init() to let users collect the
error. Change all callers to currently pass NULL error argument. This change
is needed for the following reasons:
- A subsequent commit changes the CPU enumeration logic in cpu_exec_init()
resulting in cpu_exec_init() to fail if c
Currently CPUState.cpu_index is monotonically increasing and a newly
created CPU always gets the next higher index. The next available
index is calculated by counting the existing number of CPUs. This is
fine as long as we only add CPUs, but there are architectures which
are starting to support CPU
Move cpu_exec_init() call from instance_init to realize. This allows
any failures from cpu_exec_init() to be handled appropriately.
Also add corresponding cpu_exec_exit() call from unrealize.
Signed-off-by: Bharata B Rao
Reviewed-by: David Gibson
---
target-ppc/translate_init.c | 9 +++--
1
On Mon, 4 May 2015, Quan Xu wrote:
> This patch adds infrastructure for xen front drivers living in qemu,
> so drivers don't need to implement common stuff on their own. It's
> mostly xenbus management stuff: some functions to access XenStore,
> setting up XenStore watches, callbacks on device dis
On Mon, 4 May 2015, Quan Xu wrote:
> @@ -97,6 +116,7 @@ extern struct XenDevOps xen_kbdmouse_ops; /*
> xen_framebuffer.c */
> extern struct XenDevOps xen_framebuffer_ops; /* xen_framebuffer.c */
> extern struct XenDevOps xen_blkdev_ops; /* xen_disk.c*/
> extern struct XenDevO
* Kevin Wolf (kw...@redhat.com) wrote:
> Am 08.05.2015 um 10:42 hat Stefan Hajnoczi geschrieben:
> > On Tue, May 05, 2015 at 04:23:56PM +0100, Dr. David Alan Gilbert wrote:
> > > * Stefan Hajnoczi (stefa...@redhat.com) wrote:
> > > > On Fri, Apr 24, 2015 at 11:36:35AM +0200, Paolo Bonzini wrote:
>
Paolo Bonzini writes:
> On 08/05/2015 11:32, Markus Armbruster wrote:
> +/* NBD errors are based on errno numbers, so there is a 1:1 mapping,
> + * but only a limited set of errno values is specified in the protocol.
> + * Everything else is squashed to EINVAL.
> + */
Is
On Thu, May 07, 2015 at 05:45:48PM +0200, Paolo Bonzini wrote:
> This is the behavior in the operating system, for example Linux's
> blkdev_write_iter has the following:
>
> if (bdev_read_only(I_BDEV(bd_inode)))
> return -EPERM;
>
> This does not apply to opening a device
Am 07.05.2015 um 16:50 hat Paolo Bonzini geschrieben:
> On 07/05/2015 16:34, Kevin Wolf wrote:
> > Am 07.05.2015 um 16:16 hat Paolo Bonzini geschrieben:
> >>
> >>
> >> On 07/05/2015 16:07, Kevin Wolf wrote:
> >>> This is not right for two reasons: The first is that this is
> >>> BlockBackend code
>
Paolo Bonzini writes:
> Right now, NBD includes potentially platform-specific error values in
> the wire protocol.
>
> Luckily, most common error values are more or less universal: in
> particular, of all errno values <= 34 (up to ERANGE), they are all the
> same on supported platforms except for
On Thu, May 07, 2015 at 05:45:48PM +0200, Paolo Bonzini wrote:
> This is the behavior in the operating system, for example Linux's
> blkdev_write_iter has the following:
>
> if (bdev_read_only(I_BDEV(bd_inode)))
> return -EPERM;
>
> This does not apply to opening a device
On 08/05/2015 12:08, Kevin Wolf wrote:
> Actually, considering all the information in this thread, I'm inclined
> that we should change both sides. qemu-nbd because ENOSPC might be what
> clients expect by analogy with Linux block devices, even if the
> behaviour for accesses beyond the device si
This ensures that werror=enospc works fine for NBD-backed devices.
Recovery can be done through live snapshots even if the NBD server
does not support online resizing.
Suggested-by: Kevin Wolf
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini
---
nbd.c | 4 ++--
1 file changed, 2 insertio
On Fri, 08 May 2015 09:45:00 +0300
Pavel Fedin wrote:
> Hello!
>
> > Hm, weren't there some patches for irqfd on arm?
>
> Yes, there were. However, they had a design problem by breaking backwards
> compatibility
> with unmodified virtio. Their idea was to set up one more shared memory area
On Thu, May 07, 2015 at 05:45:48PM +0200, Paolo Bonzini wrote:
> This is the behavior in the operating system, for example Linux's
> blkdev_write_iter has the following:
>
> if (bdev_read_only(I_BDEV(bd_inode)))
> return -EPERM;
>
> This does not apply to opening a device
On 08/05/2015 12:12, Markus Armbruster wrote:
>> The corresponding patch to the NBD protocol description can be found at
>> http://article.gmane.org/gmane.linux.drivers.nbd.general/3154.
[...]
>> - EFBIG is part of the universal set of errors, but it is also changed
>> to ENOSPC because it is
Hello!
> Yes, I think it makes sense to just pick the low-hanging fruit for
> virtio-mmio and wait for pci.
Does this mean that my series can be accepted as it is? Since PCI is
potentially better
solution, MMIO is a low priority in my project, and i have lots of other tasks.
This means
i unfo
Am 08.05.2015 um 12:16 hat Paolo Bonzini geschrieben:
> On 08/05/2015 12:08, Kevin Wolf wrote:
> > If so, the commands seem to be hopelessly underspecified, especially
> > with respect to error conditions. And where it says something about
> > errors, it doesn't make sense: The server is forbidden
On Fri, May 08, 2015 at 12:27:59PM +0200, Paolo Bonzini wrote:
> And there are probably other NBD servers around. CCing Rich Jones so
> that he can fix nbdkit.
Thanks. FWIW currently nbdkit will send any arbitrary errno returned
by a system call, and it doesn't do any platform-specific encoding.
Can I use a virtqueue asynchronously between guest and backend?
By that I mean that any end of the communication channel (virtqueue)
can push/pop how much data he wants anytime, without worrying that it
will pop a thing that it pushed on the queue, and in fact the other
end should have popped it? O
Am 07.05.2015 um 06:04 hat Zhe Qiu geschrieben:
> From: phoeagon
>
> In reference to
> b0ad5a455d7e5352d4c86ba945112011dbeadfb8~078a458e077d6b0db262c4b05fee51d01de2d1d2,
> metadata writes to qcow2/cow/qcow/vpc/vmdk are all synced prior to
> succeeding writes.
The justification for these patch
On Fri, 08 May 2015 13:30:18 +0300
Pavel Fedin wrote:
> Hello!
>
> > Yes, I think it makes sense to just pick the low-hanging fruit for
> > virtio-mmio and wait for pci.
>
> Does this mean that my series can be accepted as it is? Since PCI is
> potentially better
> solution, MMIO is a low pr
Am 06.05.2015 um 20:01 hat Max Reitz geschrieben:
> On 06.05.2015 14:23, Fam Zheng wrote:
> >This fixes the bug introduced by commit c6ac36e (vmdk: Optimize cluster
> >allocation).
> >
> >Sometimes, write_len could be larger than cluster size, because it
> >contains both data and marker. We must a
Am 06.05.2015 um 19:50 hat Max Reitz geschrieben:
> On 05.05.2015 11:28, Fam Zheng wrote:
> >Richard Jones caught this bug with afl fuzzer.
> >
> >In fact, that's the only possible value to overflow (extent->l1_size =
> >0x2000) l1_size:
> >
> >l1_size = extent->l1_size * sizeof(long) => 0x8000
Am 06.05.2015 um 13:29 hat Kevin Wolf geschrieben:
> Before a freed cluster can be reused, pending discards for this cluster
> must be processed.
>
> The original assumption was that this was not a problem because discards
> are only cached during discard/write zeroes operations, which are
> synch
Is eventfd blocking? By that I mean: If I signal the guest for
something, will that thread remain blocked till the guest clears the
interrupt?
On 08/05/2015 12:34, Kevin Wolf wrote:
> Am 08.05.2015 um 12:16 hat Paolo Bonzini geschrieben:
>> On 08/05/2015 12:08, Kevin Wolf wrote:
>>> If so, the commands seem to be hopelessly underspecified, especially
>>> with respect to error conditions. And where it says something about
>>> errors, it
I sent a patch that fixes the original problem that Maria reported. It's
hard to say whether this is the same problem as you saw, Sam, but it's
quite possible.
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml,
On 08/05/2015 12:58, Catalin Vasile wrote:
> Is eventfd blocking? By that I mean: If I signal the guest for
> something, will that thread remain blocked till the guest clears the
> interrupt?
No. If you want that, write 2^64-2 to the eventfd and do a
pfd.fd = ...
pfd.events = POLLOUT;
On 08/05/2015 13:24, Paolo Bonzini wrote:
>
>
> On 08/05/2015 12:58, Catalin Vasile wrote:
>> Is eventfd blocking? By that I mean: If I signal the guest for
>> something, will that thread remain blocked till the guest clears the
>> interrupt?
>
> No. If you want that, write 2^64-2 to the even
Hi all,
I noticed last week that the openbios.git mirror on git.qemu.org hadn't
been updated after a commit I made to SVN trunk, and after some
investigation work by Stefan it seems that the upstream remote is given
as a git:// URL pointing directly to a repository at a 64.62.x.x IP address.
This
On 08/05/2015 13:38, Dimitris Aragiorgis wrote:
> Building the QEMU tools fails if we #define DEBUG_BLOCK inside
> block/raw-posix.c. This happens because qemu-log.o is missing from
> block-obj-y, which causes the link to fail. Fix this.
>
> Signed-off-by: Dimitris Aragiorgis
Let's just remove
Hi,
This patch series adds "arg=" sub-option to --semihosting-config group. It
allows building up a list of input arguments as it can appear multiple
times in the command line. This is a flexible solution for creating
argc/argv for the guest program (needed by UHI semihosting for example).
RFC pat
Add new "arg" sub-argument to the --semihosting-config allowing to pass
multiple input argument separately. It is required for example by UHI
semihosting to construct argc and argv.
Signed-off-by: Leon Alrae
---
include/exec/semihost.h | 12
qemu-options.hx | 19
Remove semihosting_enabled and semihosting_target and replace them with
SemihostingConfig structure containing equivalent fields. The structure
is defined in vl.c where it is actually set.
Also introduce separate header file include/exec/semihost.h allowing to
access semihosting config related stu
On 08/05/2015 13:38, Dimitris Aragiorgis wrote:
> Until now, an SG device was identified only by checking if its path
> started with "/dev/sg". Then, hdev_open() set bs->sg accordingly.
> This is very fragile, e.g. it fails with symlinks or relative paths.
> We should rely on the actual propertie
On 08/05/2015 13:38, Dimitris Aragiorgis wrote:
> During migration, QEMU uses fsync()/fdatasync() on the open file
> descriptor for read-write block devices to flush data just before
> stopping the VM.
>
> However, fsync() on a scsi-generic device returns -EINVAL which
> causes the migration to
... and the status register should say so.
Fixes "usbus0: controller did not stop" error printed by freebsd.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-uhci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/usb/hcd-uhci.c b/hw/usb/hcd-uhci.c
index 64a7d87..3f0ed62 100644
From: Gonglei
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-network.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/hw/usb/dev-network.c b/hw/usb/dev-network.c
index 9be3a64..743c231 100644
--- a/hw/usb/dev-network.c
+++ b/hw/usb/dev-netwo
On 08/05/2015 13:38, Dimitris Aragiorgis wrote:
> Instead of checking bs->sg use bdrv_is_sg() consistently throughout
> the code.
>
> Signed-off-by: Dimitris Aragiorgis
> ---
> block.c |6 +++---
> block/iscsi.c |2 +-
> block/raw-posix.c |4 ++--
> 3 files changed, 6
to staging (2015-05-07 18:22:03 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-usb-20150508-1
for you to fetch changes up to ca5a21c40d95d7a4e26ea0a304fd2cd8ad4e6ae1:
uhci: controller is halted after reset (2015-05-08 13:0
This makes xhci generate multiple short packet events in case of
multi-trb transfers. Which is wrong. We need to fix this in a
different way.
This reverts commit aa6857891df614c620e6e9fc4bc4af6e0e49cafd.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-xhci.c | 15 +++
1 file changed,
When we find a IOC bit set on a setup trb and therefore queue an event,
that should not stop events being generated for following data trbs.
So clear the 'reported' flag.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-xhci.c | 8
1 file changed, 8 insertions(+)
diff --git a/hw/usb/hcd-xhc
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-xhci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/usb/hcd-xhci.c b/hw/usb/hcd-xhci.c
index ba15ae0..2af3dd6 100644
--- a/hw/usb/hcd-xhci.c
+++ b/hw/usb/hcd-xhci.c
@@ -2224,6 +2224,8 @@ static void xhci_kick_ep(XHCIState *xhci, unsigned int
From: Gonglei
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-bluetooth.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/hw/usb/dev-bluetooth.c b/hw/usb/dev-bluetooth.c
index 9bf6730..b19ec76 100644
--- a/hw/usb/dev-bluetooth.c
+++ b/hw/usb
From: Gonglei
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/redirect.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/hw/usb/redirect.c b/hw/usb/redirect.c
index 2416de8..242a654 100644
--- a/hw/usb/redirect.c
+++ b/hw/usb/redir
From: Gonglei
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-hub.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/hw/usb/dev-hub.c b/hw/usb/dev-hub.c
index 0482f58..c8c6855 100644
--- a/hw/usb/dev-hub.c
+++ b/hw/usb/dev-hub.c
@@ -41,6 +41,9
From: Michal Kazior
The dev->config pointer isn't set until guest
system initializes usb devices (via
usb_desc_set_config). However qemu networking can
go through some motions prior to that, e.g.:
#0 is_rndis (s=0x57261970) at hw/usb/dev-network.c:653
#1 0x5585f723 in usbnet_can_
From: Gonglei
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-hid.c | 34 --
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/hw/usb/dev-hid.c b/hw/usb/dev-hid.c
index 507c966..2e7dcd9 100644
--- a/hw/usb/dev-hid.c
+++ b/hw/usb/
From: Gonglei
Cc: Gerd Hoffmann
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-uhci.c | 43 +++
1 file changed, 31 insertions(+), 12 deletions(-)
diff --git a/hw/usb/hcd-uhci.c b/hw/usb/hcd-uhci.c
index 327f26d..64a7d87 100644
--- a
From: Gonglei
Signed-off-by: Gonglei
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-wacom.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/hw/usb/dev-wacom.c b/hw/usb/dev-wacom.c
index 844eafa..c2450e7 100644
--- a/hw/usb/dev-wacom.c
+++ b/hw/usb/dev-wacom.c
@@ -56,6
1 - 100 of 337 matches
Mail list logo
