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

Re: [Xen-users] pvgrub2 legacy_configfile issues: /sbin/init exec error -8


  • To: Andy Smith <andy@xxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxx
  • From: Sarah Newman <srn@xxxxxxxxx>
  • Date: Sat, 11 Feb 2017 09:04:18 -0800
  • Delivery-date: Sat, 11 Feb 2017 17:05:30 +0000
  • Dkim-filter: OpenDKIM Filter v2.10.3 mail.prgmr.com BA13A28C026
  • List-id: Xen user discussion <xen-users.lists.xen.org>

On 02/11/2017 12:10 AM, Andy Smith wrote:
> Hi Mark,
> 
> Thanks for the response. Do you have legacy_configfile working on
> your setup?
> 

It looks to me like the problem is related to the legacy_configfile translation 
putting in the first parameter twice? I see this from our ubuntu-based
build

 +----------------------------------------------------------------------------+
 |# Unsupported legacy command: root                (hd1,0)                   |
 |legacy_kernel   '/boot/vmlinuz-3.16.0-4-amd64' '/boot/vmlinuz-3.16.0-4-amd6\|
 |4' 'root=LABEL=RESCUE' 'console=hvc0' 'ro' 'rootflags=barrier=0' 'fastboot'\|
 | 'aufs=tmpfs'                                                               |
 |legacy_initrd '/boot/initrd.img-3.16.0-4-amd64' '/boot/initrd.img-3.16.0-4-\|
 |amd64'                                                                      |


When I boot this as-is I get:

[    0.042343] Unpacking initramfs...
[    0.194916] Freeing initrd memory: 8404K (ffff880001f18000 - 
ffff88000274d000)
....
[    1.552324] Failed to execute /init (error -8)
[    1.553314] Starting init: /sbin/init exists but couldn't execute it (error 
-8)
[    1.554303] Starting init: /bin/sh exists but couldn't execute it (error -8)
[    1.554312] Kernel panic - not syncing: No working init found.  Try passing 
init= option to kernel. See Linux Documentation/init.txt for guidance.

When I make the following edit:

 +----------------------------------------------------------------------------+
 |# Unsupported legacy command: root                (hd1,0)                   |
 |legacy_kernel   '/boot/vmlinuz-3.16.0-4-amd64' '/boot/vmlinuz-3.16.0-4-amd6\|
 |4' 'root=LABEL=RESCUE' 'console=hvc0' 'ro' 'rootflags=barrier=0' 'fastboot'\|
 | 'aufs=tmpfs'                                                               |
 |legacy_initrd '/boot/initrd.img-3.16.0-4-amd64'                             |

I still get the lines

[    0.047220] Unpacking initramfs...
[    0.132981] Freeing initrd memory: 4204K (ffff880001f18000 - 
ffff880002333000)

And it finishes booting, no message about failing to execute init.

Assuming you can duplicate this behavior: I'm not sure where in the grub2 code 
base the double insertion of the first argument happens, but it seems
like once it's located it should be easy to fix.

--Sarah

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.