I was considering attempting to contribute some time to QEMU, but have been
unable to locate any information about how the project is organized or how to
go about getting involved. All I managed to find was this mailing list. Could
someone point me to the appropriate location or possibly who to
BTW what happened to qemu-commit?
It deosn't seem to be working.
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
> Hi,
>
> Could someone with commit rights please stand up to feel responsible for
> PPC?
>
> Usually, when I send a patch to qemu-devel, I know who to address to
> i
On Fri, Dec 04, 2009 at 08:09:35AM -0600, Anthony Liguori wrote:
> Isaku Yamahata wrote:
>> This is the preparation patch for q35 chipset and PCIE support.
>> Anthony, any chance to merge? Can you please give me comments?
>>
>
> I'd like to see Michael review the PCI changes and Gerd review the
On 04.12.2009, at 18:47, Paul Brook wrote:
> On Monday 30 November 2009, Alexander Graf wrote:
>> Currently we have this stupid role of disallowing:
>>
>> if (r)
>> break;
>
> This has been discussed to death several times, in several different paces,
> and with no clear resolution or co
Paul Brook wrote:
On Monday 30 November 2009, Alexander Graf wrote:
Currently we have this stupid role of disallowing:
if (r)
break;
This has been discussed to death several times, in several different paces,
and with no clear resolution or consensus, so I'm going to make an
Richard W.M. Jones wrote:
The idea would be for management tools (eg. libvirt) to add the lock
parameter for all virtual machines that they manage.
I don't see how this is worse than what we have now -- ie. no
possibility of locking at all and a very real risk of disk corruption.
Anyway, we cou
From: Riku Voipio
Same stuff can be grabbed with:
git pull git://gitorious.org/qemu-maemo/qemu-maemo.git linux-user-for-upstream
Riku Voipio (3):
enable tb unlinking when compiled with NPTL
linux-user: Fix mmap_lock ordering
linux-user: cleanup force_sig() calls
exec.c |
From: Riku Voipio
Force_sig should be always called with TARGET_ signals.
Not that it really matters with SEGV, so this patch is
just for cleanup and improving consistency.
Signed-off-by: Riku Voipio
---
linux-user/signal.c | 40
1 files changed, 20 i
From: Riku Voipio
mmap_lock() can be called while tb_lock() is being held. To
avoid deadlock when one thread is holding mmap_lock and another
tb_lock, _always_ lock first tb_lock().
Signed-off-by: Riku Voipio
---
linux-user/main.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
From: Riku Voipio
Fixes recieving signals when guest code is being executed in a tight
loop. For an example, try interrupting the following code with ctrl-c.
http://nchipin.kos.to/test-loop.c
The tight loop is ofcourse brainless, but it is also exactly how the waitpid*
testcases
are implemente
On Fri, Dec 04, 2009 at 11:15:12AM -0600, Anthony Liguori wrote:
> Richard W.M. Jones wrote:
>> [from the commit message ...]
>>
>> Allow qemu to acquire shared and exclusive locks on disk images.
>> This is done by extending the -drive option with an additional,
>> optional parameter:
>>
>> -dri
Michael S. Tsirkin wrote:
On Wed, Dec 02, 2009 at 01:04:38PM +0100, Juan Quintela wrote:
This driver send a struct directly in the wire, where the struct
contains:
- target_phis_addr_t (can be 32 or 64 bits depending of host)
- void * (on host)
- size_t.
It has no hope of working across 32/6
On Monday 30 November 2009, Alexander Graf wrote:
> Currently we have this stupid role of disallowing:
>
> if (r)
> break;
This has been discussed to death several times, in several different paces,
and with no clear resolution or consensus, so I'm going to make an executive
decision:
When using encrypted disk images, QEMU will prompt the user
for passwords when started.
This makes sense for the user protocol, but doesn't for QMP.
The solution is to have Monitor command which allows the user
or a Client to set passwords in advance, so that we avoid
the prompt completely.
This
Signed-off-by: Luiz Capitulino
---
qerror.c |4
qerror.h |3 +++
2 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/qerror.c b/qerror.c
index 92d9622..18be7e3 100644
--- a/qerror.c
+++ b/qerror.c
@@ -61,6 +61,10 @@ const QErrorStringTable qerror_table[] = {
.desc
We don't have prompts in QMP, so we need to set passwords in advance,
details in the second patch.
We also add a new error class for invalid passwords.
Richard W.M. Jones wrote:
[from the commit message ...]
Allow qemu to acquire shared and exclusive locks on disk images.
This is done by extending the -drive option with an additional,
optional parameter:
-drive [...],lock=none
-drive [...],lock=shared
-drive [...],lock=exclusive
lock=no
Return a QDict with server information. Connected clients are returned
as a QList of QDicts.
The new functions (vnc_qdict_remote_addr(), vnc_qdict_local_addr() and
put_addr_qdict()) are used to insert 'host' and 'service' information
in the returned QDict.
This patch is big, but I don't see how t
Return a QDict with information about the just added device.
This commit should not change user output.
Please, note that this patch does not do error handling
conversion. In error conditions the handler still calls
monitor_printf().
Signed-off-by: Luiz Capitulino
---
hw/pci-hotplug.c | 40 +
Each device is represented by a QDict. The returned QObject is a QList
of all devices.
This commit should not change user output.
Signed-off-by: Luiz Capitulino
---
monitor.c |3 ++-
qemu-char.c | 43 +--
qemu-char.h |4 +++-
3 files changed,
Each device statistic information is stored in a QDict and
the returned QObject is a QList of all devices.
This commit should not change user output.
Signed-off-by: Luiz Capitulino
---
block.c | 82
block.h |3 +-
monitor.c
Each block device information is stored in a QDict and the
returned QObject is a QList of all devices.
This commit should not change user output.
Signed-off-by: Luiz Capitulino
---
Makefile |6 +-
block.c | 123 +++--
block.h |
Return a QDict, which may contain more two QDicts, depending on
the type of migration we're performing.
IMPORTANT: as a QInt stores a int64_t integer, RAM values are going
to be stored as int64_t and not as uint64_t as they are today. If
this is a problem QInt will have to be changed.
This commit
Each mouse is represented by a QDict, the returned QObject is a QList of
all mice.
This commit should not change user output.
Signed-off-by: Luiz Capitulino
---
console.h |3 +-
monitor.c |3 +-
vl.c | 62 ++--
3 files chang
The returned QObject is a QString, snprintf() is used because the
UUID_FMT is too complex for qobject_from_jsonf().
Signed-off-by: Luiz Capitulino
---
monitor.c | 15 ---
1 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/monitor.c b/monitor.c
index f9a698f..961f6e1 10
Return a QString with HPET information.
Signed-off-by: Luiz Capitulino
---
monitor.c | 24 +---
1 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/monitor.c b/monitor.c
index 96fde16..f9a698f 100644
--- a/monitor.c
+++ b/monitor.c
@@ -548,10 +548,27 @@ static v
Return a QString with the current VM name.
Signed-off-by: Luiz Capitulino
---
monitor.c | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/monitor.c b/monitor.c
index d3ab2ab..96fde16 100644
--- a/monitor.c
+++ b/monitor.c
@@ -507,10 +507,15 @@ static void do_inf
Return a QString with kvm status information.
Signed-off-by: Luiz Capitulino
---
monitor.c | 31 +--
1 files changed, 25 insertions(+), 6 deletions(-)
diff --git a/monitor.c b/monitor.c
index 03f5d7a..d3ab2ab 100644
--- a/monitor.c
+++ b/monitor.c
@@ -1738,17 +1738
Return a QString with status information.
Signed-off-by: Luiz Capitulino
---
monitor.c | 33 +++--
1 files changed, 27 insertions(+), 6 deletions(-)
diff --git a/monitor.c b/monitor.c
index 8cedfa9..03f5d7a 100644
--- a/monitor.c
+++ b/monitor.c
@@ -1865,16 +1865,3
New monitor commands should always return values in bytes.
Signed-off-by: Luiz Capitulino
---
monitor.c | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/monitor.c b/monitor.c
index 5bf32f0..8cedfa9 100644
--- a/monitor.c
+++ b/monitor.c
@@ -1889,12 +1889,18 @@
A helper function to get a QList from a QDict.
Signed-off-by: Luiz Capitulino
---
Makefile |2 +-
qdict.c | 13 +
qdict.h |2 ++
3 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index b4356ae..f1b0131 100644
--- a/Makefile
+++ b/Makefile
This is a helper function that does type checking before retrieving
a QBool from the dictionary.
Signed-off-by: Luiz Capitulino
---
Makefile |2 +-
qdict.c | 15 +++
qdict.h |1 +
3 files changed, 17 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index ea
Other subsystems will need to link against them.
Signed-off-by: Luiz Capitulino
---
Makefile |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index 85ad688..ea90c23 100644
--- a/Makefile
+++ b/Makefile
@@ -82,6 +82,12 @@ ALL_SUBDIRS=$(TARGET_DI
An easy way to include all QEMU objects.
Signed-off-by: Luiz Capitulino
---
qemu-objects.h | 24
1 files changed, 24 insertions(+), 0 deletions(-)
create mode 100644 qemu-objects.h
diff --git a/qemu-objects.h b/qemu-objects.h
new file mode 100644
index 000..e1d1e
Hi,
This series covers almost half of the info handlers conversions to the
QObject style, the other half is a bit more complicated as some handlers
can be defined by different machine types.
changelog
-
v1 -> v2
- Rebase
- do_info_vnc(): drop keys with 'none' strings
v0 -> v1
- Mino
[from the commit message ...]
Allow qemu to acquire shared and exclusive locks on disk images.
This is done by extending the -drive option with an additional,
optional parameter:
-drive [...],lock=none
-drive [...],lock=shared
-drive [...],lock=exclusive
lock=none is the default, and it me
Markus Armbruster wrote:
Commit a7d27b53 made zero-sized allocations a fatal error, deviating
from ISO C's malloc() & friends. Revert that, but take care never to
return a null pointer, like malloc() & friends may do (it's
implementation defined), because that's another source of bugs.
Rational
The multiboot implementation assumed that there is only one program header
(which contains the entry point) and that the entry point is at the start of
the code. This doesn't hold true generally and caused too little data to be
loaded.
Fix the loading code to pass the whole loaded data to the Mult
Gerd Hoffmann wrote:
On 12/04/09 01:04, Anthony Liguori wrote:
Problem is, control is not a property of the character device. To
express this in a consistent way with everything else, you would have to
make this QemuOpts-like so it would look like
-monitor control,device=tcp:localhost:444,serve
On Fri, Dec 04, 2009 at 11:33:13AM +0100, Alexander Graf wrote:
> SeaBIOS needs to write to the f-segment. So it needs to have some way to set
> that from read-only to read-write, write in it and when it's done set it to
> read-only again.
>
> On PCI we have a mechanism for that. The ISA machine d
Isaku Yamahata wrote:
This is the preparation patch for q35 chipset and PCIE support.
Anthony, any chance to merge? Can you please give me comments?
I'd like to see Michael review the PCI changes and Gerd review the pc
changes.
I'm uncertain if some of the pc refactoring is the right inte
Alexander Graf wrote:
On 04.12.2009, at 06:38, malc wrote:
http://airlied.livejournal.com/69291.html
Link courtesy Laurent Desnogues.
Oh, finally. That VMware SVGA driver was broken forever.
The VMware SVGA driver has a lot of potential except that the Windows
driver has a real
Kevin Wolf wrote:
Part of the first patch of the -drive rerror series has been merged once more
on top of the rest of the series. This effectively disables the rerror option
and always goes with the default value. Reverting the commit re-enables the
option.
This reverts commit fc072ec4df0996682d
Alexander Graf wrote:
SeaBIOS needs to write to the f-segment. So it needs to have some way to set
that from read-only to read-write, write in it and when it's done set it to
read-only again.
On PCI we have a mechanism for that. The ISA machine does not though. To stay
regression free and happil
Avi Kivity wrote:
> On 12/03/2009 09:23 PM, Jan Kiszka wrote:
>> Jan Kiszka wrote:
>>
>>> Problem 2
>>> -
>>> Setup: qemu head with vmstate fixes. kvm-kmod master, 64-bit host& guest.
>>> Effect: The migration target either locks up or reboots immediately.
>>> I've nailed this down to
This allows to suspend command interpretation and execution
synchronously, e.g. during migration.
Signed-off-by: Jan Kiszka
---
monitor.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/monitor.c b/monitor.c
index 3286ba2..a3be1c8 100644
--- a/monitor.c
+++ b/monitor.c
On 12/04/09 12:48, Luiz Capitulino wrote:
I think we should create a new option for monitor configuration, like this:
-mon mode={control,readline},chardev=,more-options-here
So you'll create a qmp monitor socket this way:
-chardev socket,path=/tmp/qmpsock,id=qmp,server,nowait
-mon
On Fri, 04 Dec 2009 12:17:51 +0100
Gerd Hoffmann wrote:
> On 12/04/09 01:04, Anthony Liguori wrote:
> > Problem is, control is not a property of the character device. To
> > express this in a consistent way with everything else, you would have to
> > make this QemuOpts-like so it would look like
On 12/04/09 01:04, Anthony Liguori wrote:
Problem is, control is not a property of the character device. To
express this in a consistent way with everything else, you would have to
make this QemuOpts-like so it would look like
-monitor control,device=tcp:localhost:444,server
But so far, the mon
Part of the first patch of the -drive rerror series has been merged once more
on top of the rest of the series. This effectively disables the rerror option
and always goes with the default value. Reverting the commit re-enables the
option.
This reverts commit fc072ec4df0996682dfbff6c735e2bbc0d9313
On Fri, 2009-12-04 at 11:00 +0100, Arnaud Patard wrote:
> Riku Voipio writes:
> > On Fri, Oct 02, 2009 at 02:25:36PM +0200, Paul Bolle wrote:
> >> Note that I have some reservations about the current init_paths() and
> >> path() code:
> >> - their names seem to confusing. Maybe those should be ini
SeaBIOS needs to write to the f-segment. So it needs to have some way to set
that from read-only to read-write, write in it and when it's done set it to
read-only again.
On PCI we have a mechanism for that. The ISA machine does not though. To stay
regression free and happily enable users to contin
On 04.12.2009, at 06:38, malc wrote:
>
> http://airlied.livejournal.com/69291.html
>
> Link courtesy Laurent Desnogues.
Yikes - just looked over the patch. I take that merge comment back :)
Alex
On 04.12.2009, at 06:38, malc wrote:
>
> http://airlied.livejournal.com/69291.html
>
> Link courtesy Laurent Desnogues.
Oh, finally. That VMware SVGA driver was broken forever.
If it doesn't worsen the SVGA situation, mind to drag the changes in?
Alex
Am 04.12.2009 10:54, schrieb Kevin Wolf:
> Hi Anthony,
>
> the description of this patch made it into commit 5f370b1, but the
> content of this commit is obviously nonsense (adds only an empty line).
> It's still uint32_t in current master. Can you take the patch into your
> queue once again? It s
Am 02.12.2009 17:46, schrieb Anthony Liguori:
> I've got all of the patches I'm considering for 0.12 currently in
> staging. I'm going to work through and test/commit these in a few
> chunks over the next few days before freezing the tree.
You seem to have missed this one:
qemu-io: Fix memory
Riku Voipio writes:
Hi,
> On Fri, Oct 02, 2009 at 02:25:36PM +0200, Paul Bolle wrote:
>> Note that I have some reservations about the current init_paths() and
>> path() code:
>> - their names seem to confusing. Maybe those should be init_base() and
>> base() or something similar;
>> - why does i
Hi Anthony,
the description of this patch made it into commit 5f370b1, but the
content of this commit is obviously nonsense (adds only an empty line).
It's still uint32_t in current master. Can you take the patch into your
queue once again? It should still apply cleanly.
Kevin
Am 18.11.2009 12:1
On Fri, Oct 02, 2009 at 02:25:36PM +0200, Paul Bolle wrote:
> Note that I have some reservations about the current init_paths() and
> path() code:
> - their names seem to confusing. Maybe those should be init_base() and
> base() or something similar;
> - why does init_paths() copy all filenames in
Am 30.11.2009 21:51, schrieb Christoph Hellwig:
> On Mon, Nov 30, 2009 at 04:54:31PM +0100, Kevin Wolf wrote:
>> Users don't expect that they need to specify host_device/cdrom/floppy when
>> "creating" an image on a block device or converting with an device as target.
>> Currently creating as raw l
Am 03.12.2009 20:55, schrieb Anthony Liguori:
> Gleb Natapov wrote:
>> On Fri, Nov 27, 2009 at 01:25:36PM +0100, Kevin Wolf wrote:
>>
>>> Either rename variables and functions to refer to write errors (which is
>>> what
>>> they actually do) or introduce a parameter to distinguish reads and wri
On 12/03/2009 09:23 PM, Jan Kiszka wrote:
Jan Kiszka wrote:
Problem 2
-
Setup: qemu head with vmstate fixes. kvm-kmod master, 64-bit host& guest.
Effect: The migration target either locks up or reboots immediately.
I've nailed this down to 84d0b66c778d881eafca2a5d0d66678211c4e861. E
62 matches
Mail list logo
