On 12/29/2011 01:04 PM, Peter Maydell wrote:
On 29 December 2011 18:35, Anthony Liguori wrote:
On 12/29/2011 11:49 AM, Peter Maydell wrote:
The next obvious question is: are we going to make a serious attempt?
(For instance, in a hypothetical tests-required world, would we
tell those nice folk
On 29 December 2011 21:46, Anthony Liguori wrote:
> But 0% test coverage is absolutely not enough. So the first step is to get
> an infrastructure together that we can all live with and start writing
> tests.
Agreed.
How does your framework deal with non-x86 targets? Finding and
installing a wo
On 12/29/2011 05:04 PM, Peter Maydell wrote:
On 29 December 2011 18:35, Anthony Liguori wrote:
On 12/29/2011 11:49 AM, Peter Maydell wrote:
The next obvious question is: are we going to make a serious attempt?
(For instance, in a hypothetical tests-required world, would we
tell those nice folk
On 30/12/11 05:21, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 09:20:00AM +, Alexey Korolev wrote:
Patches have been tested on several configurations which includes
linux 2.6.18 - 3.0&
windows 2008. Everything works quite well.
Which qemu version did you use?
I tried both 0.15 and 1
On 12/29/2011 04:10 PM, Peter Maydell wrote:
On 29 December 2011 21:46, Anthony Liguori wrote:
But 0% test coverage is absolutely not enough. So the first step is to get
an infrastructure together that we can all live with and start writing
tests.
Agreed.
How does your framework deal with n
On 12/28/2011 07:25 PM, Isaku Yamahata wrote:
Intro
=
This patch series implements postcopy live migration.[1]
As discussed at KVM forum 2011, dedicated character device is used for
distributed shared memory between migration source and destination.
Now we can discuss/benchmark/compare with p
On 12/29/2011 12:38 PM, Dor Laor wrote:
From the recent threads it looks to me that the 2 advantages of
qemu-test over kvm-autotest are:
1. python is not used within the guest
^ Just a (relatively small) subset of KVM autotest tests do require
python in the guest (the ones that execute the a
On 12/29/2011 03:02 PM, Anthony Liguori wrote:
On 12/29/2011 10:53 AM, Avi Kivity wrote:
On 12/29/2011 06:39 PM, Anthony Liguori wrote:
It might have made sense to split the kvm-testing functionality of
autotest, and have autotest drive that. We could even have called it
qemu-test.
I specific
On 12/29/2011 05:17 PM, Lucas Meneghel Rodrigues wrote:
On 12/29/2011 03:02 PM, Anthony Liguori wrote:
On 12/29/2011 10:53 AM, Avi Kivity wrote:
On 12/29/2011 06:39 PM, Anthony Liguori wrote:
It might have made sense to split the kvm-testing functionality of
autotest, and have autotest drive t
On 12/29/2011 10:33 PM, Anthony Liguori wrote:
So I decided to do some snooping. Here are some stats:
anthony@titi:~/git/autotest/client/tests/kvm/tests$ wc -l *.py
150 balloon_check.py
68 boot_savevm.py
190 cdrom.py
1875 cgroup.py
111 cpu_hotplug.py
170 enospc.py
71 floppy.py
72 getfd.py
89 hdp
On 12/29/2011 10:20 PM, Lucas Meneghel Rodrigues wrote:
On 12/29/2011 10:33 PM, Anthony Liguori wrote:
So I decided to do some snooping. Here are some stats:
anthony@titi:~/git/autotest/client/tests/kvm/tests$ wc -l *.py
150 balloon_check.py
68 boot_savevm.py
190 cdrom.py
1875 cgroup.py
111 cpu
DANIEL CATALIN COROZEL
C/ Arzobispo Carrillo,Nº3 ,4ºB
28803 Alcala de Henares (Madrid)
Telefonos: 697 524 592
Correo electronico:tucumineimpre...@yahoo.com
NIE: X-06862287-F
FORMACION ACADEMICA
1999-2002
Curso de CONSTRUCTION (Pintura ,alicatado, solado y albañile
Hi, kemari is a good job but I wonder why you chose "event-driven"? The
interval between synchronization maybe out of control, maybe very long if there
is a CPU-intensive task without any IO or maybe too frequent if there is a net
pressure test.
Why not synchronize periodically? Thanks!
On 30/12/11 05:18, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 06:40:26PM +1300, Alexey Korolev wrote:
On 29/12/11 00:43, Michael S. Tsirkin wrote:
On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote:
All devices behind a bridge need to have all their regions consecutive and
n
On Wed, Dec 28, 2011 at 01:43:02PM +0200, Michael S. Tsirkin wrote:
> On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote:
> > All devices behind a bridge need to have all their regions consecutive and
> > not overlapping with all the normal memory ranges.
> > Since prefetchable memory i
On 30/12/11 05:21, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
Can't figure this out. What does this do?
Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas.
That's not good, it's a legal configuration.
To be more complete : Bi
On 30/12/11 05:21, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
Can't figure this out. What does this do?
Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas.
That's not good, it's a legal configuration.
To be more complete : Bi
On Thu, Dec 29, 2011 at 06:00:04PM +1300, Alexey Korolev wrote:
> On 29/12/11 15:56, Kevin O'Connor wrote:
> >On Wed, Dec 28, 2011 at 06:26:05PM +1300, Alexey Korolev wrote:
> >>--- a/src/pciinit.c
> >>+++ b/src/pciinit.c
> >>@@ -22,6 +22,7 @@ enum pci_region_type {
> >> PCI_REGION_TYPE_IO,
>
On Fri, Dec 30, 2011 at 06:10:13PM +1300, Alexey Korolev wrote:
> On 30/12/11 05:21, Michael S. Tsirkin wrote:
> >On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
> >>>Can't figure this out. What does this do?
> >>Bios will panic if it founds prefmem BARs in both 32bit and 64bit area
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
> On 29/12/11 00:43, Michael S. Tsirkin wrote:
> >On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote:
> >>All devices behind a bridge need to have all their regions consecutive and
> >>not overlapping with all the normal me
>> >There are two main things we can do:
>> >1. Make the 64 bit device only use the low 32 bit
>> It was my first implementation. Unfortunately older versions of
>> Linux (Like 2.6.18) hang during startup with this.
>> As far as I remember it was qemu-0.15 so may be 1.0 have no such an
>> issue.
On Thu, Dec 29, 2011 at 4:17 PM, Andreas Färber wrote:
> Am 29.12.2011 08:55, schrieb Khansa Butt:
>> On Fri, Dec 9, 2011 at 5:04 AM, Andreas Färber
>> wrote:
+ /* if cpu has FPU, MIPS_HFLAG_F64 must be included in env->hflags
+ so that floating point operations can be emulate
101 - 123 of 123 matches
Mail list logo
