Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI patches.
thanks,
-chris
On 22.03.2010, at 22:49, Anthony Liguori wrote:
On 03/22/2010 03:10 PM, Daniel P. Berrange wrote:
What's the feeling about this from the libvirt side of things? Is there
interest in support hypervisor specific interfaces should we be looking
to provide our own management interface for
Replaces direct phys_ram_dirty access with wrapper functions to prevent
direct access to the phys_ram_dirty bitmap.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by: OHMURA Kei ohmura@lab.ntt.co.jp
---
exec.c | 45 -
1
Before replacing byte-based dirty bitmap with bit-based dirty bitmap,
clearing direct accesses to the bitmap first seems to be good point to
start with.
This patch set is based on the following discussion.
http://www.mail-archive.com/k...@vger.kernel.org/msg30724.html
Also rebased to qemu.git
Adds wrapper functions to prevent direct access to the phys_ram_dirty bitmap.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by: OHMURA Kei ohmura@lab.ntt.co.jp
---
cpu-all.h | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
diff
Hi, my name is haeil.
I want to get small linux image file for ARM platform or x86 platform. This
image file must be QCOW2 format because I want to use snapshot function.
Already I did try to covert the raw image file(download from qemu.org) to
QCOW2 image format by using convert function.
Chris Wright chr...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI patches.
- migration (we didn't end last week)
- virtIODevice model (see Virtio cleaup thread). What is the best model
for
2010/3/23 현해일 pla...@gmail.com:
Hi, my name is haeil.
I want to get small linux image file for ARM platform or x86 platform. This
image file must be QCOW2 format because I want to use snapshot function.
Already I did try to covert the raw image file(download from qemu.org) to
QCOW2
On 03/22/10 22:53, Anthony Liguori wrote:
On 03/22/2010 04:33 PM, Gerd Hoffmann wrote:
libvirt is very unfriendly to qemu hackers. There is no easy way to
add command line switches. There is no easy way to get access to the
monitor. I can get it done by pointing emulator to a wrapper script
and
On 03/23/2010 09:39 AM, Yoshiaki Tamura wrote:
Before replacing byte-based dirty bitmap with bit-based dirty bitmap,
clearing direct accesses to the bitmap first seems to be good point to
start with.
Reviewed-by: Avi Kivity a...@redhat.com
--
error compiling committee.c: too many
On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
Hi!
I just wanted to make another FreeBSD qemu git head snaphot port update,
and found both i386-softmmu and x86_64-softmmu no longer boot, they seem
to hang
Chris Wright wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI patches.
- state and roadmap for upstream merge of in-kernel device models
(looks to me like this central merge effort is stalled ATM)
Aurelien Jarno aurel...@aurel32.net writes:
On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
Hi!
I just wanted to make another FreeBSD qemu git head snaphot port update,
and found both i386-softmmu and
v1 - v2
cosmetic change of if block arrangement
Signed-off-by: Naphtali Sprei nsp...@redhat.com
---
vl.c | 13 +
1 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/vl.c b/vl.c
index d69250c..11c68f2 100644
--- a/vl.c
+++ b/vl.c
@@ -1222,19 +1222,16 @@ DriveInfo
On 03/23/10 09:54, Jes Sorensen wrote:
On 03/22/10 22:53, Anthony Liguori wrote:
On 03/22/2010 04:33 PM, Gerd Hoffmann wrote:
libvirt is very unfriendly to qemu hackers. There is no easy way to
add command line switches. There is no easy way to get access to the
monitor. I can get it done by
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 change is unwanted:
* Use the old string argument in QMP. Easy.
* Don't convert
On 03/23/10 11:25, Gerd Hoffmann wrote:
On 03/23/10 09:54, Jes Sorensen wrote:
One problem I have found, and I am not sure how to fix this in this
context. Sometimes when hacking on qemu, I want to try out a new
qemu binary on an existing image, without replacing the system wide
one and may
Second argument is now on or off instead of up or down.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
net.c | 10 ++
qemu-monitor.hx |8
2 files changed, 6 insertions(+), 12 deletions(-)
diff --git a/net.c b/net.c
index 80e9025..673b6ec 100644
---
Signed-off-by: Markus Armbruster arm...@redhat.com
---
net.c |7 ---
net.h |2 +-
qemu-monitor.hx |3 ++-
3 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/net.c b/net.c
index 673b6ec..96f2670 100644
--- a/net.c
+++ b/net.c
@@ -1283,7 +1283,7 @@
To make 'b' available for boolean argument.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
monitor.c |8
qemu-monitor.hx |2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/monitor.c b/monitor.c
index 35cbce7..3ce9a4e 100644
--- a/monitor.c
+++
- 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).
cheers,
Gerd
On 03/19/2010 03:12 PM, Anthony Liguori wrote:
On 03/19/2010 07:58 AM, Paolo Bonzini wrote:
1) Change the default CPUID bits from 6/2/3 to 6/6/1, this passes the
Linux kernel check. But I am not sure if that would introduce
regressions, since some OSes apply quirks if they detect certain
On Mon, Mar 22, 2010 at 08:16:01PM -0500, Anthony Liguori wrote:
On 03/22/2010 07:49 PM, Paul Brook wrote:
Solutions:
- VirtIOPCIBus and hang devices from there (anthony). Why? because
this is a simulated pci bus, we can implement the features that we
need (not full pci) in the three
Gerd Hoffmann kra...@redhat.com 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).
This is a war for another day :-)
I
On 03/23/2010 12:50 PM, Jan Kiszka wrote:
Avi Kivity wrote:
On 03/23/2010 11:31 AM, Jan Kiszka wrote:
Chris Wright wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI
patches.
On 03/23/10 11:31, Jes Sorensen wrote:
On 03/23/10 11:25, Gerd Hoffmann wrote:
[r...@xenb ~]# virsh dumpxml fedora | grep emulator
emulator/root/bin/qemu-wrapper/emulator
[r...@xenb ~]# cat /root/bin/qemu-wrapper
Ah right thanks! However, it's a hack to get around the real problem
with
Avi Kivity wrote:
On 03/23/2010 12:50 PM, Jan Kiszka wrote:
Avi Kivity wrote:
On 03/23/2010 11:31 AM, Jan Kiszka wrote:
Chris Wright wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI
On 03/23/2010 11:06 AM, Markus Armbruster wrote:
Aurelien Jarnoaurel...@aurel32.net writes:
On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
Hi!
I just wanted to make another FreeBSD qemu git head snaphot port
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
Right. The only real challenge is dealing with legacy save/restore and
command line syntax. For save/restore, we can possibly have a dummy
device that can split the VirtioPCI device state from the virtio device
states and do the right thing.
I'm not sure what we should do for command
On Tue, Mar 23, 2010 at 11:40:46AM +, Paul Brook wrote:
Right. The only real challenge is dealing with legacy save/restore and
command line syntax. For save/restore, we can possibly have a dummy
device that can split the VirtioPCI device state from the virtio device
states and do
Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:50:57AM +0100, Juan Quintela wrote:
Gerd Hoffmann kra...@redhat.com 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
Hi,
I read, that it´s possible, to emulate an x64-Processor with QEMU on an
x86-based PC, isn´t it.
When I run the installation of Ubuntu-9.10-x64 under Qemu-Manager 6.0 under
Windows-XP, I always get an storage-error.
Who can help me, to solve that problem?
With best regards,
Christoph Funda
On 03/23/2010 01:13 PM, Jan Kiszka wrote:
The benefit would be that qemu-kvm.git would become a staging tree
instead of the master repository for kvm users. As an example, we
wouldn't have any bisectability problems. kvm features would need to be
written just once.
The last item
Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Mar 23, 2010 at 11:40:46AM +, Paul Brook wrote:
Right. The only real challenge is dealing with legacy save/restore and
command line syntax. For save/restore, we can possibly have a dummy
device that can split the VirtioPCI device
On 03/23/2010 01:11 AM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI patches.
I can't make today's call. I'd hoping there's a discussion about
libqemu and libvirt though and that
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari Pulavarty wrote:
Write Results:
==
I see degraded IO performance when doing sequential IO write
tests with vhost-blk compared to virtio-blk.
# time dd of=/dev/vda if=/dev/zero bs=2M oflag=direct
I get ~110MB/sec with
On 03/23/2010 04:52 AM, Avi Kivity wrote:
On 03/23/2010 11:31 AM, Jan Kiszka wrote:
Chris Wright wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI
patches.
- state and roadmap for upstream merge of
On 03/23/2010 02:45 PM, Anthony Liguori wrote:
On 03/23/2010 04:52 AM, Avi Kivity wrote:
On 03/23/2010 11:31 AM, Jan Kiszka wrote:
Chris Wright wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI
patches.
, R4, R4.5 and R5.
The warning suggest the block device is seen as having a size of 0,
though oddly it seems to be able to read from it since it gets the
size
of the BFS in the superblock...
I've rebuilt with DEBUG_IDE and put a log here:
http://revolf.free.fr/beos/qemu-beosr5-bad-ide-20100323
On 03/23/10 13:45, Anthony Liguori wrote:
I don't think we can pull in:
- extboot
- ia64
- in-kernel pit[1]
- associated command line options
- device passthrough
The question is, if we dropped those things, would people actually use
qemu.git instead of qemu-kvm.git. If the answer is no, what
It's a known bug but nobody knows or has time to apply a solution.
Bochs had the same bug and corrected it about November 2009, maybe
checking their commit will make light to correct QEMU.
Ok, I might have a look at it, thanks.
It seems VirtualBox has the same issue. Older versions (ZETA)
Juan Quintela quint...@redhat.com wrote:
Chris Wright chr...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
Yes, usability is a valid topic esp. if you promise to come w/ GUI patches.
- migration (we didn't end last week)
I told last Tuesday that I will
Hello,
[any reason you dropped the CC list? CC'ing qemu-devel, where this is
relevant.]
On (Tue) Mar 23 2010 [21:46:28], Liang YANG wrote:
I check the 'lspci -v' result, only find RTL-8139 realtek ethernet. I
think the option model=virtio does't make effect.
Then something is wrong. I get a
Hello,
These patches rework the way ports are announced to the guests. A
control message is used to let the guest know a new port is
added. Initial port discovery and port hot-plug work via this way now.
This was done to have the host and guest port numbering in sync to
avoid surprises after
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 | 10
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
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
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 bd44ec6..e915491 100644
---
If some ports that were hot-plugged on the source are not available on
the destination, fail migration instead of trying to deref a NULL
pointer.
Signed-off-by: Amit Shah amit.s...@redhat.com
Reported-by: Juan Quintela quint...@redhat.com
---
hw/virtio-serial-bus.c |7 +++
1 files
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
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 | 22 +++---
1 files changed, 15 insertions(+), 7 deletions(-)
diff --git
Amit Shah amit.s...@redhat.com wrote:
Hello,
These patches rework the way ports are announced to the guests. A
control message is used to let the guest know a new port is
added. Initial port discovery and port hot-plug work via this way now.
This was done to have the host and guest port
On 03/23/2010 09:51 AM, Daniel Veillard wrote:
On Mon, Mar 22, 2010 at 02:25:00PM -0500, Anthony Liguori wrote:
Hi,
Hi Anthony,
I've mentioned this to a few folks already but I wanted to start a
proper thread.
We're struggling in qemu with usability and one area that
migration (we didn't end last week)
- monotonic increasing version doesn't capture individual features
(backporting features may not require earlier features, now id is
incorrect)
- use subsections
- can create new namespace within subsection (ide/$featre/$distro)
- would need to
On (Tue) Mar 23 2010 [20:00:19], Amit Shah wrote:
@@ -369,16 +370,23 @@ static void handle_output(VirtIODevice *vdev, VirtQueue
*vq)
* with it. Just ignore the data in that case.
*/
if (!port-info-have_data) {
-ret = 0;
goto next_buf;
On 03/23/2010 10:57 AM, Paul Brook wrote:
I think there is a serious divergence of approach there, instanciating
API stating 'we are gonna deprecate them sooner or later' tell the
application developper 'my time is more important than yours' and not
really something I like to carry to the API
On Mon, Mar 22, 2010 at 10:48:02AM +0530, Amit Shah wrote:
On (Sat) Mar 20 2010 [09:40:50], Avi Kivity wrote:
On 03/19/2010 01:58 PM, Amit Shah wrote:
+
+offset = 0;
+for (i = 0; i elem.out_num; i++) {
+memcpy(buf + offset, elem.out_sg[i].iov_base,
+
I think there is a serious divergence of approach there, instanciating
API stating 'we are gonna deprecate them sooner or later' tell the
application developper 'my time is more important than yours' and not
really something I like to carry to the API users.
The main goal of libvirt
On (Tue) Mar 23 2010 [17:51:26], Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 10:48:02AM +0530, Amit Shah wrote:
On (Sat) Mar 20 2010 [09:40:50], Avi Kivity wrote:
On 03/19/2010 01:58 PM, Amit Shah wrote:
+
+offset = 0;
+for (i = 0; i elem.out_num; i++) {
+
This fixes a copy/paste bug introduced in commit
2d48377a8531de63ec1d0c4b9b1959dc4b78356c that pushed TARGET_WORDS_BIGENDIAN
dependency to board level.
Signed-off-by: Lars Munch l...@segv.dk
---
hw/pxa2xx.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/pxa2xx.c
On Tue, Mar 23, 2010 at 09:45:08PM +0530, Amit Shah wrote:
On (Tue) Mar 23 2010 [17:51:26], Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 10:48:02AM +0530, Amit Shah wrote:
On (Sat) Mar 20 2010 [09:40:50], Avi Kivity wrote:
On 03/19/2010 01:58 PM, Amit Shah wrote:
+
+
Hi,
Can anyone tell me what subpage for in exec.c?
Best regards
Hello,
I am involved in a project that we use Qemu user mode for i386
(./i386-linux-user/qemu-i386). I want to modify the source code
in such a way to make qemu execute a buffer of bytes (given from the comman
line for example) rather than loading
an ELF file and executing. I started looking at
On 03/22/2010 09:25 PM, Anthony Liguori wrote:
Hi,
I've mentioned this to a few folks already but I wanted to start a
proper thread.
We're struggling in qemu with usability and one area that concerns me
is the disparity in features that are supported by qemu vs what's
implemented in
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 fundamental topic here is, do we introduce these missing
components to allow people to build directly to
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qerror.c |4
qerror.h |3 +++
2 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/qerror.c b/qerror.c
index 8d885cd..560e70d 100644
--- a/qerror.c
+++ b/qerror.c
@@ -141,6 +141,10 @@ static const QErrorStringTable
Markus Armbruster (3):
QError: New QERR_MIGRATION_IN_PROGRESS
QError: New QERR_MIGRATION_FAILED
monitor: Convert do_migrate() to QError
migration.c |9 +
qerror.c|8
qerror.h|6 ++
3 files changed, 19 insertions(+), 4 deletions(-)
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 relatively little
practical benefit, so leave it for later.
Signed-off-by: Markus
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qerror.c |4
qerror.h |3 +++
2 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/qerror.c b/qerror.c
index 560e70d..05ea9de 100644
--- a/qerror.c
+++ b/qerror.c
@@ -141,6 +141,10 @@ static const QErrorStringTable
On Tue, Mar 23, 2010 at 11:06:20AM -0500, Anthony Liguori wrote:
On 03/23/2010 10:57 AM, Paul Brook wrote:
I think there is a serious divergence of approach there, instanciating
API stating 'we are gonna deprecate them sooner or later' tell the
application developper 'my time is more important
On Tue, Mar 23, 2010 at 08:00:21PM +0200, 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 fundamental topic here is, do we introduce
On 3/23/10, Aurelien Jarno aurel...@aurel32.net wrote:
On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
Hi!
I just wanted to make another FreeBSD qemu git head snaphot port update,
and found both
Hi,
On 03/23/2010 02:24 PM, Blue Swirl wrote:
On 3/23/10, Aurelien Jarnoaurel...@aurel32.net wrote:
On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
Hi!
I just wanted to make another FreeBSD
On 3/23/10, Michael Qiu fallw...@gmail.com wrote:
Hi,
Can anyone tell me what subpage for in exec.c?
It's there so that several devices can register MMIO ranges that
happen to be in the same target physical page.
On 03/23/2010 01: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 fundamental topic here is, do we introduce these
missing
On 03/23/2010 01:07 PM, Daniel P. Berrange wrote:
On Tue, Mar 23, 2010 at 11:06:20AM -0500, Anthony Liguori wrote:
On 03/23/2010 10:57 AM, Paul Brook wrote:
I think there is a serious divergence of approach there, instanciating
API stating 'we are gonna deprecate them sooner or
Thanks, applied.
On 3/22/10, Juergen Lock n...@jelal.kn-bremen.de wrote:
Signed-off-by: Juergen Lock n...@jelal.kn-bremen.de
--- a/bsd-user/main.c
+++ b/bsd-user/main.c
@@ -759,6 +759,10 @@ int main(int argc, char **argv)
}
cpu_model = NULL;
+#if defined(cpudef_setup)
+
* After Anthony patches, and Luiz comments
Qemu support for multiple keyboard devices:
Patch #1 adding keyboard is done to list instead of last added keyboard
wins, when removing keyboard via device_del - next keyboard
selected.
Patch #2 adding 2 new monitor command to handle
Currently you get segfault when trying to remove keyboard (device_del
monitor command) because no keyboard handling is done.
This patch add QEMUPutKbdEntry structure, handling each keyboard entry.
Adding a keyboard add to the list, removing keyboard select the previous
keyboard in list.
Anthony Liguori anth...@codemonkey.ws writes:
Hi,
On 03/23/2010 02:24 PM, Blue Swirl wrote:
On 3/23/10, Aurelien Jarnoaurel...@aurel32.net wrote:
On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
Two new monitor commands: adding ability to handle which keyboard qemu will
use and to see which keyboard are currently available.
$ info keyboard
$ keyboard_set index
Signed-off-by: Shahar Havivi shah...@redhat.com
---
console.h |4 ++
input.c | 104
Hi,
Inspired by vhost-net implementation, I did initial prototype
of vhost-blk to see if it provides any benefits over QEMU virtio-blk.
I haven't handled all the error cases, fixed naming conventions etc.,
but the implementation is stable to play with. I tried not to deviate
from vhost-net
Hi, all.
I have just touched QEMU and I am doing experiments of malware using the
emulator.
I need some development docs for reference.
Appreciate your help.
Hi,
I read, that it´s possible, to emulate an x64-Processor with QEMU on an
x86-based PC, isn´t it.
When I run the installation of Ubuntu-9.10-x64 under Qemu-Manager 6.0 under
Windows-XP, I always get an storage-error.
Who can help me, to solve that problem?
With best regards,
Christoph
I use the qemu-kvm-0.12-3 version source file. Just follow the typical
three steps: ./configure make make install.
After I configure, following is output:
Install prefix/usr/local
BIOS directory/usr/local/share/qemu
binary directory /usr/local/bin
Manual directory
Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari Pulavarty wrote:
Write Results:
==
I see degraded IO performance when doing sequential IO write
tests with vhost-blk compared to virtio-blk.
# time dd of=/dev/vda if=/dev/zero bs=2M oflag=direct
I get
Michael S. Tsirkin wrote:
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari Pulavarty wrote:
Write Results:
==
I see degraded IO performance when doing sequential IO write
tests with vhost-blk compared to virtio-blk.
# time dd of=/dev/vda if=/dev/zero bs=2M oflag=direct
I get
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:
==
I see degraded IO performance when doing sequential IO write
On Fri, Mar 19, 2010 at 11:31:15AM +0100, Paolo Bonzini wrote:
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
dyngen-exec.h | 26 --
tcg/arm/tcg-target.h|2 --
tcg/hppa/tcg-target.h |2 --
tcg/i386/tcg-target.h |2 --
On Sat, Feb 20, 2010 at 11:31:31AM -0800, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
Thanks, applied.
---
hppa-dis.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hppa-dis.c b/hppa-dis.c
index 9d96d72..49f99c8 100644
---
On Sat, Feb 20, 2010 at 11:32:23AM -0800, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
Thanks, applied.
---
tcg/tcg.c | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/tcg/tcg.c b/tcg/tcg.c
index 1818868..d753149 100644
On Wed, Mar 17, 2010 at 07:56:12AM -0700, Richard Henderson wrote:
On 03/16/2010 06:58 PM, Stuart Brady wrote:
The tcg_reg_free() calls worry me slightly, but I assume they're safe...
Yeah, that one's rather gross.
Since Aurelien's generic div/rem patch I could simply remove all
that
On Wed, Mar 17, 2010 at 01:56:07PM +0100, Johan Bengtsson wrote:
Do not try to insert a conditional jump over next instruction when the
condition code is AL as this will trigger an internal error.
Signed-off-by: Johan Bengtsson teofrast...@gmail.com
Thanks, applied.
---
http://bochs.cvs.sourceforge.net/bochs/bochs/CHANGES?view=markupcontent-type=text/vnd.viewcvs-markuprevision=REL_2_4_2_FINAL
2.2.5 December 2005 BeOS boot failure fix in the PCI IDE code
2.3.5 September 2007 [1500216] Bochs fails to boot BeOs CD
I had a look at it, but it seems it's only
Hi,
Here's some planning for getting most files compiled as few times as
possible. Comments and suggestions are welcome.
I have now converted most of the easy cases which were compiled for
all targets, saving about 200 compiles for full build with default set
of targets (~1500 files compiled).
On Mon, 22 Mar 2010 10:28:59 +0100
Markus Armbruster arm...@redhat.com wrote:
Cleaner integration of location tracking with qemu-tool.c. Move
qerror_report() where it belongs.
v2: Remove an assertion that unreachable code can't be reached, at
Blue Swirl's request. Rebased.
Markus
On Mon, 22 Mar 2010 10:48:53 +0100
Markus Armbruster arm...@redhat.com wrote:
Monitor commands to go with -netdev.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
net.c | 57
++-
net.h |2 +
http://bochs.cvs.sourceforge.net/bochs/bochs/CHANGES?view=markupcontent-type=text/vnd.viewcvs-markuprevision=REL_2_4_2_FINAL
2.2.5 December 2005 BeOS boot failure fix in the PCI IDE code
2.3.5 September 2007 [1500216] Bochs fails to boot BeOs CD
Hmm actually, I begin to think it just
1 - 100 of 122 matches
Mail list logo
