CURL library API has changed, the current curl driver is not working.
This patch rewrites the use of API as well as the structure of internal
states.
BDRVCURLState holds the pointer to curl multi interface (man 3
libcurl-multi), and 4 lists for internal states:
- CURLState holds state for libcur
We use socket provided by curl in the driver. Libcurl multi interface
has option CURLMOPT_SOCKETFUNCTION for socket.
Per man 3 curl_multi_setopt:
...
CURLMOPT_SOCKETFUNCTION
Pass a pointer to a function matching the curl_socket_callback
prototype. The curl_multi_socket_action(3)
String field length is duplicated in two places. Make it a sizeof.
Signed-off-by: Fam Zheng
---
block/curl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/curl.c b/block/curl.c
index 0aede58..901deb2 100644
--- a/block/curl.c
+++ b/block/curl.c
@@ -567,7 +567,7 @@ sta
The driver calls curl_multi_do to take action at several points, while
it's also registered as socket fd handler. This patch removes internal
call of curl_multi_do because they are not necessary when handler can be
called by socket data update.
Since curl_multi_do becomes a pure fd handler, the fu
Added an option to let curl disable ssl certificate check.
Signed-off-by: Fam Zheng
---
block/curl.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/block/curl.c b/block/curl.c
index f4e2571..9352c6c 100644
--- a/block/curl.c
+++ b/block/curl.c
@@ -95,6 +95,8 @@
Change curl_size_cb to curl_header_cb, as what the function is really
doing. Fix the registering, CURLOPT_WRITEFUNCTION is apparently wrong,
should be CURLOPT_HEADERFUNCTION.
Parsing size from header is not necessary as we're using
curl_easy_getinfo(state->curl, CURLINFO_CONTENT_LENGTH_DOWNLOAD
libcurl uses timer to manage ongoing sockets, it needs us to supply
timer. This patch introduce QEMUTimer to BDRVCURLState and handles
timeouts as libcurl expects (curl_multi_timer_cb sets given timeout
value on the timer and curl_timer_cb calls curl_multi_socket_action on
triggered).
Signed-off-b
Introduce a cache quota: BDRVCURLState.cache_quota.
When adding new CURLDataCache to BDRVCURLState, if number of existing
CURLDataCache is larger than CURL_CACHE_QUOTA, try to release some first
to limit the in memory cache size.
A least used entry is selected for releasing.
Signed-off-by: Fam Zh
Data buffer was contained by CURLState, they are allocated and freed
together. This patch try to isolate them, by introducing a dedicated
cache list to BDRVCURLState. The benifit is we can now release the
CURLState (and associated sockets) while keep the fetched data for later
use, and simplies the
Make subsequecial changes to make use of introduced CURLDataCache. Moved
acb struct from CURLState to BDRVCURLState, and changed to list.
Signed-off-by: Fam Zheng
---
block/curl.c | 156 +--
1 file changed, 78 insertions(+), 78 deletions(-)
Make it consistent to other structures to use QLIST to store CURLState.
It also simplifies initialization and releasing of data.
Signed-off-by: Fam Zheng
---
block/curl.c | 95
1 file changed, 50 insertions(+), 45 deletions(-)
diff --
Il 20/05/2013 08:24, Stefan Hajnoczi ha scritto:
>> > You only need to fdatasync() before every guest flush, no?
> No, you need to set the dirty bit before issuing the write on the
> host. Otherwise the image data may be modified without setting the
> appropriate dirty bit. That would allow data
On 20 May 2013 07:17, Stefan Hajnoczi wrote:
> If you are not trying to do an out-of-tree build then maybe the
> Makefile is buggy here on Mac OS X:
> ifneq ($(realpath $(SRC_PATH)),$(realpath .))
manooth$ realpath
-bash: realpath: command not found
...might be why this rune does not work on Mac
On 20 May 2013 09:11, Peter Maydell wrote:
> On 20 May 2013 07:17, Stefan Hajnoczi wrote:
>> If you are not trying to do an out-of-tree build then maybe the
>> Makefile is buggy here on Mac OS X:
>> ifneq ($(realpath $(SRC_PATH)),$(realpath .))
>
> manooth$ realpath
> -bash: realpath: command not
From: Dmitry Fleytman
Virtio-net driver currently negotiates network offloads
on startup via features mechanism and have no ability to
disable and re-enable offloads later.
This patch introduced a new control command that allows
to configure device network offloads state dynamically.
The patch al
On Mon, May 20, 2013 at 03:03:34PM +0800, Fam Zheng wrote:
> CURL library API has changed, the current curl driver is not working.
> This patch rewrites the use of API as well as the structure of internal
> states.
I tried this, but it segfaults:
Program terminated with signal 11, Segmentation f
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode can't fork (bash: fork: Invalid argument)
Status in QEMU:
Conf
Signed-off-by: Lei Li
---
linux-user/syscall.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 30e93bc..72c6866 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -8236,7 +8236,7 @@ abi_long do_syscall(void *
On Mon, May 20, 2013 at 09:41:06AM +0100, Richard W.M. Jones wrote:
> On Mon, May 20, 2013 at 03:03:34PM +0800, Fam Zheng wrote:
> > CURL library API has changed, the current curl driver is not working.
> > This patch rewrites the use of API as well as the structure of internal
> > states.
>
> I
Michael Tokarev writes:
> Rehashing an old thread again...
>
> 28.02.2013 21:25, M. Mohan Kumar wrote:
>> Michael Tokarev writes:
>>
>>
>>> 28.02.2013 17:55, M. Mohan Kumar wrote:
Michael Tokarev writes:
Hi,
Please try mounting with -oversion=9p2000.L
With q
Commit e7a09b92b70786f9e8c5fbf787e0248c6ebbe707 added a trace at each
memory freeing, but unfortunately inverted size and pointer when printing
them. Fix trace.
This also led to a compilation error on 32 bit hosts:
In file included from include/trace.h:4:0,
from trace/generated-ev
Il 07/05/2013 20:08, Peter Maydell ha scritto:
>> >
>> > -section = phys_page_find(address_space_memory.dispatch, addr >>
>> > TARGET_PAGE_BITS);
>> > +section = address_space_translate(&address_space_memory, addr, &addr,
>> > &l,
>> > + false);
> I fi
Il 20/05/2013 08:51, Lei Li ha scritto:
> When register and open a chardev udp, the backend name should be udp
> not dgram, and we do not have backend dgram in the chardev list. This
> patch makes the new qapi udp backend consistent with the original
> udp device.
This changes the QMP API, so it
Il 20/05/2013 08:51, Lei Li ha scritto:
> Now we have ringbuf char device, but the backend name of it
> is a little confusion. We actually register it by 'memory', but
> the description in qemu-option, the name of open functions
> and the new api backend called it 'ringbuf'. It should keep
> consis
From: Hu Tao
This fixes a problem that after guest panic happens, virsh dump without
--memory-only fails:
ERROR: invalid runstate transition: 'guest-panicked' -> 'finish-migrate'
Reported-by: Christian Borntraeger
Cc: qemu-sta...@nongnu.org
Signed-off-by: Hu Tao
Signed-off-by: Paolo Bonzini
Il 20/05/2013 10:18, Michael S. Tsirkin ha scritto:
> diff --git a/include/hw/virtio/virtio-net.h b/include/hw/virtio/virtio-net.h
> index beeead7..b315ac9 100644
> --- a/include/hw/virtio/virtio-net.h
> +++ b/include/hw/virtio/virtio-net.h
> @@ -31,6 +31,8 @@
> /* The feature bitmap for virtio ne
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
Il 20/05/2013 12:43, Paolo Bonzini ha scritto:
> Il 20/05/2013 08:51, Lei Li ha scritto:
>> Now we have ringbuf char device, but the backend name of it
>> is a little confusion. We actually register it by 'memory', but
>> the description in qemu-option, the name of open functions
>> and the new api
I see the following patches on the list that IMO deserve inclusion into
1.5. All of them should be low-risk.
<1368718348-15199-1-git-send-email-ema...@freebsd.org>
[PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict
<1369046780-17498-1-git-send-email-pbonz...@redhat.com>
[PATCH for-1.5 r
Hi Alex,
Alex Williamson wrote:
> On Sun, 2013-05-19 at 23:26 +0400, Maik Broemme wrote:
> > Hi Knut,
> >
> > Knut Omang wrote:
> > >
> > > On Mon, 2013-05-13 at 16:23 -0600, Alex Williamson wrote:
> > > > On Mon, 2013-05-13 at 22:55 +0200, Knut Omang wrote:
> > > > > Hi all,
> > > > >
> > >
Tray statuses should be also reset. Some guests may lock the tray and
right after resetting the guest it should be unlocked and closed. This
is done on power-on, reset and resume from suspend/hibernate on bare-metal.
This fix is already committed for IDE CD.
Check the commit a7f3d65b65b8c86a5ff0c0
Am 20.05.2013 11:20, schrieb Lei Li:
> Signed-off-by: Lei Li
> ---
> linux-user/syscall.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 30e93bc..72c6866 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/sysc
Am 20.05.2013 12:33, schrieb Hervé Poussineau:
> Commit e7a09b92b70786f9e8c5fbf787e0248c6ebbe707 added a trace at each
> memory freeing, but unfortunately inverted size and pointer when printing
> them. Fix trace.
>
> This also led to a compilation error on 32 bit hosts:
> In file included from inc
Il 20/05/2013 13:06, Pavel Hrdina ha scritto:
> Tray statuses should be also reset. Some guests may lock the tray and
> right after resetting the guest it should be unlocked and closed. This
> is done on power-on, reset and resume from suspend/hibernate on bare-metal.
>
> This fix is already commi
Am 20.05.2013 13:00, schrieb Paolo Bonzini:
> I see the following patches on the list that IMO deserve inclusion into
> 1.5. All of them should be low-risk.
>
> <1368718348-15199-1-git-send-email-ema...@freebsd.org>
> [PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict
>
> <1369046780-1749
Il 15/05/2013 16:34, Stefan Hajnoczi ha scritto:
> +wait_for_overlapping_requests(job, start, end);
> +cow_request_begin(&cow_request, job, start, end);
> +
> +for (; start < end; start++) {
> +if (hbitmap_get(job->bitmap, start)) {
> +DPRINTF("brdv_co_backup_cow ski
Il 20/05/2013 13:28, Stefan Weil ha scritto:
> Am 20.05.2013 13:00, schrieb Paolo Bonzini:
>> I see the following patches on the list that IMO deserve inclusion into
>> 1.5. All of them should be low-risk.
>>
>> <1368718348-15199-1-git-send-email-ema...@freebsd.org>
>> [PATCH v2] Rename hexdump to
On 18 May 2013 13:02, Stefan Weil wrote:
> Macro MOD_SHIFT is also defined in imm.h:
>
> /qemu/hw/arm/spitz.c:280:1: warning: "MOD_SHIFT" redefined
> /usr/lib/gcc/amd64-mingw32msvc/4.4.4/../../../../amd64-mingw32msvc/include/imm.h:309:1:
> warning: this is the location of the previous definition
Paolo Bonzini writes:
> I see the following patches on the list that IMO deserve inclusion into
> 1.5. All of them should be low-risk.
>
> <1368718348-15199-1-git-send-email-ema...@freebsd.org>
> [PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict
Ack.
> <1369046780-17498-1-git-send-em
Paolo Bonzini writes:
> Il 20/05/2013 13:28, Stefan Weil ha scritto:
>> Am 20.05.2013 13:00, schrieb Paolo Bonzini:
>>> I see the following patches on the list that IMO deserve inclusion into
>>> 1.5. All of them should be low-risk.
>>>
>>> <1368718348-15199-1-git-send-email-ema...@freebsd.org>
On 17 May 2013 14:23, Peter Maydell wrote:
> target-arm/Makefile.objs |1 +
> target-arm/kvm.c | 164
> +-
> target-arm/kvm_arm.h | 33 ++
> target-arm/machine.c | 30 +++--
> 4 files changed, 222 insertions(+), 6
On Mon, May 20, 2013 at 01:00:56PM +0200, Paolo Bonzini wrote:
> I see the following patches on the list that IMO deserve inclusion into
> 1.5. All of them should be low-risk.
>
> <1368718348-15199-1-git-send-email-ema...@freebsd.org>
> [PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict
"Michael S. Tsirkin" writes:
> On Mon, May 13, 2013 at 02:20:02PM -0600, Alex Williamson wrote:
>> To support guest MSI affinity changes update the MSI message any time
>> the guest writes to the address or data fields.
>>
>> Signed-off-by: Alex Williamson
>
> Seems the only way we can fix this
On 14 May 2013 05:32, John Rigby wrote:
> @@ -10038,6 +10042,11 @@ void cpu_dump_state(CPUARMState *env, FILE *f,
> fprintf_function cpu_fprintf,
> int i;
> uint32_t psr;
>
> +if (is_a64(env)) {
> +cpu_dump_state_a64(env, f, cpu_fprintf, flags);
> +return;
> +}
>
On Mon, May 20, 2013 at 07:51:40AM -0500, Anthony Liguori wrote:
> "Michael S. Tsirkin" writes:
>
> > On Mon, May 13, 2013 at 02:20:02PM -0600, Alex Williamson wrote:
> >> To support guest MSI affinity changes update the MSI message any time
> >> the guest writes to the address or data fields.
>
On Mon, May 20, 2013 at 12:57:47PM +0200, Juan Quintela wrote:
>
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Thanks, Juan.
Generating acpi tables.
Cc'd a bunch of people who might be interested in this topic.
Kevin - could you join on Tuesday? There appears a disc
On Mon, May 20, 2013 at 12:52:57PM +0200, Paolo Bonzini wrote:
> Il 20/05/2013 10:18, Michael S. Tsirkin ha scritto:
> > diff --git a/include/hw/virtio/virtio-net.h b/include/hw/virtio/virtio-net.h
> > index beeead7..b315ac9 100644
> > --- a/include/hw/virtio/virtio-net.h
> > +++ b/include/hw/virti
Il 20/05/2013 15:36, Michael S. Tsirkin ha scritto:
> On Mon, May 20, 2013 at 12:52:57PM +0200, Paolo Bonzini wrote:
>> Il 20/05/2013 10:18, Michael S. Tsirkin ha scritto:
>>> diff --git a/include/hw/virtio/virtio-net.h b/include/hw/virtio/virtio-net.h
>>> index beeead7..b315ac9 100644
>>> --- a/in
Il 04/04/2013 09:55, Dmitry Fleytman ha scritto:
> From: Dmitry Fleytman
>
> Virtio-net driver currently negotiates network offloads
> on startup via features mechanism and have no ability to
> disable and re-enable offloads later.
> This patch introduced a new control command that allows
> to co
On Mon, May 20, 2013 at 03:39:33PM +0200, Paolo Bonzini wrote:
> Il 20/05/2013 15:36, Michael S. Tsirkin ha scritto:
> > On Mon, May 20, 2013 at 12:52:57PM +0200, Paolo Bonzini wrote:
> >> Il 20/05/2013 10:18, Michael S. Tsirkin ha scritto:
> >>> diff --git a/include/hw/virtio/virtio-net.h
> >>> b
On Mon, May 20, 2013 at 03:43:51PM +0200, Paolo Bonzini wrote:
> Il 04/04/2013 09:55, Dmitry Fleytman ha scritto:
> > From: Dmitry Fleytman
> >
> > Virtio-net driver currently negotiates network offloads
> > on startup via features mechanism and have no ability to
> > disable and re-enable offloa
"Michael S. Tsirkin" writes:
> On Mon, May 20, 2013 at 12:52:57PM +0200, Paolo Bonzini wrote:
>> Il 20/05/2013 10:18, Michael S. Tsirkin ha scritto:
>> > diff --git a/include/hw/virtio/virtio-net.h
>> > b/include/hw/virtio/virtio-net.h
>> > index beeead7..b315ac9 100644
>> > --- a/include/hw/vir
> So I rebased this patch myself, but don't have the latest windows
> driver bits to test it.
> Dmitry, could you please test and report on list?
>
> Thanks!
Michael, many thanks for this rebase.
I've tested this diff on latest windows driver with corresponding
patches and it works as expected.
On 05/20/2013 12:51 AM, Lei Li wrote:
> When register and open a chardev udp, the backend name should be udp
> not dgram, and we do not have backend dgram in the chardev list. This
> patch makes the new qapi udp backend consistent with the original
> udp device.
>
> Signed-off-by: Lei Li
> ---
>
Am 20.05.2013 14:25, schrieb Anthony Liguori:
> Paolo Bonzini writes:
>
>> Il 20/05/2013 13:28, Stefan Weil ha scritto:
>>> Am 20.05.2013 13:00, schrieb Paolo Bonzini:
I see the following patches on the list that IMO deserve inclusion into
1.5. All of them should be low-risk.
On 05/20/2013 04:59 AM, Paolo Bonzini wrote:
> Il 20/05/2013 12:43, Paolo Bonzini ha scritto:
>> Il 20/05/2013 08:51, Lei Li ha scritto:
>>> Now we have ringbuf char device, but the backend name of it
>>> is a little confusion. We actually register it by 'memory', but
>>> the description in qemu-op
On 05/20/2013 05:00 AM, Paolo Bonzini wrote:
> I see the following patches on the list that IMO deserve inclusion into
> 1.5. All of them should be low-risk.
>
> <1368718348-15199-1-git-send-email-ema...@freebsd.org>
> [PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict
>
> <1369046780-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 20/05/2013 17:05, Eric Blake ha scritto:
> On 05/20/2013 04:59 AM, Paolo Bonzini wrote:
>> Il 20/05/2013 12:43, Paolo Bonzini ha scritto:
>>> Il 20/05/2013 08:51, Lei Li ha scritto:
Now we have ringbuf char device, but the backend name of it
>
If the user specifies a target list themselves, check each entry
to make sure it's a target we recognise. This allows us to print
a helpful error message, rather than falling through (where we
would probably eventually end up hitting the uninformative
"ERROR: Unsupported target CPU").
Signed-off-b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 20/05/2013 17:07, Eric Blake ha scritto:
> On 05/20/2013 05:00 AM, Paolo Bonzini wrote:
>> I see the following patches on the list that IMO deserve
>> inclusion into 1.5. All of them should be low-risk.
>>
>> <1368718348-15199-1-git-send-email-ema
These patches clean up configure's handling of the list of known
targets. Firstly we autogenerate the default list based on the
set of default-config files; this reduces by 1 the number of
places that need editing when a new target is added to QEMU.
Secondly we improve the quality of our error mess
Autogenerate the default target list based on what files exist
in default-configs; this allows us to remove one of the places
that has to be kept up to date with a complete list of every
target we support.
Signed-off-by: Peter Maydell
---
configure | 84 +++-
On 19 May 2013, at 23:20, Peter Maydell wrote:
> On 19 May 2013 21:09, Mark Burton wrote:
>>Note - what I understand by a basic block is something that ends in a
>> jump/branch of some description. Hence, one thing I think you can say about a
>> basic block is that each PC value within
Until proper patch is available I'm using attached temp workaround.
After some testing GHC and produced executables appear to work correctly
in foreign arch chroot.
I'm sure there will be issues but I only need compilation to work in
foreign arch chroot because I will deploy produced executables
I think I am seeing the same symptoms when I let two QEMU instances talk
to each other over pipe serial.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1181796
Title:
Qemu locks up when incoming ser
On 19 May 2013, at 23:39, Rob Landley wrote:
> On 05/19/2013 03:09:14 PM, Mark Burton wrote:
>> Spot on Peter,
>> The (simplistic) plan is simply to take a snapshot at regular intervals,
>> when you want to step backwards, you return to a snapshot, and then re-run
>> forwards to 'just before yo
Hi,
On behalf of the QEMU Team, I'd like to announce the availability of the
QEMU 1.5.0 release!
http://wiki.qemu.org/download/qemu-1.5.0.tar.bz2
This release was developed in a little more than 90 days by over 130
unique authors averaging 20 commits a day. This represents a
year-to-year growth
Hi,
Am 20.05.2013 04:33, schrieb Peter Cheung:
> Hi all
> I have this problem in my Mac
>
> /Users/peter/workspace/qemu_latest>make
> Makefile:16: *** This is an out of tree build but your source tree
> (/Users/peter/workspace/qemu_latest) seems to have been used for an
> in-tree build. You c
Hello Pavel,
Am 19.05.2013 21:06, schrieb Pavel Pisa:
> On Sunday 19 May 2013 20:23:55 Andreas Färber wrote:
>> Am 18.05.2013 20:24, schrieb Rempel, Cynthia:
> The RTEMS development community is considering having a Google Summer
> of Code student test LinCAN on a simulated RTEMS target bo
Let the patches and pull requests start flowing! :-)
Regards,
Anthony Liguori
Reformat the qapi-schema TargetType enumeration so that it has just
one target architecture name per line. This allows patches for
adding new targets to just add a single line, rather than having
to reformat most of the list (resulting in a hard-to-check diff).
Signed-off-by: Peter Maydell
---
d1
On Sat, May 18, 2013 at 06:31:47AM +0200, Laszlo Ersek wrote:
> Qouting patch 2/6:
>
> > Since commit 39097daf ("qemu-ga: use key-value store to avoid
> > recycling fd handles after restart") we've relied on the state
> > directory for the fd handles' key-value store. Even though we don't
> > supp
Il 20/05/2013 18:21, Peter Maydell ha scritto:
> Reformat the qapi-schema TargetType enumeration so that it has just
> one target architecture name per line. This allows patches for
> adding new targets to just add a single line, rather than having
> to reformat most of the list (resulting in a har
On 20 May 2013 17:41, Eric Blake wrote:
> Yep, that raises (once again) the question of dynamic introspection -
> there's a difference between the maximum amount of information known at
> compile time, and the subset of enum values that are actually usable at
> runtime. This list is static (all k
On 05/20/2013 10:47 AM, Peter Maydell wrote:
> On 20 May 2013 17:41, Eric Blake wrote:
>> Yep, that raises (once again) the question of dynamic introspection -
>> there's a difference between the maximum amount of information known at
>> compile time, and the subset of enum values that are actuall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 20/05/2013 18:57, Eric Blake ha scritto:
> Changing the name of an architecture would be reflected by having
> a different qemu-FOO binary name, right? If that's the case, then
> introspection of which architectures are supported is done by
> list
Linux actually doesn't have definitions for the individual L0s and L1 bits
in Link Capabilities, but if/when it does, it will use these names, which
follow the Link Control naming pattern.
Signed-off-by: Bjorn Helgaas
---
hw/pci/pcie.c |2 +-
include/hw/pci/pcie_regs.h |3 +-
Indicate ASPM L0s and L1 support in Link Capabilities and make the ASPM
bits in Link Control writable. These Link Control bits don't do anything
in qemu, but having them writable means the BIOS or OS can write them as
on real hardware.
Signed-off-by: Bjorn Helgaas
---
hw/pci/pcie.c
On 20 May 2013 17:35, Paolo Bonzini wrote:
> Il 20/05/2013 18:21, Peter Maydell ha scritto:
>> Reformat the qapi-schema TargetType enumeration
> I have queued a patch for 1.6 that would change this field to a free
> string. There is no use of this enum, not even for introspection. You
> don't n
Il 20/05/2013 18:38, Peter Maydell ha scritto:
>> > I have queued a patch for 1.6 that would change this field to a free
>> > string. There is no use of this enum, not even for introspection. You
>> > don't need to know what targets were supported in the version that you
>> > compiled from. Only
On 05/20/2013 10:21 AM, Peter Maydell wrote:
> Reformat the qapi-schema TargetType enumeration so that it has just
> one target architecture name per line. This allows patches for
> adding new targets to just add a single line, rather than having
> to reformat most of the list (resulting in a hard-
On 05/19/2013 09:30 AM, Ed Maste wrote:
> On 19 May 2013 10:51, in a thread relating to the sparc-linux-user
> linker script, Michael Tokarev wrote:
>> If we apply this for 1.5, it will be the first release of debian
>> package without extra fixes. Hopefully anyway :)
>>
>> (Ofcourse we may add m
We have three variables currently in config-target.h:
- TARGET_ARCH is used to create a unique per-arch symbol, used in #ifdefs.
It is also used as a string through config-target.h, but this is almost
always wrong.
- TARGET_ARCH2 is the name of the executable (minus the qemu-/qemu-system-
p
On Sun, May 19, 2013 at 5:54 AM, Michael S. Tsirkin wrote:
> On Wed, May 15, 2013 at 04:33:08PM -0600, Bjorn Helgaas wrote:
>> Indicate ASPM L0s and L1 support in Link Capabilities and make the ASPM
>> bits in Link Control writable. These Link Control bits don't do anything
>> in qemu, but having
"Aneesh Kumar K.V" writes:
> Michael Tokarev writes:
>
>> Rehashing an old thread again...
>>
>> 28.02.2013 21:25, M. Mohan Kumar wrote:
>>> Michael Tokarev writes:
>>>
>>>
28.02.2013 17:55, M. Mohan Kumar wrote:
> Michael Tokarev writes:
>
> Hi,
>
> Please try mount
From: "Aneesh Kumar K.V"
With mapped security models like mapped-xattr and mapped-file, we save the
symlink target as file contents. Now if we ever expose a normal directory
with mapped security model and find real symlinks in export path, never
follow them and return proper error.
Signed-off-by
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1179104
Title:
client crash during debian ppc installation
Status in QEMU:
Fix Released
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1169856
Title:
OpenBIOS seek fails on NetBSD CD image
Status in QEMU:
Fix Released
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1169375
Title:
qemu.git master -> qemu segfaults during tcp migration (and other
mod
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1166954
Title:
Error compiling qemu due to missing
Status in QEMU:
Fix Released
Bu
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1075252
Title:
qemu-img cannot read VMDK4 file
Status in QEMU:
Fix Released
Bug d
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1154328
Title:
qemu locks up on typing 41 characters at once into serial console
Stat
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1110531
Title:
regression booting pxa kernels
Status in QEMU:
Fix Released
Bug des
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1127369
Title:
i386 emulation unreliable since commit
b76f0d8c2e3eac94bc7fd90a510cb7
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1169254
Title:
latest qemu.git master -> qemu-system-x86_64 crashes when issuing
scr
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1091241
Title:
NetBSD/i386 6.0 guest suffers interrupt storm since qemu BIOS update
S
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1089996
Title:
Recent floppy boot regression in qemu-system-i386
Status in QEMU:
F
"Aneesh Kumar K.V" writes:
> From: "Aneesh Kumar K.V"
>
> With mapped security models like mapped-xattr and mapped-file, we save the
> symlink target as file contents. Now if we ever expose a normal directory
> with mapped security model and find real symlinks in export path, never
> follow them
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1073585
Title:
Deleting UDP socket in monitor mode
Status in QEMU:
Fix Released
Bu
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1058225
Title:
When setting hardware clock on linux guest, hwclock shows crazy date
1 - 100 of 151 matches
Mail list logo
