[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1798057] Re: Not able to start instances larger than 1 TB

From: Thomas Huth
Subject: [Bug 1798057] Re: Not able to start instances larger than 1 TB
Date: Thu, 12 Nov 2020 07:15:24 -0000

I'm assuming that the right physbits setting fixed the bug? ... so I'm
marking this ticket as "Invalid". If the problem still persists, then
please open again.

** Changed in: qemu
       Status: New => Invalid

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Not able to start instances larger than 1 TB

Status in QEMU:

Bug description:

  CPU: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
  OS: Ubuntu 18.04 AMD64
  QEMU: 1:2.11+dfsg-1ubuntu7.6 (Ubuntu Bionic Package)
  Openstack: Openstack Queens (Ubuntu Bionic Package)
  Libvirt-daemon: 4.0.0-1ubuntu8.5
  Seabios: 1.10.2-1ubuntu1

  The Problem:
  We are not able to start instances, which have a memory size over 1 TB.
  After starting the instance, they shortly lock up. Starting guests with a 
lower amount of RAM works
  perfectly. We dealt with the same problem in the past with an older Qemu 
Version (2.5) by patching some source files according to this patch:


  I think we now have somewhat the same problem here, however the source base 
changed and I'am not able to find the corresponding snippet to patch this.

  Also, guests show a wrong physical address size which is probably the cause 
of the lock ups on high memory guests:
  root@debug:~# grep physical /proc/cpuinfo 
  physical id   : 0
  address sizes : 40 bits physical, 48 bits virtual 

  Any way to fix this?

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]