Detect presence of IASL compiler and use it
to process ASL source. If not there, use pre-compiled
files in-tree. Add script to update the in-tree files.
Note: distros are known to silently update iasl
so detect correct iasl flags for the installed version on each run as
opposed to at configure tim
Make it possible to test unmapped status through QMP.
Reviewed-by: Gerd Hoffmann
Tested-by: Gerd Hoffmann
Reviewed-by: Igor Mammedov
Tested-by: Igor Mammedov
Signed-off-by: Michael S. Tsirkin
---
include/hw/pci/pcie_host.h | 3 +++
hw/pci/pcie_host.c | 3 ---
2 files changed, 3 inser
There is only one failure point: bdrv_change_backing_file in this
function, so we can drop the qlist and try to change the backing file
before deleting anything.
This way bdrv_drop_intermediate is simplified while keeping the
operation transactional. A bonus is dropping an active BDS is supported
Add an option '-f' to migration cmdline.
Indicating whether to enable fault tolerant or not.
Signed-off-by: Jules Wang
---
hmp-commands.hx | 10 ++
hmp.c | 3 ++-
include/migration/migration.h | 1 +
migration.c | 3 ++-
qapi-sch
By leveraging live migration feature, the sender simply starts a
new migration when the previous migration is completed.
We need to handle the variables related to live migration very
carefully. So the new migration does not restart from the very
begin of the migration, instead, it continues the p
Curling provides fault tolerant mechanism for KVM.
For more info, see 'doc/curling.txt'.
Signed-off-by: Jules Wang
---
docs/curling.txt | 51 +++
1 file changed, 51 insertions(+)
create mode 100644 docs/curling.txt
diff --git a/docs/curling.txt b
Reviewed-by: Gerd Hoffmann
Tested-by: Gerd Hoffmann
Reviewed-by: Igor Mammedov
Tested-by: Igor Mammedov
Signed-off-by: Michael S. Tsirkin
---
include/hw/nvram/fw_cfg.h | 4
hw/nvram/fw_cfg.c | 33 -
2 files changed, 32 insertions(+), 5 deletions(-
The receiver does migration loop until the migration connection is
lost. Then, it is started as a backup.
The receiver does not load vm state once the migration begins.
Instead, it perfetches one whole migration data into a buffer,
then loads vm state from that buffer afterwards.
Signed-off-by: J
v2 -> v3:
* add documentation of new option in qapi-schema.
* long option name: ft -> fault-tolerant
v1 -> v2:
* cmdline: migrate curling:tcp::
-> migrate -f tcp::
* sender: use QEMU_VM_FILE_MAGIC_FT as the header of the migration
to indicate this is a ft migration.
* receive
Il 14/10/2013 22:10, Wolfgang Richter ha scritto:
> Okay, I think my impression might be wrong, but I thought
> 'drive-mirror' would become deprecated with the new 'drive-backup'
> command and code.
>
> If we look at what they do (current documentation and code),
> 'drive-backup' AFAIK behaves the
From: Zhouy
To: qemu-devel@nongnu.org
Date: Tue, 15 Oct 2013 15:20:47 -0400
Subject: Re: [PATCH 1/1] add output register property and update the
outputports level when necessary
I found some instruction of output port register in the datasheet:
" Reads from the output port register reflect the v
Hi,
> Yes but at the cost of overspecifying it.
> I think it's down to the name: it's called pcimem64-start
> but it can actually be less than 4G and we need to worry what to
> do then. Also, 64 doesn't really mean >4G.
>
> So how about "reserve-memory-over-4g"?
> bios then does 1ull << 32 + re
Eduardo Habkost writes:
> This makes the code more readable, making each condition that makes a
> field be skipped much more visible, and reduces one level of indentation
> in the code.
>
> Signed-off-by: Eduardo Habkost
> ---
> savevm.c | 156
>
Hi folks,
Settled another week, who can pick?
Thanks,
Wanlong Gao
> As you know, QEMU can't direct it's memory allocation now, this may cause
> guest cross node access performance regression.
> And, the worse thing is that if PCI-passthrough is used,
> direct-attached-device uses DMA transfer be
On 10/15/2013 02:05 PM, Stefan Weil wrote:
Am 15.10.2013 07:57, schrieb mike:
On 10/15/2013 01:07 PM, Stefan Weil wrote:
Am 15.10.2013 06:17, schrieb Mike Qiu:
Changelog to v1:
Find remainder of macaddr->a[5] by modulo 256,
otherwise it may be overflow by add index++.
The default ma
On Tue, Oct 15, 2013 at 12:26:10PM +0530, Anup Patel wrote:
> Hi Andrew,
>
> On Mon, Oct 14, 2013 at 9:29 PM, Andrew Jones wrote:
> > This is a virtio version of hw/misc/debugexit and should evolve into a
> > virtio version of pc-testdev. pc-testdev uses the PC's ISA bus, whereas
> > this testdev
Old kernels (< 3.1) handle hvcX devices different in different parts.
Sometime the kernel assumes that the hvc device numbers start from zero
and if there is just one hvc, then it is hvc0.
However kernel's add_preferred_console() uses the very last byte of
the VTY's "reg" property as an hvc number
Am 15.10.2013 um 05:38 hat mike geschrieben:
> On 10/14/2013 10:36 PM, Markus Armbruster wrote:
> >Mike Qiu writes:
> >
> >>Without this, output of 'info block'
> >>
> >>scsi0-hd0: /images/f18-ppc64.qcow2 (qcow2)
> >> [not inserted]
> >>scsi0-cd2: [not inserted]
> >> Removable device: not loc
From: "Aneesh Kumar K.V"
We will use this in later patches to make sure we use the right load
functions when copying hpte entries.
Signed-off-by: Aneesh Kumar K.V
---
hw/ppc/spapr.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
index 004184d..22f2a8
On Tue, Oct 15, 2013 at 10:01:01AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > Yes but at the cost of overspecifying it.
> > I think it's down to the name: it's called pcimem64-start
> > but it can actually be less than 4G and we need to worry what to
> > do then. Also, 64 doesn't really mean >4G.
>
On Tue, 15 Oct 2013 10:01:01 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > Yes but at the cost of overspecifying it.
> > I think it's down to the name: it's called pcimem64-start
> > but it can actually be less than 4G and we need to worry what to
> > do then. Also, 64 doesn't really mean >4G.
> >
>
From: "Aneesh Kumar K.V"
Correctly update the htab_mask using the return value of
KVM_PPC_ALLOCATE_HTAB ioctl. Also we don't update sdr1
on GET_SREGS for HV. So don't update htab_mask if sdr1
is found to be zero. Fix the pte index calculation to be
same as that found in the kernel
Signed-off-by:
From: "Aneesh Kumar K.V"
With kvm enabled, we store the hash page table information in the hypervisor.
Use ioctl to read the htab contents. Without this we get the below error when
trying to read the guest address
(gdb) x/10 do_fork
0xc0098660 : Cannot access memory at address
0xc00
Am 15.10.2013 um 03:27 hat Fam Zheng geschrieben:
> Since 0ebd24e0, cdrom doesn't have read-only on by default, which will
> error out when using an read only image. Fix it by setting the default
> value when parsing opts.
>
> Reported-by: Edivaldo de Araujo Pereira
> Signed-off-by: Fam Zheng
>
On Tue, Oct 15, 2013 at 11:05:48AM +0200, Igor Mammedov wrote:
> On Tue, 15 Oct 2013 10:01:01 +0200
> Gerd Hoffmann wrote:
>
> > Hi,
> >
> > > Yes but at the cost of overspecifying it.
> > > I think it's down to the name: it's called pcimem64-start
> > > but it can actually be less than 4G and
Hi,
> > What is the state of the qemu side patches btw?
> I've them ready but they conflict with you 1Tb in e820 RFC,
> I can post relevant patches as soon as we agree on this topic.
> May I pick up your patch and post it along with pcimem64-start patches?
Yes, makes sense it just pick it into
Hi,
> > > What is the state of the qemu side patches btw?
> > I've them ready but they conflict with you 1Tb in e820 RFC,
> > I can post relevant patches as soon as we agree on this topic.
> > May I pick up your patch and post it along with pcimem64-start patches?
>
> So for qemu we really need
On Tue, 10/15 11:13, Kevin Wolf wrote:
> Am 15.10.2013 um 03:27 hat Fam Zheng geschrieben:
> > Since 0ebd24e0, cdrom doesn't have read-only on by default, which will
> > error out when using an read only image. Fix it by setting the default
> > value when parsing opts.
> >
> > Reported-by: Edivald
Kevin Wolf writes:
> Am 15.10.2013 um 05:38 hat mike geschrieben:
>> On 10/14/2013 10:36 PM, Markus Armbruster wrote:
>> >Mike Qiu writes:
>> >
>> >>Without this, output of 'info block'
>> >>
>> >>scsi0-hd0: /images/f18-ppc64.qcow2 (qcow2)
>> >> [not inserted]
>> >>scsi0-cd2: [not inserted]
>>
Since 0ebd24e0, cdrom doesn't have read-only on by default, which will
error out when using an read only image. Fix it by setting the default
value when parsing opts.
Reported-by: Edivaldo de Araujo Pereira
Signed-off-by: Fam Zheng
---
v2: fix backward compatibility by force read-only with cdro
On Tue, 15 Oct 2013 12:16:43 +0300
"Michael S. Tsirkin" wrote:
> On Tue, Oct 15, 2013 at 11:05:48AM +0200, Igor Mammedov wrote:
> > On Tue, 15 Oct 2013 10:01:01 +0200
> > Gerd Hoffmann wrote:
> >
> > > Hi,
> > >
> > > > Yes but at the cost of overspecifying it.
> > > > I think it's down to t
On Tue, Oct 15, 2013 at 2:06 PM, Andrew Jones wrote:
> On Tue, Oct 15, 2013 at 12:26:10PM +0530, Anup Patel wrote:
>> Hi Andrew,
>>
>> On Mon, Oct 14, 2013 at 9:29 PM, Andrew Jones wrote:
>> > This is a virtio version of hw/misc/debugexit and should evolve into a
>> > virtio version of pc-testdev
On Tue, Oct 15, 2013 at 3:17 PM, Anup Patel wrote:
> On Tue, Oct 15, 2013 at 2:06 PM, Andrew Jones wrote:
>> On Tue, Oct 15, 2013 at 12:26:10PM +0530, Anup Patel wrote:
>>> Hi Andrew,
>>>
>>> On Mon, Oct 14, 2013 at 9:29 PM, Andrew Jones wrote:
>>> > This is a virtio version of hw/misc/debugexit
On Tue, 15 Oct 2013 11:24:19 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > > > What is the state of the qemu side patches btw?
> > > I've them ready but they conflict with you 1Tb in e820 RFC,
> > > I can post relevant patches as soon as we agree on this topic.
> > > May I pick up your patch and post
Hi,
It's probably going to be a bit tough this time. We are pretty late in
the qemu 1.7 devel cycle, soft freeze today, and a big chunk of code
(ahci-tables-from qemu) which needs seabios support[1] is just about to
be pulled.
That leaves only two weeks (with kvm forum in the middle!) until qe
On 10/15/2013 04:58 PM, Kevin Wolf wrote:
Am 15.10.2013 um 05:38 hat mike geschrieben:
On 10/14/2013 10:36 PM, Markus Armbruster wrote:
Mike Qiu writes:
Without this, output of 'info block'
scsi0-hd0: /images/f18-ppc64.qcow2 (qcow2)
[not inserted]
scsi0-cd2: [not inserted]
Removable
On 10/15/2013 05:31 PM, Markus Armbruster wrote:
Kevin Wolf writes:
Am 15.10.2013 um 05:38 hat mike geschrieben:
On 10/14/2013 10:36 PM, Markus Armbruster wrote:
Mike Qiu writes:
Without this, output of 'info block'
scsi0-hd0: /images/f18-ppc64.qcow2 (qcow2)
[not inserted]
scsi0-cd2: [
On 15 October 2013 10:47, Anup Patel wrote:
> On Tue, Oct 15, 2013 at 2:06 PM, Andrew Jones wrote:
>> I'm not opposed to it, but at the moment I'm not sure how we would
>> utilize it within kvm-unit-tests. Maybe it would be useful for another
>> application though? So maybe we can add it as an ad
On 3 October 2013 15:37, Peter Maydell wrote:
> Ah, that means the ARM ARM table is incorrect, because it implies
> that VSEL is conditional (which it definitely isn't). I need to look
> at where the new insns are in the T32/A32 encodings in more
> detail, then, which I don't have time for just at
On 27 September 2013 09:11, Alex Bennée wrote:
>
> christoffer.d...@linaro.org writes:
>
>> Save and restore the ARM KVM VGIC state from the kernel. We rely on
>
>>
>> static const VMStateDescription vmstate_gic = {
>> .name = "arm_gic",
>> -.version_id = 6,
>> -.minimum_version_id
On Tue, Oct 15, 2013 at 11:14:12AM +0100, Peter Maydell wrote:
> On 15 October 2013 10:47, Anup Patel wrote:
> > On Tue, Oct 15, 2013 at 2:06 PM, Andrew Jones wrote:
> >> I'm not opposed to it, but at the moment I'm not sure how we would
> >> utilize it within kvm-unit-tests. Maybe it would be us
Hi all:
Windows2008 Guest run without pressure for long time. Sometimes, it stop and
looks like hanging. But when I connect to it with VNC, It resume to run, but
VM's time is delayed .
When the vm is hanging, I check the main thread of QEMU. I find that the thread
is blocked in g_poll function
On Tue, Oct 15, 2013 at 4:08 PM, Gleb Natapov wrote:
> On Tue, Oct 15, 2013 at 11:14:12AM +0100, Peter Maydell wrote:
>> On 15 October 2013 10:47, Anup Patel wrote:
>> > On Tue, Oct 15, 2013 at 2:06 PM, Andrew Jones wrote:
>> >> I'm not opposed to it, but at the moment I'm not sure how we would
Am 15.10.2013 um 11:45 hat Fam Zheng geschrieben:
> Since 0ebd24e0, cdrom doesn't have read-only on by default, which will
> error out when using an read only image. Fix it by setting the default
> value when parsing opts.
>
> Reported-by: Edivaldo de Araujo Pereira
> Signed-off-by: Fam Zheng
>
From: Alex Bennée
This adds a build matrix definition for travis-ci.org continuous
integration service. It is usable on any public repository hosted on
GitHub. Once you have created an account signed into Travis you can
enable it on selected projects via travis-ci.org/profile. Alternatively
you c
Hi Anthony,
Here is my first pull request to add a simple .travis.yml profile to the
code base. I'm hoping to expand the range of testing once this is merged
(the tcg code gen tests are next on my list). However as it stands this
already catches build failures and regressions.
Since v4:
- dropp
Hello,
>Le Tuesday 15 Oct 2013 à 18:07:16 (+0800), mike a écrit :
> On 10/15/2013 04:58 PM, Kevin Wolf wrote:
> >Am 15.10.2013 um 05:38 hat mike geschrieben:
> >>On 10/14/2013 10:36 PM, Markus Armbruster wrote:
> >>>Mike Qiu writes:
> >>>
> Without this, output of 'info block'
>
> s
On 26 September 2013 22:03, Christoffer Dall
wrote:
> Save and restore the ARM KVM VGIC state from the kernel. We rely on
> QEMU to marshal the GICState data structure and therefore simply
> synchronize the kernel state with the QEMU emulated state in both
> directions.
>
> We take some care on t
mohamad.ge...@gmail.com writes:
> Signed-off-by: Mohamad Gebai
> ---
> docs/tracing.txt | 31 +++
> 1 file changed, 31 insertions(+)
>
> diff --git a/docs/tracing.txt b/docs/tracing.txt
> index bfc261b..64683db 100644
> --- a/docs/tracing.txt
> +++ b/docs/tracing.t
Il 14/10/2013 18:45, Eduardo Habkost ha scritto:
> +if (field->field_exists && !field->field_exists(opaque, version_id))
> {
> +continue;
> +}
> +if (field->version_id > version_id) {
> +continue;
> +}
What Markus observed...
I think the ch
On Mon, Oct 14, 2013 at 01:05:14PM -0400, Mohamad Gebai wrote:
> Sorry for the delay, just submitted the updated documentation.
Great, thanks. Things are busy here due to KVM Forum/LinuxCon Europe
next week. I'll try to take a look this week though so we can merge
this.
Stefan
Il 15/10/2013 12:21, Xiexiangyou ha scritto:
> Hi all:
>
> Windows2008 Guest run without pressure for long time. Sometimes, it
> stop and looks like hanging. But when I connect to it with VNC, It
> resume to run, but VM's time is delayed . When the vm is hanging, I
> check the main thread of QEMU.
On Mon, 14 Oct 2013 15:42:37 -0700
Anthony Liguori wrote:
> "Michael S. Tsirkin" writes:
>
> > Anthony, I know you wanted to review some of the patches,
> > since you didn't respond either all's well or you
> > could not find the time.
> > I think we are better off merging them for 1.7 and then
On Tue, Oct 15, 2013 at 10:01:12AM +0200, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > This makes the code more readable, making each condition that makes a
> > field be skipped much more visible, and reduces one level of indentation
> > in the code.
> >
> > Signed-off-by: Eduardo Hab
Hi Paolo,
This looks ok, but I don't find the branch where it applies?
Seems it's already fixed on master.
Thanks,
Fred
On 14/10/2013 18:23, Paolo Bonzini wrote:
We do not need to access vdev on the MSI-X fast path of virtio_pci_notify.
Signed-off-by: Paolo Bonzini
---
It is possibl
Il 15/10/2013 14:13, Frederic Konrad ha scritto:
> Hi Paolo,
>
> This looks ok, but I don't find the branch where it applies?
>
> Seems it's already fixed on master.
It's on top of the previous 11 patches.
Paolo
Thanks for your reply :-)
The QEMU version is 1.5.1,and the KVM version is 3.6
QEMU command:
/usr/bin/qemu-kvm -name win2008_dc_5 -S -machine
pc-i440fx-1.5,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp
4,maxcpus=64,sockets=16,cores=4,threads=1 -uuid
13e08e3e-cd23-4450-8bd3-60e7c220316d -no
Andreas,
To go beyond RFC with this series, I need to explain why TYPE_CPU
cannot_instantiate_with_device_add_yet. Would you be so kind and help
me out with a suitable comment?
You can find examples in PATCH 2-7/9.
- Original Message -
From: "Igor Mammedov"
To: "Igor Mammedov"
Cc: "Anthony Liguori" , "Eduardo Habkost"
, qemu-devel@nongnu.org, "Vadim Rozenfeld"
, "Paolo Bonzini" , "Andreas Färber"
Sent: Monday, October 14, 2013 3:09:11 PM
Subject: Re: [Qemu-devel] [PATCH qom-cpu 00/21 v9] targe
On Tue, Oct 08, 2013 at 07:02:44PM +0200, Paolo Bonzini wrote:
> Il 20/09/2013 16:57, Paolo Bonzini ha scritto:
> > This series fixes hot-unplug of virtio devices, which can crash due to
> > dangling pointer accesses.
> >
> > The current implementation supports guest-initiated hot-unplug via the
>
Il 15/10/2013 14:18, Xiexiangyou ha scritto:
> (gdb) bt
> #0 0x7f9ba661a423 in poll () from /lib64/libc.so.6
> #1 0x0059460f in os_host_main_loop_wait (timeout=4294967295) at
> main-loop.c:226
> #2 0x005946a4 in main_loop_wait (nonblocking=0) at main-loop.c:464
> #3 0x0
Currently 64-bit PCI BARs are unconditionally mapped by BIOS right
over 4G + RamSizeOver4G location, which doesn't allow to reserve
extra space before 64-bit PCI window. For memory hotplug an extra
RAM space might be reserved after present 64-bit RAM end and BIOS
should map 64-bit PCI BARs after it
On 10/14/2013 11:07 PM, Stefan Weil wrote:
>
> Is it reasonable to get a random mac address in your guest? I don't
> think so. It would no longer be possible to connect to a guest using
> ssh, restart that guest and connect again with ssh.
Agreed - libvirt ALWAYS passes a MAC to qemu, even if the
On Tue, 15 Oct 2013 11:14:36 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > > What is the state of the qemu side patches btw?
> > I've them ready but they conflict with you 1Tb in e820 RFC,
> > I can post relevant patches as soon as we agree on this topic.
> > May I pick up your patch and post it alon
On 15 October 2013 13:24, Markus Armbruster wrote:
> To go beyond RFC with this series, I need to explain why TYPE_CPU
> cannot_instantiate_with_device_add_yet.
...isn't this just because it's an abstract type?
-- PMM
On Tue, Oct 15, 2013 at 12:04:05PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> It's probably going to be a bit tough this time. We are pretty late in
> the qemu 1.7 devel cycle, soft freeze today, and a big chunk of code
> (ahci-tables-from qemu) which needs seabios support[1] is just about to
> be p
Paolo, or maybe Andreas,
To go beyond RFC with this series, I need to explain why isa-i8259 and
kvm-i8259 cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
Both are derived from TYPE_PIC_COMMON, which is derived from
TYPE_ISA_DEVICE.
I figure isa-i8259 cannot_insta
Ping
http://patchwork.ozlabs.org/patch/281527/
Regards,
Petar
From: Petar Jovanovic [petar.jovano...@rt-rk.com]
Sent: Tuesday, October 08, 2013 7:32 PM
To: qemu-devel@nongnu.org
Cc: Petar Jovanovic; aurel...@aurel32.net; riku.voi...@linaro.org;
peter.mayd.
On 10/14/13 10:18, Phi Debian wrote:
> Hi All,
>
> I tried to subscribe to this list, but never got teh confirm mail.
>
> So I write here non subscribed, so add my email addr in replies.
>
> I am trying to use guest-dump-memory on arm (arm32, armv7* name it)
> with qemu 1.6.1. The command is 'im
On 21 July 2013 13:52, Anthony Liguori wrote:
> Peter Maydell writes:
>> I've just noticed that this is still inconsistent. That
>> page says:
>>
>> "Soft feature freeze. Major features should have initial code
>> committed by this date."
>>
>> but it links to http://wiki.qemu.org/Planning/SoftFe
Il 15/10/2013 14:43, Markus Armbruster ha scritto:
> Paolo, or maybe Andreas,
>
> To go beyond RFC with this series, I need to explain why isa-i8259 and
> kvm-i8259 cannot_instantiate_with_device_add_yet, or drop that. I'd
> appreciate your help.
>
> Both are derived from TYPE_PIC_COMMON, which
Also sort the test-* entries in the latter.
Signed-off-by: Laszlo Ersek
---
.gitignore | 9 -
tests/.gitignore | 11 +--
2 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/.gitignore b/.gitignore
index 8e1b73f..7f4c106 100644
--- a/.gitignore
+++ b/.gitignore
Hi Markus,
Am 15.10.2013 14:24, schrieb Markus Armbruster:
> To go beyond RFC with this series, I need to explain why TYPE_CPU
> cannot_instantiate_with_device_add_yet. Would you be so kind and help
> me out with a suitable comment?
>From what I remember this was done when I started the whole pr
Andreas,
To go beyond RFC with this series, I need to explain why the IDE
controller functions of southbridges piix3-ide, piix3-ide-xen, piix4-ide
and via-ide cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
Our modelling of PCI devices is weird, to put it politely
On 16 September 2013 13:50, wrote:
> From: Alex Bennée
>
> Commit 9b8c69243 broke the ability to boot the kernel as the value
> returned by unassigned_mem_read returned non-zero and left the kernel
> looping forever waiting for it to change (see integrator_led_set in
> the kernel code).
This ge
On Tue, 15 Oct 2013 10:58:39 +0800
Fam Zheng wrote:
> This file is moved out from QMP/ to BUILD dir, change the ignore file
> too.
>
> Signed-off-by: Fam Zheng
Reviewed-by: Luiz Capitulino
PS: Assuming this will be taken by Michael.
> ---
> .gitignore | 2 +-
> 1 file changed, 1 insertion(
Am 15.10.2013 15:21, schrieb Markus Armbruster:
> Andreas,
>
> To go beyond RFC with this series, I need to explain why the IDE
> controller functions of southbridges piix3-ide, piix3-ide-xen, piix4-ide
> and via-ide cannot_instantiate_with_device_add_yet, or drop that. I'd
> appreciate your help
On 10/15/2013 08:36 PM, Eric Blake wrote:
On 10/14/2013 11:07 PM, Stefan Weil wrote:
Is it reasonable to get a random mac address in your guest? I don't
think so. It would no longer be possible to connect to a guest using
ssh, restart that guest and connect again with ssh.
Agreed - libvirt ALWA
Ping^2, seven weeks after initial post and code review.
Frankly, our mechanism for committing patches which aren't
obviously localised to a specific subsystem sucks :-(
It seems like pretty much every time it takes multiple
pings and a month or two before anything gets into the tree.
(at least thi
:59 -0700)
are available in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20131015-xtensa
for you to fetch changes up to ca529f8e13557cc2feb2eee3872d422712d9bcb0:
target-xtensa: add in_asm logging (2013-10-15
On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
> "Michael S. Tsirkin" writes:
>
> > Anthony, I know you wanted to review some of the patches,
> > since you didn't respond either all's well or you
> > could not find the time.
> > I think we are better off merging them for 1.7 and then -
On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin wrote:
> On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
>> "Michael S. Tsirkin" writes:
>>
>> > Anthony, I know you wanted to review some of the patches,
>> > since you didn't respond either all's well or you
>> > could not fi
Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
>
> Last week I forgot to send the call for topics. We still have a topic there.
There are no topics for Today agenda, so no call.
Later, Juan.
On Tue, Oct 15, 2013 at 6:43 AM, Gerd Hoffmann wrote:
> On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
>> "Michael S. Tsirkin" writes:
>>
>> > Anthony, I know you wanted to review some of the patches,
>> > since you didn't respond either all's well or you
>> > could not find the time.
>
Il 15/10/2013 15:51, Anthony Liguori ha scritto:
> From 41/43:
>
> "The interface is actually backwards-compatible with
> existing PIIX4 ACPI (though not migration compatible)."
>
> And does "AFAIK" translate to, "I have tested migration from new and
> old and old and new with this series"? I s
Peter Maydell writes:
> On 15 October 2013 13:24, Markus Armbruster wrote:
>> To go beyond RFC with this series, I need to explain why TYPE_CPU
>> cannot_instantiate_with_device_add_yet.
>
> ...isn't this just because it's an abstract type?
Abstract types have TypeInfo member abstract set. Not
On Tue, 15 Oct 2013 06:51:30 -0700
Anthony Liguori wrote:
> On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin wrote:
> > On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
> >> "Michael S. Tsirkin" writes:
> >>
> >> > Anthony, I know you wanted to review some of the patches,
>
On 10/15/2013 07:10 AM, Laszlo Ersek wrote:
> Also sort the test-* entries in the latter.
>
> Signed-off-by: Laszlo Ersek
> ---
> .gitignore | 9 -
> tests/.gitignore | 11 +--
> 2 files changed, 9 insertions(+), 11 deletions(-)
This feels backwards to me. I'd much rathe
On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
> "Michael S. Tsirkin" writes:
>
> > Anthony, I know you wanted to review some of the patches,
> > since you didn't respond either all's well or you
> > could not find the time.
> > I think we are better off merging them for 1.7 and then -
On Tue, Oct 15, 2013 at 06:51:30AM -0700, Anthony Liguori wrote:
> On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin wrote:
> > On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
> >> "Michael S. Tsirkin" writes:
> >>
> >> > Anthony, I know you wanted to review some of the patche
On Tue, Oct 15, 2013 at 7:01 AM, Paolo Bonzini wrote:
> Il 15/10/2013 15:51, Anthony Liguori ha scritto:
>> From 41/43:
>>
>> "The interface is actually backwards-compatible with
>> existing PIIX4 ACPI (though not migration compatible)."
>>
>> And does "AFAIK" translate to, "I have tested migrati
On Tue, Oct 15, 2013 at 06:53:54AM -0700, Anthony Liguori wrote:
> On Tue, Oct 15, 2013 at 6:43 AM, Gerd Hoffmann wrote:
> > On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
> >> "Michael S. Tsirkin" writes:
> >>
> >> > Anthony, I know you wanted to review some of the patches,
> >> > sinc
On Tue, Oct 15, 2013 at 7:20 AM, Michael S. Tsirkin wrote:
> On Tue, Oct 15, 2013 at 06:51:30AM -0700, Anthony Liguori wrote:
>> On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin wrote:
>> > On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
>> >> "Michael S. Tsirkin" writes:
>>
On 12 September 2013 11:17, Peter Maydell wrote:
> This patch series adds a 'virt' platform which uses the
> kernel's mach-virt (fully device-tree driven) support
> to create a simple minimalist platform intended for
> use for KVM VM guests.
>
> The major change here is that I've added a PL011 UAR
On Tue, Oct 15, 2013 at 07:17:59AM -0700, Anthony Liguori wrote:
> On Tue, Oct 15, 2013 at 7:01 AM, Paolo Bonzini wrote:
> > Il 15/10/2013 15:51, Anthony Liguori ha scritto:
> >> From 41/43:
> >>
> >> "The interface is actually backwards-compatible with
> >> existing PIIX4 ACPI (though not migrat
peter.mayd...@linaro.org writes:
> On 16 September 2013 13:50, wrote:
>> From: Alex Bennée
>>
>> Commit 9b8c69243 broke the ability to boot the kernel as the value
>> returned by unassigned_mem_read returned non-zero and left the kernel
>> looping forever waiting for it to change (see integrat
On Tue, Oct 15, 2013 at 07:21:34AM -0700, Anthony Liguori wrote:
> On Tue, Oct 15, 2013 at 7:20 AM, Michael S. Tsirkin wrote:
> > On Tue, Oct 15, 2013 at 06:51:30AM -0700, Anthony Liguori wrote:
> >> On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin
> >> wrote:
> >> > On Mon, Oct 14, 2013 at
On 15 October 2013 15:25, Alex Bennée wrote:
> peter.mayd...@linaro.org writes:
>> This sounds like the code was written based on the kernel, not
>> on the board docs, which is wrong, so I think it could use
>> rephrasing. There's no need to mention previous behaviour either
>> IMHO -- people who
Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
> -VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2, vmstate_pci_status,
> - struct pci_status),
> +VMSTATE_STRUCT_TEST(pci0_status, PIIX4PMState,
> +vmstate_test_no_use_acpi_pci_hotplug
On Tue, Oct 15, 2013 at 04:31:31PM +0200, Paolo Bonzini wrote:
> Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
> > -VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2, vmstate_pci_status,
> > - struct pci_status),
> > +VMSTATE_STRUCT_TEST(pci0_status, PIIX4PMSta
1 - 100 of 196 matches
Mail list logo
