Am 16.09.2010 19:20 schrieb Anthony Liguori:
> Instead of using FILE, I'd suggest using a BlockDriver to read and write
> the data.
I'll fix that as soon as I figured how to use this interface.
> I think it would be very nice to add write support too so that writes to
> CMOS were persisted across
Am 16.09.2010 18:49, Stefan Weil schrieb:
> The intention of this patch is ok. Loading CMOS with initial data
> is needed. I just want to add two questions / remarks how the
> implementation might be improved.
>
> Are there use cases where having a smaller CMOS size is better?
> For example, when
stefa...@linux.vnet.ibm.com wrote on Mon, 6 Sep 2010 11:04:38 +0100:
> QEMU Enhanced Disk format is a disk image format that forgoes features
> found in qcow2 in favor of better levels of performance and data
> integrity. Due to its simpler on-disk layout, it is possible to safely
> perform meta
Try to attach disk from file. I set the target name ‘vd20’
In VM node(it already loaded the acpiphp kernel module) it gets its new
file name ‘vda’
There’s two issues using like that
1. Virsh Domblkstat doesn’t work I thought that the target name I
setted(vd20) doesn’t match vm node se
On Wed, Sep 15, 2010 at 07:15:28PM +0200, Andrea Arcangeli wrote:
> Subject: add 40-48 bit RAM range to seabios
>
> From: Andrea Arcangeli
>
> Needed to show >1TB RAM to guests.
>
> This uses a new cmos port at 0x5e that shall read zero to be backwards
> compatible.
>
> Signed-off-by: Andrea A
Am 14.09.2010 07:48, Ted Harkington wrote:
> Hello,
>
> I have been trying to figure out why I cannot debug a 64 bit kernel of my
> own invention.
>
> I launch qemu-system-x86_64 with the -s -S flags, we also specify -cpu
> core2duo -vga std and a -hda with an ext2 FS holding our multiboot kernel
On Thu, 16 Sep 2010 23:49:51 +0200
Frans de Boer wrote:
> Dear reader,
>
> Using qemu-kvm-0.13-rc1 and having the boot partition as if=virtio,
> causes the attached blue screen when booting Windows XP SP3.
> Changing the interface to ide (if=ide) and the system boots normal.
Do you have the vir
** Changed in: qemu
Status: New => Confirmed
** Description changed:
--
Problems with the number of serial ports for more than two
https://bugs.launchpad.net/bugs/612452
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in
Dear Reader,
When I switch with SHIFT-CTRL-ALT-2 to the monitor mode, the resolution
of the used window goes back to 640*480. There a lot of command
available and typing help lists then all. in one long list without pause
to examine the commands. Is there a way to have a help listing per
screen in
Dear reader,
Using qemu-kvm-0.13-rc1 and having the boot partition as if=virtio,
causes the attached blue screen when booting Windows XP SP3.
Changing the interface to ide (if=ide) and the system boots normal.
I am running OpenSuse 11.3 with kernel 2.6.35.4.
If more info is needed, please don't h
16.09.2010 20:14, maxmo74 wrote:
> This bug seems to be solved and closed here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574051
>
> Is it solved in 0.12.5 or 0.13.0rc1 yet?
>
> ** Bug watch added: Debian Bug tracker #574051
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574051
QMP has its own dispatch table and documentation file
(qemu-monitor-qmp.hx), we can now drop the following QMP specific
from qemu-monitor.hx:
o SQMP/EQMP sections
o The qmp_capabilities command
o The query-commands command
However, note that QObject handlers entries are not being remo
Calls a QObject handler and emits the QMP response, also drops
monitor_call_handler() which is now unused.
Signed-off-by: Luiz Capitulino
---
monitor.c | 39 +++
1 files changed, 15 insertions(+), 24 deletions(-)
diff --git a/monitor.c b/monitor.c
index c33
This avoids handle_user_command() calling monitor_call_handler(),
which is currently shared with QMP.
Signed-off-by: Luiz Capitulino
---
monitor.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/monitor.c b/monitor.c
index d77eb4c..c332e06 100644
--- a/monitor.c
The new table is a copy of HMP's table, containing only QObject
handlers.
In the near future HMP will be making QMP calls and then we will
be able to drop QObject handlers from HMP's table.
>From now on, QMP and HMP have different query command dispatch
tables.
Signed-off-by: Luiz Capitulino
--
This function was only needed when QMP and HMP were sharing dispatch
tables, this is no longer true so just drop it.
Signed-off-by: Luiz Capitulino
---
monitor.c |5 -
monitor.h |1 -
2 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/monitor.c b/monitor.c
index ce3e5b5..
QMP has its own dispatch tables, we can now drop the following
checks:
o 'info' command: this command doesn't exist in QMP's
dispatch table, the right thing will happen when it's
issued by a client (ie. command not found error)
o monitor_handler_ported(): all QMP handlers ar
This file contains a copy of the following information from the
qemu-monitor.hx file:
o QObject handlers entries
o QMP documentation (all SQMP/EQMP sections)
Right now it's only used to generate the QMP docs in QMP/, but
next commits will turn this into QMP's command dispatch table.
It's
This is a HMP specific handler, it makes no sense to have it
under QMP.
Signed-off-by: Luiz Capitulino
---
monitor.c |5 ++---
qemu-monitor.hx |3 +--
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/monitor.c b/monitor.c
index 1d52362..ea66ac3 100644
--- a/monitor.c
That name makes no sense anymore, as dispatch tables have been split,
a better name is handler_is_qobject(), which really communicates
the handler's type.
Signed-off-by: Luiz Capitulino
---
monitor.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/monitor.c b/monito
Also update QMP functions to use it. The table is generated
from the qemu-monitor-qmp.hx file.
>From now on, QMP and HMP have different command dispatch
tables.
Signed-off-by: Luiz Capitulino
---
Makefile.target |7 +--
monitor.c | 11 +--
2 files changed, 14 insertions(
Let's follow the convention introduced by the previous commit and
call it handler_is_async().
Signed-off-by: Luiz Capitulino
---
monitor.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/monitor.c b/monitor.c
index e599e4d..d77eb4c 100644
--- a/monitor.c
+++ b/m
We now iterate over QMP's dispatch tables, no need to check for
QMP-only handlers anymore.
Signed-off-by: Luiz Capitulino
---
monitor.c | 13 -
1 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/monitor.c b/monitor.c
index 53f8665..6998b3f 100644
--- a/monitor.c
+++ b/m
As of last commit, QMP doesn't use do_info() anymore. Simplify it.
Signed-off-by: Luiz Capitulino
---
monitor.c | 39 ---
1 files changed, 8 insertions(+), 31 deletions(-)
diff --git a/monitor.c b/monitor.c
index 0ddc826..b76e227 100644
--- a/monitor.c
+++
Next commit will change how query commands are handled in a
way that the 'cmd' sanity check is also going to be needed
for query commands handling.
Let's move it out of the else body then.
Signed-off-by: Luiz Capitulino
---
monitor.c | 10 +-
1 files changed, 5 insertions(+), 5 deleti
If I understood it correcty, the is_async_return() logic was only
used to prevent QMP from issuing duplicated success responses
for asynchronous handlers.
However, QMP doesn't use do_info() anymore so this is dead logic
and (hopefully) can be safely dropped.
Signed-off-by: Luiz Capitulino
---
m
Next commit needs this new function: it will introduce the
the QMP's command dispatch table and qmp_find_cmd() will be
used to search on it.
Signed-off-by: Luiz Capitulino
---
monitor.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/monitor.c b/monitor.c
index ea6
Since its inception, QMP has been using HMP's do_info() function
to run query commands.
This was a bad choice, as it made do_info() more complex and
contributed to couple QMP and HMP.
This commit fixes that by doing the following changes:
1. Introduce qmp_find_query_cmd() and use it to directl
It's a generic version of monitor_find_command() which searches
the dispatch table passed as an argument.
Future commits will introduce new dispatch tables, so we need
common code to search them.
Signed-off-by: Luiz Capitulino
---
monitor.c | 10 --
1 files changed, 8 insertions(+), 2
The subject says it all: with this series applied we'll get different
dispatch tables for HMP and QMP, which has the side effect of making
QMP commands (such as qmp_capabilities) disappear from HMP's scope.
This is also the beginning of the Monitor's redesign, which aims to
separate QMP, HMP and c
Am 16.09.2010 um 19:13 schrieb Michael Tokarev:
> 16.09.2010 18:01, Peter Lieven wrote:
>> Hi,
>>
>> with Ubuntu 10.04 Desktop guest in Qemu-KVM 0.12.4 I sometimes see a
>> condition where the CTRL key
>> is locked and cannot be released anymore. The only way I have found to
>> solve this is to r
On 16 September 2010 19:54, Michal Suchanek wrote:
> On 16 September 2010 16:46, Avi Kivity wrote:
>> On 09/16/2010 04:37 PM, Michal Suchanek wrote:
>>>
>>> On 16 September 2010 15:38, Avi Kivity wrote:
>>> > On 09/16/2010 03:34 PM, Michal Suchanek wrote:
>>> >>
>>> >> On 16 September 2010
This patch allows to reduce the boot time from an NBD server from 225 seconds to
5 seconds (time between the "boot cd:0" and the kernel init) for the
following command lines:
./qemu-nbd -t ../ISO/debian-500-powerpc-netinst.iso
and
./ppc-softmmu/qemu-system-ppc -cdrom nbd:localhost:1024
Signed-off
Am 09.09.2010 19:32, schrieb Stefan Weil:
Am 03.08.2010 11:48, schrieb Juan Quintela:
Stefan Weil wrote:
Fix some inconsistencies (tabs and punctuation)
and try to improve grammar and spelling.
Cc: Juan Quintela
Signed-off-by: Stefan Weil
Acked-by: Juan Quintela
Anthony, please apply.
Stef
16.09.2010 18:01, Peter Lieven wrote:
> Hi,
>
> with Ubuntu 10.04 Desktop guest in Qemu-KVM 0.12.4 I sometimes see a
> condition where the CTRL key
> is locked and cannot be released anymore. The only way I have found to
> solve this is to restart
> the VM.
>
> Has anyone else experienced this so
On 09/15/2010 11:06 AM, Juan Quintela wrote:
Anthony Liguori wrote:
The use of protocols in backing_files is currently broken because of some
checks for adjusting relative pathnames.
Additionally, there's a spurious read when using an nbd protocol that can be
quite destructive when using c
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
migration.c |4 ++--
qemu-monitor.hx |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/migration.c b/migration.c
index 468d517..9ee8b17 100644
--- a/migration.c
+++ b/migration.c
@@ -132,10 +132,10 @@ int do_migr
On 09/16/2010 08:58 AM, Mathias Krause wrote:
In contrast to the BIOS and Option ROMs the CMOS content cannot be
predefined by the user. Also the amount of useable CMOS ARM is pretty
limited, even though the amount of CMOS bytes emulated by qemu is
already twice as much as of the original MC14681
LinkedIn
I'd like to add you to my professional network on LinkedIn.
- Georgios Portokalidis
Georgios Portokalidis
Postdoctoral researcher at Columbia University
Greater New York City Area
Confirm that you know Georgios Portokalidis
https://www.linkedin.com/e/-kkb1ec-ge5s0j1m-
This bug seems to be solved and closed here: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=574051
Is it solved in 0.12.5 or 0.13.0rc1 yet?
** Bug watch added: Debian Bug tracker #574051
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574051
--
Problems with the number of serial ports fo
Note that most of the section is generated by sysprep (the drivers
referencing C:\windows), only small part at the end is generated by my
script for additional drivers (references C:\drivers).
The previous images that did not have this section worked only on
controllers compatible with the MS gene
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
cutils.c | 39 +++
qemu-common.h |1 +
vl.c | 26 +++---
3 files changed, 47 insertions(+), 19 deletions(-)
diff --git a/cutils.c b/cutils.c
index 036ae3c..dabbed4 1
From: Jes Sorensen
This patch introduces cutils.c: strtobytes() and gets rid of the
multiple custom hacks for parsing byte sizes. In addition it add
supports for specifying human style sizes such as 1.5G. Last it
eliminates the horrible abuse of a float to store the byte size for
migrate_set_spee
Am 16.09.2010 15:58, schrieb Mathias Krause:
In contrast to the BIOS and Option ROMs the CMOS content cannot be
predefined by the user. Also the amount of useable CMOS ARM is pretty
limited, even though the amount of CMOS bytes emulated by qemu is
already twice as much as of the original MC146818
On 09/16/2010 04:37 PM, Michal Suchanek wrote:
On 16 September 2010 15:38, Avi Kivity wrote:
>On 09/16/2010 03:34 PM, Michal Suchanek wrote:
>>
>> On 16 September 2010 12:08, Avi Kivitywrote:
>> > On 09/14/2010 07:29 PM, Michal Suchanek wrote:
>> >>
>> >>Hello
>> >>
>> >>
On 16 September 2010 16:46, Avi Kivity wrote:
> On 09/16/2010 04:37 PM, Michal Suchanek wrote:
>>
>> On 16 September 2010 15:38, Avi Kivity wrote:
>> > On 09/16/2010 03:34 PM, Michal Suchanek wrote:
>> >>
>> >> On 16 September 2010 12:08, Avi Kivity wrote:
>> >> > On 09/14/2010 07:2
From: Jes Sorensen
Octet format relies on strtobytes which supports K/k, M/m, G/g, T/t
suffixes and unit support for humans, like 1.3G
Signed-off-by: Jes Sorensen
---
monitor.c | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monit
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
cutils.c | 34 ++
1 files changed, 26 insertions(+), 8 deletions(-)
diff --git a/cutils.c b/cutils.c
index dabbed4..67767a9 100644
--- a/cutils.c
+++ b/cutils.c
@@ -259,34 +259,52 @@ int fcntl_setfl(int fd, in
From: Jes Sorensen
'f' double is no longer used, and we should be using floating point
variables to store byte sizes. Remove it.
Signed-off-by: Jes Sorensen
---
monitor.c | 17 +
1 files changed, 1 insertions(+), 16 deletions(-)
diff --git a/monitor.c b/monitor.c
index 36300
On Thu, Sep 16, 2010 at 10:28:01AM -0400, Alexander Graf wrote:
> Roedel, Joerg wrote:
> > I'll remove it then. It would have been nice to have it there because it
> > will improve performance of svm emulation. But if it is about emulating
> > the real cpu then I'll just drop it.
>
> speed == -cpu
On 16 September 2010 15:38, Avi Kivity wrote:
> On 09/16/2010 03:34 PM, Michal Suchanek wrote:
>>
>> On 16 September 2010 12:08, Avi Kivity wrote:
>> > On 09/14/2010 07:29 PM, Michal Suchanek wrote:
>> >>
>> >> Hello
>> >>
>> >> I was trying to update some windows XP (SP3) images on kvm.
>>
Roedel, Joerg wrote:
> On Thu, Sep 16, 2010 at 10:17:09AM -0400, Alexander Graf wrote:
>
>> Roedel, Joerg wrote:
>>
>>> On Thu, Sep 16, 2010 at 10:06:48AM -0400, Avi Kivity wrote:
>>>
>>>
On 09/14/2010 05:52 PM, Joerg Roedel wrote:
> This patch a
On Thu, Sep 16, 2010 at 10:17:09AM -0400, Alexander Graf wrote:
> Roedel, Joerg wrote:
> > On Thu, Sep 16, 2010 at 10:06:48AM -0400, Avi Kivity wrote:
> >
> >> On 09/14/2010 05:52 PM, Joerg Roedel wrote:
> >>
> >>> This patch adds the svm cpuid feature flags to the qemu
> >>> intializatio
On 09/16/2010 04:21 PM, Roedel, Joerg wrote:
On Thu, Sep 16, 2010 at 10:03:19AM -0400, Avi Kivity wrote:
>On 09/14/2010 05:52 PM, Joerg Roedel wrote:
> > As requested by Alex this patch makes kvm64 the default CPU
> > model when qemu is started with -enable-kvm.
> >
> >
>
> This break
On Thu, Sep 16, 2010 at 10:03:19AM -0400, Avi Kivity wrote:
> On 09/14/2010 05:52 PM, Joerg Roedel wrote:
> > As requested by Alex this patch makes kvm64 the default CPU
> > model when qemu is started with -enable-kvm.
> >
> >
>
> This breaks compatiblity; if started with -M 0.13 or prior we sho
Roedel, Joerg wrote:
> On Thu, Sep 16, 2010 at 10:06:48AM -0400, Avi Kivity wrote:
>
>> On 09/14/2010 05:52 PM, Joerg Roedel wrote:
>>
>>> This patch adds the svm cpuid feature flags to the qemu
>>> intialization path. It also adds the svm features available
>>> on phenom to its cpu-defin
On Thu, Sep 16, 2010 at 10:06:48AM -0400, Avi Kivity wrote:
> On 09/14/2010 05:52 PM, Joerg Roedel wrote:
> > This patch adds the svm cpuid feature flags to the qemu
> > intialization path. It also adds the svm features available
> > on phenom to its cpu-definition and extends the host cpu
> > ty
Am 16.09.2010 15:00, schrieb Anthony Liguori:
> On 09/16/2010 03:08 AM, Kevin Wolf wrote:
>> Am 11.09.2010 16:04, schrieb Anthony Liguori:
>>
>>> The use of protocols in backing_files is currently broken because of some
>>> checks for adjusting relative pathnames.
>>>
>>> Additionally, there's
On 09/14/2010 05:52 PM, Joerg Roedel wrote:
This patch adds the svm cpuid feature flags to the qemu
intialization path. It also adds the svm features available
on phenom to its cpu-definition and extends the host cpu
type to support all svm features KVM can provide.
Does phenom really have v
On 09/14/2010 05:52 PM, Joerg Roedel wrote:
As requested by Alex this patch makes kvm64 the default CPU
model when qemu is started with -enable-kvm.
This breaks compatiblity; if started with -M 0.13 or prior we should
default to qemu64.
--
error compiling committee.c: too many arguments t
Hi,
with Ubuntu 10.04 Desktop guest in Qemu-KVM 0.12.4 I sometimes see a
condition where the CTRL key
is locked and cannot be released anymore. The only way I have found to
solve this is to restart
the VM.
Has anyone else experienced this so far?
BR,
Peter
Hi,
with qemu-kvm 0.12.4 a saw a 64-bit linux guest with kernel 2.6.32 crash
with a oops when using scsi emulation.
it seems to be this bug:
http://www.mail-archive.com/k...@vger.kernel.org/msg08927.html
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/564924
does anyone know if this has
In contrast to the BIOS and Option ROMs the CMOS content cannot be
predefined by the user. Also the amount of useable CMOS ARM is pretty
limited, even though the amount of CMOS bytes emulated by qemu is
already twice as much as of the original MC146818. Nevertheless those
limitations are pretty ann
Hi,
I found the following assertion in my log files after a system reset was
executed
kvm: lsi_scsi: error: ORDERED queue not implemented
last message repeated 5 times
kvm: lsi_scsi: error: Unimplemented message 0x0d
kvm: lsi_scsi: error: Unimplemented message 0x0c
kvm: lsi_scsi: error: Unimpl
** Attachment added: "screenshot of the blue screen"
https://bugs.launchpad.net/qemu/+bug/639651/+attachment/1593631/+files/gkrellShoot_2010-09-16_152436.png
** Description changed:
Positng the issue here since I did not get any reply on the ML.
I was trying to update some windows XP
On 09/16/2010 03:34 PM, Michal Suchanek wrote:
On 16 September 2010 12:08, Avi Kivity wrote:
>On 09/14/2010 07:29 PM, Michal Suchanek wrote:
>>
>> Hello
>>
>> I was trying to update some windows XP (SP3) images on kvm.
>>
>> It worked fine several times but last time I added mass storage
On 16 September 2010 12:08, Avi Kivity wrote:
> On 09/14/2010 07:29 PM, Michal Suchanek wrote:
>>
>> Hello
>>
>> I was trying to update some windows XP (SP3) images on kvm.
>>
>> It worked fine several times but last time I added mass storage
>> drivers to sysprep and now on the second boot after
On 09/16/2010 03:08 AM, Kevin Wolf wrote:
Am 11.09.2010 16:04, schrieb Anthony Liguori:
The use of protocols in backing_files is currently broken because of some
checks for adjusting relative pathnames.
Additionally, there's a spurious read when using an nbd protocol that can be
quite destr
The thumb2 decoder contained a mixup between the bit controlling
doubling and the bit controlling if the operation was an add or a sub.
Signed-off-by: Johan Bengtsson
---
target-arm/translate.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-arm/translate.c b/t
The PKHxx instructions were not recognized by the thumb2 decoder. The
solution provided in this changeset is identical to the arm-mode
implementation.
Signed-off-by: Johan Bengtsson
---
target-arm/translate.c | 63 ++-
1 files changed, 45 insertions(
On Thu, Sep 16, 2010 at 11:20:43AM +0200, Michael S. Tsirkin wrote:
> On Thu, Sep 16, 2010 at 10:06:16AM +0300, Eduard - Gabriel Munteanu wrote:
[snip]
>
> No, DMADevice is a device that does DMA.
> So e.g. a PCI device would embed one.
> Remember, traslations are per device, right?
> DMAMmu is
On 09/16/2010 12:42 PM, Jes Sorensen wrote:
On 09/16/10 12:40, Avi Kivity wrote:
On 09/15/2010 09:31 PM, Jes Sorensen wrote:
Floating point is just plain wrong.
Why? If command-line processing becomes too slow, you can always buy a
math co-processor.
Because it's imprecise anyway
As Av
On 09/16/2010 12:42 PM, Jes Sorensen wrote:
On 09/16/10 12:40, Avi Kivity wrote:
> On 09/15/2010 09:31 PM, Jes Sorensen wrote:
>> Floating point is just plain wrong.
>
> Why? If command-line processing becomes too slow, you can always buy a
> math co-processor.
>
Because it's imprecise an
On 09/16/10 12:40, Avi Kivity wrote:
> On 09/15/2010 09:31 PM, Jes Sorensen wrote:
>> Floating point is just plain wrong.
>
> Why? If command-line processing becomes too slow, you can always buy a
> math co-processor.
>
Because it's imprecise anyway and requires dealing with fp regs.
Besides,
On 09/15/2010 09:31 PM, Jes Sorensen wrote:
Floating point is just plain wrong.
Why? If command-line processing becomes too slow, you can always buy a
math co-processor.
--
error compiling committee.c: too many arguments to function
On 09/16/10 09:19, Paolo Bonzini wrote:
> On 09/15/2010 09:31 PM, Jes Sorensen wrote:
>> Floating point is just plain wrong. If someone wants to do something
>> like in your example they really ask for an error.
>
> An error, not an overflow.
>
> Adding overflow checking on top of your patch is a
On 09/14/2010 07:29 PM, Michal Suchanek wrote:
Hello
I was trying to update some windows XP (SP3) images on kvm.
It worked fine several times but last time I added mass storage
drivers to sysprep and now on the second boot after reseal (the first
is mini-setup) I get a BSOD with message
DRIVER
Am 15.09.2010 20:24, schrieb edison:
> On Thu, Sep 9, 2010 at 7:08 PM, Anthony Liguori wrote:
>> On 09/09/2010 08:43 PM, disheng...@gmail.com wrote:
>>>
>>> From: edison
>>>
>>> Add a new option when "savevm": savevm -n snapshotName, which only takes
>>> snapshot on disk, but doesn't save vm state
On Mon, Sep 13, 2010 at 03:45:34PM -0500, Anthony Liguori wrote:
> On 09/13/2010 03:01 PM, Michael S. Tsirkin wrote:
> >So I think the following will give the idea of what an API
> >might look like that will let us avoid the scary hacks in
> >e.g. the ide layer and other generic layers that need to
On Thu, Sep 16, 2010 at 10:06:16AM +0300, Eduard - Gabriel Munteanu wrote:
> On Mon, Sep 13, 2010 at 10:01:20PM +0200, Michael S. Tsirkin wrote:
> > So I think the following will give the idea of what an API
> > might look like that will let us avoid the scary hacks in
> > e.g. the ide layer and ot
Got this from a qemu-microblaze user:
/opt3/home/jwilliams/petalinux/petalinux-v1.00-
devel/devel/packager/gnu/qemu/qemu-src/hw/virtio-9p.c: In function
???v9fs_setattr_post_chmod???:
/opt3/home/jwilliams/petalinux/petalinux-v1.00-
devel/devel/packager/gnu/qemu/qemu-src/hw/virtio-9p.c:1410: er
Am 15.09.2010 19:56, schrieb edison:
> On Tue, Sep 14, 2010 at 3:35 AM, Kevin Wolf wrote:
>>
>> Am 10.09.2010 02:08, schrieb disheng...@gmail.com:
>>> diff --git a/block.h b/block.h
>>> index 5f64380..9ec6219 100644
>>> --- a/block.h
>>> +++ b/block.h
>>> @@ -211,6 +211,8 @@ int bdrv_snapshot_goto
Am 11.09.2010 16:04, schrieb Anthony Liguori:
> The use of protocols in backing_files is currently broken because of some
> checks for adjusting relative pathnames.
>
> Additionally, there's a spurious read when using an nbd protocol that can be
> quite destructive when using copy-on-read. Potent
Am 15.09.2010 18:03, schrieb Juan Quintela:
> Kevin Wolf wrote:
>> Am 11.09.2010 16:04, schrieb Anthony Liguori:
>
>> There is a simple generic implementation:
>>
>> drv = bs->drv;
>> drv->close(bs);
>> drv->open(bs, bs->open_flags);
>>
>> Note that this only reopens e.g. the qcow2 layer, but not
On 09/15/2010 09:31 PM, Jes Sorensen wrote:
On 09/15/10 17:45, Paolo Bonzini wrote:
On 09/15/2010 02:23 PM, jes.soren...@redhat.com wrote:
switch (*endptr++) {
case 'K':
case 'k':
value<<= 10;
break;
case 0:
+if (divider) {
+
On Mon, Sep 13, 2010 at 03:45:34PM -0500, Anthony Liguori wrote:
> On 09/13/2010 03:01 PM, Michael S. Tsirkin wrote:
> > So I think the following will give the idea of what an API
> > might look like that will let us avoid the scary hacks in
> > e.g. the ide layer and other generic layers that need
On Mon, Sep 13, 2010 at 10:01:20PM +0200, Michael S. Tsirkin wrote:
> So I think the following will give the idea of what an API
> might look like that will let us avoid the scary hacks in
> e.g. the ide layer and other generic layers that need to do DMA,
> without either binding us to pci, adding
87 matches
Mail list logo
