kernel-packages team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

On 4 February 2014 09:46, Dimitri John Ledkov <launchpad@xxxxxxxxxxxx> wrote:
> On 30 January 2014 22:57, Jamie Strandboge <jamie@xxxxxxxxxx> wrote:
>> apport information
>>
>> ** Tags added: apport-collected saucy
>>
>> ** Description changed:
>>
>>   On up to date 14.04, if I create a vm with:
>>   virt-install --connect=qemu:///system --name=sb-saucy-amd64 --arch=x86_64 --ram=768 \
>>   --disk=path=<path to>/sb-saucy-amd64.qcow2,size=8,format=qcow2,bus=ide,sparse=True \
>>   --virt-type=kvm --accelerate --hvm --cdrom=<path to>/saucy-desktop-amd64.iso \
>>   --os-type=linux --os-variant=generic26 --graphics=vnc --network=network=default,model=virtio \
>>   --video=cirrus --noreboot --boot=loader=OVMF.fd
>>
>
> I believe --boot=loader=OVMF.fd is not correct option. A valid one is
> --boot-loader=OVMF.fd.

Bah, checked my old scripts and manual, the
--boot=loader=path/to/ovmf.fd is correct syntax.

> Nonetheless, that wouldn't be ideal way to execute OVMF.fd. It's
> better to make a copy of OVMF.fd and provision the copy to qemu as a
> -pflash copy-of-OVMF.fd in Read-Write mode, cause then one can store
> all variables & secureboot keys which survive a reboot. Does
> virt-install support provisioning "-pflash" devices?

-- 
Regards,

Dimitri.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1274376

Title:
  14.04 ovmf causes oops when running update-grub under kvm

Status in “edk2” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  On up to date 14.04, if I create a vm with:
  virt-install --connect=qemu:///system --name=sb-saucy-amd64 --arch=x86_64 --ram=768 \
  --disk=path=<path to>/sb-saucy-amd64.qcow2,size=8,format=qcow2,bus=ide,sparse=True \
  --virt-type=kvm --accelerate --hvm --cdrom=<path to>/saucy-desktop-amd64.iso \
  --os-type=linux --os-variant=generic26 --graphics=vnc --network=network=default,model=virtio \
  --video=cirrus --noreboot --boot=loader=OVMF.fd

  I get to the EFI boot menu. Choose Install Ubuntu, then automatic
  partitioning, with everything else defaults. By the time it gets to
  'Running update-grub', the installer kernel oops with the attached
  screenshot (to get it, go to tty1 when grub starts installing, then it
  will eventually oops when update-grub is run).

  If I downgrade to ovmf that is in 13.10, the install completes without a traceback. Obviously, the kernel should not traceback, but clearly there is a problem with edk2 too, so I am filing the bug there. Please reassign as necessary.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=5c808fe7-5d32-4495-9356-68f006fa5726
  InstallationDate: Installed on 2014-01-30 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131011)
  IwConfig:
   eth0      no wireless extensions.
   
   lo        no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=23bf8ad7-6ea2-4551-aac2-051639a48858 ro quiet splash vt.handoff=7
  ProcVersionSignature: User Name 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware                             1.116
  RfKill:
   
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1274376/+subscriptions