On Thu, Oct 02, 2014 at 01:00:04PM +0200, Paolo Bonzini wrote:
> Il 01/10/2014 22:23, Wouter Verhelst ha scritto:
> > Hi,
> >
> > On Fri, Sep 05, 2014 at 03:26:09PM +0200, Wouter Verhelst wrote:
> >> Tunneling the entire protocol inside an SSL connection doesn't fix that;
> >> if an attacker is ab
et-arm-20140929' into staging (2014-09-30
> 11:02:06 +0100)
>
> are available in the git repository at:
>
>
> git://git.kraxel.org/qemu tags/pull-console-20141002-1
>
> for you to fetch changes up to 89ec031b09c81821e349c364575fad652395cf94:
>
> pixman: fix qem
On Thu, Oct 02, 2014 at 03:26:28PM +0200, Andreas Färber wrote:
> Am 02.10.2014 um 15:21 schrieb Stefan Hajnoczi:
> > On Wed, Oct 01, 2014 at 02:33:47PM +0200, Markus Armbruster wrote:
> >> Markus Armbruster writes:
> >
> > This discussion seems orthogonal to your patch. But I'm not applying it
On Thu, Oct 02, 2014 at 03:42:21PM +0200, Markus Armbruster wrote:
> Stefan Hajnoczi writes:
>
> > On Tue, Sep 30, 2014 at 01:59:30PM +0200, Markus Armbruster wrote:
> >> +bool id_wellformed(const char *id)
> >> +{
> >> +int i;
> >> +
> >> +if (!qemu_isalpha(id[0])) {
> >> +return
Andreas Färber writes:
> Am 02.10.2014 um 15:21 schrieb Stefan Hajnoczi:
>> On Wed, Oct 01, 2014 at 02:33:47PM +0200, Markus Armbruster wrote:
>>> Markus Armbruster writes:
>>
>> This discussion seems orthogonal to your patch. But I'm not applying it
>> yet to give more time for discussion/rev
Am 02.10.2014 um 16:21 schrieb Markus Armbruster:
> Andreas Färber writes:
>
>> Am 02.10.2014 um 15:21 schrieb Stefan Hajnoczi:
>>> On Wed, Oct 01, 2014 at 02:33:47PM +0200, Markus Armbruster wrote:
Markus Armbruster writes:
>>>
>>> This discussion seems orthogonal to your patch. But I'm n
Hi,
with kernel with an obsolete version (< 3.8) DIMM configuration is not
working as defined in a boot-up values, though it is possible to add
dimm during runtime and it will be recognized just well. ACPI tables
and the of DMI for kernels which are recognizing on-boot modules and
for ones which a
On Wed, Oct 01, 2014 at 02:19:23PM -0400, John Snow wrote:
> The Q35 board initialization does not currently bother to look
> for any drives added by the various syntactical sugar shorthands
> to be added to the AHCI HBA. These include -hda through -hdd,
> -cdrom, and -drive if=ide shorthands.
>
>
Each of qdev-monitor-test and blockdev-test has just one test case,
and both are about drive_del.
Signed-off-by: Markus Armbruster
---
tests/Makefile | 5 +--
tests/blockdev-test.c | 59 -
tests/{qdev-monitor-tes
Executed in this order, drive_del and device_del's automatic drive
deletion take notoriously tricky special paths.
Signed-off-by: Markus Armbruster
---
tests/drive_del-test.c | 32
1 file changed, 32 insertions(+)
diff --git a/tests/drive_del-test.c b/tests/driv
Signed-off-by: Markus Armbruster
---
tests/drive_del-test.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/tests/drive_del-test.c b/tests/drive_del-test.c
index 67309fd..2baf0b7 100644
--- a/tests/drive_del-test.c
+++ b/tests/drive_del-test.c
@@ -17,7 +17,6 @@
stati
The meat is in the last patch, the others are just cleanup.
Markus Armbruster (6):
drive_del-test: Merge of qdev-monitor-test, blockdev-test
blockdev-test: Use single rather than double quotes in QMP
blockdev-test: Clean up bogus drive_add argument
blockdev-test: Simplify by using g_assert
The first argument should be a PCI address, which pci-addr=auto isn't.
Doesn't really matter, as drive_add ignores its first argument when
its second argument has if=none. Clean it up anyway.
Signed-off-by: Markus Armbruster
---
tests/drive_del-test.c | 2 +-
1 file changed, 1 insertion(+), 1 d
QMP accepts both single and double quotes. This is the only test
using double quotes. They need to be quoted in C strings. Replace
them by single quotes.
Signed-off-by: Markus Armbruster
---
tests/drive_del-test.c | 32
1 file changed, 16 insertions(+), 16 del
On Thu, Oct 02, 2014 at 06:52:52PM +1000, Alexey Kardashevskiy wrote:
> When migrated using libvirt with "--copy-storage-all", at the end of
> migration there is race between NBD mirroring task trying to do flush
> and migration completion, both end up invalidating cache. Since qcow2
> driver does
Signed-off-by: Markus Armbruster
---
tests/drive_del-test.c | 60 +-
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/tests/drive_del-test.c b/tests/drive_del-test.c
index 2baf0b7..463479d 100644
--- a/tests/drive_del-test.c
+++ b/tes
08:
>
> Merge remote-tracking branch
> 'remotes/pmaydell/tags/pull-target-arm-20140929' into staging (2014-09-30
> 11:02:06 +0100)
>
> are available in the git repository at:
>
>
> git://git.kraxel.org/qemu tags/pull-input-20141002-1
>
> for you to fet
Andreas Färber writes:
> Am 02.10.2014 um 16:21 schrieb Markus Armbruster:
>> Andreas Färber writes:
>>
>>> Am 02.10.2014 um 15:21 schrieb Stefan Hajnoczi:
On Wed, Oct 01, 2014 at 02:33:47PM +0200, Markus Armbruster wrote:
> Markus Armbruster writes:
This discussion seems or
On Wed, Oct 01, 2014 at 09:06:36PM +0200, Max Reitz wrote:
> On 01.10.2014 19:01, Stefan Hajnoczi wrote:
> >+typedef struct {
> >+BlockJob *job;
> >+QEMUBH *bh;
> >+AioContext *aio_context;
> >+BlockJobDeferToMainLoopFn *fn;
> >+void *opaque;
> >+} BlockJobDeferToMainLoopData;
>
On Wed, Oct 01, 2014 at 09:38:39PM +0200, Max Reitz wrote:
> On 01.10.2014 19:01, Stefan Hajnoczi wrote:
> >The backup block job must run in the BlockDriverState AioContext so that
> >it works with dataplane.
> >
> >The basics of acquiring the AioContext are easy in blockdev.c.
> >
> >The completio
On Tue, Sep 30, 2014 at 01:44:48PM -0400, Al Patel wrote:
> In the current system, what are the extra threads?
The set of thread is dynamic because worker threads are started and
terminated depending on guest activity. You cannot make assumptions
about threads and QEMU provides monitor commands t
On 10/02/2014 08:51 AM, Markus Armbruster wrote:
> QMP accepts both single and double quotes. This is the only test
> using double quotes. They need to be quoted in C strings. Replace
> them by single quotes.
Ooh, the use of single quotes on input is undocumented, and a violation
of JSON. We al
On Tue, Sep 30, 2014 at 11:35:17AM +0800, Fam Zheng wrote:
> diff --git a/main-loop.c b/main-loop.c
> index d2e64f1..4641ef4 100644
> --- a/main-loop.c
> +++ b/main-loop.c
> @@ -234,7 +234,8 @@ static int os_host_main_loop_wait(int64_t timeout)
> spin_counter++;
> }
>
> -ret = q
On 10/02/2014 08:51 AM, Markus Armbruster wrote:
> The first argument should be a PCI address, which pci-addr=auto isn't.
> Doesn't really matter, as drive_add ignores its first argument when
> its second argument has if=none. Clean it up anyway.
>
> Signed-off-by: Markus Armbruster
> ---
> tes
On 10/02/2014 08:51 AM, Markus Armbruster wrote:
> Each of qdev-monitor-test and blockdev-test has just one test case,
> and both are about drive_del.
>
> Signed-off-by: Markus Armbruster
> ---
> tests/Makefile | 5 +--
> tests/blockdev-test.c
On 10/02/2014 08:51 AM, Markus Armbruster wrote:
> Signed-off-by: Markus Armbruster
> ---
> tests/drive_del-test.c | 9 ++---
> 1 file changed, 2 insertions(+), 7 deletions(-)
Reviewed-by: Eric Blake
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http:
On 10/02/2014 08:51 AM, Markus Armbruster wrote:
> Signed-off-by: Markus Armbruster
> ---
> tests/drive_del-test.c | 60
> +-
> 1 file changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/tests/drive_del-test.c b/tests/drive_del-test.c
> in
Public bug reported:
Qemu passes through all devices on Bus 3 with host-usb all right when
issued so on the command line such as
... -device usb-ehci,id=USBCtrl -device host-
usb,bus=USBCtrl.0,hostaddr=5
but it does not pass through the devices newly hotplugged to the host
after Qemu has already
On Fri, Sep 26, 2014 at 09:43:18PM +0800, Xiaodong Gong wrote:
> Now qemu only supports vhd type VHD_FIXED and VHD_DYNAMIC, so qemu
> can't read snapshot volume of vhd, and can't support other storage
> features of vhd file.
>
> This patch add read parent information in function "vpc_open", read
>
On 10/02/2014 08:51 AM, Markus Armbruster wrote:
> Executed in this order, drive_del and device_del's automatic drive
> deletion take notoriously tricky special paths.
>
> Signed-off-by: Markus Armbruster
> ---
> tests/drive_del-test.c | 32
> 1 file changed, 32
On Thu, Sep 25, 2014 at 03:51:44PM +0200, Paolo Bonzini wrote:
> The GNU Makefile standards have "make install" and "make
> install-strip" targets. It would be nice to add "make install-strip"
> and at the same time flip the default from --enable-strip to
> --disable-strip.
Makes sense.
Stefan
*** This bug is a duplicate of bug 1294898 ***
https://bugs.launchpad.net/bugs/1294898
** This bug has been marked a duplicate of bug 1294898
gtk: menubar visible in fullscreen mode with gtk3
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
Hi,
Overall looking good but has issues with not freeing tcg_temps and some
style problem which
failed with the checkpatch.pl script.
Otherwise
Reviewed-by: Yongbok Kim
Regards,
Yongbok
On 27/06/2014 16:22, Leon Alrae wrote:
In terms of encoding MIPS32R6 MIN.fmt, MAX.fmt, MINA.fmt, MAXA.fm
From: Corey Minyard
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/qemu-char.c b/qemu-char.c
index 8623c70..f9d2a02 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -84,6 +84,7 @@
#def
From: Corey Minyard
This keeps them from having to be passed around and makes them
available for later functions, like printing and reconnecting.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 65 -
1 file
From: Corey Minyard
This way we can tell if the socket is connected or not. It also splits
the string conversions out into separate functions to make this more
convenient.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 110 +++---
From: Corey Minyard
Move all socket configuration to qmp_chardev_open_socket().
qemu_chr_open_socket_fd() just opens the socket. This is getting ready
for the reconnect code, which will call open_sock_fd() on a reconnect
attempt.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qe
From: Corey Minyard
It seems that it might be a good idea to know what is at the remote
end of a socket for tracking down issues. So add that to the
socket filename.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 27 ++-
1 file changed, 18 i
One more time, with the rework added to qemu_chr_finish_socket_connection()
that I should have seen. It didn't generate any errors, so there was no
point in having error returns from it.
Also added an assert to qemu_chr_socket_restart_timer().
Thanks,
-corey
From: Corey Minyard
Adds a "reconnect" option to socket backends that gives a reconnect
timeout. This only applies to client sockets. If the other end
of a socket closes the connection, qemu will attempt to reconnect
after the given number of seconds.
Signed-off-by: Corey Minyard
---
qapi-sc
Eric Blake writes:
> On 10/02/2014 08:51 AM, Markus Armbruster wrote:
>> Each of qdev-monitor-test and blockdev-test has just one test case,
>> and both are about drive_del.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> tests/Makefile | 5 +--
>> tests/bloc
Eric Blake writes:
> On 10/02/2014 08:51 AM, Markus Armbruster wrote:
>> QMP accepts both single and double quotes. This is the only test
>> using double quotes. They need to be quoted in C strings. Replace
>> them by single quotes.
>
> Ooh, the use of single quotes on input is undocumented, a
Eric Blake writes:
> On 10/02/2014 08:51 AM, Markus Armbruster wrote:
>> Executed in this order, drive_del and device_del's automatic drive
>> deletion take notoriously tricky special paths.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> tests/drive_del-test.c | 32 ++
Can anyone tell me if in any QEMU release x-data-plane is considered "stable"?
If its unclear, I am referring to the feature introduced in QEMU 1.4 for high
performance disk I/O called virtio-blk data plane.
http://blog.vmsplice.net/2013/03/new-in-qemu-14-high-performance-virtio.html
I've tried
Il 02/10/2014 16:59, Markus Armbruster ha scritto:
> Andreas Färber writes:
>
>> Am 02.10.2014 um 16:21 schrieb Markus Armbruster:
>>> Andreas Färber writes:
>>>
Am 02.10.2014 um 15:21 schrieb Stefan Hajnoczi:
> On Wed, Oct 01, 2014 at 02:33:47PM +0200, Markus Armbruster wrote:
>> M
This adds synchronisation of the 6 vcpu registers (only 32bits of
them) that vmport.c needs between Xen and QEMU.
This is to avoid a 2nd and 3rd exchange between QEMU and Xen to
fetch and put these 6 vcpu registers used by the code in vmport.c
and vmmouse.c
Add new array to XenIOState that allows
Changes v1 to v2:
More info in commit message.
Stefano Stabellini
the registers being passes explicitely by Xen rather than
"hiding" them into other ioreq fields.
Added vmware_ioreq_t
Paolo Bonzini & Alexander Graf
Fixup env access
Added cpu_by_ioreq_id.
Set c
Hello.
I'd like to ask if it would be possible to add support for at least one
model of WiFi device on guest machines?
I realize the feature request has been discussed previously (here:
http://lists.nongnu.org/archive/html/qemu-devel/2007-03/msg00575.html ), but
my reason for wanting it is sligh
Hello,
On Thu, Oct 2, 2014 at 10:14 PM, Васил Рангелов wrote:
> Hello.
>
> I'd like to ask if it would be possible to add support for at least one
> model of WiFi device on guest machines?
USB and/or PCI passthorugh might help here, or am I getting something wrong?
>
>
> I realize the feature r
Hi.
A USB/PCI device that is passed through to the VM would get a real WiFi inside
a VM, but doing THAT would place the VM in a *real* wireless network.
The problem is that's not the goal.
The goal is to introduce a WiFi into a *virtual* wireless network, i.e. a WiFi
network between this VM an
Hello.
I'd like to ask if it would be possible to add support for at least one
model of WiFi device on guest machines?
I realize the feature request has been discussed previously (here:
http://lists.nongnu.org/archive/html/qemu-devel/2007-03/msg00575.html ), but
my reason for wanting it is sligh
Public bug reported:
Under certain circumstances, QEMU 2.1.2 fails to discard the underlaying
block. The command to start QEMU is:
qemu-system-x86_64 -machine pc,accel=kvm -m 2G -smp 2 -vga std -usb
-usbdevice tablet -drive if=none,id=ff,aio=native,discard=unmap,detect-
zeroes=unmap,file=/tmp/tes
Note that `cat /dev/zero` followed by `blkdiscard` has no issues.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1376938
Title:
detect-zeroes=unmap fails to discard in some cases
Status in QEMU:
Not a bug, Linux increases the Device ID each time a new device gets
hotplugged. If you need to use this option, pair it with already
connected drivers by parsing the output of lsusb for instance.
You can still use combinations of hostbus, vendorid, productid, etc.
** Changed in: qemu
Stat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/2014 07:56 PM, Alexey Kardashevskiy wrote:
> This extends use of VMS_ALLOC flag from arrays to VBUFFER as well.
>
> This defines VMSTATE_VBUFFER_ALLOC_UINT32 which makes use of
> VMS_ALLOC and uses uint32_t type for a size.
Adding Juan to c
On Thu, Oct 02, 2014 at 07:56:02PM +1000, Alexey Kardashevskiy wrote:
> This extends use of VMS_ALLOC flag from arrays to VBUFFER as well.
>
> This defines VMSTATE_VBUFFER_ALLOC_UINT32 which makes use of VMS_ALLOC
> and uses uint32_t type for a size.
>
> Signed-off-by: Alexey Kardashevskiy
Revi
On Thu, Oct 02, 2014 at 07:56:03PM +1000, Alexey Kardashevskiy wrote:
> The only case when sPAPR NVRAM migrates now is if is backed by a file and
> copy-storage migration is performed. In other cases NVRAM does not
> migrate regardless whether it is backed by a file or not.
>
> This enables shadow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/2014 12:52 AM, Stefan Hajnoczi wrote:
> On Thu, Oct 02, 2014 at 06:52:52PM +1000, Alexey Kardashevskiy wrote:
>> When migrated using libvirt with "--copy-storage-all", at the end
>> of migration there is race between NBD mirroring task trying
On 30 September 2014 17:55, Gerd Hoffmann wrote:
>
> On Di, 2014-09-30 at 10:27 +1000, Dave Airlie wrote:
>> > Triggered by the framebuffer endian issues we have with stdvga I've
>> > started to check where we stand with virtio-gpu and whenever we have to
>> > fix something in the virtio protocol
101 - 159 of 159 matches
Mail list logo
