On 25/12/2014 08:46, Chen, Tiejun wrote:
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index f528343..910bc48 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -672,6 +672,7 @@ static void update_memslots(struct kvm_memslots *slots,
WARN_ON(mslots[i].id !=
Chen, Tiejun wrote:
On 2014/12/24 19:02, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 15:26, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 9:50, Chen, Tiejun wrote:
On 2014/12/22 17:23, Jamie Heilman wrote:
KVM internal error. Suberror: 1
emulation failure
EAX=000de494
On 2014/12/25 18:52, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/24 19:02, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 15:26, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 9:50, Chen, Tiejun wrote:
On 2014/12/22 17:23, Jamie Heilman wrote:
KVM internal error.
the same thing
with disabled perfctr wrmsr message. However, it doesn't look like
Sorry I'm not sure if I understood current status. Looks 3.19-rc1 my
patch just fix that error above,
KVM: entry failed, hardware error 0x8021
...
Right?
I'm entirely out of the woods, because one of my
Chen, Tiejun wrote:
On 2014/12/23 15:26, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 9:50, Chen, Tiejun wrote:
On 2014/12/22 17:23, Jamie Heilman wrote:
KVM internal error. Suberror: 1
emulation failure
EAX=000de494 EBX= ECX= EDX=0cfd
ESI=0059
On 24/12/2014 12:02, Jamie Heilman wrote:
Running qemu-system-x86_64 -machine pc,accel=kvm -nodefaults works,
my real (headless) kvm guests work, but this new patch makes running
qemu-system-x86_64 -machine pc,accel=kvm fail again, this time with
errors in the host to the tune of:
On 2014/12/24 19:02, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 15:26, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/23 9:50, Chen, Tiejun wrote:
On 2014/12/22 17:23, Jamie Heilman wrote:
KVM internal error. Suberror: 1
emulation failure
EAX=000de494 EBX=
On 2014/12/24 19:11, Paolo Bonzini wrote:
On 24/12/2014 12:02, Jamie Heilman wrote:
Running qemu-system-x86_64 -machine pc,accel=kvm -nodefaults works,
my real (headless) kvm guests work, but this new patch makes running
qemu-system-x86_64 -machine pc,accel=kvm fail again, this time with
Chen, Tiejun wrote:
On 2014/12/21 20:46, Jamie Heilman wrote:
With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
get:
KVM: entry failed, hardware error 0x8021
Looks some MSR writing issues such a failed entry.
If you're running a guest on an Intel machine without
On 2014/12/22 17:23, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/21 20:46, Jamie Heilman wrote:
With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
get:
KVM: entry failed, hardware error 0x8021
Looks some MSR writing issues such a failed entry.
If you're
On 2014/12/23 9:50, Chen, Tiejun wrote:
On 2014/12/22 17:23, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/21 20:46, Jamie Heilman wrote:
With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
get:
KVM: entry failed, hardware error 0x8021
Looks some MSR writing
Chen, Tiejun wrote:
On 2014/12/23 9:50, Chen, Tiejun wrote:
On 2014/12/22 17:23, Jamie Heilman wrote:
Chen, Tiejun wrote:
On 2014/12/21 20:46, Jamie Heilman wrote:
With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
get:
KVM: entry failed, hardware error 0x8021
the same thing
with disabled perfctr wrmsr message. However, it doesn't look like
Sorry I'm not sure if I understood current status. Looks 3.19-rc1 my
patch just fix that error above,
KVM: entry failed, hardware error 0x8021
...
Right?
I'm entirely out of the woods, because one of my
With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
get:
KVM: entry failed, hardware error 0x8021
If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT
On 2014/12/21 20:46, Jamie Heilman wrote:
With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I
get:
KVM: entry failed, hardware error 0x8021
Looks some MSR writing issues such a failed entry.
If you're running a guest on an Intel machine without unrestricted mode
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.libguestfs.channel.0
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
Domain id=2 is tainted: custom-argv
Domain id=2 is tainted: host-cpu
KVM: entry failed, hardware error 0x7
RAX
On 06/12/2012 01:23 PM, Johannes Bauer wrote:
On 10.06.2012 17:19, Avi Kivity wrote:
Looks like we weren't dealing with interrupts correctly. I pushed some
patches, please pull again and retry.
Updated to cf3d9372065470403e0780599ca612553211a10b and it works
perfectly for me!
Good to
On 06/07/2012 10:14 PM, Johannes Bauer wrote:
On 07.06.2012 19:25, Avi Kivity wrote:
Note that c does NOT cause the VM to resume, only info registers
does. dmesg shows nothing out of the ordinary.
I'm guessing this is 5152902652. Try bumping 'unsigned count = 130' (by
adding zeros at the
On 06/06/2012 09:07 PM, Johannes Bauer wrote:
On 06.06.2012 17:53, Avi Kivity wrote:
# rmmod kvm_intel
# modprobe kvm_intel emulate_invalid_guest_state=1
Warning: experimental code.
Tried it out -- I don't get the error anymore, but qemu just hangs on
boot with 100% CPU. :-(
Please
On 07.06.2012 09:12, Avi Kivity wrote:
add -monitor stdio to the command line and then:
(qemu) info registers
(qemu) x/20i 0xcsbase + $eip
Run info registers a few times and note whether eip changes or not.
It does not. Here's where it hangs:
(qemu) info registers
EAX=23de
On 06/07/2012 01:03 PM, Johannes Bauer wrote:
On 07.06.2012 09:12, Avi Kivity wrote:
add -monitor stdio to the command line and then:
(qemu) info registers
(qemu) x/20i 0xcsbase + $eip
Run info registers a few times and note whether eip changes or not.
It does not. Here's where it
On 06/07/2012 01:54 PM, Avi Kivity wrote:
On 06/07/2012 01:03 PM, Johannes Bauer wrote:
On 07.06.2012 09:12, Avi Kivity wrote:
add -monitor stdio to the command line and then:
(qemu) info registers
(qemu) x/20i 0xcsbase + $eip
Run info registers a few times and note whether eip changes
On 07.06.2012 16:52, Avi Kivity wrote:
Please try the big-real-mode branch again. It contains emulation for
the missing instruction, plus a bunch of tweaks which allowed it to boot
Fedora 17 smp with emulate_invalid_guest_state=1.
Progress!
So now I'm on
Linux joequad
On 06/07/2012 06:39 PM, Johannes Bauer wrote:
On 07.06.2012 16:52, Avi Kivity wrote:
Please try the big-real-mode branch again. It contains emulation for
the missing instruction, plus a bunch of tweaks which allowed it to boot
Fedora 17 smp with emulate_invalid_guest_state=1.
Progress!
On 07.06.2012 19:25, Avi Kivity wrote:
Note that c does NOT cause the VM to resume, only info registers
does. dmesg shows nothing out of the ordinary.
I'm guessing this is 5152902652. Try bumping 'unsigned count = 130' (by
adding zeros at the end, don't bother with anything less). If you
On 07.06.2012 19:25, Avi Kivity wrote:
Note that c does NOT cause the VM to resume, only info registers
does. dmesg shows nothing out of the ordinary.
I'm guessing this is 5152902652. Try bumping 'unsigned count = 130' (by
adding zeros at the end, don't bother with anything less). If you
On 07.06.2012 21:46, Johannes Bauer wrote:
In an infinite loop. Which looks to be as if it is continuously exiting
after just one iteration (count at leave is 1299). Maybe I'll fiddle
some more and am able to provide some insight (probably you already know
what's going on, but it won't hurt I
On 06/03/2012 04:01 PM, Johannes Bauer wrote:
# rmmod kvm_intel
# modprobe kvm_intel emulate_invalid_guest_state=1
Warning: experimental code.
Tried it out -- I don't get the error anymore, but qemu just hangs on
boot with 100% CPU. :-(
Please retry with
On 06.06.2012 17:53, Avi Kivity wrote:
# rmmod kvm_intel
# modprobe kvm_intel emulate_invalid_guest_state=1
Warning: experimental code.
Tried it out -- I don't get the error anymore, but qemu just hangs on
boot with 100% CPU. :-(
Please retry with
On 05.06.2012 15:59, David Ahern wrote:
You need to install the plugins for trace-cmd:
make install_plugins
you could also try setting:
export TRACE_CMD_PLUGIN_DIR=/path/to/plugins
Aha, with that I get more messages:
trace-cmd: No such file or directory
cound not load plugin
On 6/4/12 12:28 PM, Johannes Bauer wrote:
On 04.06.2012 10:53, Gleb Natapov wrote:
On Sun, Jun 03, 2012 at 06:25:33PM +0200, Johannes Bauer wrote:
Therefore, I've uploaded the compressed trace.dat file, so you can maybe
have a look why the report tool barfs and interpret it correctly. I
can't
On Sun, Jun 03, 2012 at 06:25:33PM +0200, Johannes Bauer wrote:
Therefore, I've uploaded the compressed trace.dat file, so you can maybe
have a look why the report tool barfs and interpret it correctly. I
can't figure it out. The trace is here:
http://spornkuller.de/trace.dat.bz2
I can
On 06/04/2012 11:53 AM, Gleb Natapov wrote:
On Sun, Jun 03, 2012 at 06:25:33PM +0200, Johannes Bauer wrote:
Therefore, I've uploaded the compressed trace.dat file, so you can maybe
have a look why the report tool barfs and interpret it correctly. I
can't figure it out. The trace is here:
On 04.06.2012 10:53, Gleb Natapov wrote:
On Sun, Jun 03, 2012 at 06:25:33PM +0200, Johannes Bauer wrote:
Therefore, I've uploaded the compressed trace.dat file, so you can maybe
have a look why the report tool barfs and interpret it correctly. I
can't figure it out. The trace is here:
On 04.06.2012 20:28, Johannes Bauer wrote:
What is your command line?
bin/qemu-system-x86_64 -cpu host -enable-kvm -net nic -net
user,smb=Share,restrict=on -drive
media=disk,file=Windows7_x32.qcow2,if=virtio -m 2048 -smp 1 -nographic
Just noticed that the output I just provided was for the
:
the installation first works fine but upon first reboot qemu terminates
with:
KVM: entry failed, hardware error 0x8021
If you're runnning a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
the installation first works fine but upon first reboot qemu terminates
with:
KVM: entry failed, hardware error 0x8021
If you're runnning a guest on an Intel machine without
On 03.06.2012 14:33, Avi Kivity wrote:
when trying to install Windows7 in a qemu-kvm 1.0.1 installation on
Gentoo on my host running
Is that a 32-bit or 64-bit Windows 7?
64 bit. But I've also (in despair) tried installing 32 Bit Windows 7,
with the exact same effect.
EAX=0010
On 03.06.2012 14:33, Avi Kivity wrote:
You can run vmxcap [1] and see.
Ah, I forgot to attach the output of vmxcap, which might be of interest.
First the host where it does not work:
pin-based controls
External interrupt exiting yes
NMI exiting
On 06/03/2012 04:01 PM, Johannes Bauer wrote:
On 03.06.2012 14:33, Avi Kivity wrote:
when trying to install Windows7 in a qemu-kvm 1.0.1 installation on
Gentoo on my host running
Is that a 32-bit or 64-bit Windows 7?
64 bit. But I've also (in despair) tried installing 32 Bit Windows 7,
On 03.06.2012 15:43, Avi Kivity wrote:
On 06/03/2012 04:01 PM, Johannes Bauer wrote:
On 03.06.2012 14:33, Avi Kivity wrote:
when trying to install Windows7 in a qemu-kvm 1.0.1 installation on
Gentoo on my host running
Is that a 32-bit or 64-bit Windows 7?
64 bit. But I've also (in
41 matches
Mail list logo
