Absolutely, please close it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/599958
Title:
Timedrift problems with Win7: hpet missing time drift fixups
Status in QEMU:
Incomplete
Bug description:
.
On Tue, May 22, 2018 at 10:14 PM, Lucas Meneghel Rodrigues
wrote:
> On Tue, May 22, 2018 at 9:50 PM, Cleber Rosa wrote:
>>
>>
>> On 05/21/2018 07:32 PM, Philippe Mathieu-Daudé wrote:
>>> On 05/21/2018 07:33 PM, Alistair Francis wrote:
>>>> On Sun, May
On Tue, May 22, 2018 at 9:50 PM, Cleber Rosa wrote:
>
>
> On 05/21/2018 07:32 PM, Philippe Mathieu-Daudé wrote:
>> On 05/21/2018 07:33 PM, Alistair Francis wrote:
>>> On Sun, May 20, 2018 at 8:16 PM, Fam Zheng wrote:
On Fri, 05/18 11:34, Alistair Francis wrote:
> Avocado is not trivial t
Sure, please close it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1162644
Title:
qemu-system-x86_64 crashed with SIGABRT in __assert_fail_base()
Status in QEMU:
Incomplete
Status in qemu pack
This doesn't reproduce with the latest version of QEMU, you may close
it.
--
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 unittest emulator failure on latest git master
Status in
Just for the record, I've tested it using the virt-test reproducer and
indeed the problem is fixed with this patchset. I'm sorry for the delay!
Thanks :)
On Mon, Feb 23, 2015 at 9:56 AM, Alexander Graf wrote:
After the vmdesc self-describing JSON blob landed upstream, some
people
noticed the
On Fri, Feb 13, 2015 at 9:18 AM, Alexander Graf wrote:
On 13.02.15 10:04, Dr. David Alan Gilbert wrote:
* Alexander Graf (ag...@suse.de) wrote:
On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
Copying Alex.
OK, after bisecting, this is what I'v
ord of
vm registers taken periodically during the testing process.
Cheers,
Lucas
On Thu, Feb 12, 2015 at 10:36 PM, Alexander Graf wrote:
On 13.02.15 01:29, Lucas Meneghel Rodrigues wrote:
Copying Alex.
OK, after bisecting, this is what I've got:
8118f0950fc77cce7873002a5021172d
5be2cfbb1de9dfa
7aaf3d10ef7f73413b228e854fe6f04317151e46 M tests
So there you go. I'm going to sleep, if you need any extra help let me know.
Cheers,
Lucas
On Thu, Feb 12, 2015 at 8:56 PM, Lucas Meneghel Rodrigues wrote:
> OK, indeed I can reproduce the problem. It's specific to th
On Thu, Feb 12, 2015 at 8:56 PM, Lucas Meneghel Rodrigues wrote:
> OK, indeed I can reproduce the problem. It's specific to the
> filedescriptor migration. An easy way to reproduce it is by doing:
>
> git clone https://github.com/autotest/virt-test.git
>
> cd vi
pulate_device
callback
memory: unregister AddressSpace MemoryListener within BQL
Signed-off-by: Peter Maydell
On Thu, Feb 12, 2015 at 8:19 PM, Lucas Meneghel Rodrigues wrote:
> From what the log says, after a round of migrations 'info migrate' does
> not respond after 4 minutes
>From what the log says, after a round of migrations 'info migrate' does not
respond after 4 minutes, timing out. Virt Test then shuts down the VM. When
it tries to check the qcow2 image, it is corrupted. I'm checking out the
latest master to see how reproducible this problem is.
On Thu, Feb 12, 2
On 12/10/2013 05:31 PM, Paul Moore wrote:
On Tuesday, December 10, 2013 04:48:54 PM Lucas Meneghel Rodrigues wrote:
On 12/10/2013 01:20 AM, Corey Bryant wrote:
IMHO the test suite should probe to see if sandbox is working or not,
and
just not use the "-sandbox on" arg if the ho
On 12/10/2013 01:20 AM, Corey Bryant wrote:
IMHO the test suite should probe to see if sandbox is working or not,
and
just not use the "-sandbox on" arg if the host doesn't support it.
But I think this could be done on virt-test as well :)
This would make sense.
Although it sounds like Luca
On 12/09/2013 03:20 PM, Eduardo Otubo wrote:
This option was requested by virt-test team so they can run tests with
Qemu and "-sandbox on" set without breaking whole test if host doesn't
have support for seccomp in kernel. It covers two possibilities:
1) Host kernel support does not support se
The problem showed up this morning again, same top commit:
10/07 01:34:42 INFO | git:0150| git commit ID is
a684f3cf9b9b9c3cb82be87aafc463de8974610c (tag v1.4.0-4237-ga684f3c)
This time around, debug symbols were enabled on the configure line:
10/07 01:35:31 DEBUG|build_help:0588| Enablin
Good point, I've just changed the configure line to include --enable-
debug.
About the relation of the crash with the top commit, We can't ensure it
was because of this top commit, could be other patches that were applied
from one day to another. We only test qemu.git once a day, we don't have
eno
On 10/02/2013 10:08 PM, Lucas Meneghel Rodrigues wrote:
I've noticed this when virt-test QEMU monitor protocol
code was getting all confused with output like:
'Removable device: not locked, tray closed\n [not inserted](qemu)'
Since it was breaking some assumptions on that code.
enient, but here
the human monitor is supposed to print the newline anyway.
CC: Stefan Hajnoczi
Signed-off-by: Lucas Meneghel Rodrigues
---
hmp.c| 2 +-
roms/seabios | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hmp.c b/hmp.c
index 5891507..2d2e5f8 100644
---
Public bug reported:
During today's automated qemu.git testing, a segmentation fault while
installing Windows 7 SP1 happened.
qemu.git top commit:
10/02 01:30:24 INFO | git:0150| git commit ID is
a684f3cf9b9b9c3cb82be87aafc463de8974610c (tag v1.4.0-4237-ga684f3c)
commit a684f3cf9b9b9c3cb
On 10/01/2013 10:32 PM, Anthony Liguori wrote:
Should be better now.
Thanks, Anthony!
On 10/01/2013 04:52 PM, Alex Bennée wrote:
l...@redhat.com writes:
On 10/01/2013 04:37 PM, Alex Bennée wrote:
l...@redhat.com writes:
Hello:
In the daily qemu.git autotest run, I started to see the following
problem while checking out the qemu.git tree and checking out the
submodules:
O
On 10/01/2013 04:37 PM, Alex Bennée wrote:
l...@redhat.com writes:
Hello:
In the daily qemu.git autotest run, I started to see the following
problem while checking out the qemu.git tree and checking out the
submodules:
$ git submodule update
fatal: reference is not a tree: ece025f5980bae88
Hello:
In the daily qemu.git autotest run, I started to see the following
problem while checking out the qemu.git tree and checking out the
submodules:
$ git submodule update
Submodule path 'dtc': checked out 'bc895d6d09695d05ceb8b52486ffe861d6cfbdde'
Submodule path 'pixman': checked out '97
Yep, I did let this one slip...
In any case, I don't see this problem anymore, it was fixed a long while
ago. Are you trying QEMU from the latest master?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
On 23/05/13 05:50 AM, Michael S. Tsirkin wrote:
Hey guys,
I've updated the kvm networking todo wiki with current projects.
Will try to keep it up to date more often.
Original announcement below.
I've put up a wiki page with a kvm networking todo list,
mainly to avoid effort duplication, bu
ed.
This looks good to me, thanks Stefan!
Acked-by: Lucas Meneghel Rodrigues
Signed-off-by: Stefan Hajnoczi
---
v3:
* Use $ escaping in tests/Makefile [eblake]
v2:
* Randomize MALLOC_PERTURB_ value [armbru]
* Preserve existing MALLOC_PERTURB_ variable, if set [danpb]
test
On 17/05/13 07:58 AM, Markus Armbruster wrote:
"Daniel P. Berrange" writes:
On Fri, May 17, 2013 at 11:54:12AM +0200, Markus Armbruster wrote:
Stefan Hajnoczi writes:
glibc wipes malloc(3) memory when the MALLOC_PERTURB_ environment
variable is set. The value of the environment variable d
On 17/05/13 08:15 AM, Stefan Hajnoczi wrote:
On Fri, May 17, 2013 at 11:54 AM, Markus Armbruster wrote:
Stefan Hajnoczi writes:
glibc wipes malloc(3) memory when the MALLOC_PERTURB_ environment
variable is set. The value of the environment variable determines the
bit pattern used to wipe me
On 17/05/13 07:07 AM, Daniel P. Berrange wrote:
If you want punishment, why not go for extra punishment?
MALLOC_PERTURB_=$(($RANDOM % 255 + 1))
That could lead to non-reproducable failures though. I think it is better
to use a fixed value so that you're more likely to be able to reproduce
the
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 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
.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):
"
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
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
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
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
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
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
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
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.
On my F19 box, it's failing about 2/3 of the attempts. What is funny is
that on the Ubuntu 13.04 box, I can't get the problem reproduced
anymore, for some reason beyond me.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.
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
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/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 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/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 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
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
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/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
On 01/07/2013 03:16 PM, Stefan Weil wrote:
Am 07.01.2013 09:35, schrieb Gerd Hoffmann:
On 01/04/13 22:57, Stefan Weil wrote:
pc-testdev.c cannot be compiled with MinGW:
CCi386-softmmu/hw/i386/../pc-testdev.o
hw/i386/../pc-testdev.c:38:22: warning: sys/mman.h: file not found
hw/i386/../p
On Sat, Jan 5, 2013 at 6:52 AM, Qingtang Zhou wrote:
> * On 2012-12-31 17:55:24 -0200, Lucas Meneghel Rodrigues (look...@gmail.com)
> wrote:
>> Hmmm, about this one, I'm worried about making things more complex...
>>
>> The way I see the problem at hand, I'
On Fri, Jan 4, 2013 at 1:06 PM, Gerd Hoffmann wrote:
> Hi,
>
>> So while I am impartial to this specific patch, some easy way to run a
>> comprehensive test coverage without having to manually name each test
>> using --tests= would be very handy! Something like --all-tests maybe?
>
> Hint from t
On 01/04/2013 11:13 AM, Andreas Färber wrote:
Am 31.12.2012 20:55, schrieb Lucas Meneghel Rodrigues:
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 cre
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
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
On 12/13/2012 12:48 PM, Lucas Meneghel Rodrigues wrote:
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.
Hello Anthony
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 +
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
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
, 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
--
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
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
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
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):
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
On 12/13/2012 12:28 PM, Gerd Hoffmann wrote:
Hi,
hw/pc-testdev.c | 167 +
That should have been in patch 2/2 I guess?
Oops, rebase error :( Will re-spin and re-send.
Thanks!
cheers,
Gerd
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
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
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
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
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
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
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
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
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
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 +
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
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
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 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
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/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
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
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
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
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
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_
** 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
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
1 - 100 of 205 matches
Mail list logo
