yahoo-eng-team team mailing list archive

[Ripal Nathuji <ripal.nathuji@xxxxxxxxxxx>]

Public bug reported:

If you configure nova to run on Calxeda ARM with libvirt/KVM, the
generated libvirt configuration passes console as:

<os>
    …
    <cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>
</os>

For ARM guests the libvirt configuration should use 'console=ttyAMA0',
hence as it stands you lose serial output for the guest. Currently the
console settings are hard coded in nova/virt/libvirt/driver.py . I think
we should modify that to be operator configurable via an option in
nova.conf. I can submit a change accordingly, but would like feedback on
if this sounds reasonable.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1259323

Title:
  Libvirt console parameter incorrect for ARM KVM

Status in OpenStack Compute (Nova):
  New

Bug description:
  If you configure nova to run on Calxeda ARM with libvirt/KVM, the
  generated libvirt configuration passes console as:

  <os>
      …
      <cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>
  </os>

  For ARM guests the libvirt configuration should use 'console=ttyAMA0',
  hence as it stands you lose serial output for the guest. Currently the
  console settings are hard coded in nova/virt/libvirt/driver.py . I
  think we should modify that to be operator configurable via an option
  in nova.conf. I can submit a change accordingly, but would like
  feedback on if this sounds reasonable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1259323/+subscriptions