From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50501) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fIUQY-00026C-Hu for qemu-devel@nongnu.org; Tue, 15 May 2018 03:31:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fIUQV-00077T-Dj for qemu-devel@nongnu.org; Tue, 15 May 2018 03:31:18 -0400 Received: from indium.canonical.com ([91.189.90.7]:36030) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fIUQV-000767-6t for qemu-devel@nongnu.org; Tue, 15 May 2018 03:31:15 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1fIUQT-0001KN-Dd for ; Tue, 15 May 2018 07:31:13 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 4FD7F2E8F42 for ; Tue, 15 May 2018 07:31:13 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 15 May 2018 07:17:01 -0000 From: =?utf-8?b?7oO/IENocmlzdGlhbiBFaHJoYXJkdCDug78=?= <1769053@bugs.launchpad.net> Reply-To: Bug 1769053 <1769053@bugs.launchpad.net> Sender: bounces@canonical.com References: <152541524728.557.4600864098110042577.malonedeb@gac.canonical.com> Message-Id: <152636862197.28061.16069412499623128753.malone@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1769053] Re: Cannot start a guest with more than 1TB of RAM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Crit prio on Qemu which was explained to work just fine is not correct IMHO. After checking with David he meant to want to raise the prio on the suggest= ed libvirt extensions instead. I'm re-triaging this bug for that and will p= ing David Berrange if work on this is already tracked on a libvirt-BZ or wo= rked on in general. ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: New =3D> Triaged ** Changed in: libvirt (Ubuntu) Importance: Undecided =3D> High ** Changed in: qemu (Ubuntu) Importance: Critical =3D> Undecided -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1769053 Title: Cannot start a guest with more than 1TB of RAM Status in QEMU: Invalid Status in libvirt package in Ubuntu: Triaged Status in qemu package in Ubuntu: Invalid Bug description: Attempting to start a KVM guest with more than 1TB of RAM fails. It looks like we might need some extra patches: https://lists.gnu.org/archive/html/qemu-discuss/2017-12/msg00005.html ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 4 16:21:14 2018 InstallationDate: Installed on 2017-04-05 (393 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=3D/vmlinuz-4.15.0-20-generic root=3D/dev/ma= pper/ubuntu--vg-root ro quiet splash transparent_hugepage=3Dmadvise vt.hand= off=3D1 SourcePackage: qemu UpgradeStatus: Upgraded to bionic on 2018-04-30 (3 days ago) dmi.bios.date: 02/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS1393= 60:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1769053/+subscriptions