On 03/24/10 00:13, Jamie Lokier wrote:
Gerd Hoffmann wrote:
- networking: man, setting networking is a mess, libvirt just does it
for you.
+1
Even when not using libvirt for a reason or another I usually hook my
virtual machines into virbr0 (libvirt default network).
I had the opposite
Andi Kleen a...@firstfloor.org wrote:
Juan Quintela quint...@redhat.com writes:
- networking: man, setting networking is a mess, libvirt just does it
for you.
Agreed it's messy, but isn't this something that the standard qemu
command line tool could potentially do better by itself? I
Blue Swirl blauwir...@gmail.com wrote:
Hi,
Here's some planning for getting most files compiled as few times as
possible. Comments and suggestions are welcome.
I took some thought about this at some point. Problems here start from
Recursive Makefile condered Harmful (tm).
Look at how we
Jun Koi junkoi2...@gmail.com wrote:
Hi,
Is it possible to use -monitor option to expose the monitor on socket
interface, such as TCP or Unix domain port, so I can access the
monitor using non-stdio way?
man qemu
search -monitor
-monitor dev
Redirect the monitor to host
The harder cases are those where the device code depends somehow on
the architecture. Some thoughts follow.
vl.c: a lot of work. Maybe the CPUState stuff should be separated to a new file.
dma.c: DMA_schedule needs access to CPUState.
Most users of CPUState (e.g. qemu-timer.c and hw/dma.c)
On Tue, Mar 23, 2010 at 12:55:07PM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Tue, Mar 23, 2010 at 10:57:33AM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari Pulavarty wrote:
Write Results:
Thanks a lot, Juan!
Jun
On Wed, Mar 24, 2010 at 6:41 PM, Juan Quintela quint...@redhat.com wrote:
Jun Koi junkoi2...@gmail.com wrote:
Hi,
Is it possible to use -monitor option to expose the monitor on socket
interface, such as TCP or Unix domain port, so I can access the
monitor using
On Saturday 20 March 2010 23:00:49 Alexander Graf wrote:
Am 20.03.2010 um 15:02 schrieb Mohammed Gamal m.gamal...@gmail.com:
On Sat, Mar 20, 2010 at 3:18 PM, Avi Kivity a...@redhat.com wrote:
On 03/20/2010 10:55 AM, Alexander Graf wrote:
I'd say that a GSoC project would rather focus on
On Mon, Mar 22, 2010 at 04:49:21PM -0500, Anthony Liguori wrote:
On 03/22/2010 03:10 PM, Daniel P. Berrange wrote:
This isn't necessarily libvirt's problem if it's mission is to provide a
common hypervisor API that covers the most commonly used features.
That is more or less our current
On Wed, Mar 24, 2010 at 07:17:26AM +0200, Avi Kivity wrote:
On 03/23/2010 08:00 PM, Avi Kivity wrote:
On 03/23/2010 06:06 PM, Anthony Liguori wrote:
I thought the monitor protocol *was* our API. If not, why not?
It is. But our API is missing key components like guest
enumeration. So the
On 03/24/2010 12:36 PM, Daniel P. Berrange wrote:
On Wed, Mar 24, 2010 at 07:17:26AM +0200, Avi Kivity wrote:
On 03/23/2010 08:00 PM, Avi Kivity wrote:
On 03/23/2010 06:06 PM, Anthony Liguori wrote:
I thought the monitor protocol *was* our API. If not, why not?
On 03/24/2010 02:47 AM, Paolo Bonzini wrote:
1) make CPUState define only common fields. Include CPUState at the
beginning of each per-target CPUXYZState.
Irritatingly, the common fields contain quite big TLBs. And the
offsets from the start of env affect the compactness of the code
generated
Hello,
This is an idle question in the sense that, much as I would like to, I know for
a
fact that I won't have the time to look at implementing this. I'm not expecting
other people to seriously look at doing it either, but I would be interested on
your
thoughts.
If the technical
On Tue, Mar 23, 2010 at 12:55:07PM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Tue, Mar 23, 2010 at 10:57:33AM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari Pulavarty wrote:
Write Results:
When input some invialid words in QMP port, qemu outputs this error message:
parse error: invalid keyword `%s'
This patch makes qemu output the content, like:
parse error: invalid keyword `unknow_cmd'
Signed-off-by: Amos Kong ak...@redhat.com
---
json-parser.c |7 ++-
1 files changed, 6
On 03/24/2010 05:17 AM, Amos Kong wrote:
-fprintf(stderr, parse error: %s\n, msg);
+va_list ap;
+va_start(ap, msg);
+fprintf(stderr, parse error: );
+vfprintf(stderr, msg, ap);
+fprintf(stderr, \n);
Technically you need va_end here.
r~
On 03/24/2010 05:42 AM, Avi Kivity wrote:
The filtering access part of this daemon is also not mapping well onto
libvirt's access model, because we don't soley filter based on UID in
libvirtd. We have it configurable based on UID, policykit, SASL,
TLS/x509
already, and intend adding role
I can't quite see what such a libqemu would buy us compared to straight
QMP.
Talking QMP should be easy, provided you got a suitable JSON library.
I agree. My undesranding is this was one of the large motivations behind using
JSON: It's a common protocol that already has convenient bindings
On 03/24/2010 02:19 PM, Anthony Liguori wrote:
qemud
- daemonaizes itself
- listens on /var/lib/qemud/guests for incoming guest connections
- listens on /var/lib/qemud/clients for incoming client connections
- filters access according to uid (SCM_CREDENTIALS)
- can pass a new monitor
On 03/24/2010 02:30 PM, Anthony Liguori wrote:
On 03/24/2010 07:27 AM, Avi Kivity wrote:
On 03/24/2010 02:19 PM, Anthony Liguori wrote:
qemud
- daemonaizes itself
- listens on /var/lib/qemud/guests for incoming guest connections
- listens on /var/lib/qemud/clients for incoming client
On 03/24/2010 02:32 PM, Anthony Liguori wrote:
You don't get a directory filled with a zillion socket files pointing
at dead guests. Agree that's a poor return on investment.
Deleting it on atexit combined with flushing the whole directory at
startup is a pretty reasonable solution to this
On 03/24/2010 07:29 AM, Avi Kivity wrote:
On 03/24/2010 02:23 PM, Anthony Liguori wrote:
On 03/24/2010 05:42 AM, Avi Kivity wrote:
The filtering access part of this daemon is also not mapping well onto
libvirt's access model, because we don't soley filter based on UID in
libvirtd. We have it
On 03/23/2010 09:24 PM, Anthony Liguori wrote:
We also provide an API for guest creation (the qemu command line).
As an aside, I'd like to see all command line options have qmp
equivalents (most of them can be implemented with a 'set' command that
writes qdev values). This allows a
On 03/24/2010 07:27 AM, Avi Kivity wrote:
On 03/24/2010 02:19 PM, Anthony Liguori wrote:
qemud
- daemonaizes itself
- listens on /var/lib/qemud/guests for incoming guest connections
- listens on /var/lib/qemud/clients for incoming client connections
- filters access according to uid
On 03/24/2010 02:30 PM, Paul Brook wrote:
On 03/23/2010 09:24 PM, Anthony Liguori wrote:
We also provide an API for guest creation (the qemu command line).
As an aside, I'd like to see all command line options have qmp
equivalents (most of them can be implemented with a 'set'
On 03/24/2010 02:23 PM, Anthony Liguori wrote:
On 03/24/2010 05:42 AM, Avi Kivity wrote:
The filtering access part of this daemon is also not mapping well onto
libvirt's access model, because we don't soley filter based on UID in
libvirtd. We have it configurable based on UID, policykit,
On 03/24/2010 07:25 AM, Paul Brook wrote:
I can't quite see what such a libqemu would buy us compared to straight
QMP.
Talking QMP should be easy, provided you got a suitable JSON library.
I agree. My undesranding is this was one of the large motivations behind using
JSON: It's a common
IMO the no_user flag is a bug, and should not exist.
Sorry, what's that?
Usually an indication that a device has been incorrectly or inproperly
converted to the qdev interface.
Paul
If the technical documentation at
http://www.usenix.org/publications/library/proceedings/usenix05/tech/freeni
x/full_papers/bellard/bellard_html/index.html is still valid (I think it
is), Qemu has two modes of handling access to guest memory - system
emulation, in which an entire guest
On 03/24/2010 03:59 AM, Gerd Hoffmann wrote:
On 03/24/10 00:13, Jamie Lokier wrote:
Gerd Hoffmann wrote:
- networking: man, setting networking is a mess, libvirt just does it
for you.
+1
Even when not using libvirt for a reason or another I usually hook my
virtual machines into virbr0
In practice I've seen this not working correctly in the past, i.e. my
^^^
br0 didn't pop up in the virt-manager nic setup page.
Please file a bug: virt-manager has had bridge detection for years, so
something must be going wrong.
When input some invialid words in QMP port, qemu outputs this error message:
parse error: invalid keyword `%s'
This patch makes qemu output the content, like:
parse error: invalid keyword `unknow_cmd'
Signed-off-by: Amos Kong ak...@redhat.com
---
json-parser.c |7 ++-
1 files changed, 6
The bochs vbe interface got a new register a while back, which specifies
the linear framebuffer size in 64k units. This patch adds support for
the new register to qemu. With this patch applied vgabios 0.6c works
with qemu.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/vga.c |3
On 03/24/2010 12:19 PM, Richard Henderson wrote:
On 03/24/2010 02:47 AM, Paolo Bonzini wrote:
1) make CPUState define only common fields. Include CPUState at the
beginning of each per-target CPUXYZState.
Irritatingly, the common fields contain quite big TLBs. And the
offsets from the start of
I was wondering whether something in-between would also
be feasible. That is, chunks of guest address space (say 4MB chunks for
the sake of the argument) are mmapped into the address space of the Qemu
process on the host, and when an access to guest memory is made, there is
an initial check
The target could be started with max_nr_ports for a virtio-serial device
lesser than what was available on the source machine. Fail the migration
in such a case.
Signed-off-by: Amit Shah amit.s...@redhat.com
Reported-by: Juan Quintela quint...@redhat.com
---
hw/virtio-serial-bus.c | 13
The number of ports on the source as well as the destination machines
should match. If they don't, it means some ports that got hotplugged on
the source aren't instantiated on the destination. Or that ports that
were hot-unplugged on the source are created on the destination.
Signed-off-by: Amit
If the host connection to a port is closed on the destination machine
after migration, whereas the connection was open on the source, the
guest has to be informed of that.
Similar for a host connection open on the destination.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
Allow the port 'id's to be set by a user on the command line. This is
needed by management apps that will want a stable port numbering scheme
for hot-plug/unplug and migration.
Since the port numbers are shared with the guest (to identify ports in
control messages), we just send a control message
The virtio-serial code doesn't mix declarations and definitions, so
separate them out on different lines.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-serial-bus.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/hw/virtio-serial-bus.c
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-console.c|2 +-
hw/virtio-serial-bus.c |2 +-
hw/virtio-serial.h |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/virtio-console.c b/hw/virtio-console.c
index 17b221d..6b8 100644
---
If adding of ports or devices in the guest fails we can send out a QMP
event so that management software can deal with it.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-serial-bus.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git
The check for a 0-sized write request to a guest port is not necessary;
the while loop below won't be executed in this case and all will be
fine.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-serial-bus.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git
When adding a port or a device to the guest fails, management software
might be interested in knowing and then cleaning up the host-side of the
port. Introduce QMP events to signal such errors.
Signed-off-by: Amit Shah amit.s...@redhat.com
CC: Luiz Capitulino lcapitul...@redhat.com
---
Data should be written only when ports are open.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-serial-bus.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/hw/virtio-serial-bus.c b/hw/virtio-serial-bus.c
index efcc66c..80fbff4 100644
---
The virtio-net code uses iov_fill() which fills an iov from a linear
buffer. The virtio-serial-bus code does something similar in an
open-coded function.
Create a new iov.c file that has iov_from_buf().
Convert virtio-net and virtio-serial-bus over to use this functionality.
virtio-net used ints
iov_to_buf() puts the buffer contents in the iov in a linearized buffer.
iov_size() gets the length of the contents in the iov.
The iov_to_buf() function is the memcpy_to_iovec() function that was
used in virtio-ballon.c.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/iov.c|
Current control messages are small enough to not be split into multiple
buffers but we could run into such a situation in the future or a
malicious guest could cause such a situation.
So handle the entire iov request for control messages.
Also ensure the size of the control request is = what we
Current guests don't send more than one iov but it can change later.
Ensure we handle that case.
Signed-off-by: Amit Shah amit.s...@redhat.com
CC: Avi Kivity a...@redhat.com
---
hw/virtio-serial-bus.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git
Paul Brook p...@codesourcery.com writes:
IMO the no_user flag is a bug, and should not exist.
Sorry, what's that?
Usually an indication that a device has been incorrectly or inproperly
converted to the qdev interface.
Can also be an indication that the device can't support multiple
Amos Kong ak...@redhat.com writes:
When input some invialid word 'unknowcmd' through QMP port, qemu outputs this
error message:
parse error: invalid keyword `%s'
This patch makes qemu output the content of invalid keyword, like:
parse error: invalid keyword `unknowcmd'
Signed-off-by: Amos
Paul Brook p...@codesourcery.com writes:
IMO the no_user flag is a bug, and should not exist.
Sorry, what's that?
Usually an indication that a device has been incorrectly or inproperly
converted to the qdev interface.
Can also be an indication that the device can't support
On 03/24/2010 03:56 PM, Paul Brook wrote:
On 03/24/2010 12:19 PM, Richard Henderson wrote:
On 03/24/2010 02:47 AM, Paolo Bonzini wrote:
1) make CPUState define only common fields. Include CPUState at the
beginning of each per-target CPUXYZState.
Irritatingly, the common fields contain quite
On Wed, 24 Mar 2010 12:42:16 +0200
Avi Kivity a...@redhat.com wrote:
So, at best qemud is a toy for people who are annoyed by libvirt.
Is the reason for doing this in qemu because libvirt is annoying? I don't see
how adding yet another layer/daemon is going to improve ours and user's life
(the
On 03/24/2010 07:45 AM, Paolo Bonzini wrote:
On 03/24/2010 12:19 PM, Richard Henderson wrote:
On 03/24/2010 02:47 AM, Paolo Bonzini wrote:
1) make CPUState define only common fields. Include CPUState at the
beginning of each per-target CPUXYZState.
Irritatingly, the common fields contain
1) make CPUState define only common fields. Include CPUState at the
beginning of each per-target CPUXYZState.
Irritatingly, the common fields contain quite big TLBs. And the
offsets from the start of env affect the compactness of the code
generated from TCG. We really really want the
We're in a bad situation with the S390 qemu target. It only works with KVM,
so people can't test it when they don't have access to a real S390 machine.
While trying to build and use s390x-softmmu again I stumbled across a couple
of issues, all addressed in this patch set. The patches should all
We don't implement any virtual memory in the S390 target so far, so let's
add a stub for this now mandatory function.
Fixes building of S390 target.
Signed-off-by: Alexander Graf ag...@suse.de
---
target-s390x/helper.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git
As soon as virtio-pci.c gets compiled and used on S390 the internal qdev magic
gets confused and tries to give us PCI devices instead of S390 virtio devices.
Since we don't have PCI on S390, we can safely not compile virtio-pci at all.
In order to do this I added a new config option CONFIG_PCI
The KVM kernel module on S390 refuses to create a VM when the switch_amode
kernel parameter is not used.
Since that is not exactly obvious, let's give the user a nice warning.
Signed-off-by: Alexander Graf ag...@suse.de
---
kvm-all.c |7 ++-
1 files changed, 6 insertions(+), 1
On 3/24/10, Juan Quintela quint...@redhat.com wrote:
Blue Swirl blauwir...@gmail.com wrote:
Hi,
Here's some planning for getting most files compiled as few times as
possible. Comments and suggestions are welcome.
I took some thought about this at some point. Problems here start
Michael S. Tsirkin wrote:
On Tue, Mar 23, 2010 at 12:55:07PM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Tue, Mar 23, 2010 at 10:57:33AM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari
On 3/24/10, Richard Henderson r...@twiddle.net wrote:
On 03/24/2010 02:47 AM, Paolo Bonzini wrote:
1) make CPUState define only common fields. Include CPUState at the
beginning of each per-target CPUXYZState.
Irritatingly, the common fields contain quite big TLBs. And the
offsets
On 3/24/10, Alexander Graf ag...@suse.de wrote:
As soon as virtio-pci.c gets compiled and used on S390 the internal qdev magic
gets confused and tries to give us PCI devices instead of S390 virtio
devices.
Since we don't have PCI on S390, we can safely not compile virtio-pci at all.
In
Blue Swirl wrote:
On 3/24/10, Alexander Graf ag...@suse.de wrote:
As soon as virtio-pci.c gets compiled and used on S390 the internal qdev
magic
gets confused and tries to give us PCI devices instead of S390 virtio
devices.
Since we don't have PCI on S390, we can safely not compile
On Wed, Mar 24, 2010 at 10:58:50AM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Tue, Mar 23, 2010 at 12:55:07PM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin wrote:
On Tue, Mar 23, 2010 at 10:57:33AM -0700, Badari Pulavarty wrote:
Michael S. Tsirkin
On 3/24/10, Alexander Graf ag...@suse.de wrote:
Blue Swirl wrote:
On 3/24/10, Alexander Graf ag...@suse.de wrote:
As soon as virtio-pci.c gets compiled and used on S390 the internal qdev
magic
gets confused and tries to give us PCI devices instead of S390 virtio
devices.
On Tue, 23 Mar 2010 11:27:54 +0100
Markus Armbruster arm...@redhat.com wrote:
PATCH 3/4 changes syntax of set_link's second argument from up|down to
on|off. I feel that the argument needs to be boolean in QMP, and this
is the simplest way to get it.
Alternatives I could try if the syntax
This patch adds initial support for the -machine option, that allows
command line specification of machine attributes (always relying on safe
defaults). Besides its value per-se, it is the saner way we found to
allow for enabling/disabling of kvm's in-kernel irqchip.
A machine with
this way, the machine_init function itself can know which machine is current
in use, not only the late init code.
---
vl.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index d69250c..ceddeac 100644
--- a/vl.c
+++ b/vl.c
@@ -4841,6 +4841,9 @@ int
Blue Swirl blauwir...@gmail.com wrote:
On 3/24/10, Juan Quintela quint...@redhat.com wrote:
Blue Swirl blauwir...@gmail.com wrote:
Hi,
Here's some planning for getting most files compiled as few times as
possible. Comments and suggestions are welcome.
I took some thought about
On Tue, 23 Mar 2010 11:27:56 +0100
Markus Armbruster arm...@redhat.com wrote:
This is a boolean value. Human monitor accepts on or off.
Consistent with option parsing (see parse_option_bool()).
Signed-off-by: Markus Armbruster arm...@redhat.com
---
monitor.c | 31
On Tue, 23 Mar 2010 19:07:21 +0100
Markus Armbruster arm...@redhat.com wrote:
Human monitor error message changes from unknown migration protocol:
FOO to Invalid parameter uri.
The conversion is shallow: the FOO_start_outgoing_migration() aren't
converted. Converting them is a big job for
On 03/24/2010 02:26 PM, Glauber Costa wrote:
This patch adds initial support for the -machine option, that allows
command line specification of machine attributes (always relying on safe
defaults). Besides its value per-se, it is the saner way we found to
allow for enabling/disabling of kvm's
On 03/24/10 18:04, Juan Quintela wrote:
Gerd Hoffmannkra...@redhat.com wrote:
The bochs vbe interface got a new register a while back, which specifies
the linear framebuffer size in 64k units. This patch adds support for
the new register to qemu. With this patch applied vgabios 0.6c works
The bochs vbe interface got a new register a while back, which specifies
the linear framebuffer size in 64k units. This patch adds support for
the new register to qemu. With this patch applied vgabios 0.6c works
with qemu.
[ v2: Don't savevm the new register. Doing so breaks migration,
On 03/24/2010 06:42 PM, Luiz Capitulino wrote:
On Wed, 24 Mar 2010 12:42:16 +0200
Avi Kivitya...@redhat.com wrote:
So, at best qemud is a toy for people who are annoyed by libvirt.
Is the reason for doing this in qemu because libvirt is annoying?
Mostly.
I don't see
how
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl wrote:
rtl8139.c, e1000.c: need to convert ldl/stl to
cpu_physical_memory_read/write.
I don't see how it would help. These still get target_phys_addr_t which
is per-target.
On Wed, 24 Mar 2010 21:49:45 +0200
Avi Kivity a...@redhat.com wrote:
On 03/24/2010 06:42 PM, Luiz Capitulino wrote:
On Wed, 24 Mar 2010 12:42:16 +0200
Avi Kivitya...@redhat.com wrote:
So, at best qemud is a toy for people who are annoyed by libvirt.
Is the reason for
On 03/24/2010 10:07 AM, Richard Henderson wrote:
struct CPUSmallCommonState
{
// most of the stuff from CPU_COMMON.
// sorted for some thought of padding elimination. ;-)
};
struct CPULargeCommonState
{
CPUTLBEntry tlb_table[NB_MMU_MODES][CPU_TLB_SIZE];
On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl wrote:
rtl8139.c, e1000.c: need to convert ldl/stl to
cpu_physical_memory_read/write.
I don't see how it would
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl wrote:
rtl8139.c, e1000.c: need to convert ldl/stl to
On Wed, Mar 24, 2010 at 10:24:12PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl
On 03/24/2010 03:24 PM, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkinm...@redhat.com wrote:
On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkinm...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Mar 24, 2010 at 10:24:12PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, 24 Mar 2010 20:19:28 +0530
Amit Shah amit.s...@redhat.com wrote:
When adding a port or a device to the guest fails, management software
might be interested in knowing and then cleaning up the host-side of the
port. Introduce QMP events to signal such errors.
I'm completely unfamiliar
On Wed, 24 Mar 2010 17:00:14 +0100
Markus Armbruster arm...@redhat.com wrote:
Amos Kong ak...@redhat.com writes:
When input some invialid word 'unknowcmd' through QMP port, qemu outputs
this
error message:
parse error: invalid keyword `%s'
This patch makes qemu output the content of
Hi,
I've been investigating why some of my code failed on qemu, but
succeeded in bochs and on real hardware. In particular, it turns out
that qemu would reset the FS/GS_BASE_MSR whenever I did iret from ring
0 to 3.
I traced it down to this bit of code (in target-i386/op_helper.c):
static
Make win2k install hack unconditional as it is still restricted to
x86 only in vl.c.
Replace TARGET_PAGE_SIZE with 4096 because that figure is already
used later.
Signed-off-by: Blue Swirl blauwir...@gmail.com
---
Makefile.objs|1 +
Makefile.target
On 24.03.2010, at 21:32, Anthony Liguori wrote:
On 03/24/2010 03:12 PM, Luiz Capitulino wrote:
On Wed, 24 Mar 2010 21:49:45 +0200
Avi Kivitya...@redhat.com wrote:
On 03/24/2010 06:42 PM, Luiz Capitulino wrote:
On Wed, 24 Mar 2010 12:42:16 +0200
Avi Kivitya...@redhat.com
On Wed, Mar 24, 2010 at 02:43:35PM -0500, Anthony Liguori wrote:
On 03/24/2010 02:26 PM, Glauber Costa wrote:
This patch adds initial support for the -machine option, that allows
command line specification of machine attributes (always relying on safe
defaults). Besides its value per-se, it is
On Wed, Mar 24, 2010 at 10:24:12PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
On 3/24/10, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl
On 03/24/2010 03:58 PM, Glauber Costa wrote:
On Wed, Mar 24, 2010 at 02:43:35PM -0500, Anthony Liguori wrote:
On 03/24/2010 02:26 PM, Glauber Costa wrote:
This patch adds initial support for the -machine option, that allows
command line specification of machine attributes (always
On Wed, 24 Mar 2010 21:54:09 +0100
Alexander Graf ag...@suse.de wrote:
On 24.03.2010, at 21:32, Anthony Liguori wrote:
On 03/24/2010 03:12 PM, Luiz Capitulino wrote:
On Wed, 24 Mar 2010 21:49:45 +0200
Avi Kivitya...@redhat.com wrote:
On 03/24/2010 06:42 PM, Luiz Capitulino
On 03/24/2010 04:25 PM, Luiz Capitulino wrote:
I see it as a related problem, because what seems to be under discussion
is the quality of our interfaces with humans and tools.
Also, when we were discussing the usuability problems I remember that
you
*WARNING: I might be wrong here, please
Hello All,
Please review patch for TBL SPR read access for generic PPC.
*Description:*
POWER specification docs define TBL/TBU SPRs as readable in user
and privileged modes. Therefore SPRs permissions were changed in gen_tbl
function in target-ppc/translate_init.c file.
*Testing:*
Tested with
Gerd Hoffmann kra...@redhat.com wrote:
The bochs vbe interface got a new register a while back, which specifies
the linear framebuffer size in 64k units. This patch adds support for
the new register to qemu. With this patch applied vgabios 0.6c works
with qemu.
[ v2: Don't savevm the new
Gerd Hoffmann kra...@redhat.com wrote:
On 03/24/10 18:04, Juan Quintela wrote:
Gerd Hoffmannkra...@redhat.com wrote:
The bochs vbe interface got a new register a while back, which specifies
the linear framebuffer size in 64k units. This patch adds support for
the new register to qemu. With
But now there is a bigger problem, how to pass the property to the
device. It's not fair to require the user to remember to set it.
It should not be a property of the device. All devices have a native
endianness (for PCI this is little-endian), and the intermediate
busses/interconnects should
I have a native build under qemu that gets killed if it doesn't produce a line
of output for 60 seconds (hang detection enforced by the host monitoring
qemu's stdout with --nographic, not from within qemu).
In the most recent release version, it never came close to triggering on mips
with a 30
1 - 100 of 123 matches
Mail list logo
