From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35183) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gK1RN-00035C-7O for qemu-devel@nongnu.org; Tue, 06 Nov 2018 08:30:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gK1RI-0002LO-QU for qemu-devel@nongnu.org; Tue, 06 Nov 2018 08:30:45 -0500 Received: from indium.canonical.com ([91.189.90.7]:45384) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gK1RI-0002K1-K9 for qemu-devel@nongnu.org; Tue, 06 Nov 2018 08:30:40 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1gK1RH-0000em-DR for ; Tue, 06 Nov 2018 13:30:39 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 620112E804A for ; Tue, 6 Nov 2018 13:30:39 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 06 Nov 2018 13:17:04 -0000 From: johann peyrard <1801933@bugs.launchpad.net> Reply-To: Bug 1801933 <1801933@bugs.launchpad.net> Sender: bounces@canonical.com Message-Id: <154151022459.20108.13605520748922076387.malonedeb@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1801933] [NEW] default memory parameter too small on x86_64 today List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: Launching a centos74 iso VM today does not work anymore on x86_64 without increasing the size of the memory parameter. For example with this command : $ /opt/qemu-3.0.0/bin/qemu-system-x86_64 --curses -enable-kvm -drive file=3Dfile.dd,index=3D0,media=3Ddisk -drive file=3Dcentos- x86_64.iso,index=3D1,media=3Dcdrom [ 3.047614] Failed to execute /init [ 3.048315] Kernel panic - not syncing: No init found. Try passing init= =3D option to kernel. See Linux Documentation/init.txt for guidance. [ 3.049258] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-693.21.1.el= 7.x86 Increasing the size from the default 128MiB to 512MiB let the VM works with= out problem. So, ok, it's not a qemu problem, it's more a "User problem" and interface p= roblem for me. But it push me in the end to launch VirtualBox instead of qemu, because the= default parameter does not work anymore... And I had no time to investigat= e why it does not work because the message is not visible. Debian iso with the same command line for example show a message to tell me= that there is not enough memory, so it help me to track the real issue beh= ind. But... In the end, I think today, the default memory parameter on x86_64 is= too small and it can lead some people like me to switch to VirtualBox. VirtualBox, in the wizard is set by default to 4MiB Ram size, which tell yo= u... Ok I need to put more. And, you know that 4MiB is not enough in the en= d. Regards, Johann ** Affects: qemu Importance: Undecided Status: New ** Description changed: - Launching a centos7 VM today does not work anymore on x86_64 without + Launching a centos7 iso VM today does not work anymore on x86_64 without increasing the size of the memory parameter. For example with this command : = $ /opt/qemu-3.0.0/bin/qemu-system-x86_64 --curses -enable-kvm -drive file=3Dfile.dd,index=3D0,media=3Ddisk -drive file=3Dcentos- x86_64.iso,index=3D1,media=3Dcdrom = [ 3.047614] Failed to execute /init [ 3.048315] Kernel panic - not syncing: No init found. Try passing in= it=3D option to kernel. See Linux Documentation/init.txt for guidance. [ 3.049258] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-693.21.1.= el7.x86 = - = Increasing the size from the default 128MiB to 512MiB let the VM works wi= thout problem. So, ok, it's not a qemu problem, it's more a "User problem" and interface= problem for me. But it push me in the end to launch VirtualBox instead of qemu, because t= he default parameter does not work anymore... And I had no time to investig= ate why it does not work because the message is not visible. Debian iso with the same command line for example show a message to tell = me that there is not enough memory, so it help me to track the real issue b= ehind. = But... In the end, I think today, the default memory parameter on x86_64 = is too small and it can lead some people like me to switch to VirtualBox. VirtualBox, in the wizard is set by default to 4MiB Ram size, which tell = you... Ok I need to put more. But, you know that 4MiB is not enough in the = end. = - = Regards, = Johann ** Description changed: - Launching a centos7 iso VM today does not work anymore on x86_64 without - increasing the size of the memory parameter. For example with this - command : + Launching a centos74 iso VM today does not work anymore on x86_64 + without increasing the size of the memory parameter. For example with + this command : = $ /opt/qemu-3.0.0/bin/qemu-system-x86_64 --curses -enable-kvm -drive file=3Dfile.dd,index=3D0,media=3Ddisk -drive file=3Dcentos- x86_64.iso,index=3D1,media=3Dcdrom = [ 3.047614] Failed to execute /init [ 3.048315] Kernel panic - not syncing: No init found. Try passing in= it=3D option to kernel. See Linux Documentation/init.txt for guidance. [ 3.049258] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-693.21.1.= el7.x86 = Increasing the size from the default 128MiB to 512MiB let the VM works wi= thout problem. So, ok, it's not a qemu problem, it's more a "User problem" and interface= problem for me. But it push me in the end to launch VirtualBox instead of qemu, because t= he default parameter does not work anymore... And I had no time to investig= ate why it does not work because the message is not visible. Debian iso with the same command line for example show a message to tell = me that there is not enough memory, so it help me to track the real issue b= ehind. = But... In the end, I think today, the default memory parameter on x86_64 = is too small and it can lead some people like me to switch to VirtualBox. VirtualBox, in the wizard is set by default to 4MiB Ram size, which tell = you... Ok I need to put more. But, you know that 4MiB is not enough in the = end. = Regards, = Johann ** Description changed: Launching a centos74 iso VM today does not work anymore on x86_64 without increasing the size of the memory parameter. For example with this command : = $ /opt/qemu-3.0.0/bin/qemu-system-x86_64 --curses -enable-kvm -drive file=3Dfile.dd,index=3D0,media=3Ddisk -drive file=3Dcentos- x86_64.iso,index=3D1,media=3Dcdrom = [ 3.047614] Failed to execute /init [ 3.048315] Kernel panic - not syncing: No init found. Try passing in= it=3D option to kernel. See Linux Documentation/init.txt for guidance. [ 3.049258] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-693.21.1.= el7.x86 = Increasing the size from the default 128MiB to 512MiB let the VM works wi= thout problem. So, ok, it's not a qemu problem, it's more a "User problem" and interface= problem for me. But it push me in the end to launch VirtualBox instead of qemu, because t= he default parameter does not work anymore... And I had no time to investig= ate why it does not work because the message is not visible. Debian iso with the same command line for example show a message to tell = me that there is not enough memory, so it help me to track the real issue b= ehind. = But... In the end, I think today, the default memory parameter on x86_64 = is too small and it can lead some people like me to switch to VirtualBox. - VirtualBox, in the wizard is set by default to 4MiB Ram size, which tell = you... Ok I need to put more. But, you know that 4MiB is not enough in the = end. + VirtualBox, in the wizard is set by default to 4MiB Ram size, which tell = you... Ok I need to put more. And, you know that 4MiB is not enough in the = end. = Regards, = Johann -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1801933 Title: default memory parameter too small on x86_64 today Status in QEMU: New Bug description: Launching a centos74 iso VM today does not work anymore on x86_64 without increasing the size of the memory parameter. For example with this command : $ /opt/qemu-3.0.0/bin/qemu-system-x86_64 --curses -enable-kvm -drive file=3Dfile.dd,index=3D0,media=3Ddisk -drive file=3Dcentos- x86_64.iso,index=3D1,media=3Dcdrom [ 3.047614] Failed to execute /init [ 3.048315] Kernel panic - not syncing: No init found. Try passing in= it=3D option to kernel. See Linux Documentation/init.txt for guidance. [ 3.049258] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.0-693.21.1.= el7.x86 Increasing the size from the default 128MiB to 512MiB let the VM works wi= thout problem. So, ok, it's not a qemu problem, it's more a "User problem" and interface= problem for me. But it push me in the end to launch VirtualBox instead of qemu, because t= he default parameter does not work anymore... And I had no time to investig= ate why it does not work because the message is not visible. Debian iso with the same command line for example show a message to tell = me that there is not enough memory, so it help me to track the real issue b= ehind. But... In the end, I think today, the default memory parameter on x86_64 = is too small and it can lead some people like me to switch to VirtualBox. VirtualBox, in the wizard is set by default to 4MiB Ram size, which tell = you... Ok I need to put more. And, you know that 4MiB is not enough in the = end. Regards, Johann To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1801933/+subscriptions