Am 11.09.2014 um 16:45 hat Markus Armbruster geschrieben:
> For some device models, the guest can prevent unplug. Some users need a
> way to forcibly revoke device model access to the block backend then, so
> the underlying images can be safely used for something else.
>
> drive_del lets you do t
I observe two errors with latest master:
ui/qemu-pixman.c: In function ‘qemu_pixelformat_from_pixman’:
ui/qemu-pixman.c:42: error: ‘PIXMAN_TYPE_RGBA’ undeclared (first use in this
function)
ui/qemu-pixman.c:42: error: (Each undeclared identifier is reported only once
ui/qemu-pixman.c:42: error: f
Hi folks,
Lets kick off the virtio-gpu review process, starting with the virtio
protocol.
This is a tiny patch series for qemu. Patch #1 carries the header file
describing the virtual hardware: config space, command structs being
sent over the rings, defines etc. Patch #2 adds a text file des
This patch adds the header file with structs and defines for
the virtio based gpu device. Covers 2d operations only.
Signed-off-by: Gerd Hoffmann
---
include/hw/virtio/virtgpu_hw.h | 158 +
1 file changed, 158 insertions(+)
create mode 100644 include/hw/
Signed-off-by: Gerd Hoffmann
---
docs/specs/virtio-gpu.txt | 165 ++
1 file changed, 165 insertions(+)
create mode 100644 docs/specs/virtio-gpu.txt
diff --git a/docs/specs/virtio-gpu.txt b/docs/specs/virtio-gpu.txt
new file mode 100644
index 000..
On 09/11/2014 08:25 AM, Luiz Capitulino wrote:
> BLOCK_IO_ERROR events are logged by libvirt, which helps with
> post mortem analysis of guests. However, one information that
> we miss today is a human readable string describing the cause
> of the I/O error.
>
> This commit adds that string it to
On 11 September 2014 16:09, Gerd Hoffmann wrote:
> This patch adds the header file with structs and defines for
> the virtio based gpu device. Covers 2d operations only.
>
> Signed-off-by: Gerd Hoffmann
> ---
> include/hw/virtio/virtgpu_hw.h | 158
> +
>
On 09/11/2014 09:09 AM, Gerd Hoffmann wrote:
> This patch adds the header file with structs and defines for
> the virtio based gpu device. Covers 2d operations only.
>
> Signed-off-by: Gerd Hoffmann
> ---
> include/hw/virtio/virtgpu_hw.h | 158
> +
> 1 f
On 11 September 2014 16:09, Gerd Hoffmann wrote:
> This patch adds the header file with structs and defines for
> the virtio based gpu device. Covers 2d operations only.
Please don't cc subscriber only mailing lists
(virtio-...@lists.oasis-open.org) on posts to qemu-devel;
it just means everybod
On Do, 2014-09-11 at 17:59 +0300, Michael S. Tsirkin wrote:
> I observe two errors with latest master:
>
> ui/qemu-pixman.c: In function ‘qemu_pixelformat_from_pixman’:
> ui/qemu-pixman.c:42: error: ‘PIXMAN_TYPE_RGBA’ undeclared (first use in this
> function)
> ui/qemu-pixman.c:42: error: (Each u
Hi,
> In file included from /usr/include/gtk-2.0/gtk/gtk.h:228,
> from ui/gtk.c:48:
> /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47: warning: function
> declaration isn’t a prototype
That isn't new. Bug in the gtk2 header files. gtk3 has it fixed, but
gtk2.x seems to stay bug
Kevin Wolf writes:
> Am 10.09.2014 um 10:13 hat Markus Armbruster geschrieben:
>> The pointer from BlockBackend to BlockDriverState is a strong
>> reference, managed with bdrv_ref() / bdrv_unref(), the back-pointer is
>> a weak one.
>>
>> Convenience function blk_new_with_bs() creates a BlockBac
On 09/11/2014 09:09 AM, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann
> ---
> docs/specs/virtio-gpu.txt | 165
> ++
> 1 file changed, 165 insertions(+)
> create mode 100644 docs/specs/virtio-gpu.txt
>
> diff --git a/docs/specs/virtio-gpu.txt b/
Hi,
> > +enum virtgpu_ctrl_type {
> > +VIRTGPU_UNDEFINED = 0,
> >
>
> This is clearly all well out of line with our
> coding style guide, which isn't a terribly good start...
Oh yea, code style is fun. This file is needed in both qemu & linux
kernel, which have different code styles.
Commit cdaa86a54 ("Add G_IO_HUP handler for socket chardev") exposed a
bug in the way the HMP monitor handles its input. When a client closes
the connection to the monitor, tcp_chr_read() will catch the HUP
'signal' and call tcp_chr_disconnect() to close the server-side
connection too. Due to the
Hi,
the first patch fixes an issue with HMP monitors, which was exposed with v2.1.0
(commits cdaa86a and 812c10). The second one fixes a typo in a helper C program
used in qemu-iotests.
We think that they should be cherry-picked for the next stable release.
Thanks,
Stratos
Stratos Psomadakis (2
On Do, 2014-09-11 at 16:20 +0100, Peter Maydell wrote:
> On 11 September 2014 16:09, Gerd Hoffmann wrote:
> > This patch adds the header file with structs and defines for
> > the virtio based gpu device. Covers 2d operations only.
>
> Please don't cc subscriber only mailing lists
> (virtio-...@l
Il 11/09/2014 17:42, Gabriel L. Somlo ha scritto:
> Building SeaBIOS w/o EHCI and UHCI won't allow me to type into
> Chameleon's boot prompt at all (and yes, I do end up getting the
> "usb-kbd: warning: key event queue full" errors after a few
> keystrokes).
Can you configure Chamaleon to avoid th
On Thu, 11 Sep 2014 01:08:39 +0200, Paolo Bonzini wrote:
> Il 10/09/2014 16:06, Gabriel L. Somlo ha scritto:
> > If it's in QEMU, it's only tickled by the OVMF + OSX combination.
> > Fedora works (around it) fine, and everyone's happy when using
> > SeaBIOS (and Chameleon, in OSX's case).
> >
> >
Make sure to pass the correct fd via SCM_RIGHTS in socket_scm_helper.c
(i.e. fd_to_send, not socket-fd).
Signed-off-by: Stratos Psomadakis
Signed-off-by: Dimitris Aragiorgis
---
tests/qemu-iotests/socket_scm_helper.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/q
On 09/11/2014 11:43 AM, Gerd Hoffmann wrote:
> On Do, 2014-09-11 at 16:20 +0100, Peter Maydell wrote:
>> On 11 September 2014 16:09, Gerd Hoffmann wrote:
>>> This patch adds the header file with structs and defines for
>>> the virtio based gpu device. Covers 2d operations only.
>>
>> Please don't
On Wed, 10 Sep 2014 20:30:47 +0300
"Michael S. Tsirkin" wrote:
> commit cc943c36faa192cd4b32af8fe5edb31894017d35
> pci: Use bus master address space for delivering MSI/MSI-X messages
> breaks virtio-net for rhel6.[56] x86 guests because they don't
> enable bus mastering for virtio PCI devices
On vm stop, vm_running state set to stopped
before device is notified, so callbacks can get envoked with
vm_running = false; and this is not an error.
Cc: qemu-sta...@nongnu.org
Cc: Jason Wang
Signed-off-by: Michael S. Tsirkin
---
hw/net/virtio-net.c | 2 --
1 file changed, 2 deletions(-)
diff
This reverts commit a1bc7b827e422e1ff065640d8ec5347c4aadfcd8.
virtio: don't call device on !vm_running
It turns out that virtio net assumes that vm_running
is updated before device status callback in many places,
so this change leads to asserts.
Previous commit fixes the root issue that motivat
On Thu, Sep 11, 2014 at 09:11:40AM -0500, Michael Roth wrote:
> Quoting Dietmar Maurer (2014-09-11 04:55:05)
> > Seems that we get a crash when we live-migrate a VMs using virtio-net-pci
> > (vhost=on).
> > This worked in 2.1.0. Any ideas?
>
> Is this what you're seeing on the source side?
>
> q
On Thu, Sep 11, 2014 at 05:49:08PM +0200, Paolo Bonzini wrote:
> Il 11/09/2014 17:42, Gabriel L. Somlo ha scritto:
> > Building SeaBIOS w/o EHCI and UHCI won't allow me to type into
> > Chameleon's boot prompt at all (and yes, I do end up getting the
> > "usb-kbd: warning: key event queue full" err
Il 11/09/2014 18:35, Gabriel L. Somlo ha scritto:
>> > Can you configure Chamaleon to avoid the boot prompt?
> Yes. After doing that, usb starts working once OS X is fully booted.
>
> Works with either piix or q35 just fine.
>
> Does this mean it's likely to be an OVMF uhci/ehci issue specific to
I split off these patches from the series I sent last week. Peter's NOR flash
patch has been merged in the mean time, and the CPU reset patch needs to be
discussed more widely before we can move forward with it.
So what remains are changes in the DTB handling in hw/arm/boot.c, to load a
DTB even w
From: Michael S. Tsirkin
commit cc943c36faa192cd4b32af8fe5edb31894017d35
pci: Use bus master address space for delivering MSI/MSI-X messages
breaks virtio-net for rhel6.[56] x86 guests because they don't
enable bus mastering for virtio PCI devices. For the same reason,
rhel6.[56] ppc64 guests
If we are running the 'virt' machine, we may have a device tree blob but no
kernel to supply it to if no -kernel option was passed. In that case, copy it
to the base of RAM where it can be picked up by a bootloader.
Signed-off-by: Ard Biesheuvel
---
hw/arm/boot.c | 10 ++
1 file changed,
Add an address limit input parameter to load_dtb() so that we can
tell load_dtb() how much memory the dtb is allowed to consume. If
the dtb doesn't fit, return 0, otherwise return the actual size of
the loaded dtb.
Reviewed-by: Peter Maydell
Signed-off-by: Ard Biesheuvel
---
hw/arm/boot.c | 34
Add support for loading DTB images when booting ELF images using
-kernel. If there are no conflicts with the placement of the ELF
segments, the DTB image is loaded at the base of RAM.
Signed-off-by: Ard Biesheuvel
---
hw/arm/boot.c | 22 --
1 file changed, 20 insertions(+), 2
On Thu, Sep 11, 2014 at 06:00:39PM +0200, Greg Kurz wrote:
> On Wed, 10 Sep 2014 20:30:47 +0300
> "Michael S. Tsirkin" wrote:
>
> > commit cc943c36faa192cd4b32af8fe5edb31894017d35
> > pci: Use bus master address space for delivering MSI/MSI-X messages
> > breaks virtio-net for rhel6.[56] x86
In order to make the device tree blob (DTB) available in memory not only at
first boot, but also after system reset, use rom_blob_add_fixed() to install
it into memory.
Reviewed-by: Peter Maydell
Signed-off-by: Ard Biesheuvel
---
hw/arm/boot.c | 5 -
1 file changed, 4 insertions(+), 1 delet
Paolo Bonzini wrote:
> This is a hypercall that should have kicked VCPU 3 (see rcx).
>
> Can you please apply this patch and gather a trace of the host
> (using "trace-cmd -e kvm qemu-kvm ")?
Sure, no problem. I've built the trace-cmd tool against udis86 (I hope) and
have put the resulting trac
> + blk_bs(blk_by_legacy_dinfo(dinfo)));
This seems to be a fairly common pattern: "blk_bs(blk_by_legacy_dinfo())".
How about a helper function ?
On Thu, Sep 11, 2014 at 06:40:38PM +0200, Paolo Bonzini wrote:
> Il 11/09/2014 18:35, Gabriel L. Somlo ha scritto:
> >> > Can you configure Chamaleon to avoid the boot prompt?
> > Yes. After doing that, usb starts working once OS X is fully booted.
> >
> > Works with either piix or q35 just fine.
Il 11/09/2014 19:11, Gabriel L. Somlo ha scritto:
> On Thu, Sep 11, 2014 at 06:40:38PM +0200, Paolo Bonzini wrote:
>> Il 11/09/2014 18:35, Gabriel L. Somlo ha scritto:
> Can you configure Chamaleon to avoid the boot prompt?
>>> Yes. After doing that, usb starts working once OS X is fully booted
This is a error in user mode, I think it should be very easy to
reproduce.
On Thu, Sep 11, 2014 at 4:55 AM, Leon Alrae
wrote:
> Could you please provide backtrace and give more details to reproduce
> the issue?
>
> --
> You received this bug notification because you are subscribed to the bug
> r
Kevin Wolf writes:
> Am 10.09.2014 um 10:13 hat Markus Armbruster geschrieben:
>> Make the BlockBackend own the DriveInfo. Change blockdev_init() to
>> return the BlockBackend instead of the DriveInfo.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> block/block-backend.c | 38 +++
On Thu, Sep 11, 2014 at 06:45:33PM +0200, Greg Kurz wrote:
> From: Michael S. Tsirkin
>
> commit cc943c36faa192cd4b32af8fe5edb31894017d35
> pci: Use bus master address space for delivering MSI/MSI-X messages
> breaks virtio-net for rhel6.[56] x86 guests because they don't
> enable bus masteri
(I've cc'd in Fam, Stefan, and Kevin for Block stuff, and
Yang and Eddie for Colo)
* Walid Nouri (walid.no...@gmail.com) wrote:
> Hello Michael, Hello Paolo
> i have ???studied??? the available documentation/Information and tried to
> get an idea of the QEMU live block operation pos
On Thu, Sep 11, 2014 at 08:47:01PM +0300, Michael S. Tsirkin wrote:
> On Thu, Sep 11, 2014 at 06:45:33PM +0200, Greg Kurz wrote:
> > From: Michael S. Tsirkin
> >
> > commit cc943c36faa192cd4b32af8fe5edb31894017d35
> > pci: Use bus master address space for delivering MSI/MSI-X messages
> > bre
On Thu, Sep 11, 2014 at 06:00:39PM +0200, Greg Kurz wrote:
> On Wed, 10 Sep 2014 20:30:47 +0300
> "Michael S. Tsirkin" wrote:
>
> > commit cc943c36faa192cd4b32af8fe5edb31894017d35
> > pci: Use bus master address space for delivering MSI/MSI-X messages
> > breaks virtio-net for rhel6.[56] x86
commit cc943c36faa192cd4b32af8fe5edb31894017d35
pci: Use bus master address space for delivering MSI/MSI-X messages
breaks virtio-net for rhel6.[56] x86 guests because they don't
enable bus mastering for virtio PCI devices. For the same reason,
rhel6.[56] ppc64 guests cannot boot on a virtio-bl
Benoît Canet writes:
> The Wednesday 10 Sep 2014 à 10:13:33 (+0200), Markus Armbruster wrote :
>> Make the BlockBackend own the DriveInfo. Change blockdev_init() to
>> return the BlockBackend instead of the DriveInfo.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> block/block-backend.c
On Thu, 11 Sep 2014, Owen Smith wrote:
> > -Original Message-
> > From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> > Sent: 11 September 2014 02:01
> > To: Owen Smith
> > Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org; Stefano Stabellini
> > Subject: Re: [PATCH 2/3] x
On Thu, 11 Sep 2014, Owen Smith wrote:
> > -Original Message-
> > From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> > Sent: 11 September 2014 02:23
> > To: Owen Smith
> > Cc: qemu-devel@nongnu.org; xen-de...@lists.xen.org; Stefano Stabellini
> > Subject: Re: [PATCH 3/3] x
commit cc943c36faa192cd4b32af8fe5edb31894017d35
pci: Use bus master address space for delivering MSI/MSI-X messages
breaks virtio-net for rhel6.[56] x86 guests because they don't
enable bus mastering for virtio PCI devices. For the same reason,
rhel6.[56] ppc64 guests cannot boot on a virtio-bl
On Thu, Sep 11, 2014 at 05:21:13PM +0200, Gerd Hoffmann wrote:
> On Do, 2014-09-11 at 17:59 +0300, Michael S. Tsirkin wrote:
> > I observe two errors with latest master:
> >
> > ui/qemu-pixman.c: In function ‘qemu_pixelformat_from_pixman’:
> > ui/qemu-pixman.c:42: error: ‘PIXMAN_TYPE_RGBA’ undecla
commit cc943c36faa192cd4b32af8fe5edb31894017d35
pci: Use bus master address space for delivering MSI/MSI-X messages
breaks virtio-net for rhel6.[56] x86 guests because they don't
enable bus mastering for virtio PCI devices. For the same reason,
rhel6.[56] ppc64 guests cannot boot on a virtio-bl
Kevin Wolf writes:
> Am 10.09.2014 um 10:13 hat Markus Armbruster geschrieben:
>> On BlockBackend destruction, unref its BlockDriverState. Replaces the
>> callers' unrefs.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> block/block-backend.c | 9 ++---
>> blockdev.c| 11 +++-
I forgot to add that qemu-mips64 works for me, that's why I asked for
the details to reproduce the issue (i.e. what is "lang", what tools you
used to build it, command line etc.)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https:/
On Thu, 11 Sep 2014 21:20:03 +0300
"Michael S. Tsirkin" wrote:
> commit cc943c36faa192cd4b32af8fe5edb31894017d35
> pci: Use bus master address space for delivering MSI/MSI-X messages
> breaks virtio-net for rhel6.[56] x86 guests because they don't
> enable bus mastering for virtio PCI devices
Benoît Canet writes:
> The Wednesday 10 Sep 2014 à 10:13:36 (+0200), Markus Armbruster wrote :
[...]
>> --- a/monitor.c
>> +++ b/monitor.c
>> @@ -4208,24 +4208,6 @@ static void file_completion(Monitor *mon, const char
>> *input)
>> closedir(ffs);
>> }
>>
>> -typedef struct MonitorBlockCo
Eric Blake writes:
> On 09/10/2014 02:13 AM, Markus Armbruster wrote:
>> device_name[] is can become non-empty only in bdrv_new_named() and
>
> s/is //
Fixing, thanks!
>> bdrv_move_feature_fields(). The latter is used only to undo damage
>> done by bdrv_swap(). The former is called only by bl
> On Do, 2014-09-11 at 16:20 +0100, Peter Maydell wrote:
> > On 11 September 2014 16:09, Gerd Hoffmann wrote:
> > > This patch adds the header file with structs and defines for
> > > the virtio based gpu device. Covers 2d operations only.
> >
> > Please don't cc subscriber only mailing lists
> >
Benoît Canet writes:
> The Wednesday 10 Sep 2014 à 10:13:37 (+0200), Markus Armbruster wrote :
>> device_name[] is can become non-empty only in bdrv_new_named() and
>> bdrv_move_feature_fields(). The latter is used only to undo damage
>> done by bdrv_swap(). The former is called only by blk_new
I can see the problem with any simple program:
1. cat t.c
#include
int main()
{
printf("Hello QEMU.\n");
}
2. mips64-gcc -static t.c -o t
3. qemu-mips64 t
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
I built QEMU on Ubuntu 12.04 with the s
Benoît Canet writes:
> The Thursday 11 Sep 2014 à 07:00:41 (-0600), Eric Blake wrote :
>> On 09/11/2014 05:34 AM, Benoît Canet wrote:
>> > The Wednesday 10 Sep 2014 à 10:13:37 (+0200), Markus Armbruster wrote :
>> >> device_name[] is can become non-empty only in bdrv_new_named() and
>> >> bdrv_mo
Benoît Canet writes:
>> + blk_bs(blk_by_legacy_dinfo(dinfo)));
>
> This seems to be a fairly common pattern: "blk_bs(blk_by_legacy_dinfo())".
> How about a helper function ?
Yes, except the pattern is going to evaporate in patch 14 :)
Benoît Canet writes:
> I have trouble to review this as I don't understand the qdevs parts.
> Maybe someone else could have a look at it.
The patch is big, but all it really does is replacing
dinfo->bdrv
by
blk_bs(blk_legacy_dinfo(dinfo))
Line wrapping muddies the waters a bit. I al
This patch series enable floating point instruction in 440x5 CPUs
which have the capabilities to have optional APU FPU in double precision mode.
1) Allow fc[tf]id[*] mnemonics for non TARGET_PPC64 with a new insn2 flag
2) Create a new 440x5 implementing floating point instructions
Pierre Mallard
Benoît Canet writes:
> I think you should rebase this on top of Fam's null driver.
This patch is prone to conflicts, but I expect them to be trivial. I'll
rebase onto whatever is current when we're ready to merge.
This patch add a new processor type 440x5wDFPU for Virtex 5 PPC440
with an external APU FPU in double precision mode
---
target-ppc/cpu-models.c |3 +++
target-ppc/translate_init.c | 38 ++
2 files changed, 41 insertions(+)
diff --git a/target-ppc/cpu
Review led to a couple of changes with ripple effects on later patches.
I suggest y'all await my v2 before you continue.
Thanks a lot for the review so far!
This patch remove limitation for fc[tf]id[*] on 32 bits targets and
add a new insn flag for signed integer 64 conversion PPC2_FP_CVT_S64
---
target-ppc/cpu.h|5 -
target-ppc/fpu_helper.c |6 --
target-ppc/helper.h |4 +---
target-ppc/translate.c |
The Thursday 11 Sep 2014 à 21:12:44 (+0200), Markus Armbruster wrote :
> Benoît Canet writes:
>
> >> + blk_bs(blk_by_legacy_dinfo(dinfo)));
> >
> > This seems to be a fairly common pattern: "blk_bs(blk_by_legacy_dinfo())".
> > How about a helper function ?
>
> Y
On 09/11/2014 01:34 PM, Benoît Canet wrote:
> The Thursday 11 Sep 2014 à 21:12:44 (+0200), Markus Armbruster wrote :
>> Benoît Canet writes:
>>
+ blk_bs(blk_by_legacy_dinfo(dinfo)));
>>>
>>> This seems to be a fairly common pattern: "blk_bs(blk_by_legacy_dinf
On Thu, Sep 11, 2014 at 06:40:38PM +0200, Paolo Bonzini wrote:
> Il 11/09/2014 18:35, Gabriel L. Somlo ha scritto:
> >> > Can you configure Chamaleon to avoid the boot prompt?
> > Yes. After doing that, usb starts working once OS X is fully booted.
> >
> > Works with either piix or q35 just fine.
The time it takes for block layer patches to be reviewed and merged is a
concern. Kevin and I want to discuss this issue, which was raised by
Benoit, on the mailing list.
The volume of patches is so high that Kevin and I cannot review them
all in a timely manner. We are adjusting the process as
On 09/11/2014 12:03 PM, Markus Armbruster wrote:
> Benoît Canet writes:
>
>> The Wednesday 10 Sep 2014 à 10:13:33 (+0200), Markus Armbruster wrote :
>>> Make the BlockBackend own the DriveInfo. Change blockdev_init() to
>>> return the BlockBackend instead of the DriveInfo.
>>>
>>> Signed-off-by:
On 09/11/14 22:16, Gabriel L. Somlo wrote:
> On Thu, Sep 11, 2014 at 06:40:38PM +0200, Paolo Bonzini wrote:
>> Il 11/09/2014 18:35, Gabriel L. Somlo ha scritto:
> Can you configure Chamaleon to avoid the boot prompt?
>>> Yes. After doing that, usb starts working once OS X is fully booted.
>>>
>
When using Gdb to remote-debug a program, if we try to single-step an
invalid instruction,
Qemu will never return control to the remote Gdb.
The source of this problem is external interrupts being masked out
in cpu_exec if cpu->singlestep_enabled has the SSTEP_NOIRQ flag set.
To solve this I've add
On Tue, 2014-09-09 at 21:34 +1000, Alexey Kardashevskiy wrote:
> I did some tests on LE/BE guest/host combinations and came up with
> these 2 patches. Please comment. Thanks.
Have you tried BE guest/LE host? IIRC, the g3beige tcg guest on x86
host used to work with a vfio-pci NIC. The ROM is of
> EOF
> ---
> If you have feedback or questions, let us know. The process can be
> tweaked as time goes on so we can continue to improve.
Great mail.
Now we need a wiki entry describing the process.
Also we need something reminding who is the maintainer of the current week.
Best regards
Benoît
> Am 11.09.2014 um 22:46 schrieb Laszlo Ersek :
>
>> On 09/11/14 22:16, Gabriel L. Somlo wrote:
>>> On Thu, Sep 11, 2014 at 06:40:38PM +0200, Paolo Bonzini wrote:
>>> Il 11/09/2014 18:35, Gabriel L. Somlo ha scritto:
>> Can you configure Chamaleon to avoid the boot prompt?
Yes. After do
From: Damjan Marion
Header length check should happen only if backend is kernel. For user
backend there is no reason to reset this bit.
vhost-user code does not define .has_vnet_hdr_len so
VIRTIO_NET_F_MRG_RXBUF cannot be negotiated even if both sides
support it.
Signed-off-by: Damjan Marion
-
Am 11.09.2014 19:44, schrieb Dr. David Alan Gilbert:
For keeping the complete system state consistent on the secondary system
there must be a possibility for MC to commit/discard block device state
changes. In normal operation the mirrored block device state changes (block
buffer) are committed
[cc'ing RTH who may have a better grasp on how the builtin single step is
supposed to work.]
On 11 September 2014 22:02, Martin Galvan
wrote:
> When using Gdb to remote-debug a program, if we try to single-step an
> invalid instruction,
> Qemu will never return control to the remote Gdb.
> The so
On Tue, 2014-09-09 at 08:31 +0100, Eric Auger wrote:
> This RFC series aims at enabling KVM platform device passthrough.
> It implements a VFIO platform device, derived from VFIO PCI device.
>
> The VFIO platform device uses the host VFIO platform driver which must
> be bound to the assigned devic
On Thu, Sep 11, 2014 at 04:14:09PM -0600, Alex Williamson wrote:
> On Tue, 2014-09-09 at 08:31 +0100, Eric Auger wrote:
> > This RFC series aims at enabling KVM platform device passthrough.
> > It implements a VFIO platform device, derived from VFIO PCI device.
> >
> > The VFIO platform device use
On Thu, 2014-09-11 at 15:23 -0700, Christoffer Dall wrote:
> On Thu, Sep 11, 2014 at 04:14:09PM -0600, Alex Williamson wrote:
> > On Tue, 2014-09-09 at 08:31 +0100, Eric Auger wrote:
> > > This RFC series aims at enabling KVM platform device passthrough.
> > > It implements a VFIO platform device,
Quoting Paolo Bonzini (2014-09-11 09:35:58)
> Il 11/09/2014 16:26, Michael Roth ha scritto:
> > Also, the .kind field of a QAPI Union type is something we generate for use
> > by the generated visitor code. In the case of an unspecified discriminator
> > we generated the enum type for that field in
On Thu, Sep 11, 2014 at 04:51:14PM -0600, Alex Williamson wrote:
> On Thu, 2014-09-11 at 15:23 -0700, Christoffer Dall wrote:
> > On Thu, Sep 11, 2014 at 04:14:09PM -0600, Alex Williamson wrote:
> > > On Tue, 2014-09-09 at 08:31 +0100, Eric Auger wrote:
> > > > This RFC series aims at enabling KVM
Hi qemu devs,
I was wondering if anyone would be willing to test this patch with intel
or, if it will be useful, I can add support nouveau, radeon, vmxgfx / any
other mesa + drm gfx driver. I won't be able to easily test the latter
config, but given the nature of this patch, adding those IOCTLs sh
In some cases an input visitor might bail out on filling out a
struct for various reasons, such as missing fields when running
in strict mode. In the case of a QAPI Union type, this may lead
to cases where the .kind field which encodes the union type
is uninitialized. Subsequently, other visitors,
This more of an exercise of the dealloc visitor, where it may
erroneously use an uninitialized discriminator field as indication
that union fields corresponding to that discriminator field/type are
present, which can lead to attempts to free random chunks of heap
memory.
Cc: qemu-sta...@nongnu.org
If the .data field of a QAPI Union is NULL, we don't need to free
any of the union fields..
Make use of the new visit_start_union interface to access this
information and instruct the generated code to not visit these
fields when this occurs.
Cc: qemu-sta...@nongnu.org
Reported-by: Fam Zheng
Sug
This series introduces visit_start_enum and visit_end_enum as a way
of allowing visitors to trigger generated code to bail out on visiting
union fields if the visitor implementation deems doing so to be unsafe.
See patch 1 for the circumstances that cause the segfault in the
dealloc visitor.
This
On Thu, Sep 11, 2014 at 11:34:03PM +0200, Alexander Graf wrote:
> >> With Chameleon (and SeaBIOS), I see all three UHCIs (with no attached
> >> devices), and EHCI (with the now-high-speed keyboard and mouse).
> >>
> >> With OVMF, I have EHCI with the high-speed (and working)
> >> keyboard+mouse, b
On 09/11/2014 03:13 PM, Peter Maydell wrote:
>> The long story: Qemu generates an exception_with_syndrome instruction
>> when it realizes the instruction it's trying to translate is invalid.
>> That instruction in turn modifies cs->exception_index and calls
>> cpu_loop_exit.
>> Normally, the value
在 09/12/2014 01:44 AM, Dr. David Alan Gilbert 写道:
(I've cc'd in Fam, Stefan, and Kevin for Block stuff, and
Yang and Eddie for Colo)
* Walid Nouri (walid.no...@gmail.com) wrote:
Hello Michael, Hello Paolo
i have ???studied??? the available documentation/Information and tried to
On 09/12/2014 07:20 AM, Alex Williamson wrote:
> On Tue, 2014-09-09 at 21:34 +1000, Alexey Kardashevskiy wrote:
>> I did some tests on LE/BE guest/host combinations and came up with
>> these 2 patches. Please comment. Thanks.
>
> Have you tried BE guest/LE host?
Yes.
> IIRC, the g3beige tcg g
在 09/11/2014 09:50 AM, Michael R. Hines 写道:
On 09/10/2014 11:43 PM, Walid Nouri wrote:
Hello Michael, Hello Paolo
i have „studied“ the available documentation/Information and tried to get an
idea of the QEMU live block operation possibilities.
I think the MC protocol doesn’t need synchronous
Hi Bharata,
On 09/11/2014 08:37 PM, Bharata B Rao wrote:
> On Thu, Sep 11, 2014 at 3:23 PM, Gu Zheng wrote:
>> On 09/11/2014 05:35 PM, Bharata B Rao wrote:
>>
>>> On Thu, Aug 28, 2014 at 9:06 AM, Gu Zheng wrote:
After ACPI get a signal to eject a vCPU, the vCPU must be
removed from CP
On Wed, Jul 9, 2014 at 5:53 PM, Paolo Bonzini wrote:
> Uses the same select/WSAEventSelect scheme as main-loop.c.
> WSAEventSelect() is edge-triggered, so it cannot be used
> directly, but it is still used as a way to exit from a
> blocking g_poll().
>
> Before g_poll() is called, we poll sockets
On Wed, Jul 9, 2014 at 5:53 PM, Paolo Bonzini wrote:
> Uses the same select/WSAEventSelect scheme as main-loop.c.
> WSAEventSelect() is edge-triggered, so it cannot be used
> directly, but it is still used as a way to exit from a
> blocking g_poll().
>
> Before g_poll() is called, we poll sockets
Hi Igor,
On 09/11/2014 06:12 PM, Igor Mammedov wrote:
> On Thu, 11 Sep 2014 11:04:10 +0800
> Gu Zheng wrote:
>
>> Hi Igor,
>> On 09/10/2014 09:28 PM, Igor Mammedov wrote:
>>
>>> On Wed, 3 Sep 2014 17:06:13 +0800
>>> Gu Zheng wrote:
>>>
Signed-off-by: Gu Zheng
---
hw/acpi/
On 09/11/2014 05:20 PM, Michael Roth wrote:
> In some cases an input visitor might bail out on filling out a
> struct for various reasons, such as missing fields when running
> in strict mode. In the case of a QAPI Union type, this may lead
> to cases where the .kind field which encodes the union t
101 - 200 of 226 matches
Mail list logo
