Public bug reported: Hello! I had hit an problem described and fixed here: https://bugzilla.redhat.com/show_bug.cgi?id=1020622:
When creating VM with more than one drive attached to virtio-scsi bus Seabios can not detect the second drive. Especially it breaks using of config drive with Openstack. System: # lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Package: # apt-cache policy seabios seabios: Installed: 1.10.2-1ubuntu1~cloud0 Candidate: 1.10.2-1ubuntu1~cloud0 Version table: *** 1.10.2-1ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike/main i386 Packages 100 /var/lib/dpkg/status 1.8.2-1ubuntu1 500 500 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial/main i386 Packages Steps to reproduce: 1. Create an instance with more than 1 drive attached to virtio-scsi bus, bootable drive have to be on non-zero numbered LUN. 2. Try to boot instance with one of these drives. Expected result: Boot from bootable drive connected as non-zero LUN. Actual result: "no bootable device" on instance's screen when accessing VNC console, no visible second drive when using Boot Menu. Workaround: copy Seabios binaries from latest RH release over stock binaries. ** Affects: seabios (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734679 Title: Seabios failed to detect virtio-scsi device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1734679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs