On 26.06.2013 12:47, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I remove kvmvapic.bin the virtual machine boots with
qemu-kvm 1.5.0. I
On Thu, Jun 27, 2013 at 04:09:50PM +0200, Stefan Pietsch wrote:
On 26.06.2013 12:47, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I
On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I remove kvmvapic.bin the virtual machine boots with
qemu-kvm 1.5.0. I just verified this with Linux kernel
On 23.06.2013 19:36, Gleb Natapov wrote:
On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
On 23.06.2013 09:51, Gleb Natapov wrote:
On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
and
On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote:
On 23.06.2013 19:36, Gleb Natapov wrote:
On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
On 23.06.2013 09:51, Gleb Natapov wrote:
On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
Can you provide
On 24.06.2013 13:47, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote:
On 23.06.2013 19:36, Gleb Natapov wrote:
On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
On 23.06.2013 09:51, Gleb Natapov wrote:
On Thu, Jun 20, 2013 at 07:01:49PM +0200,
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
On 24.06.2013 13:47, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote:
On 23.06.2013 19:36, Gleb Natapov wrote:
On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
On 23.06.2013
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I remove kvmvapic.bin the virtual machine boots with
qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
emulate_invalid_guest_state=0 or
On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
and emulate_invalid_guest_state=0. Also run x/20i $pc-20 in qemu
monitor after the hang.
25391454e73e3156202264eb3c473825afe4bc94
On 23.06.2013 09:51, Gleb Natapov wrote:
On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
and emulate_invalid_guest_state=0. Also run x/20i $pc-20 in qemu
monitor after the hang.
On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
On 23.06.2013 09:51, Gleb Natapov wrote:
On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
and emulate_invalid_guest_state=0. Also run x/20i
On 19.06.2013 16:38, Gleb Natapov wrote:
On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote:
On 19.06.2013 15:41, Gleb Natapov wrote:
On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
KVM: VMX: don't
On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
On 13.06.2013 16:59, Stefan Pietsch wrote:
On 13.06.2013 15:42, Paolo Bonzini wrote:
Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
git bisect tells me:
79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
On 19.06.2013 15:41, Gleb Natapov wrote:
On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
KVM: VMX: don't clobber segment AR of unusable segments.
25391454e73e3156202264eb3c473825afe4bc94
On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote:
On 19.06.2013 15:41, Gleb Natapov wrote:
On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
KVM: VMX: don't clobber segment AR of unusable segments.
On 17.06.2013 18:07, Paolo Bonzini wrote:
Il 16/06/2013 02:25, Stefan Pietsch ha scritto:
Bisecting leads to
git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398
git bisect good 007a3b547512d69f67ceb9641796d64552bd337e
git bisect good 1f3141e80b149e7215313dff29e9a0c47811b1d1
git bisect
Il 16/06/2013 02:25, Stefan Pietsch ha scritto:
Bisecting leads to
git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398
git bisect good 007a3b547512d69f67ceb9641796d64552bd337e
git bisect good 1f3141e80b149e7215313dff29e9a0c47811b1d1
git bisect good
On 13.06.2013 16:59, Stefan Pietsch wrote:
On 13.06.2013 15:42, Paolo Bonzini wrote:
Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
git bisect tells me:
79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
This is an s390 commit, so the bisect somehow went wrong. Can you
On 09.06.2013 11:43, Gleb Natapov wrote:
On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote:
On 06.06.2013 13:40, Gleb Natapov wrote:
On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
The
Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
git bisect tells me:
79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
This is an s390 commit, so the bisect somehow went wrong. Can you
confirm that 3.7 works and 3.8 doesn't?
Please check these pairs:
9e2d59a and
Il 13/06/2013 09:42, Paolo Bonzini ha scritto:
Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
git bisect tells me:
79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
This is an s390 commit, so the bisect somehow went wrong. Can you
confirm that 3.7 works and 3.8 doesn't?
On 13.06.2013 15:42, Paolo Bonzini wrote:
Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
git bisect tells me:
79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
This is an s390 commit, so the bisect somehow went wrong. Can you
confirm that 3.7 works and 3.8 doesn't?
On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote:
On 06.06.2013 13:40, Gleb Natapov wrote:
On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
The machine hangs after Enabling APIC
On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
On 05.06.2013 14:10, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM
On Thu, Jun 06, 2013 at 09:42:40AM +0300, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
On 05.06.2013 14:10, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May
On 06.06.2013 08:42, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
On 05.06.2013 14:10, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100,
On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
On 06.06.2013 08:42, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
On 05.06.2013 14:10, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
On 19.05.2013
On 06.06.2013 13:40, Gleb Natapov wrote:
On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
The machine hangs after Enabling APIC mode: Flat. Using 1 I/O APICs.
OK, since it looks like it hangs during
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a 32-bit host. Stefan found this when running GRML, a live
distribution which can be downloaded from:
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a 32-bit host. Stefan found this when
On 05.06.2013 14:10, Gleb Natapov wrote:
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a 32-bit host. Stefan found this when running GRML, a live
distribution which can be downloaded from:
On Wed, May 29, 2013 at 05:05:55PM +0200, Stefan Pietsch wrote:
On 19.05.2013 14:32, Gleb Natapov wrote:
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a 32-bit host. Stefan found this when
On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a 32-bit host. Stefan found this when running GRML, a live
distribution which can be downloaded from:
Dear KVM maintainers, it appears that there is a gap in x86 emulation,
at least on a 32-bit host. Stefan found this when running GRML, a live
distribution which can be downloaded from:
http://download.grml.org/grml32-full_2013.02.iso. His original
reported is at http://bugs.debian.org/707257.
On 09.05.2013 20:56, Stefan Pietsch wrote:
On 09.05.2013 03:08, Ben Hutchings wrote:
Please could you test some of the intermediate versions at
http://snapshot.debian.org/package/linux/ to find the first upstream
version where this was broken.
The first version which does not work is
On 09.05.2013 03:08, Ben Hutchings wrote:
Please could you test some of the intermediate versions at
http://snapshot.debian.org/package/linux/ to find the first upstream
version where this was broken.
The first version which does not work is 3.6.4-1~experimental.1.
3.5.5-1~experimental.1
Package: linux-image-3.8-1-686-pae
Version: 3.8.11-1
KVM fails with the unstable kernel 3.8.11-1.
#
kvm -m 512 -cdrom grml32-full_2013.02.iso
KVM: entry failed, hardware error 0x8021
If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be
Control: tag -1 moreinfo
On Wed, 2013-05-08 at 17:45 +0200, Stefan Pietsch wrote:
Package: linux-image-3.8-1-686-pae
Version: 3.8.11-1
KVM fails with the unstable kernel 3.8.11-1.
[...]
Running KVM works on this host with the kernel package
linux-image-3.2.0-4-686-pae 3.2.41-2.
Please
39 matches
Mail list logo
