On 03/16/2010 03:21 AM, Anthony Liguori wrote:
On 03/15/2010 10:06 AM, Avi Kivity wrote:
On 03/15/2010 03:23 PM, Anthony Liguori wrote:
On 03/15/2010 08:11 AM, Avi Kivity wrote:
On 03/15/2010 03:03 PM, Joerg Roedel wrote:
I will add another project - iommu emulation. Could be very useful
f
On 03/15/2010 10:06 AM, Avi Kivity wrote:
On 03/15/2010 03:23 PM, Anthony Liguori wrote:
On 03/15/2010 08:11 AM, Avi Kivity wrote:
On 03/15/2010 03:03 PM, Joerg Roedel wrote:
I will add another project - iommu emulation. Could be very useful
for doing device assignment to nested guests, whi
On Mon, Mar 15, 2010 at 08:14:29AM -0500, Anthony Liguori wrote:
> On 03/15/2010 07:42 AM, Avi Kivity wrote:
>> On 03/15/2010 02:38 PM, Joerg Roedel wrote:
>>> On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
>Hi there,
>
>>
On Mon, Mar 15, 2010 at 02:03:11PM +0100, Joerg Roedel wrote:
> On Mon, Mar 15, 2010 at 05:53:13AM -0700, Muli Ben-Yehuda wrote:
> > On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
> > > On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
> >
> > > > Hi there,
> > > >
> > > > Our wiki
On Mon, Mar 15, 2010 at 03:11:42PM +0200, Avi Kivity wrote:
> On 03/15/2010 03:03 PM, Joerg Roedel wrote:
>>
I will add another project - iommu emulation. Could be very useful
for doing device assignment to nested guests, which could make
testing a lot easier.
>>> Our e
On Mon, Mar 15, 2010 at 05:53:13AM -0700, Muli Ben-Yehuda wrote:
> On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
> > On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
>
> > > Hi there,
> > >
> > > Our wiki page for the Summer of Code 2010 is doing quite well:
> > >
> > >http://wiki.qe
On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
> On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
> > Hi there,
> >
> > Our wiki page for the Summer of Code 2010 is doing quite well:
> >
> >http://wiki.qemu.org/Google_Summer_of_Code_2010
>
> I will add another project - iommu emulati
On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
> On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
>> Hi there,
>>
>> Our wiki page for the Summer of Code 2010 is doing quite well:
>>
>> http://wiki.qemu.org/Google_Summer_of_Code_2010
>>
>
> I will add another project - iommu emul
On 03/15/2010 03:31 PM, Anthony Liguori wrote:
On 03/11/2010 08:19 AM, Paul Brook wrote:
On 03/11/2010 06:57 AM, Paul Brook wrote:
+struct QEMUNotifier
+{
+void (*notify)(QEMUNotifier *notifier);
+};
I suggest combining this with QEMUBH.
I take it your not opposed to converting QEMUBH to
For QMP, we just add an attribute which is backwards compatible. For the human
monitor, we add (absolute) to the end of the line.
Signed-off-by: Anthony Liguori
---
input.c | 18 --
1 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/input.c b/input.c
index c956e06
Right now, DisplayState clients rely on polling the mouse mode to determine
when the device is changed to an absolute device. Use a notification list to
add an explicit notification.
Signed-off-by: Anthony Liguori
---
console.h |3 +++
input.c | 37 -
When we switch to absolute mode, we send out a notification (if the client
supports it). Today, we only send this notification when the client sends us
a mouse event and we're in the wrong mode.
Signed-off-by: Anthony Liguori
---
vnc.c | 13 -
vnc.h |2 ++
2 files changed, 10
Today we poll the mouse mode whenever there is a mouse movement. There is a
subtle usability problem with this though.
If we're in relative mode and grab is enabled, when we change to absolute mode,
we break grab. This gives a user a seamless transition when the new pointer
is enabled.
But beca
And convert usb-hid to use it (to avoid regression with bisection)
Right now, when we do info mice and we've added a usb tablet, we don't see it
until the guest starts using the tablet. We implement this behavior in order
to provide a means to delay registration of a mouse handler since we treat
kbd_mouse_is_absolute tells us whether the current mouse handler is an absolute
device. kbd_mouse_has_absolute tells us whether we have any device that is
capable of absolute input.
This lets us tell a user that they have configured an absolute device but that
the guest is not currently using it.
Notifiers are data-less callbacks and a notifier list is a list of registered
notifiers that all are interested in a particular event.
We'll use this in a few patches to implement mouse change notification.
Signed-off-by: Anthony Liguori
---
v1 -> v2
- Do not do memory allocations by placing li
On 03/11/2010 08:19 AM, Paul Brook wrote:
On 03/11/2010 06:57 AM, Paul Brook wrote:
+struct QEMUNotifier
+{
+void (*notify)(QEMUNotifier *notifier);
+};
I suggest combining this with QEMUBH.
I take it your not opposed to converting QEMUBH to be a QEMUNotifier?
If so
On 3/15/10, Paolo Bonzini wrote:
> >
> > > I'd consider not changing assert(0)->abort()
> > > if there is code after the assert that looks like an attempt at
> recovering.
> > > Example:
> > >
> > >if (!p) {
> > >printf ("the impossible has happened!");
> > >assert (0);
> > >
On Fri, Mar 12, 2010 at 03:20:48PM +0100, Jan Kiszka wrote:
> Patch 1 is for upstream and should be applied to uq/master as well, patch
> 2 is for qemu-kvm only.
>
> Jan Kiszka (2):
> KVM: x86: Add debug register saving and restoring
> qemu-kvm: x86: Add support for saving&restoring debug regi
On 03/15/2010 01:16 PM, Chris Webb wrote:
I tried to grab a recursive clone of qemu.git in order to get the head of
the seabios and vgabios trees to match the head of qemu.git, but the
operation failed with
$ git clone --recursive git://git.qemu.org/qemu.git qemu-r
Initialized empty Git re
Blue Swirl writes:
> On 3/15/10, Markus Armbruster wrote:
>> Blue Swirl writes:
>>
>> > When building with -DNDEBUG, assert(0) will not stop execution
>> > so it must not be used for abnormal termination.
>>
>>
>> For each case: are you sure the code does not recover after assert(0)?
>> Not
I'd consider not changing assert(0)->abort()
if there is code after the assert that looks like an attempt at recovering.
Example:
if (!p) {
printf ("the impossible has happened!");
assert (0);
}
return p->q;
should be changed to abort, while
if (!p) {
Paolo Bonzini writes:
I sympathize with the general idea, but I don't like dead code
>>> after abort(). What about cleaning that up?
>>>
>> Good idea, but it should be a separate patch. This patch is "safe",
>> whereas the cleanup patch could cause problems if it's not done
>> carefully.
>
On 3/15/10, Paolo Bonzini wrote:
>
>
> >
> > >
> > > > I sympathize with the general idea, but I don't like dead code
> > > >
> > > after abort(). What about cleaning that up?
> > >
> > >
> > Good idea, but it should be a separate patch. This patch is "safe",
> > whereas the cleanup patch could c
I sympathize with the general idea, but I don't like dead code
after abort(). What about cleaning that up?
Good idea, but it should be a separate patch. This patch is "safe",
whereas the cleanup patch could cause problems if it's not done
carefully.
This patch is "safe", however I'd consid
On 3/15/10, Kevin Wolf wrote:
> Am 15.03.2010 18:40, schrieb Blue Swirl:
>
> > On 3/15/10, Kevin Wolf wrote:
> >> This patch series introduces a new block driver which acts as a protocol
> and
> >> whose purpose it is to fail requests. To be more precise, I want it to
> fail in
> >> config
I tried to grab a recursive clone of qemu.git in order to get the head of
the seabios and vgabios trees to match the head of qemu.git, but the
operation failed with
$ git clone --recursive git://git.qemu.org/qemu.git qemu-r
Initialized empty Git repository in /home/chris/git/qemu-r/.git/
rem
Am 15.03.2010 18:40, schrieb Blue Swirl:
> On 3/15/10, Kevin Wolf wrote:
>> This patch series introduces a new block driver which acts as a protocol and
>> whose purpose it is to fail requests. To be more precise, I want it to fail
>> in
>> configurable places, so that qemu-iotests can be exten
On 3/15/10, Kevin Wolf wrote:
> This patch series introduces a new block driver which acts as a protocol and
> whose purpose it is to fail requests. To be more precise, I want it to fail
> in
> configurable places, so that qemu-iotests can be extended with tests for the
> error paths (for exam
On 3/15/10, Markus Armbruster wrote:
> Blue Swirl writes:
>
> > When building with -DNDEBUG, assert(0) will not stop execution
> > so it must not be used for abnormal termination.
>
>
> For each case: are you sure the code does not recover after assert(0)?
> Not saying it does, just asking whe
This patch fixes few resource leaks in the iwmmxt disassemble.
Signed-off-by: Lars Munch
---
target-arm/translate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/target-arm/translate.c b/target-arm/translate.c
index cdfe946..2ab7881 100644
--- a/target-arm/translate.
This adds blkdebug events to qcow2 to allow injecting I/O errors in specific
places.
Signed-off-by: Kevin Wolf
---
block.h | 19 +++
block/blkdebug.c | 17 +
block/qcow2-cluster.c | 15 +++
3 files changed, 51 insertions(+), 0
Block drivers can trigger a blkdebug event whenever they reach a place where it
could be useful to inject an error for testing/debugging purposes.
Rules are read from a blkdebug config file and describe which action is taken
when an event is triggered. For now this is only injecting an error (with
To be able to use config files for blkdebug, we need to make these functions
available in the tools. This involves moving two functions that can only be
built in the context of the emulator.
Signed-off-by: Kevin Wolf
---
Makefile.objs|4 ++--
hw/qdev-properties.c | 19 +
Add a mechanism to inject errors instead of passing requests on. With no
further patches applied, you can use it by setting inject_errno in gdb.
Signed-off-by: Kevin Wolf
---
block/blkdebug.c | 63 ++
1 files changed, 63 insertions(+), 0 dele
This isn't doing anything interesting. It creates the blkdebug block driver as
a protocol which just passes everything through to raw.
Signed-off-by: Kevin Wolf
---
Makefile.objs|2 +-
block/blkdebug.c | 104 ++
2 files changed, 105 in
Introduce a new function qemu_read_config_file which reads the VM configuration
from a config file. Unlike qemu_config_parse it doesn't take a open file but a
filename and reduces code duplication as a side effect.
Signed-off-by: Kevin Wolf
---
qemu-config.c | 15 +++
qemu-config.h
qemu_config_parse gets the option groups as a parameter now instead of
hardcoding the VM configuration groups. This way it can be used for other
configurations, too.
Signed-off-by: Kevin Wolf
---
qemu-config.c | 15 ---
qemu-config.h |2 +-
2 files changed, 9 insertions(+), 8 d
This patch series introduces a new block driver which acts as a protocol and
whose purpose it is to fail requests. To be more precise, I want it to fail in
configurable places, so that qemu-iotests can be extended with tests for the
error paths (for example for the case when something with metadata
> >> Also, it seems -no-shutdown doesn't actually "stop the emulation"
> > > as
> >> said in the manual, it actually keeps the vm running (and using
> > > cpu),
> >> despite the OS trying to shutdown via ACPI. At least I tested so
> > > with
> >> Haiku (and acpi=true in kernel config), which proper
On 03/15/2010 10:55 AM, Daniel P. Berrange wrote:
On Mon, Mar 15, 2010 at 04:01:27PM +0100, Fran?ois Revol wrote:
Hello,
while working on a demonstrator for a green-IT project, to show
scheduled machine shutdown and powering depending on various
conditions, I wondered if I could use QEMU wit
On Mon, Mar 15, 2010 at 12:26:27PM +, Paul Brook wrote:
> > +static uint32_t get_elf_hwcap(void)
> > +{
> > +return thread_env->features;
> > +}
>
> No. These values are not the same.
>
> Paul
>
Yes, these values are indeed not the same. Below is an updated patch with a
function similar
On Mon, Mar 15, 2010 at 12:53:25PM +, Paul Brook wrote:
> > +#if !defined(CONFIG_USER_ONLY)
> > if (arm_feature(env, ARM_FEATURE_XSCALE)
> > && ((env->cp15.c15_cpar ^ 0x3fff) & (1 << cpnum)))
> > return 1;
> > +#endif
>
> This is almost certainly the wrong way to fix this.
>
On Mon, Mar 15, 2010 at 04:01:27PM +0100, Fran?ois Revol wrote:
> Hello,
> while working on a demonstrator for a green-IT project, to show
> scheduled machine shutdown and powering depending on various
> conditions, I wondered if I could use QEMU with wake-on-lan
> transparently, but it seems it's
> > As for WOL, it would still be handy to have I think... btw, do we
> > support suspending the emulation via ACPI ? VirtualBox has
> > something
> > called "Pause" mode, which I'm not sure actually if it's reflected
> > to
> > ACPI, which allows to avoid wasting cpu when not usign the guest,
> >
On 03/15/2010 10:37 AM, François Revol wrote:
Le Mon, 15 Mar 2010 15:26:24 +, Paul Brook a écrit :
Ideally this would evolve into supporting IPMI, which would allow
managing VMs exactly like physical servers without concern, appart
launching the actual process first.
cf.
http://en.wikipe
Le Mon, 15 Mar 2010 15:26:24 +, Paul Brook a écrit :
> > Ideally this would evolve into supporting IPMI, which would allow
> > managing VMs exactly like physical servers without concern, appart
> > launching the actual process first.
> > cf.
> > http://en.wikipedia.org/wiki/Intelligent_Platform
> Ideally this would evolve into supporting IPMI, which would allow
> managing VMs exactly like physical servers without concern, appart
> launching the actual process first.
> cf.
> http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface
> http://openipmi.sourceforge.net/
>
> Anyon
Am Montag, 15. März 2010 15:48:03 schrieb Riku Voipio:
> On Mon, Mar 15, 2010 at 01:46:10PM +0100, Jan-Simon Möller wrote:
> > We're still investigating the topic. So far, we tracked one failure down
> > to ldconfig.real which is a static arm binary executed after the chroot
> > got the basic packa
On 03/15/2010 03:23 PM, Anthony Liguori wrote:
On 03/15/2010 08:11 AM, Avi Kivity wrote:
On 03/15/2010 03:03 PM, Joerg Roedel wrote:
I will add another project - iommu emulation. Could be very useful
for doing device assignment to nested guests, which could make
testing a lot easier.
Our ex
Hello,
while working on a demonstrator for a green-IT project, to show
scheduled machine shutdown and powering depending on various
conditions, I wondered if I could use QEMU with wake-on-lan
transparently, but it seems it's not implemented at all.
I though I could try to add support for it, and w
On Mon, Mar 15, 2010 at 01:46:10PM +0100, Jan-Simon Möller wrote:
> We're still investigating the topic. So far, we tracked one failure down to
> ldconfig.real which is a static arm binary executed after the chroot got the
> basic packages installed. If we setup a chroot with an older qemu-arm and
Kevin Wolf wrote:
> Am 13.03.2010 20:18, schrieb Michael Tokarev:
>> Apparently this does not work, and for a lng time:
>>
>> $ kvm -fda fat:dir
>> [ it opens the sdl window ]
>> $ kvm -fda fat:dir -snapshot
>> qemu: could not open disk image fat:dir: No such file or directory
>>
>> Is it s
On 03/15/2010 08:24 AM, Joerg Roedel wrote:
On Mon, Mar 15, 2010 at 03:11:42PM +0200, Avi Kivity wrote:
On 03/15/2010 03:03 PM, Joerg Roedel wrote:
I will add another project - iommu emulation. Could be very useful
for doing device assignment to nested guests, which could mak
Real pcnet device (AT2450) apparently has subsystem
device and vendor id set to 0, this is out of spec
(which requires that vendor id is obtained from PCI SIG)
but windows xp driver seems to need this in order
to associate.
qemu sets pci subsystem id to qumranet/qemu
since d350d97d196a632b6c7493ac
On 03/15/2010 08:11 AM, Avi Kivity wrote:
On 03/15/2010 03:03 PM, Joerg Roedel wrote:
I will add another project - iommu emulation. Could be very useful
for doing device assignment to nested guests, which could make
testing a lot easier.
Our experiments show that nested device assignment is
On 03/15/2010 07:42 AM, Avi Kivity wrote:
On 03/15/2010 02:38 PM, Joerg Roedel wrote:
On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
Hi there,
Our wiki page for the Summer of Code 2010 is doing quite well:
http://wiki.qemu.org
On 03/15/2010 03:03 PM, Joerg Roedel wrote:
I will add another project - iommu emulation. Could be very useful
for doing device assignment to nested guests, which could make
testing a lot easier.
Our experiments show that nested device assignment is pretty much
required for I/O perfor
> +#if !defined(CONFIG_USER_ONLY)
> if (arm_feature(env, ARM_FEATURE_XSCALE)
> && ((env->cp15.c15_cpar ^ 0x3fff) & (1 << cpnum)))
> return 1;
> +#endif
This is almost certainly the wrong way to fix this.
Paul
> > I had QEMU working on PowerPC and ARM in chroots from the Linux versions:
> >
> > - Fedora 11 / 12
> > - Ubuntu 9.04, 9.10, 10.04
> > - Debian 4, 5 and Sid
> >
> > for ARM and PowerPC. My host OS is openSUSE 11.2 using a 2.6.31 kernel,
> > or openSUSE 11.1. All machines are 64 Bit machines.
> >
On 03/15/2010 02:38 PM, Joerg Roedel wrote:
On Mon, Mar 15, 2010 at 02:25:41PM +0200, Avi Kivity wrote:
On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
Hi there,
Our wiki page for the Summer of Code 2010 is doing quite well:
http://wiki.qemu.org/Google_Summer_of_Code_2010
When using linux-user for emulating an pxa270 we cannot generate an illegal
instruction trap to the kernel to save/load the iwmmxt registers.
Signed-off-by: Lars Munch
---
target-arm/translate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/target-arm/translate.c b/t
On 03/14/2010 02:19 PM, Naphtali Sprei wrote:
Really use read-only flags for opening the file when asked for read-only
Signed-off-by: Naphtali Sprei
---
qemu-nbd.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/qemu-nbd.c b/qemu-nbd.c
index eac0c21..a393583 100644
--
> +static uint32_t get_elf_hwcap(void)
> +{
> +return thread_env->features;
> +}
No. These values are not the same.
Paul
On 03/10/2010 11:30 PM, Luiz Capitulino wrote:
Hi there,
Our wiki page for the Summer of Code 2010 is doing quite well:
http://wiki.qemu.org/Google_Summer_of_Code_2010
I will add another project - iommu emulation. Could be very useful for
doing device assignment to nested guests, wh
Use arm features based on cpu model. The hardcoded feature list gave
problems in the setjmp/longjmp functions of glibc since it tried to use
VFP instructions even though I specified a pxa270 as cpu model.
Signed-off-by: Lars Munch
---
linux-user/elfload.c | 10 ++
1 files changed, 6 in
Am 13.03.2010 20:18, schrieb Michael Tokarev:
> Apparently this does not work, and for a lng time:
>
> $ kvm -fda fat:dir
> [ it opens the sdl window ]
> $ kvm -fda fat:dir -snapshot
> qemu: could not open disk image fat:dir: No such file or directory
>
> Is it supposed to work?
Wow, tha
On Sat, Mar 13, 2010 at 03:00:52PM +0100, Martin Mohring wrote:
> I am sorry to bring us all down to earth, we all had wished that this stuff
> gets finally fixed, but it seems that those patches applied to QEMU master
> have killed QEMU user mode.
sid and maemo userlands work for me like befor
Blue Swirl writes:
> When building with -DNDEBUG, assert(0) will not stop execution
> so it must not be used for abnormal termination.
For each case: are you sure the code does not recover after assert(0)?
Not saying it does, just asking whether you checked.
> Use cpu_abort() when in CPU contex
69 matches
Mail list logo
