I only saw this because it expired now :-/
Anyone affected by this might want to take a look at bug 1776189 where
Ubuntu added a special machine type to more easily set "host-phys-bits"
which is the qemu flag to have more (usually the host has more)
available (at the cost of migratability). That
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1562653
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1562653
Title:
Ubuntu
Can you still reproduce this problem with the latest version of upstream
QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1562653
Title:
For cpus which have not EPT feature, should change
CR3_L_MODE_RESERVED_BITS in arch/x86/include/asm/kvm_host.h:
-#define CR3_L_MODE_RESERVED_BITS 0xFF00ULL
+#define CR3_L_MODE_RESERVED_BITS 0xFE00ULL
--
You received this bug notification because you are a member of qemu-
The issue is sloved after change cpuid[8008];
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -2547,7 +2547,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index,
uint32_t count,
if (env->features[FEAT_8000_0001_EDX] & CPUID_EXT2_LM) {
/* 64 bit processor */
/*
After I changed PHYS_ADDR_MASK, qemu vm can start when memory >=1024G ,
but kvm vm still hang.
-# define PHYS_ADDR_MASK 0xffLL
+# define PHYS_ADDR_MASK 0xfffLL
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I mean vm hang when memory >= 1100G (1024G when enable ide cdrom)
instead of 1.5G.
If disable hpet, the vm will hang at
acpi_ex_system_memory_space_handler when memory >= 1100G
If disable kvm, vm is good when memory <= 1020G, but also hang when
memory >= 1024G.
There is no critical information
Hi,
just to be sure, if you run
kvm -vnc :1 -m 1.5G
kvm -vnc :1 -m 1.5G --no-hpet
do those also crash?
Can you please show the contents of
/var/log/libvirt/qemu/u1510-1.log
** Package changed: kvm (Ubuntu) => qemu (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New