On Wed, Mar 16, 2011 at 11:21:22AM +0100, Fabien Chouteau wrote:
>
> Signed-off-by: Fabien Chouteau
> ---
> target-ppc/translate.c | 201
> +++-
> 1 files changed, 197 insertions(+), 4 deletions(-)
Thanks, applied.
> diff --git a/target-ppc/transla
2011/3/18 Juan Quintela :
> Yoshiaki Tamura wrote:
>> Juan, Anthony,
>>
>> It seems this patch broke live migration in my environment. The guest
>> hangs after switching to remote. The following is parameters of the
>> guest.
>>
>> -L /usr/local/seabios --enable-kvm -M pc -m 512 -smp 1 -monitor
On Mon, Jan 31, 2011 at 03:11:01PM +0200, Gleb Natapov wrote:
> Currently linuxboot.bin and multiboot.bin option roms override int19
> vector to intercept boot process. No sane option rom should do that.
> Provide bev entry instead that will be called by BIOS if option rom
> is selected for booting
The nwnames field in TWALK message is assumed to be >=0 and <= MAXWELEM
which is defined as macro P9_MAXWELEM (16) in virtio-9p.h as per 9p2000 RFC.
Appropriate changes are required in V9fsWalkState and v9fs_walk.
v2:
- Added check in v9fs_walk_complete as well.
Signed-off-by: Harsh Prateek Bora
On Mon, Mar 21, 2011 at 09:19:56PM +, Peter Maydell wrote:
> On 21 March 2011 20:41, Aurelien Jarno wrote:
> > On Mon, Mar 07, 2011 at 11:10:32AM +, Peter Maydell wrote:
> >> + /* 0x4e00 LAN9118 Ethernet */
> >> + if (nd_table[0].vlan) {
> >> + lan9118_init(&nd_table[0], 0
On 03/21/2011 07:25 PM, Stefan Berger wrote:
On 03/15/2011 10:53 AM, Juan Quintela wrote:
commit 82fa39b75181b730d6d4d09f443bd26bcfcd045c
only contains half of the fix. It forgots the save state fix for
UINT8 indexes.
Anthony, please apply, without this migration using hpet is broken.
(only c
On Mon, Mar 21, 2011 at 04:10:22PM +0200, Michael S. Tsirkin wrote:
> > @@ -37,8 +37,27 @@
> >
> > typedef PCIHostState I440FXState;
> >
> > +#define PIIX_NUM_PIC_IRQS 16 /* i8259 * 2 */
> > +#define PIIX_NUM_PIRQS 4ULL/* PIRQ[A-D] */
>
> I've changed this to
> ((uint6
On 03/15/2011 10:53 AM, Juan Quintela wrote:
commit 82fa39b75181b730d6d4d09f443bd26bcfcd045c
only contains half of the fix. It forgots the save state fix for
UINT8 indexes.
Anthony, please apply, without this migration using hpet is broken.
(only current user).
I have just been bisecting the c
On Monday 21 Mar 2011 21:40:31 Stefan Hajnoczi wrote:
> > Yes, iPXE for UEFI exists and works. Last tested by me about a week ago,
> > on various IBM UEFI systems.
> >
> > Compared to a "legacy" BIOS network boot, you can't do anything very
> > interesting with UEFI. Features such as iSCSI, FCoE,
Hello,
I noticed that the layout of the PL050 keyboard used on Integrator/CP
incompatibly changed sometime between Qemu 0.10.5 and Qemu 0.11.1. The
current layout used in Qemu's model of Integrator/CP is the standard PC
layout. What puzzles me is whether this was a fix or a regression. Does
anybod
This devices uses libcacard (internal) to emulate a smartcard conforming
to the CAC standard. It attaches to the usb-ccid bus. Usage instructions
(example command lines) are in the following patch in docs/ccid.txt. It
uses libcacard which uses nss, so it can work with both hw cards and
certificates
The passthru ccid card is a device sitting on the usb-ccid bus and
using a chardevice to communicate with a remote device using the
VSCard protocol defined in libcacard/vscard_common.h
Usage docs available in following patch in docs/ccid.txt
Signed-off-by: Alon Levy
---
Changes from v20->v21:
Public bug reported:
Good time of day everybody,
I have been trying to make usermode qemu on ARM with plugapps
(archlinux) with archlinux i386 chroot to work.
1. I installed arch linux in a virtuabox and created a chroot for it with
mkarchroot. Transferred it to my pogo plug into /i386/
2. I co
From: Robert Relyea
client to talk to ccid-card-passthru and use smartcard on client to
perform actual operations.
---
libcacard/Makefile|7 +-
libcacard/vscclient.c | 730 +
2 files changed, 736 insertions(+), 1 deletions(-)
create mode
From: Robert Relyea
In this mode libcacard doesn't emulate a card, but just passes apdu's
straight to the underlying card.
Not to be confused with ccid-card-passthru, which doesn't use libcacard
at all. So with this functionality in libcacard you can talk directly
to the host accessible card, fo
Add documentation for the usb-ccid device and accompanying two card
devices, ccid-card-emulated and ccid-card-passthru.
Signed-off-by: Alon Levy
---
docs/ccid.txt | 135 +
1 files changed, 135 insertions(+), 0 deletions(-)
create mode 100
A CCID device is a smart card reader. It is a USB device, defined at [1].
This patch introduces the usb-ccid device that is a ccid bus. Next patches will
introduce two card types to use it, a passthru card and an emulated card.
[1] http://www.usb.org/developers/devclass_docs/DWG_Smart-Card_CCID_R
---
Signed-off-by: Alon Levy
v20->v21 changes: (Jes Sorenson review)
* license set to 2+
* long comment fixes, remove empty line at eof.
* add reference to COPYING
v19->v20 changes:
* checkpatch.pl
v15->v16 changes:
Protocol change:
* VSCMsgInit capabilities and magic
* removed ReaderRe
From: Robert Relyea
---
docs/libcacard.txt | 483
1 files changed, 483 insertions(+), 0 deletions(-)
create mode 100644 docs/libcacard.txt
diff --git a/docs/libcacard.txt b/docs/libcacard.txt
new file mode 100644
index 000..5dee6fa
---
This patchset adds three new devices, usb-ccid, ccid-card-passthru and
ccid-card-emulated, providing a CCID bus, a simple passthru protocol
implementing card requiring a client, and a standalone emulated card.
It also introduces a new directory libcaccard with CAC card emulation,
CAC is a type of
qemu-thread.h relies on uint64_t being defined, but doesn't include
inttypes.h explicitly. This makes it easier to use it from vscclient (part
of libcacard).
---
qemu-thread.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu-thread.h b/qemu-thread.h
index edc7ab6..0a7
---
Makefile | 32
Makefile.objs | 32
2 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/Makefile b/Makefile
index 89e88b4..209e14d 100644
--- a/Makefile
+++ b/Makefile
@@ -112,38 +112,6 @@ ui/vnc.o: QEMU_CFL
2011/3/21 Sébastien BRICE :
> Hi everyone
>
> I have been using qemu-kvm with success the last two years and its really
> amazing.
> I am new to this mailing list and i am requesting your assistance because i
> struggle to have my virtual card working with an 'exotic' virtual System
>
> seb@debian:
On 03/14/2011 03:13 PM, Alexander Graf wrote:
Hi guys,
While I was off on vacation a pretty nasty bug emerged. It's our old
friend the non-existent -cpu qemu64 CPU type. To refresh your memories,
this is the definition of the default 64-bit CPU type in Qemu:
{
.name = "qemu64",
On Mon, Mar 21, 2011 at 9:17 PM, Michael Brown wrote:
> On Monday 21 Mar 2011 21:06:24 Stefan Hajnoczi wrote:
>> On Mon, Mar 21, 2011 at 6:27 PM, Anthony Liguori
> wrote:
>> > On 03/21/2011 01:14 PM, Jordan Justen wrote:
>> >> This weekend I spent some time working on loading SeaBIOS from OVMF to
On 3/21/2011 2:34 PM, Venkateswararao Jujjuri (JV) wrote:
> On 3/21/2011 2:16 PM, Stefan Hajnoczi wrote:
>> On Mon, Mar 21, 2011 at 6:31 PM, Harsh Prateek Bora
>> wrote:
>>> The nwnames field in TWALK message is assumed to be >=0 and <= MAXWELEM
>>> which is defined as macro P9_MAXWELEM (16) in vi
On Mon, Mar 21, 2011 at 3:05 PM, Anthony Liguori wrote:
> 2) The daemon maintains metadata for each image that includes an extent
> mapping and then a clustered allocated bitmap within each extent (similar to
> FVD).
s/clustered allocated bitmap/cluster allocation bitmap/ ?
> 3) All writes resul
On 3/21/2011 2:16 PM, Stefan Hajnoczi wrote:
> On Mon, Mar 21, 2011 at 6:31 PM, Harsh Prateek Bora
> wrote:
>> The nwnames field in TWALK message is assumed to be >=0 and <= MAXWELEM
>> which is defined as macro P9_MAXWELEM (16) in virtio-9p.h as per 9p2000 RFC.
>> Appropriate changes are required
On Mon, Mar 21, 2011 at 14:17, Michael Brown wrote:
> On Monday 21 Mar 2011 21:06:24 Stefan Hajnoczi wrote:
>> On Mon, Mar 21, 2011 at 6:27 PM, Anthony Liguori
>> > Is there gPXE for UEFI yet?
>>
>> I have never tried it myself, but I think it should work. CCed
>> Michael Brown to check.
>
> Yes
On Mon, Mar 21, 2011 at 11:27, Anthony Liguori wrote:
> On 03/21/2011 01:14 PM, Jordan Justen wrote:
>>
>> This weekend I spent some time working on loading SeaBIOS from OVMF to
>> start a legacy boot. I was able to get x86& x86-64 Linux to legacy
>> boot using this method.
>>
>> Unfortunately,
On 21 March 2011 20:41, Aurelien Jarno wrote:
> On Mon, Mar 07, 2011 at 11:10:32AM +, Peter Maydell wrote:
>> + /* 0x4e00 LAN9118 Ethernet */
>> + if (nd_table[0].vlan) {
>> + lan9118_init(&nd_table[0], 0x4e00, pic[15]);
>> + }
>
> It basically means we silently ignore
On Monday 21 Mar 2011 21:06:24 Stefan Hajnoczi wrote:
> On Mon, Mar 21, 2011 at 6:27 PM, Anthony Liguori
wrote:
> > On 03/21/2011 01:14 PM, Jordan Justen wrote:
> >> This weekend I spent some time working on loading SeaBIOS from OVMF to
> >> start a legacy boot. I was able to get x86& x86-64 Li
On Mon, Mar 21, 2011 at 6:31 PM, Harsh Prateek Bora
wrote:
> The nwnames field in TWALK message is assumed to be >=0 and <= MAXWELEM
> which is defined as macro P9_MAXWELEM (16) in virtio-9p.h as per 9p2000 RFC.
> Appropriate changes are required in V9fsWalkState and v9fs_walk.
>
> Signed-off-by:
On Tue, Mar 08, 2011 at 07:54:39PM +0100, Andreas Färber wrote:
> Am 08.03.2011 um 09:29 schrieb Peter Maydell:
>
> >Maybe we should have a patchset that does the uncontroversial
> >change (bits32->uint32_t &c, which I think should be purely
> >mechanical) while we argue about this bit?
>
> That
On Mon, Mar 21, 2011 at 6:27 PM, Anthony Liguori wrote:
> On 03/21/2011 01:14 PM, Jordan Justen wrote:
>>
>> This weekend I spent some time working on loading SeaBIOS from OVMF to
>> start a legacy boot. I was able to get x86& x86-64 Linux to legacy
>> boot using this method.
>>
>> Unfortunately
On Tue, 22 Mar 2011 04:47:18 am Peter Maydell wrote:
> This fairly simple patchset adds a new 'max_ram' field to the QEMUMachine
> structure so that a board model can specify the maximum RAM it will accept.
> We can then produce a friendly diagnostic message when the user tries to
> start qemu with
On Mon, Mar 21, 2011 at 02:31:37PM +0100, Kevin Wolf wrote:
> Am 16.03.2011 11:47, schrieb Kevin Wolf:
> > The following changes since commit cc015e9a5dde2f03f123357fa060acbdfcd570a4:
> >
> > add Win32 IPI service (2011-03-13 14:44:22 +)
> >
> > are available in the git repository at:
> >
On Mon, Mar 21, 2011 at 02:35:32PM +0100, Paolo Bonzini wrote:
> On 03/14/2011 08:14 AM, Paolo Bonzini wrote:
> > On 03/13/2011 12:33 AM, Anthony Liguori wrote:
> >> Really nice series.
> >>
> >> The whole thing Reviewed-by: Anthony Liguori
> >>
> >> Did you really mean to RFC this? I don't think
On Mon, Mar 07, 2011 at 08:04:07PM +, Stefan Hajnoczi wrote:
> The PCI/PCI-X Family of Gigabit Ethernet Controllers Software
> Developer’s Manual states the following about the POPTS field:
>
> Provides a number of options which control the handling of this
> packet. This field is ignored
On Mon, Mar 07, 2011 at 11:10:32AM +, Peter Maydell wrote:
> Add a model of the ARM Versatile Express board (with A9MPx4
> daughterboard).
>
> Signed-off-by: Peter Maydell
> ---
> Makefile.target |1 +
> hw/vexpress.c | 224
> +++
>
On Mon, Mar 07, 2011 at 11:10:31AM +, Peter Maydell wrote:
> Add support for the Versatile Express SYS_CFG registers, which provide
> a generic means of reading or writing configuration information from
> various parts of the board. We only implement shutdown and reset.
>
> Also make the RESET
On 03/21/2011 12:47 PM, Peter Maydell wrote:
This fairly simple patchset adds a new 'max_ram' field to the QEMUMachine
structure so that a board model can specify the maximum RAM it will accept.
We can then produce a friendly diagnostic message when the user tries to
start qemu with a '-m' option
The nwnames field in TWALK message is assumed to be >=0 and <= MAXWELEM
which is defined as macro P9_MAXWELEM (16) in virtio-9p.h as per 9p2000 RFC.
Appropriate changes are required in V9fsWalkState and v9fs_walk.
Signed-off-by: Harsh Prateek Bora
---
hw/9pfs/virtio-9p.c |5 -
hw/9pfs/vi
On 03/21/2011 01:14 PM, Jordan Justen wrote:
This weekend I spent some time working on loading SeaBIOS from OVMF to
start a legacy boot. I was able to get x86& x86-64 Linux to legacy
boot using this method.
Unfortunately, (I think) it is not nearly as nice a having a true CSM.
Basically, you
This weekend I spent some time working on loading SeaBIOS from OVMF to
start a legacy boot. I was able to get x86 & x86-64 Linux to legacy
boot using this method.
Unfortunately, (I think) it is not nearly as nice a having a true CSM.
Basically, you have to decide at some point in the OVMF boot t
Allow boards to specify their maximum RAM size in the QEMUMachine struct.
This allows us to provide a useful diagnostic if the user tries to specify
a RAM size that the board cannot support.
Signed-off-by: Peter Maydell
---
hw/boards.h |1 +
vl.c| 16 +++-
2 files chang
Specify the maximum memory permitted for the various ARM devboard
models (integratorcp, realview-eb, realview-eb-mpcore, realview-pb-a8,
realview-pbx-a9, versatilepb, versatileab). This means we now handle
attempts to specify too much RAM gracefully rather than causing
the guest to crash in an obsc
This fairly simple patchset adds a new 'max_ram' field to the QEMUMachine
structure so that a board model can specify the maximum RAM it will accept.
We can then produce a friendly diagnostic message when the user tries to
start qemu with a '-m' option asking for more RAM than that. (Currently
most
Hi Jan,
I will send a patch.
Thanks
-Bharat
> -Original Message-
> From: Jan Kiszka [mailto:jan.kis...@siemens.com]
> Sent: Monday, March 21, 2011 5:04 PM
> To: Bhushan Bharat-R65777
> Cc: qemu-devel@nongnu.org
> Subject: Re: Query: gdbstub software breakpoint removal
>
> On 2011-03-21
On 03/21/2011 10:16 AM, Alexander Graf wrote:
On 21.03.2011, at 16:05, Anthony Liguori wrote:
5) Copy-on-write references potentially become very interesting for image
streaming because you can avoid any I/O for blocks that are already stored
locally.
This is not fully baked yet but I thoug
On 21.03.2011, at 16:05, Anthony Liguori wrote:
> We've been evaluating block migration in a real environment to try to
> understand what the overhead of it is compared to normal migration. The
> results so far are pretty disappointing. The speed of local disks ends up
> becoming a big bottl
On Wed, Mar 16, 2011 at 11:21:22AM +0100, Fabien Chouteau wrote:
> Signed-off-by: Fabien Chouteau
Reviewed-by: Nathan Froyd
-Nathan
We've been evaluating block migration in a real environment to try to
understand what the overhead of it is compared to normal migration. The
results so far are pretty disappointing. The speed of local disks ends
up becoming a big bottleneck even before the network does.
This has got me thin
On 21 March 2011 14:09, Nathan Froyd wrote:
> I'm just concerned about what would happen if we turned on softfloat's
> "float types are structure types" bit; I'm pretty sure everything would
> break horribly on targets that don't pass small structures in
> registers. Admittedly, several targets w
On Sat, Mar 19, 2011 at 10:24:52PM +0900, Isaku Yamahata wrote:
> optimize irq routing in piix_pic.c which has been a TODO.
> So far piix3 tracks each pirq level and checks whether a given pic pins is
> asserted by seeing if each pirq is mapped into the pic pin.
> This is independent on irq routing
On Mon, Mar 21, 2011 at 02:04:31PM +, Peter Maydell wrote:
> On 21 March 2011 13:48, Nathan Froyd wrote:
> > I like the direction this patch goes; you aren't by any chance going to
> > convert the passing/returning of float* to their appropriate int* types
> > too, are you?
>
> Nope -- I thin
On 21 March 2011 13:48, Nathan Froyd wrote:
> On Mon, Mar 14, 2011 at 05:23:11PM +, Peter Maydell wrote:
>> Correct the argument and return types for the float<->int conversion helper
>> functions so that integer arguments and return values are declared as
>> uint32_t/uint64_t, not float32/flo
On Mon, Mar 14, 2011 at 05:23:11PM +, Peter Maydell wrote:
> Correct the argument and return types for the float<->int conversion helper
> functions so that integer arguments and return values are declared as
> uint32_t/uint64_t, not float32/float64. This allows us to remove the
> hand-rolled f
Hi,
First, thanks for the report!
On Mon, Mar 21, 2011 at 12:09:10PM +, Peter Maydell wrote:
> == Talk 11: PRoot: A Step Forward for QEMU User-Mode ==
> STMicroelectronics again, presenting an alternative to the usual
> "chroot plus binfmt_misc" approach for running target binaries
> seamless
On 03/14/2011 08:14 AM, Paolo Bonzini wrote:
> On 03/13/2011 12:33 AM, Anthony Liguori wrote:
>> Really nice series.
>>
>> The whole thing Reviewed-by: Anthony Liguori
>>
>> Did you really mean to RFC this? I don't think there's any sort of
>> problem applying this as it's mostly mechanical.
>
>
Am 16.03.2011 11:47, schrieb Kevin Wolf:
> The following changes since commit cc015e9a5dde2f03f123357fa060acbdfcd570a4:
>
> add Win32 IPI service (2011-03-13 14:44:22 +)
>
> are available in the git repository at:
> git://repo.or.cz/qemu/kevin.git for-anthony
>
> Brian Wheeler (1):
>
Ack series
Acked-by: Hans de Goede
On 03/17/2011 03:49 PM, Alon Levy wrote:
This patchset adds three new devices, usb-ccid, ccid-card-passthru and
ccid-card-emulated, providing a CCID bus, a simple passthru protocol
implementing card requiring a client, and a standalone emulated card.
It also
On Mon, Mar 21, 2011 at 12:24 PM, Alon Levy wrote:
> Thanks, this should fix it:
>
> diff --git a/Makefile.target b/Makefile.target
> index baa5c3f..fef56b4 100644
> --- a/Makefile.target
> +++ b/Makefile.target
Thanks it fixes it. I didn't have libnss3-dev installed.
Stefan
On 03/21/2011 03:02 PM, Kevin Wolf wrote:
Am 21.03.2011 13:23, schrieb Avi Kivity:
> On 03/09/2011 07:38 PM, Anthony Liguori wrote:
>> On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
>>> On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
After a port unplug operation, the port->info->have_data() pointer was
set to NULL. The problem is, the ->info struct is shared by all ports,
effectively disabling writes to other ports.
Reported-by: juzhang
Signed-off-by: Amit Shah
---
hw/virtio-console.c |1 -
1 files changed, 0 insertio
After a hot-unplug operation, the previous behaviour was to close the
chardev. That meant the chardev couldn't be re-used. Also, since
chardev hot-plug isn't possible so far, this means virtio-console
hot-plug isn't feasible as well.
With this change, the chardev is kept around. A new virtio-co
Prevent:
-chardev socket,path=/tmp/foo,server,nowait,id=c0 \
-device virtserialport,chardev=c0,id=vs0 \
-device virtserialport,chardev=c0,id=vs1
Reported-by: Mike Cao
Signed-off-by: Amit Shah
---
hw/qdev-properties.c |7 ++-
qemu-char.c |4
qemu-char.h |1
Enable ioeventfd for virtio-serial devices by default. Commit
25db9ebe15125deb32958c6df74996f745edf1f9 lists the benefits of using
ioeventfd.
Copying a file from guest to host over a virtio-serial channel didn't
show much difference in time or io_exit rate.
Signed-off-by: Amit Shah
---
hw/virt
There's no code change, just re-arrangement to simplify the function
after recent modifications.
Reported-by: Juan Quintela
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 12 +++-
1 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/hw/virtio-serial-bus.c b/hw/virtio-
Port 0 is reserved for virtconsole devices for backward compatibility
with the old -virtioconsole (from qemu 0.12) device type.
libvirt prior to commit 8e28c5d40200b4c5d483bd585d237b9d870372e5 used
port 0 for generic ports. libvirt will no longer do that, but disallow
instantiating generic ports
Hello,
This series fixes a few bugs reported against virtio-serial. Please
apply.
The following changes since commit e0efb993b817564ef84e462ac1fe35f89b57ad7b:
Fix conversions from pointer to int and vice versa (2011-03-20 21:39:23 +)
are available in the git repository at:
git://git.ke
Instead of using a single variable to pass to the virtio_serial_init
function, use a struct so that expanding the number of variables to be
passed on later is easier.
Signed-off-by: Amit Shah
---
hw/virtio-pci.c| 12 ++--
hw/virtio-serial-bus.c | 16
hw/virti
On Mon, Mar 21, 2011 at 09:56:56PM +0900, Isaku Yamahata wrote:
> On Mon, Mar 21, 2011 at 02:31:11PM +0200, Michael S. Tsirkin wrote:
> > On Mon, Mar 21, 2011 at 09:10:32PM +0900, Isaku Yamahata wrote:
> > > On Mon, Mar 21, 2011 at 01:37:07PM +0200, Michael S. Tsirkin wrote:
> > > > > +static int p
Please, send in any agenda items you are interested in covening.
- Merge patches speed. I just "feel", that patches are not being
handled fast enough, so ... I looked how much patches have been
integrated since Mars 1st:
(master)$ g log --pretty=fuller ed02c54d1fd5d35c06e62e3dae84ee5bb90097
Am 21.03.2011 13:23, schrieb Avi Kivity:
> On 03/09/2011 07:38 PM, Anthony Liguori wrote:
>> On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
>>> On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
qemu ensures that guest writes and qemu metadata
On Mon, Mar 21, 2011 at 02:31:11PM +0200, Michael S. Tsirkin wrote:
> On Mon, Mar 21, 2011 at 09:10:32PM +0900, Isaku Yamahata wrote:
> > On Mon, Mar 21, 2011 at 01:37:07PM +0200, Michael S. Tsirkin wrote:
> > > > +static int piix3_post_load(void *opaque, int version_id)
> > > > +{
> > > > +PII
On Mon, Mar 21, 2011 at 11:52 AM, Ulrich Obergfell wrote:
>
> The following commit breaks the code of the function palette_destroy().
>
> http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=e31e3694afef58ba191cbcc6875ec243e5971268
>
> The broken code causes a severe memory leak of 'VncPalett
On 19.03.2011, at 23:30, Michael S. Tsirkin wrote:
> Commit c81131db15dd1844d0db1d51f3cd7a105cfd2cf3
> detects old guests by comparing virtio and
> PCI status. It attempts to do this on load,
> as well, but load_config callback in a binding
> is invoked too early and so the virtio status
> isn't
On Mon, Mar 21, 2011 at 09:10:32PM +0900, Isaku Yamahata wrote:
> On Mon, Mar 21, 2011 at 01:37:07PM +0200, Michael S. Tsirkin wrote:
> > > +static int piix3_post_load(void *opaque, int version_id)
> > > +{
> > > +PIIX3State *piix3 = opaque;
> > > +piix3_update_irq_levels(piix3);
> >
> > C
On Thu, Mar 17, 2011 at 5:23 PM, Alon Levy wrote:
> On Thu, Mar 17, 2011 at 04:45:15PM +, Stefan Hajnoczi wrote:
>> On Thu, Mar 17, 2011 at 3:00 PM, Alon Levy wrote:
>> > On Thu, Mar 17, 2011 at 04:49:26PM +0200, Alon Levy wrote:
>> >> ---
>> >> Makefile | 32 -
On Mon, Mar 21, 2011 at 01:37:07PM +0200, Michael S. Tsirkin wrote:
> > +/* irq routing is changed. so rebuild bitmap */
> > +static void piix3_update_irq_levels(PIIX3State *piix3)
> > +{
> > +int pirq;
> > +
> > +piix3->pic_levels = 0;
> > +for (pirq = 0; pirq < PIIX_NUM_PIRQS; pirq++)
On Mon, Mar 21, 2011 at 11:33:57AM +, Stefan Hajnoczi wrote:
> On Thu, Mar 17, 2011 at 2:49 PM, Alon Levy wrote:
> > This patchset adds three new devices, usb-ccid, ccid-card-passthru and
> > ccid-card-emulated, providing a CCID bus, a simple passthru protocol
> > implementing card requiring a
On 03/09/2011 07:38 PM, Anthony Liguori wrote:
On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
qemu ensures that guest writes and qemu metadata writes hit the
disk
when necessary to prevent data cor
On Mon, Mar 21, 2011 at 01:37:07PM +0200, Michael S. Tsirkin wrote:
> > +static int piix3_post_load(void *opaque, int version_id)
> > +{
> > +PIIX3State *piix3 = opaque;
> > +piix3_update_irq_levels(piix3);
>
> Couldn't figure out why would we not want to
> propagate the interrupts here.
>
I went to the first QEMU Users Forum in Grenoble last week;
this is my impressions and summary of what happened. I posted this
to linaro-toolchain and it was suggested that qemu-devel folks
might be interested in it too. Sorry if it's a bit TLDR...
== Summary and general observations ==
This was
On Mon, Mar 21, 2011 at 11:33:57AM +, Stefan Hajnoczi wrote:
> On Thu, Mar 17, 2011 at 2:49 PM, Alon Levy wrote:
> > This patchset adds three new devices, usb-ccid, ccid-card-passthru and
> > ccid-card-emulated, providing a CCID bus, a simple passthru protocol
> > implementing card requiring a
The following commit breaks the code of the function palette_destroy().
http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=e31e3694afef58ba191cbcc6875ec243e5971268
The broken code causes a severe memory leak of 'VncPalette' structures
because it never frees anything:
70 void palette
On Sat, Mar 19, 2011 at 10:24:52PM +0900, Isaku Yamahata wrote:
> optimize irq routing in piix_pic.c which has been a TODO.
> So far piix3 tracks each pirq level and checks whether a given pic pins is
> asserted by seeing if each pirq is mapped into the pic pin.
> This is independent on irq routing
On Thu, Mar 17, 2011 at 2:49 PM, Alon Levy wrote:
> This patchset adds three new devices, usb-ccid, ccid-card-passthru and
> ccid-card-emulated, providing a CCID bus, a simple passthru protocol
> implementing card requiring a client, and a standalone emulated card.
>
> It also introduces a new dir
On 2011-03-21 12:01, Bhushan Bharat-R65777 wrote:
> Hi All,
>
> I can see that the software breakpoint queue is cleared in
> kvm_remove_breakpoint() in kvm-all.c. I.e
> QTAILQ_REMOVE(¤t_env->kvm_state->kvm_sw_breakpoints, bp, entry); is
> called when the breakpoint is cleared.
>
> While the q
Hi All,
I can see that the software breakpoint queue is cleared in
kvm_remove_breakpoint() in kvm-all.c. I.e
QTAILQ_REMOVE(¤t_env->kvm_state->kvm_sw_breakpoints, bp, entry); is
called when the breakpoint is cleared.
While the queue is not cleared on kvm_remove_all_breakpoints();
Is there any
On 21.03.2011, at 11:33, René Rebe wrote:
> Fix applesmc REV key string literal hex encoding.
>
> Signed-off-by: René Rebe
Acked-by: Alexander Graf
Alex
>
> --- qemu-kvm-0.14.0/hw/applesmc.c.vanilla 2011-02-22 18:55:03.73225
> +
> +++ qemu-kvm-0.14.0/hw/applesmc.c 2011-02-
On 21.03.2011, at 11:18, René Rebe wrote:
> ppc64 is backward compatible, likewise.
>
> Signed-off-by: René Rebe
Acked-by: Alexander Graf
>
> --- qemu-0.14.0/configure 2011-02-16 14:44:04.0 +
> +++ qemu-0.14.0-fixed/configure 2011-03-18 16:46:14.0 +
> @@ -3
Fix applesmc REV key string literal hex encoding.
Signed-off-by: René Rebe
--- qemu-kvm-0.14.0/hw/applesmc.c.vanilla 2011-02-22 18:55:03.73225
+
+++ qemu-kvm-0.14.0/hw/applesmc.c 2011-02-22 18:56:08.89225 +
@@ -188,7 +188,7 @@
QLIST_REMOVE(d, node);
}
> Hi Ulrich,
> Looks a lot like "vnc: tight: Fix crash after 2GB of output", right ?
>
> --
> Corentin Chary
> http://xf.iksaif.net
Hi Corentin,
yes, this appears to be the same issue as:
http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg02044.html
You posted your patch only a few minut
ppc64 is backward compatible, likewise.
Signed-off-by: René Rebe
--- qemu-0.14.0/configure 2011-02-16 14:44:04.0 +
+++ qemu-0.14.0-fixed/configure 2011-03-18 16:46:14.0 +
@@ -3038,6 +3038,8 @@
\( "$target_arch2" = "$cpu" -o \
\( "$target_arch2" = "ppce
Signed-off-by: Jan Kiszka
---
default-configs/x86_64-softmmu.mak |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/default-configs/x86_64-softmmu.mak
b/default-configs/x86_64-softmmu.mak
index 59b7893..8895028 100644
--- a/default-configs/x86_64-softmmu.mak
+++ b/default-
Signed-off-by: Jan Kiszka
---
hw/vmmouse.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/vmmouse.c b/hw/vmmouse.c
index ab8dbd6..1113f33 100644
--- a/hw/vmmouse.c
+++ b/hw/vmmouse.c
@@ -265,7 +265,6 @@ static int vmmouse_initfn(ISADevice *dev)
vmport_register(V
Latest refactorings left vmmouse nonfunctional behind. Fix it by adding
the required device initialization.
Signed-off-by: Jan Kiszka
---
hw/pc.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 4d67d9f..6939c04 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@
On Mon, Mar 21, 2011 at 9:18 AM, Corentin Chary
wrote:
> On Mon, Mar 21, 2011 at 9:08 AM, Alexander Graf wrote:
>> Hi Devang,
>>
>> On 21.03.2011, at 09:17, Devang S wrote:
>>
>> Hello,
>>
>> This year i am not eligible to participate in gsoc. But really want to
>> contribute to qemu project.
>>
1 - 100 of 113 matches
Mail list logo
