public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Aurélien <amlabs@free.fr>
To: edk2-devel@lists.01.org
Subject: bootloader only see first disk
Date: Sat, 15 Sep 2018 18:36:19 +0200	[thread overview]
Message-ID: <0784c256-7009-94d4-ce3a-c020e0317e43@free.fr> (raw)

Hi,

I don't know if it is the right place to report a bug, sorry if not.

I'm a Promox user and the last version (5.2) has a package versionned
20180612-1 actually  (
https://git.proxmox.com/?p=pve-edk2-firmware.git;a=summary ) which is
based on 5a56c0493955cf55e7eef96dbba815cfbb067d7d  commit of edk2. A
build from the current master a few days ago has the same problem.
The previous Promox version (5.1 whith this pve-qemu-kvm package) use a
edk2 version dating from 2017 or before (it could be from before
September 2016 but I'm not sure), which has no problem. I tested on my
workstation running gentoo which has a version based on UDK2017 branch
with source code from February 11, 2018 and it's working too.
So I think the problem is located in  the OVMF_CODE.fd code from 2018
(but without any certainty).


Actual behaviour (with all the various Linux distribution: Debian 9,
Ubuntu 18.04, Centos 7.5 ...) with a VM which has EFI enabled:
- grub is loaded and only see the first disk (where it is installed),
the "ls" command in the grub shell return: "(hd0) (hd0,gpt1) (cd0)"  
and  there is also hd1 and hd2 and in my case this is problematic as
/boot is on hd1.
- when pressing "escape" on the boot to go the the setup screen and just
chose "continue" it's ok (grub sees all the disks), my current
workaround to boot the installed OS.
- when installing an OS like Ubuntu, CentOS ... on the first reboot it's
ok (I thinks something in the installation, like seting a new boot entry
with grub-install, efibootmgr)

Expected behaviour:
- grub see all the disk (the ls command return hd0, hd1 hd2 ....) and
not the first one (where the EFI boot partition is located).
(sorry, I haven't tried any other boot loader)

- Step to reproduce:
 start a VM with 3 disks and EFI enabled (OVMF_CODE), install a Linux on
the 2nd disk (/ & swap) and the EFI boot partition on the first disk
(/boot/efi on "sda1"), cold start the VM.

I can help by testing with specific version (or another boot loader),
tell me.

Regards

Aurélien

ps: typical command line to start the VM:
/usr/bin/kvm \
  -id 20 \
  -name testvm.mydomain \
  -chardev 'socket,id=qmp,path=/var/run/qemu-server/20.qmp,server,nowait' \
  -mon 'chardev=qmp,mode=control' \
  -pidfile /var/run/qemu-server/20.pid \
  -daemonize \
  -smbios 'type=1,uuid=88dc4e6b-34b8-46a7-a573-26596c34855d' \
  -drive
'if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd'
\
  -drive
'if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/mnt/pve/pve-nfs-sas/images/20/vm-20-disk-4.raw'
\
  -smp '8,sockets=1,cores=8,maxcpus=8' \
  -nodefaults \
  -boot
'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg'
\
  -vga qxl \
  -vnc unix:/var/run/qemu-server/20.vnc,x509,password \
  -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi \
  -m 512 \
  -object 'memory-backend-ram,id=ram-node0,size=512M' \
  -numa 'node,nodeid=0,cpus=0-7,memdev=ram-node0' \
  -k fr \
  -object 'iothread,id=iothread-virtioscsi1' \
  -object 'iothread,id=iothread-virtioscsi2' \
  -machine 'type=pc-i440fx-2.9' \
  -device 'pci-bridge,id=pci.3,chassis_nr=3,bus=pci.0,addr=0x5' \
  -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' \
  -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' \
  -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' \
  -chardev 'socket,path=/var/run/qemu-server/20.qga,server,nowait,id=qga0' \
  -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' \
  -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' \
  -spice
'tls-port=61004,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' \
  -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' \
  -chardev 'spicevmc,id=vdagent,name=vdagent' \
  -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' \
  -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' \
  -iscsi 'initiator-name=iqn.1993-08.org.debian:01:f9e4631950da' \
  -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' \
  -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100' \
  -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1' \
  -drive
'file=/mnt/pve/pve-nfs-sas/images/20/vm-20-disk-1.raw,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on'
\
  -device
'scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=200'
\
  -device
'virtio-scsi-pci,id=virtioscsi1,bus=pci.3,addr=0x2,iothread=iothread-virtioscsi1'
\
  -drive
'file=/mnt/pve/pve-nfs-sas/images/20/vm-20-disk-2.raw,if=none,id=drive-scsi1,format=raw,cache=none,aio=native,detect-zeroes=on'
\
  -device
'scsi-hd,bus=virtioscsi1.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1'
\
  -device
'virtio-scsi-pci,id=virtioscsi2,bus=pci.3,addr=0x3,iothread=iothread-virtioscsi2'
\
  -drive
'file=/mnt/pve/pve-nfs-sas/images/20/vm-20-disk-3.raw,if=none,id=drive-scsi2,format=raw,cache=none,aio=native,detect-zeroes=on'
\
  -device
'scsi-hd,bus=virtioscsi2.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi2,id=scsi2'
\
  -netdev
'type=tap,id=net0,ifname=tap20i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'
\
  -device
'virtio-net-pci,mac=4A:63:6D:11:11:11,netdev=net0,bus=pci.0,addr=0x12,id=net0'





             reply	other threads:[~2018-09-15 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15 16:36 Aurélien [this message]
2018-09-16 10:04 ` bootloader only see first disk Laszlo Ersek
2018-09-17  8:34   ` Thomas Lamprecht
2018-09-17 10:44     ` Aurelien Minet
2018-09-17 10:28   ` Aurelien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0784c256-7009-94d4-ce3a-c020e0317e43@free.fr \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox