Failed to install guest OS with ubuntu-19.04-server-amd64.iso(daily build 2.25) in ESXi with AMD CPU.

Bug #1818188 reported by vmware-gos-Yuhua
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Fix Released
Undecided
Unassigned
install-package (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Failed to install guestOS with ubuntu-19.04-server-amd64.iso(daily build 2.25) in ESXi with AMD CPU. We get continuous flash in the the process “Select a language” of early install stage.

Please check the attached screenshot picture.
No this issue in ESXi with intel CPU.

The comment from dev Nick Shi in VMware:
  Native install on AMD physical machine (HP DL385) did not allow to open the screen either
You can get more detail on vmware bugzilla:
  https://bugzilla.eng.vmware.com/show_bug.cgi?id=2297183

So hit the issue not only in ESXi with AMD CPU but also physical machine with AMD CPU.

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in install-package (Ubuntu):
status: New → Confirmed
Revision history for this message
Joshua Powers (powersj) wrote :

Hi! Could you please provide more information as the vmware bugzilla is not accessible.

What generation of HP machine was used? G7/Gen8/Gen9/Gen10? Is it running the latest iLO and RBSU (BIOS) firmwares?

You are using the alternative ISO to do an install. That installer will only be available for a couple more releases and as such is not suggested for use going forward.

Does an install work with the primary, subiquity-based, server ISO?
http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/disco-live-server-amd64.iso

Can you try with the latest daily ISO?
http://cdimage.ubuntu.com/ubuntu-server/daily/current/disco-server-amd64.iso

When it fails can you change the console (e.g. Ctrl-Alt-F2) and see if any error messages are present?

Changed in install-package (Ubuntu):
status: Confirmed → Incomplete
Changed in debian-installer (Ubuntu):
status: New → Incomplete
Changed in install-package (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Joshua Powers (powersj) wrote :

Marking this as a debian-installer bug and as incomplete pending an update. Also marking the install-package task as invalid.

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

> Could you please provide more information as the vmware bugzilla is not accessible.

  Sorry for the link is not accessible. This link seems like have no more detail information.

> What generation of HP machine was used? G7/Gen8/Gen9/Gen10? Is it running the latest iLO and
  RBSU (BIOS) firmwares?

  Will give feedback later.

> Does an install work with the primary, subiquity-based, server ISO?
  http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/disco-live-server-amd64.iso

  I have tried with this ISO. No such issue with disco-live-server-amd64.iso and disco-desktop-amd64.iso. Hit this issue only with disco-server-amd64.iso

> Can you try with the latest daily ISO?
  http://cdimage.ubuntu.com/ubuntu-server/daily/current/disco-server-amd64.iso

  I try with latest build 5-Mar-2019. It still hit this issue

> When it fails can you change the console (e.g. Ctrl-Alt-F2)
  and see if any error messages are present?

  Command “Ctrl-Alt-F2” doesn’t work well.
  Referring to https://help.ubuntu.com/community/BootOptions , i still get the first graphic sparkling windows with tile “Select a language“ after add boot parameter "text"

Changed in install-package (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Joshua Powers (powersj) wrote :

Thanks for the quick response. Please do get back to us about the generation and firmware information.

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

> What generation of HP machine was used? G7/Gen8/Gen9/Gen10? Is it running the latest iLO and
  RBSU (BIOS) firmwares?

  1. physical machine:

     Product Name
     ProLiant DL385p Gen8

     System ROM
     A28 03/14/2018

     System ROM Date
     03/14/2018

     iLO Firmware Version
     2.61 Jul 27 2018

  2. The steps to reproduce this issue in ESXi.
     Steps:
     1). Create VM with BIOS / EFI
     2). mount iso ubuntu-19.04-server-amd64.iso(daily build 5-Mar-2019)
     3). Power on VM, The iso is recognized and it will start to install guestOS
     4). We get a continuous flash in the the process “Select a language”

     This issue can be reproduced with both BIOS and EFI

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

still hit the issue with ubuntu-19.04-server-amd64.iso daily build 19-Mar-2019

