Ubuntu16.04 netboot installation fails with illegal instruction error

[bugproxy]

Problem Description
========================
 Tried installing ubuntu16.04 using netboot method and it fails with error 'Illegal instruction'

> Tried installing ubuntu16.04 using netboot method - yupg1 guest.
> Added DHCP entry in KTE for the yupg1 guest.
> Able to select Langauage and Location from installer menu.
> It prompts for 'configure network window' as below

   ??????????????????????? [!] Configure the network ???????????????????????
   ? ?
   ? Please enter the hostname for this system. ?
   ? ?
   ? The hostname is a single word that identifies your system to the ?
   ? network. If you don't know what your hostname should be, consult your ?
   ? network administrator. If you are setting up your own home network, ?
   ? you can make something up here. ?
   ? ?
   ? Hostname: ?
   ? ?
   ? yupg1________________________________________________________________ ?
   ? ?
   ? <Go Back> <Continue> ?
   ? ?
   ?????????????????????????????????????????????????????????????????????????

> After selecting continue button, it thows message as 'Illegal instruction'

Illegal instruction

> Unable to proceed further and it continously throws above message

Host Details:
---------------
  KVM BUILD LEVEL: GA3 SP1 build 55

== Comment: #8 - Vaishnavi Bhat <email address hidden> - ==
When I started the installation and reached the point to enter the hostname, the installation hanged with 'Illegal instruction'. At this point I could not collect any debug logs. I tried installation with multipath enabled and could reach a point where I could collect the debug logs. I did not see ''Illegal instruction' on my console this time but it was recorded in the logs.

Mar 8 16:40:09 main-menu[209]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored)
Mar 8 16:40:09 main-menu[209]: INFO: Menu item 'network-preseed' selected
Mar 8 16:40:09 kernel: [ 43.752359] wget[1357]: unhandled signal 4 at 000000003159de5c nip 000000003159de5c lr 000000003159de48 code 30001
Mar 8 16:40:09 kernel: [ 43.754753] wget[1362]: unhandled signal 4 at 00000000369fde5c nip 00000000369fde5c lr 00000000369fde48 code 30001
Mar 8 16:40:16 main-menu[209]: (process:1340): expr: warning: '^.*\[[:a-fA-F0-9]*\]': using '^' as the first character
Mar 8 16:40:16 main-menu[209]: (process:1340): of a basic regular expression is not portable; it is ignored
Mar 8 16:40:16 main-menu[209]: (process:1340): Illegal instruction
Mar 8 16:40:16 main-menu[209]: (process:1340): Illegal instruction
Mar 8 16:40:16 main-menu[209]: WARNING **: Configuring 'network-preseed' failed with error code 1
Mar 8 16:40:16 main-menu[209]: WARNING **: Menu item 'network-preseed' failed.
Mar 8 16:40:20 main-menu[209]: INFO: Modifying debconf priority limit from 'high' to 'medium'
Mar 8 16:40:20 debconf: Setting debconf/priority to medium
Mar 8 16:40:20 main-menu[209]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored)
Mar 8 16:40:28 main-menu[209]: INFO: Menu item 'di-utils-shell' selected
Mar 8 16:41:56 main-menu[209]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored)
Mar 8 16:42:08 main-menu[209]: INFO: Menu item 'save-logs' selected

== Comment: #9 - INDIRA P. JOGA <email address hidden> - ==
Hi,

I am able to recreate the issue on 2 different host machines with 2 different networks

Raykvm - Travis3En network on host
Yupkvm - Austin network on host.

Tried installing ubunu16.04 using netboot on both kvm hosts and it failed with same error 'Illegal Instruction"

Regards,
Indira

== Comment: #10 - Richard M. Scheller <email address hidden> - ==
I was able to get to a shell in the installer so that I could look for broken binaries that might cause a SIGILL. I found that /usr/bin/wget is incorrectly linked as a shared object instead of an executable.

I verified from the installer command line that "wget" does, in fact, die with SIGILL:

/usr/bin # ./wget
Illegal instruction
/usr/bin #

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1555264/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Tim Gardner (timg-tpi)]

This does not appear to be a kernel problem.

[Adam Conrad (adconrad)]

What are the specs of the VM and the underlying hardware where you're seeing this issue?

[bugproxy (bugproxy)]

Default Comment by Bridge

[Adam Conrad (adconrad)]

From Comment #9, one can see that the guest in question is POWER7. 16.04 and up only support POWER8 (and up), as requested by IBM, so the SIGILL on P7 is entirely expected.

[Breno Leitão (breno-leitao)]

That is correct. Ubuntu 16.04 is NOT supported in POWER7 machines.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-03-11 15:11 EDT-------
1) The system is NOT a Power 7 box. Not sure how you deduced that.

2) THe PCI passthrough adapter was NOT the one being used during the netboot.

So, this is back to Open and Severed

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-03-11 15:19 EDT-------
From Guest XML, Power7 was specified, so that IS wrong!
So it is invalid!

<cpu mode='host-model'>
<model fallback='allow'>power7</model>
<topology sockets='2' cores='2' threads='1'/>
</cpu>

------- Comment From <email address hidden> 2016-03-11 15:29 EDT-------
Right, the hardware info log shows:

/proc/cpuinfo: cpu : POWER7 (architected), altivec supported

[bugproxy (bugproxy)]

Default Comment by Bridge