On 08/09/11 16:25, Paolo Bonzini wrote:
> qemu-nbd has a limit of slightly less than 1M per request. Work
> around this in the nbd block driver.
>
> Signed-off-by: Paolo Bonzini
> ---
> block/nbd.c | 52 ++--
> 1 files changed, 46 insertions(+),
On 09.09.2011, at 16:22, Fabien Chouteau wrote:
> On 09/09/2011 15:46, Alexander Graf wrote:
>>
>> On 09.09.2011, at 15:27, Fabien Chouteau wrote:
>>
>>> On 09/09/2011 12:55, Alexander Graf wrote:
On 09.09.2011, at 12:36, Fabien Chouteau wrote:
>>>
> +}
>>>
On 09/09/2011 04:52 PM, Nicholas Thomas wrote:
I'm a bit unsure here, actually. So you lock a mutex, send a request,
wait for a response, then unlock the mutex. Surely this code doesn't
allow more than one request to be in flight at a time?
No, it doesn't. It shouldn't be hard to do it though.
On Fri, 9 Sep 2011, David Gibson wrote:
> From: Thomas Huth
>
> The ppc64 code generation backend uses an rldicr (Rotate Left Double
> Immediate and Clear Right) instruction to implement zero extension of
> a 32 bit quantity to a 64 bit quantity (INDEX_op_ext32u_i64). However
> this is wrong -
On Fri, Sep 09, 2011 at 04:04:07PM +0200, Kevin Wolf wrote:
> Am 09.09.2011 15:54, schrieb Stefan Hajnoczi:
> > On Fri, Sep 9, 2011 at 2:48 PM, Zhi Yong Wu wrote:
> >> On Fri, Sep 9, 2011 at 6:38 PM, Stefan Hajnoczi
> >> wrote:
> >>> On Fri, Sep 09, 2011 at 05:44:36PM +0800, Zhi Yong Wu wrote:
>
We are doing an experiment with kvm-clock to validate its effectiveness,
particularly when running NTP on the host to make sure the host’s clock
stays properly sync.
Our observations leads us to a few unanswered questions, including the
possibility of a bug (our our misunderstanding of how kvm_cloc
On 09/09/2011 04:52 PM, Nicholas Thomas wrote:
> +/* qemu-nbd has a limit of slightly less than 1M per request. For safety,
> + * transfer at most 512K per request. */
> +#define NBD_MAX_SECTORS 1024
As far as I'm aware, the limit of 1MiB - header size is common to all
NBD servers. I'm not
On 09/09/2011 05:03 PM, Paolo Bonzini wrote:
I'm a bit unsure here, actually. So you lock a mutex, send a request,
wait for a response, then unlock the mutex. Surely this code doesn't
allow more than one request to be in flight at a time?
No, it doesn't. It shouldn't be hard to do it though.
Si ce message ne s'affiche pas correctement, visualisez la version en ligne.
Une solution simple :
1 machine = 12 boissons, en un seul clic !
Des recettes de qualité :
5 cafés, 3 boissons gourmandes, 3 thés
et 1 infusion, de savoureuses recettes cautionnées
par de grandes marques.
Un
Ping?
On 25 August 2011 18:59, Peter Maydell wrote:
> Signed-off-by: Peter Maydell
> ---
> Another device I needed to convert so I could connect it to omap_gpmc
> for an omap3 board (in this case overo).
>
> hw/lan9118.c | 29 +++--
> 1 files changed, 11 insertions(+),
Ping?
-- PMM
On 31 August 2011 16:55, Peter Maydell wrote:
> This patchset converts the omap_intc device to MemoryRegion and qdev.
>
> The MemoryRegion conversion is fairly straightforward; the slight
> ugliness of using get_system_memory() is just so it can be pulled
> out as a separate patch f
On Fri, 2011-09-09 at 10:32 +0300, Michael S. Tsirkin wrote:
> On Fri, Sep 09, 2011 at 03:08:21AM -0400, Amos Kong wrote:
> > Hello all,
> >
> > I'm working on hotplug pci multifunction.
> >
> > 1. qemu cmdline:
> > ./x86_64-softmmu/qemu-system-x86_64 -snapshot -m 2000
> > /home/kvm_autotest_r
On 09/08/2011 12:33 AM, bharata@gmail.com wrote:
From: Bharata B Rao
apic id returned to guest kernel in ebx for cpuid(function=1) depends on
CPUX86State->cpuid_apic_id which gets populated after the cpuid information
is cached in the host kernel. This results in broken CPU topology in guest
pci/pcie hot plug needs clean up for multifunction hotplug in long term.
Only single function device case works. Multifunction case is broken somwehat.
Especially the current acpi based hotplug should be replaced by
the standardized hot plug controller in long term.
On Fri, Sep 09, 2011 at 03:08:2
On 09/03/2011 02:35 PM, Sasha Levin wrote:
When providing QEMU with a bad '-kernel' parameter, such as a file which
is not really a kernel, QEMU will attempt to allocate a huge amount of
memory and fail either with "Failed to allocate memory: Cannot allocate
memory" or a GLib error: "GLib-ERROR *
Marcelo Tosatti wrote:
> On Fri, Sep 09, 2011 at 01:12:51AM +0800, Liu, Jinsong wrote:
> --- a/arch/x86/include/asm/msr-index.h
> +++ b/arch/x86/include/asm/msr-index.h
> @@ -229,6 +229,8 @@
> #define MSR_IA32_APICBASE_ENABLE (1<<11)
> #define MSR_IA32_APICBASE_BASE
Marcelo Tosatti wrote:
> On Fri, Sep 09, 2011 at 01:12:51AM +0800, Liu, Jinsong wrote:
> --- a/arch/x86/include/asm/msr-index.h
> +++ b/arch/x86/include/asm/msr-index.h
> @@ -229,6 +229,8 @@
> #define MSR_IA32_APICBASE_ENABLE (1<<11)
> #define MSR_IA32_APICBASE_BASE
On 09/09/2011 08:39 AM, Stefano Stabellini wrote:
Hi Anthony,
I have few not very exiting xen bug fixes laying around that haven't
been applied to master yet. None of them are new, some of them are more
than an year old.
Please pull (git branch based on 07ff2c4475df77e38a31d50ee7f3932631806c15)
On 09/09/2011 04:24 AM, Stefan Hajnoczi wrote:
The following changes since commit 07ff2c4475df77e38a31d50ee7f3932631806c15:
Merge remote-tracking branch 'origin/master' into staging (2011-09-08
09:25:36 -0500)
are available in the git repository at:
ssh://repo.or.cz/srv/git/qemu/stefanh
On 09/05/2011 03:07 AM, Avi Kivity wrote:
To make good use of transparent hugepages, KVM requires that guest-physical
and host-virtual addresses share the low 21 bits (as opposed to just the low
12 bits normally required).
Adjust qemu_vmalloc() to honor that requirement. Ignore it for small reg
On 09/07/2011 08:02 AM, Gerd Hoffmann wrote:
Hi,
This patch series fixes a bunch of build failures.
please apply,
Gerd
Applied all. Thanks.
Regards,
Anthony Liguori
Gerd Hoffmann (3):
Don't use g_thread_get_initialized.
Use hex instead of binary.
vns/tls: don't use depric
On Fri, Sep 09, 2011 at 10:05:01AM -0700, Alex Williamson wrote:
> On Fri, 2011-09-09 at 10:32 +0300, Michael S. Tsirkin wrote:
> > On Fri, Sep 09, 2011 at 03:08:21AM -0400, Amos Kong wrote:
> > > Hello all,
> > >
> > > I'm working on hotplug pci multifunction.
> > >
> > > 1. qemu cmdline:
> >
On 09/07/2011 02:44 PM, Devin J. Pohly wrote:
From: "Devin J. Pohly"
Qemu currently assumes that chtype is typedef'd to unsigned long, but
this is not necessarily the case (ncurses, for instance, can configure
this at build-time). This patch uses the predefined chtype if qemu is
configured for
On 09/07/2011 06:40 PM, Michael Roth wrote:
Since qapi-generated/ is a global QEMU include path, we need to make
sure it is created before anything is compiled, so do this in the
configure phase rather than via the Makefile.
Signed-off-by: Michael Roth
Applied. Thanks.
Regards,
Anthony Ligu
On 09/09/2011 04:00 AM, Amit Shah wrote:
When a balloon device gets unplugged, allow the balloon handlers to be
freed.
Signed-off-by: Amit Shah
Applied all. Thanks.
Regards,
Anthony Liguori
---
balloon.c | 10 ++
balloon.h |1 +
2 files changed, 11 insertions(+), 0 delet
On Sat, Sep 10, 2011 at 02:11:36AM +0800, Liu, Jinsong wrote:
> Marcelo Tosatti wrote:
> > On Fri, Sep 09, 2011 at 01:12:51AM +0800, Liu, Jinsong wrote:
> > --- a/arch/x86/include/asm/msr-index.h
> > +++ b/arch/x86/include/asm/msr-index.h
> > @@ -229,6 +229,8 @@
> > #define MSR_IA3
>>
>> My question is, which kvm_get_msrs/kvm_put_msrs routine be used by
>> live migration, the routine in target-i386/kvm.c, or in
>> kvm/libkvm/libkvm-x86.c? They both have ioctl
>> KVM_GET_MSR_INDEX_LIST/ KVM_GET_MSRS/ KVM_SET_MSRS, but I'm not
>> clear their purpose/usage difference.
>
>
On Wednesday, August 31, 2011 10:35:53 AM Stefan Berger wrote:
> Index: qemu-git/hw/tpm_tis.c
> ===
> --- /dev/null
> +++ qemu-git/hw/tpm_tis.c
> @@ -0,0 +1,841 @@
> +/*
> + * tpm_tis.c - QEMU emulator for a 1.2 TPM with TIS interface
It replaces the VMSTOP macros and allows us to drop some global variables.
Additionally, the problem with issuing 'cont' when the VM is in bad state
is addressed and we make the current state available in QMP and HMP.
** IMPORTANT: patch 04/09 is a new addition, it needs careful review.
This is
We have two states where issuing cont before system_reset can
cause problems: RSTATE_SHUTDOWN (when -no-shutdown is used) and
RSTATE_PANICKED (which only happens with kvm).
This commit fixes that by doing the following when state is
RSTATE_SHUTDOWN or RSTATE_PANICKED:
1. returning an error to th
Today, when notifying a VM state change with vm_state_notify(),
we pass a VMSTOP macro as the 'reason' argument. This is not ideal
because the VMSTOP macros tell why qemu stopped and not exactly
what the current VM state is.
One example to demonstrate this problem is that vm_start() calls
vm_state
Currently, only vm_start() and vm_stop() change the VM state.
That's, the state is only changed when starting or stopping the VM.
This commit adds the runstate_set() function, which makes it possible
to also do state transitions when the VM is stopped or running.
Additional states are also added
Today our printf format for the "info status" command is:
VM status: %s
Where the string can be "running", "running (single step mode)" or
"paused".
This commit extends it to:
VM status: %s (%s)
The second string corresponds to the "status" field as returned
by the query-status QMP command
It's where all the state handling functions prototypes are located.
Signed-off-by: Luiz Capitulino
---
cpus.h |1 -
sysemu.h |1 +
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/cpus.h b/cpus.h
index f42b54e..5885885 100644
--- a/cpus.h
+++ b/cpus.h
@@ -15,7 +15,6 @@ vo
Test against RSTATE_IN_MIGRATE instead.
Please, note that the RSTATE_IN_MIGRATE state is only set when all the
initial VM setup is done, while 'incoming_expected' was set right in
the beginning when parsing command-line options. Shouldn't be a problem
as far as I could check.
Signed-off-by: Luiz
This commit could have been folded with the previous one, however
doing it separately will allow for easy bisect and revert if needed.
Checking and testing all valid transitions wasn't trivial, chances
are this will need broader testing to become more stable.
This is a transition table as suggest
Use runstate_is_running() instead, which is introduced by this commit.
Signed-off-by: Luiz Capitulino
---
cpus.c|9 -
gdbstub.c |4 ++--
hw/etraxfs_dma.c |2 +-
hw/kvmclock.c |2 +-
hw/virtio.c |2 +-
migration.c |2 +-
monitor
This new key reports the current VM status to clients. Please, check
the documentation being added in this commit for more details.
Signed-off-by: Luiz Capitulino
---
monitor.c |3 +--
qmp-commands.hx | 19 ++-
sysemu.h|1 +
vl.c| 23
On Wednesday, August 31, 2011 10:35:54 AM Stefan Berger wrote:
> Index: qemu-git/hw/tpm_tis.c
> ===
> --- qemu-git.orig/hw/tpm_tis.c
> +++ qemu-git/hw/tpm_tis.c
> @@ -6,6 +6,8 @@
> * Author: Stefan Berger
> * David Safford
Hey guys,
So I am writing a virtIO driver for a device that supports blocking calls like
poll() etc. Now the front end paravirtualized driver mirrors the request to the
backend "host" qemu process that then does the actual call on the host kernel
on behalf of the guest. Now my question is, when
于Fri 09 Sep 2011 10:27:26 PM CST,Kevin Wolf写到:
Am 09.09.2011 07:48, schrieb Dong Xu Wang:
As raw file format does not support backing_file and copy on write feature, so
I add COW to it to support backing_file option. I store dirty bitmap in an
add-cow file. When executed, it looks like this:
q
List,
Please find a patch that adds built-in iSCSI support to QEMU when built and
linked against the multiplatform iscsi initiator library at
git://github.com/sahlberg/libiscsi.git
All previous comments and suggestions have been addressed in this patch.
I and others have done extensive testi
This provides built-in support for iSCSI to QEMU.
This has the advantage that the iSCSI devices need not be made visible to the
host, which is useful if you have very many virtual machines and very many
iscsi devices.
It also has the benefit that non-root users of QEMU can access iSCSI devices
a
The Buildbot has detected a new failure on builder s390-next_i386_debian_6_0
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/s390-next_i386_debian_6_0/builds/26
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
B
101 - 144 of 144 matches
Mail list logo
