year to 2080. This causes a year-2038 overflow
in mktimegm. Fix this by doing the days-to-seconds computation in
64-bit math.
Reported-by: Lucas Meneghel Rodrigues
Signed-off-by: Paolo Bonzini
Signed-off-by: Anthony Liguori
Confirmed that problem is solved. Closing bug
On 12/12/2012 01:29 PM, Paolo Bonzini wrote:
Il 12/12/2012 16:23, Gerd Hoffmann ha scritto:
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Wasn't
sts, 1 failures
$ echo $?
3
Gerd Hoffmann (1):
add isa-debug-exit device
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v5
hw/debugexit.c| 73 +++
hw/i386/Makefile.objs |3 +-
hw/pc-testdev
From: Gerd Hoffmann
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Changes from v1: Add access_size property to the
device, needed for kvm-unit-test
From: Gerd Hoffmann
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Changes from v1: Add access_size property to the
device, needed for kvm-unit-test
sts, 1 failures
$ echo $?
3
Gerd Hoffmann (1):
add isa-debug-exit device
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v5
hw/debugexit.c| 73 +++
hw/i386/Makefile.objs |3 +-
hw/pc-testdev
PI to
retrieve that value.
CC: Paolo Bonzini
Signed-off-by: Alexander Graf
Signed-off-by: Gerd Hoffmann
Signed-off-by: Marcelo Tosatti
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/i386/Makefile.objs |1 +
hw/pc-testdev.c | 55 -
2 files ch
sts, 1 failures
$ echo $?
3
Gerd Hoffmann (1):
hw: add isa-debug-exit device v3
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v6
hw/debugexit.c| 73 +++
hw/i386/Makefile.objs |3 +-
hw/pc-testdev
From: Gerd Hoffmann
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Changes from v2: Fixed rebase mistake
Changes from v1: Add access_size property
From: Gerd Hoffmann
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Changes from v1: Add access_size property to the
device, needed for kvm-unit-test
r kvm-unit-tests including an API to
retrieve that value.
CC: Paolo Bonzini
Signed-off-by: Alexander Graf
Signed-off-by: Gerd Hoffmann
Signed-off-by: Marcelo Tosatti
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/i386/Makefile.objs |1 +
hw/pc-testdev.c |
From: Gerd Hoffmann
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Changes from v1: Add access_size property to the
device, needed for kvm-unit-test
From: Gerd Hoffmann
When present it makes qemu exit on any write.
Mapped to port 0x501 by default.
Without this patch Anthony doesn't allow me to
remove the bochs bios debug ports because his
test suite uses this.
Changes from v2: Fixed rebase mistake
Changes from v1: Add access_size property
sts, 1 failures
$ echo $?
3
Gerd Hoffmann (1):
hw: add isa-debug-exit device v3
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v6
hw/debugexit.c| 73 +++
hw/i386/Makefile.objs |3 +-
hw/pc-testdev
sts, 1 failures
$ echo $?
3
Gerd Hoffmann (1):
hw: add isa-debug-exit device v4
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v7
hw/debugexit.c| 87 ++
hw/i386/Makefile.objs |3 +-
hw/pc-testdev
from v1:
* Add access_size property to the device,
needed for kvm-unit-tests.
Signed-off-by: Gerd Hoffmann
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/debugexit.c| 87 +++
hw/i386/Makefile.objs |2 +-
hw/pc-testdev
, since guest memory
size can be retrieved from firmware, there's a
patch for kvm-unit-tests including an API to
retrieve that value.
CC: Paolo Bonzini
Signed-off-by: Alexander Graf
Signed-off-by: Gerd Hoffmann
Signed-off-by: Marcelo Tosatti
Signed-off-by: Lucas Meneghel Rodrigues
--
satti
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/i386/Makefile.objs |1 +
hw/pc-testdev.c | 161 +
2 files changed, 162 insertions(+)
create mode 100644 hw/pc-testdev.c
diff --git a/hw/i386/Makefile.objs b/hw/i386/Makefile.objs
Changes from v2:
* Fixed rebase mistake
Changes from v1:
* Add access_size property to the device,
needed for kvm-unit-tests.
Signed-off-by: Gerd Hoffmann
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/debugexit.c| 87 +
hw/i386/Makefile.ob
Test on INVPCID when disabled: PASS
3 tests, 1 failures
$ echo $?
3
Gerd Hoffmann (1):
hw: add isa-debug-exit device v5
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v8
hw/i386/Makefile.objs |3 +-
hw/pc-testdev.c | 161 +
Ok, this looks good, applied, thanks!
On Sat, Dec 29, 2012 at 11:02 PM, Amos Kong wrote:
> type 'kvm' already been changed to 'qemu'
>
> Signed-off-by: Amos Kong
> ---
> run |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/run b/run
> index 97dcdad..aac332a 10075
Hmmm, about this one, I'm worried about making things more complex...
The way I see the problem at hand, I'd say if people want to customize
things, they'd be better of creating their own, specialized config
files rather than adding command line flags to manipulate the test
sets.
So my initial st
On 02/05/2013 11:49 PM, Lucas Meneghel Rodrigues wrote:
On 02/05/2013 09:58 AM, Michael S. Tsirkin wrote:
Vadim, can you please describe in a bit more details what the actual
issue
here is, from the windows or windows driver point of view? Is it really
that bad that the config space size
Hey Gleb, Marcelo:
I was looking at the sanity jobs for qemu.git and found this error that
happened during RHEL 6.3 guest reboot test:
02/09 05:16:45 INFO | aexpect:0797| [qemu output] KVM internal
error. Suberror: 1
02/09 05:16:45 INFO | aexpect:0797| [qemu output] emulation failure
On 02/14/2013 11:41 AM, Eduardo Habkost wrote:
I'd glad to amend patch, if there are suggestions how to generalize it and
improve "create boot image" process for distros that doesn't have
grub2-mkrescue.
A reusable tool/script would be useful even outside virt-test. Anybody
who uses -kernel/-in
On 02/14/2013 05:57 PM, Eduardo Habkost wrote:
On Thu, Feb 14, 2013 at 08:28:03PM +0100, Igor Mammedov wrote:
On Thu, 14 Feb 2013 13:13:18 +0100
Paolo Bonzini wrote:
Il 14/02/2013 12:18, Eduardo Habkost ha scritto:
qemu boots from disk image 3 times faster than direct kernel load.
That's su
Hi guys,
We're seeing the following problem during upstream testing:
qemu: VQ 0 size 0x80 Guest index 0x2d6
inconsistent with Host index 0x18: delta 0x2be
qemu: warning: error while loading state for
instance 0x0 of device ':00:04.0/virtio-blk'
load of migration failed
This
On 09/25/2012 09:59 AM, Anthony Liguori wrote:
Lucas Meneghel Rodrigues writes:
Hi guys,
We're seeing the following problem during upstream testing:
qemu: VQ 0 size 0x80 Guest index 0x2d6
inconsistent with Host index 0x18: delta 0x2be
qemu: warning: error while loading
Very easy to reproduce:
1) Build the latest qemu.git (we've captured this on internal automated
testing, verified manually), the commit for reference is:
14:07:02 INFO | git commit ID is
6f8fd2530e9a530f237240daf1c981fa5df7f978 (tag v1.2.0-461-g6f8fd25)
2) Install a linux guest in it (caugh
Public bug reported:
Very easy to reproduce:
1) Build the latest qemu.git (we've captured this on internal automated
testing, verified manually), the commit for reference is:
14:07:02 INFO | git commit ID is
6f8fd2530e9a530f237240daf1c981fa5df7f978 (tag v1.2.0-461-g6f8fd25)
2) Install a linux g
On 10/03/2012 06:55 AM, Gleb Natapov wrote:
On Mon, Oct 01, 2012 at 03:26:05PM +0200, Jan Kiszka wrote:
On 2012-10-01 15:19, Anthony Liguori wrote:
Jan Kiszka writes:
On 2012-10-01 11:31, Marcelo Tosatti wrote:
It's not just about default configs. We need to validate if the
migration format
f the thread, and had guidance from
Paolo about which ports to remove from the test
device.
CC: Paolo Bonzini
Signed-off-by: Gerd Hoffmann
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/i386/Makefile.objs | 1 +
hw/testdev.c
On 10/04/2012 12:49 AM, Lucas Meneghel Rodrigues wrote:
Add a test device which supports the kvmctl ioports,
so one can run the KVM unittest suite [1].
Usage:
qemu -device testdev
1) Removed port 0xf1, since now kvm-unit-tests use
serial
2) Removed exit code port 0xf4, since that can be
On 10/04/2012 07:48 AM, Jan Kiszka wrote:
On 2012-10-03 15:19, Paolo Bonzini wrote:
Il 03/10/2012 12:57, Lucas Meneghel Rodrigues ha scritto:
Yep, I did send patches with the testdev device present on qemu-kvm.git
to qemu.git a while ago, but there were many comments on the review, I
ended up
On 10/04/2012 09:27 AM, Jan Kiszka wrote:
On 2012-10-04 14:10, Lucas Meneghel Rodrigues wrote:
On 10/04/2012 07:48 AM, Jan Kiszka wrote:
On 2012-10-03 15:19, Paolo Bonzini wrote:
Il 03/10/2012 12:57, Lucas Meneghel Rodrigues ha scritto:
Yep, I did send patches with the testdev device present
s, 1 failures
$ echo $?
3
Hervé Poussineau (1):
debugexit: support for custom exit port (LGPL VGA BIOS port 0x501)
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v2
hw/debugexit.c| 68 +
hw/i386/Makefile.objs | 3 +-
hw
ieved from firmware, there's a
patch for kvm-unit-tests including an API to
retrieve that value.
CC: Paolo Bonzini
Signed-off-by: Gerd Hoffmann
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/i386/Makefile.objs | 1 +
From: Hervé Poussineau
Add generic support for simple I/O port which, when written to, cause
QEMU to exit with the given written value.
There is no vmstate associated with the debugging port, simply because
the entire interface is a single, stateless, write-only port.
Signed-off-by: Hervé Pouss
Public bug reported:
This issue is reproducing consistently on automated testing, verified on
manual testing (although it may require many tries).
Steps to reproduce:
1) Start a linux guest. The command line used by automated testing was:
10/05 06:48:27 INFO |kvm_vm:1605| MALLOC_PERTURB_=1
No, I haven't. I'll do my best to reserve time this week to do so.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1062411
Title:
QEMU fails during migration and reports "qemu: VQ 0 size 0x80 Guest
From: Hervé Poussineau
Add generic support for simple I/O port which, when written to, cause
QEMU to exit with the given written value.
There is no vmstate associated with the debugging port, simply because
the entire interface is a single, stateless, write-only port.
Changes from v1:
* Chang
rcelo Tosatti
Signed-off-by: Lucas Meneghel Rodrigues
---
hw/i386/Makefile.objs | 1 +
hw/pc-testdev.c | 167 ++
2 files changed, 168 insertions(+)
create mode 100644 hw/pc-testdev.c
diff --git a/hw/i386/Makefile.objs b/hw/i386/Makefile.objs
port 0x501) v2
Lucas Meneghel Rodrigues (1):
hw: Add test device for unittests execution v4
hw/debugexit.c| 75 +++
hw/i386/Makefile.objs | 3 +-
hw/pc-testdev.c | 167 ++
3 files changed, 244 insertions
** Attachment added: "results.tar.bz2"
https://bugs.launchpad.net/bugs/1047576/+attachment/3299328/+files/results.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1047576
Title:
qemu unitt
Adding relevant qemu and unittest versions
software_version_qemu_kvm=git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git:master:4c3e02beed9878a5f760eeceb6cd42c475cf0127
software_version_kvm_unit_tests=git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git:master:09b657b6d3a80d0424b8b370462a77d284
Public bug reported:
Running the emulator unittest, using the cmdline:
16:01:30 INFO | Running emulator
16:01:30 INFO | Running qemu command (reformatted):
16:01:30 INFO | /home/lmr/Code/autotest.git/autotest/client/tests/virt/kvm/qemu
16:01:30 INFO | -S
16:01:30 INFO | -name 'unittest_
On 03/05/2013 07:11 AM, Amit Shah wrote:
On (Mon) 04 Mar 2013 [16:53:55], Stefan Hajnoczi wrote:
People are working on testing for various parts of QEMU. I started
this thread to gather an update on the state of testing and see where
we still need help.
I'm not sure yet if we should propose Go
On 03/05/2013 08:17 AM, Gerd Hoffmann wrote:
On 03/05/13 11:46, Stefan Hajnoczi wrote:
On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
Hi,
How are things looking with device emulation, migration, monitor, char, etc?
At the moment autotest/virt-test is pretty much the only
On 03/04/2013 01:22 PM, Gerd Hoffmann wrote:
Hi,
How are things looking with device emulation, migration, monitor, char, etc?
At the moment autotest/virt-test is pretty much the only workable thing
for non-trivial devices because libqtest lacks infrastructure for pci
and anything building
On 03/05/2013 01:14 PM, Gerd Hoffmann wrote:
Hi,
I don't think we have *any* regular autotest coverage for master, have
we?
^ Yes, there is coverage. There's a daily job called sanity that takes
about 2.5 hours, that builds the latest kvm.git and installs it in the
host, then reboots the b
On 03/05/2013 01:23 PM, Gerd Hoffmann wrote:
Hi,
On virt-tests there are at least 48 tests that are easy to run and
involve migration. A subset of them is executed regularly in the daily
jobs:
Sure, there are a bunch of tests already, which is good.
But there are also important areas which
Latest qemu.git master is failing big time to pass sanity checks:
https://bugs.launchpad.net/qemu/+bug/1169254
We've had some issues with the test jobs, and finally managed to
stabilize the grid, so we don't have results for the last couple of
weeks to bisect the problem.
Public bug reported:
Found the problem during sanity test of the 'next' branch
git commit ID is e2ec3f976803b360c70d9ae2ba13852fa5d11665 (tag
v1.4.0-1202-ge2ec3f9)
For reference, kernel is upstream kvm.git
git commit ID is 31880c37c11e28cb81c70757e38392b42e695dc6 (tag
v3.8-12524-g31880c3)
Step
1 thing I don't see in your command line: MALLOC_PERTURB=1. I did build
it on my Fedora 19 work laptop and it is easily reproducible. I just
didn't use the echo -e:
[lmr@thinkpad-t420s qemu]$ MALLOC_PERTURB_=1 x86_64-softmmu/qemu-system-x86_64
-monitor stdio -vga std -S -vnc :0 -enable-kvm -nodef
I've hacked up a (admittedly not very pretty) reproducer script
PATH_DEVEL=x86_64-softmmu/qemu-system-x86_64
MALLOC_PERTURB_=1 $PATH_DEVEL -chardev
socket,id=hmp1,path=/tmp/hmp1-lmr,server,nowait -mon chardev=hmp1,mode=readline
-vga std -S -vnc :0 -enable-kvm -nodefaults&
QEMU_PID=$(pidof qemu-s
First bad commit is
commit c78f71378a345ea240c288993ca1378ded5504b9
Author: Gerd Hoffmann
Date: Tue Mar 5 15:24:14 2013 +0100
console: stop using DisplayState in gfx hardware emulation
Use QemuConsole instead. Updates interfaces in console.[ch] and adapts
gfx hardware emulati
Public bug reported:
Relevant qemu.git master commit:
24a6e7f4d91e9ed5f8117ecb083431a23f8609a0
When trying to migrate a VM using the TCP protocol, a segfault happened:
21:45:07 INFO | Running qemu command (reformatted):
/home/lmr/Code/qemu/x86_64-softmmu/qemu-system-x86_64 \
-S \
-name
On Tue, 2013-04-16 at 09:39 +0200, Gerd Hoffmann wrote:
> On 04/15/13 18:49, Lucas Meneghel Rodrigues wrote:
> > Latest qemu.git master is failing big time to pass sanity checks:
> >
> > https://bugs.launchpad.net/qemu/+bug/1169254
> >
> > We've had some
Problem fixed with this commit, recently pushed to master:
commit 7dda5dc82a776a39a7996020c188eb2a29187117
Author: Paolo Bonzini
Date: Tue Apr 9 17:43:43 2013 +0200
migration: initialize RAM to zero
Using qemu_memalign only leaves the RAM zero by chance, because libc
will usua
.com/11429.html
Signed-off-by: Lucas Meneghel Rodrigues
---
run | 11 +++
1 file changed, 11 insertions(+)
diff --git a/run b/run
index 170f00a..dd203aa 100755
--- a/run
+++ b/run
@@ -238,6 +238,11 @@ class VirtTestRunParser(optparse.OptionParser):
"
On Thu, 2013-04-18 at 08:53 +0200, Gerd Hoffmann wrote:
> >> Can you try this?
> >> git://git.kraxel.org/qemu rebase/pixman
> >>
>
> > With current master, qemu crashes.
>
> FYI: pull req sent, anthony merged, so it is fixed in master now.
>
> autotest might need adaptions nevertheless, on hea
Gerd sent a pull request that was merged, fixing the problem
top commit: 09dada400328d75daf79e3eca1e48e024fec148d
Problem is now fixed on latest qemu.git master.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
deve
On 12/19/2011 03:55 PM, Anthony Liguori wrote:
On 12/19/2011 11:39 AM, Avi Kivity wrote:
On 12/19/2011 07:13 PM, Anthony Liguori wrote:
Hi,
I've published a set of tests I wrote over the weekend on qemu.org.
My motivations were 1) to prevent regressions like the libguestfs one
and 2) to have a
On 12/27/2011 02:40 PM, Anthony Liguori wrote:
On 12/27/2011 09:58 AM, Avi Kivity wrote:
On 12/27/2011 05:22 PM, Anthony Liguori wrote:
The infrastructure assumes that you have a full OS available in the
guest. The tests are written in Python and make a variety of
assumptions. To my knowledge,
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 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
ified.
anthony@titi:~/git/autotest/client/tests$ git log --format="%an <%ae>"
kvm | sort -u
Amos Kong
Chris Evich
Cleber Rosa
Jerry Tang
lmr
Lucas Meneghel Rodrigues
Lucas Meneghel Rodrigues
Lukas Doktor
mbligh
Onkar N Mahajan
pradeep
Qingtang Zhou
Thomas Jarosch
Yiqiao P
On 01/13/2012 02:49 PM, Stefan Hajnoczi wrote:
Hi Lucas,
The Python script below verifies the image streaming feature. It's
built on the standard library "unittest" module, as well as QEMU's
qmp.py module. It spawns a qemu process and creates necessary disk
image files. The tests themselves is
On 08/04/2011 12:17 PM, Stefan Hajnoczi wrote:
On Sat, Jul 30, 2011 at 1:39 AM, Anthony Liguori wrote:
On behalf of the entire QEMU team, I'm please to announce the release of
QEMU 0.15.0-rc1. This is the second release candidate for the 0.15.0
release.
There are numerous ways you can help pa
Hi,
We've noticed the following error during Windows install when using the
latest qemu from HEAD:
04/03 01:45:42 INFO | aexpect:0786| [qemu output] /bin/sh: line 1: 21674 Bus
error (core dumped) MALLOC_PERTURB_=1
/usr/local/autotest/tests/kvm/qemu -name 'vm1' -nodefaults -vga s
Hi guys. For a while we have been discussing ways to make the
virtualization tests written on top of autotest useful for development
level testing.
One of our main goals is to provide useful tools for the qemu community,
since we have a good number of tests and libraries written to perform
in
On 03/08/2012 10:36 AM, Anthony Liguori wrote:
Virt/qemu tests: Minimal guest images
-
In order to make development level test possible, we need the tests to
run fast.
In order to do that, a set of minimal guest images is being developed
and we
have a version
Before I forget, I'd like to ask you about this:
On 03/08/2012 10:36 AM, Anthony Liguori wrote:
I'm really not a fan of buildroot. Note that in order to ship binaries,
full source needs to be provided in order to comply with the GPL. The
FSF at least states that referring to another website for
On 03/08/2012 02:59 PM, Ademar Reis wrote:
Agree. For QEMU developers, libvirt should not be on the way, the
interaction should be minimal or non-existent.
That's an area which will require some work in libautotest,
because due to previous QE requirements, it now invokes libvirt
methods instead
On 03/08/2012 02:59 PM, Ademar Reis wrote:
Agree. For QEMU developers, libvirt should not be on the way, the
interaction should be minimal or non-existent.
That's an area which will require some work in libautotest,
because due to previous QE requirements, it now invokes libvirt
methods instead
On 03/08/2012 03:57 PM, Anthony Liguori wrote:
On 03/08/2012 09:19 AM, Lucas Meneghel Rodrigues wrote:
Before I forget, I'd like to ask you about this:
On 03/08/2012 10:36 AM, Anthony Liguori wrote:
I'm really not a fan of buildroot. Note that in order to ship binaries,
full sourc
On 03/08/2012 04:43 PM, Anthony Liguori wrote:
On 03/08/2012 01:34 PM, Lucas Meneghel Rodrigues wrote:
On 03/08/2012 03:57 PM, Anthony Liguori wrote:
On 03/08/2012 09:19 AM, Lucas Meneghel Rodrigues wrote:
Before I forget, I'd like to ask you about this:
On 03/08/2012 10:36 AM, An
On 03/08/2012 06:24 PM, Anthony Liguori wrote:
Cons:
- Lot of code will be duplicated to cover the main code paths:
writting tests will require writting/supporting considerable
ammount of code (that already exists in autotest).
Again, existence proof that this isn't true.
Case in point, the
On 03/09/2012 09:13 AM, Anthony Liguori wrote:
On 03/08/2012 05:07 PM, Lucas Meneghel Rodrigues wrote:
Here is the qemu-test version
http://git.qemu.org/?p=qemu-test.git;a=blob;f=tests/virtio-serial.sh;h=e95ae6e0b63758262919702d51a9c83bebe2fb08;hb=master
So virtio-serial is an exception in
On 03/09/2012 11:13 AM, Anthony Liguori wrote:
It is indeed a bit nerve wrecking to hear that all you can do with the
stuff you
have been working on the last 3 years can be done better with a dozen
of shell
script functions. It's similar to say that we just like to throw lines
at a text
editor ju
On Tue, 2011-06-21 at 16:56 +0300, Avi Kivity wrote:
> On 06/21/2011 04:50 PM, Anthony Liguori wrote:
> > On 06/21/2011 06:28 AM, Avi Kivity wrote:
> >> On 06/20/2011 10:42 AM, Juan Quintela wrote:
> >>> Please send in any agenda items you are interested in covering.
> >>>
> >>
> >>
> >> https://bu
On 10/25/2011 01:03 PM, Eduardo Habkost wrote:
On Tue, Oct 25, 2011 at 03:27:35PM +0200, Gerd Hoffmann wrote:
[...]
A while ago I played with some simple IDE tests. It basically was a
small x86 kernel with an empty image that sends IDE commands and prints
some results, and a script that invokes
Hi folks:
We've captured a regression with floppy disk on recent qemu (and
qemu-kvm, after a code merge). We bisected it to be caused by:
commit 212ec7baa28cc9d819234fed1541fc1423cfe3d8
Author: Richard Henderson
Date: Mon Aug 15 15:08:45 2011 -0700
fdc: Convert to isa_register_portio_l
On 10/26/2011 01:47 PM, Kevin Wolf wrote:
Am 26.10.2011 16:41, schrieb Lucas Meneghel Rodrigues:
Hi folks:
We've captured a regression with floppy disk on recent qemu (and
qemu-kvm, after a code merge). We bisected it to be caused by:
commit 212ec7baa28cc9d819234fed1541fc1423cfe3d8
A
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/318824
Title:
DHCP/NAT: Vista fails to get IP from DHCP engine
Status in QEMU:
Invalid
Bug
This bug was opened a long time ago, and probably is no longer valid,
hence, closing it as invalid.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/588
On 10/27/2011 05:17 AM, Stefan Hajnoczi wrote:
On Wed, Oct 26, 2011 at 03:19:17PM -0200, Lucas Meneghel Rodrigues wrote:
On 10/26/2011 01:47 PM, Kevin Wolf wrote:
Am 26.10.2011 16:41, schrieb Lucas Meneghel Rodrigues:
Hi folks:
We've captured a regression with floppy disk on recent qemu
On Thu 27 Oct 2011 11:17:48 PM BRST, Zhi Yong Wu wrote:
On Fri, Oct 28, 2011 at 2:57 AM, Lucas Meneghel Rodrigues
wrote:
On 10/27/2011 05:17 AM, Stefan Hajnoczi wrote:
On Wed, Oct 26, 2011 at 03:19:17PM -0200, Lucas Meneghel Rodrigues wrote:
On 10/26/2011 01:47 PM, Kevin Wolf wrote:
Am
On 10/27/2011 11:17 PM, Zhi Yong Wu wrote:
On Fri, Oct 28, 2011 at 2:57 AM, Lucas Meneghel Rodrigues
wrote:
On 10/27/2011 05:17 AM, Stefan Hajnoczi wrote:
On Wed, Oct 26, 2011 at 03:19:17PM -0200, Lucas Meneghel Rodrigues wrote:
On 10/26/2011 01:47 PM, Kevin Wolf wrote:
Am 26.10.2011 16
Hi folks, sending this to QEMU devel to inform the current problems we
are able to reproduce on the current master branch.
So, qemu.git is presenting problems as of latest master. None of the
problems mentioned is happening on qemu-kvm.git.
Original Message
Subject: Autotest
On 11/01/2011 12:17 PM, kvm-autotest wrote:
Job ID: 2011
Job name: Upstream qemu-kvm.git sanity 11-01-2011 00:04:02
Summary: Host: Status: Completed
Status: 1 Completed
Execution time (HH:MM:SS): 01:17:02
User tests executed: 19
User tests passed: 18
User tests failed: 1
User tests success rate:
On 11/02/2011 05:48 AM, Zhi Yong Wu wrote:
On Wed, Oct 26, 2011 at 10:41 PM, Lucas Meneghel Rodrigues
wrote:
Hi folks:
We've captured a regression with floppy disk on recent qemu (and qemu-kvm,
after a code merge). We bisected it to be caused by:
c
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good idea
to share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some condition is consistently making a RHEL 6.1 linux guest not able
to bring up the network interface, causing login failures for all
On Fri 04 Nov 2011 02:50:53 PM BRST, Kevin Wolf wrote:
Am 04.11.2011 17:40, schrieb Lucas Meneghel Rodrigues:
2) The floppy regression problem which was reported some days ago on
this mailing list still happens, Kevin did post a patch that resolves it
[...]
But still wasn't integ
On Fri 04 Nov 2011 02:56:30 PM BRST, Anthony Liguori wrote:
On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good
idea to
share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some conditi
On 11/04/2011 02:56 PM, Anthony Liguori wrote:
On 11/04/2011 11:40 AM, Lucas Meneghel Rodrigues wrote:
Hi guys,
As we understand that qemu is approaching 1.0, we think it's a good
idea to
share the issues we have been seeing on recent qemu.git sanity jobs:
1) Some condition is consist
** Attachment added: "screenshot showing nw initialization failure"
https://bugs.launchpad.net/bugs/886255/+attachment/2585413/+files/vm1_2011-11-04_00-45-19.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchp
Public bug reported:
Guest: RHEL 6.1 64 bit DVD
Kernel: Latest Fedora, also reproduces with Avi's kvm.git kernel based
on 3.1: 2.6.40.6-0.fc15.x86_64
qemu version:
11/04 00:25:30 DEBUG|virt_utils:2587| Git repo qemu uri:
git://git.qemu.org/qemu.git
11/04 00:25:30 DEBUG|virt_utils:2590| Git rep
We are currently investigating the failure. One of our suspects is that
on kvm autotest, each new qemu process instance might have a new NIC mac
address, and that might be triggering some condition in qemu in
conjunction to the guest init scripts.
It is important to note that this problem does not
1 - 100 of 203 matches
Mail list logo