Changed in debian-installer (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

This is urgent issue. Is any developer working on this ? Thanks

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

Hit the issue with disco-server-amd64.iso (daily build 2019-3-31) downloaded from http://cdimage.ubuntu.com/ubuntu-server/daily/current/

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

hit this issue ubuntu-19.04-server-amd64.iso (GA)

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :
Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :
Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :
Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :
Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

Try to install guestOS with ubuntu-19.04-server-amd64.iso in ESXi for more times.

Env:
   ESXi
     Manufacturer : HP
     Model: ProLiant DL385p Gen8
     CPU: 24 CPUs x AMD Opteron(TM) Processor 6238

   Image: install GuestOS with image ubuntu-19.04-server-amd64.iso (GA)

1.
with the following VM settings, we get continuous flash in the the installing stage “choose language”
      1) default setting: vcpu 1 , memory 1G, video buffer 4M
      2) vcpu 1 , memory 2G, video buffer 8M
      3) vcpu 1 , memory 4G, video buffer 16M

steps:
     1) create a new VM in ESXi with the the above setting and other default setting for VM
     2) mount ubuntu-19.04-server-amd64.iso to CD/DVD
     3) power VM
     4) choose the default option “Install Ubuntu Server” and press “Enter” key (check attach screenshot install_ubuntu.png), it starts to install
     5) we get continuous flash in the the stage “choose language”
        (check attach screenshot flash.png)

2.
with the following VM setting, it pop up the windows “Ubuntu installer main menu” during the stage “choose language” and stage “Configure the clock”
But we can skip the failed stages to continue to finish the installation

   1) vcpu 2, memory 1G, video buffer 4M
   2) vcpu 2, memory 4G, video buffer 16M
   3) vcpu 4, memory 4G, video buffer 16M

steps:
     1) create a new VM in ESXi with the the upper setting and other default setting for VM
     2) mount ubuntu-19.04-server-amd64.iso to CD/DVD
     3) power VM
     4) choose the default option “Install Ubuntu Server” and press “Enter” key (check attach screenshot install_ubuntu.png), it starts to install
     5) It can’t stay in the phase “choose language” for the users to set language but popup the windows “Ubuntu installer main menu”. we can choose the next stage “Access software for ….” and continue to install
      (please check the attached screenshot fail_to_set_language.png)

     6) During the installing process, it failed for the stage “Configure the clock” but but popup the windows “Ubuntu installer main menu”again. we can choose the next stage “Detects disks” to continue to install
       (please check the attached screenshot fail_to_set_clock.png)

     7) finish the installation and reboot, the system can boot up.

For the above tries, with vcpu > 1, we can skip the failed stages and finish the installation.
But It still be a issue for why the installing stages “choose language” and“Configure the clock” are failed.

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

No such issue in ubuntu 19.10 server daily build Aug/28/2019

Revision history for this message
Joshua Powers (powersj) wrote :

If this is fixed in the development release (eoan), can you retest with the latest installer from disco? Please update the installer if prompted. You should have version 19.07.3 available to you now.

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

> If this is fixed in the development release (eoan), can you retest with the latest installer from > disco? Please update the installer if prompted. You should have version 19.07.3 available to you > now.

Hi Joshua,
As I remember, ubuntu-19.04-server-amd64.iso use the traditional installer not the new installer "subiquity".

Please check
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1826158#7

Thanks
Yuhua Zou

Revision history for this message
Joshua Powers (powersj) wrote :

My apologies I got my bugs mixed up. Yes, this is the normal installer, not subiquity. Again without having access to the hardware or additional logs this is going to be difficult to triage.

I see above that you tried a variety of hardware configurations in the VM and found that increasing the number of vCPUs can ensure the success of the install?

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

   > increasing the number of vCPUs can ensure the success of the install?

Yes, increasing the number of vCPUs is the workaround.
we have a kb for it:https://kb.vmware.com/s/article/70904

Thanks
Yuhua Zou

Revision history for this message
vmware-gos-Yuhua (yhzou) wrote :

As #17 say:
1) I hit this issue in ubuntu 19.04 with traditional installer but not the new installer "subiquity".
2) I did not hit such issue in ubuntu 19.10 server daily build Aug/28/2019

Beside, It doesn't hit this issue with new installer "subiquity".

So close this issue.

Changed in debian-installer (Ubuntu):
status: Confirmed → Fix Released
Changed in install-package (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.