+/*
+ * KVMPPC_INST_BOOK3S_DEBUG is debug Instruction for supporting Software
Breakpoint.
+ * Based on PowerISA v2.07, Instruction with opcode 0s will be treated as
illegal
+ * instruction.
+ */
primary opcode 0 instead?
+#define OP_ZERO 0x0
Using 0x0 where you mean 0,
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
On Behalf Of Wanpeng Li
Sent: Friday, August 01, 2014 4:12 PM
To: Paolo Bonzini; Jan Kiszka
Cc: Marcelo Tosatti; Gleb Natapov; Bandan Das; Zhang, Yang Z;
kvm@vger.kernel.org;
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org]
On Behalf Of Wanpeng Li
Sent: Friday, August 01, 2014 4:12 PM
To: Paolo Bonzini; Jan Kiszka
Cc: Marcelo Tosatti; Gleb Natapov; Bandan Das; Zhang, Yang Z;
kvm@vger.kernel.org;
Hi, Vadim
I start a vm(windows server 2008 64bit) with below qemu command, get stuck with
black screen during boot stage,
no error report by qemu and kvm hypervisor, but if I remove the item
hv_vapic, then start and run the VM successfully.
/var/run/qemu-server/5195516385344.pid -daemonize
Hi Zhang,
No I haven't seen such problem
Which kernel version are you running?
Does it include the latest lazy eli changes?
Btw, hv_spinlocks=0xfff is a pretty huge value.
Best regards,
Vadim.
- Original Message -
From: Zhang Haoyu zhan...@sangfor.com
To: Vadim Rozenfeld
+/*
+ * KVMPPC_INST_BOOK3S_DEBUG is debug Instruction for supporting Software
Breakpoint.
+ * Based on PowerISA v2.07, Instruction with opcode 0s will be treated as
illegal
+ * instruction.
+ */
primary opcode 0 instead?
+#define OP_ZERO 0x0
Using 0x0 where you mean 0,
