[daily jammy-live-server-amd64] Hangs at start of VM installation

Bug #1950914 reported by Doug Smythies
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
linux (Ubuntu)

Bug Description

I downloaded the 2021.11.14 daily:

-rw-rwxr--+ 1 doug doug 1277655040 Nov 14 09:12 jammy-live-server-amd64.iso

I tried to install it as a VM on a debian 11 server host and an Ubuntu 20.04.3 server host, both were up to date as of a few days ago. Command used (pretty much the same command I have used for years):

virt-install -n serv-jj -r 8192 \
--disk path=/home/doug/vm/serv-jj.img,bus=virtio,size=50 \
-c jammy-live-server-amd64-2021-11-14.iso \
--network bridge=br0,model=virtio,mac=52:54:00:27:1c:6e \
--video=vmvga --graphics vnc,listen= --noautoconsole -v --vcpus=4

On both hosts it just hangs a after a couple of seconds. "virsh list" shows it running and "virsh destroy" does work.

Note: I have never used the new installer before, I have always used the legacy Debain installer in the past, but I gather is is no longer supported.

Tags: iso-testing
summary: - [daily jammy-live-server-amd64] Hangs at start if VM installation
+ [daily jammy-live-server-amd64] Hangs at start of VM installation
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Revision history for this message
Doug Smythies (dsmythies) wrote :
Revision history for this message
Doug Smythies (dsmythies) wrote :

This issue still occurs on both host servers, Debian 11 and Ubuntu 20.04.4.

The only difference being that I am now using the release ISO.

Revision history for this message
Dan Bungert (dbungert) wrote :

I can reproduce this as written using Focal as the host and the 22.04 live-server iso.
If I remove the "--video=vmvga" it actually boots, and an install completed without issue.
This doesn't seem Subiquity specific, however.

Changed in subiquity:
status: New → Invalid
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1950914

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Dan Bungert (dbungert) wrote :

I will be happy to provide logs, however as the system fails boot ~1s in I'm not sure how to do so. Marking Confirmed to override.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Doug Smythies (dsmythies) wrote :

O.K. thank you for your input. I confirm deletion of "--video=vmvga" allows things to continue.

Historically, that was needed in and since 2013, when the default video "cirrus" did not work. I now observe the default video is "qxl" which seems to work.

Ya, apport logs are not needed for this bug.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libvirt (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers