← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1300861] [NEW] libvirt error when adding the os_command_line on non ami images

 

Public bug reported:

qemu fails when booting an instance with the os_command_line on non ami
images

----------------------------------------------------------------------------

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1066, in _build_instance
    set_access_ip=set_access_ip)
  File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 360, in decorated_function
    return function(self, context, *args, **kwargs)
  File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1476, in _spawn
    LOG.exception(_('Instance failed to spawn'), instance=instance)
  File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__
    six.reraise(self.type_, self.value, self.tb)
  File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1473, in _spawn
    block_device_info)
  File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2237, in spawn
    block_device_info)
  File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3572, in _create_domain_and_network
    domain = self._create_domain(xml, instance=instance, power_on=power_on)
  File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3513, in _create_domain
    domain.XMLDesc(0))
  File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__
    six.reraise(self.type_, self.value, self.tb)
  File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3508, in _create_domain
    domain.createWithFlags(launch_flags)
  File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 187, in doit
    result = proxy_call(self._autowrap, f, *args, **kwargs)
  File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 147, in proxy_call
    rv = execute(f,*args,**kwargs)
  File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 76, in tworker
    rv = meth(*args,**kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 708, in createWithFlags
    if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/5
-append only allowed with -kernel option

----------------------------------------------------------------------------

Is this the correct behaviour or should the instance be booted with a
log warning that the os_command_line isn't considered since it only
applies to ami images in qemu?

The easiest and least painful solution I could think of is to move the
code in the kernel_id check, but I don't know how that would affect
other hypervisors. Any comments by people with greater experience with
the other hypervisors are more than welcome.

** 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/1300861

Title:
  libvirt error when adding the os_command_line on non ami images

Status in OpenStack Compute (Nova):
  New

Bug description:
  qemu fails when booting an instance with the os_command_line on non
  ami images

  ----------------------------------------------------------------------------

  Traceback (most recent call last):
    File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1066, in _build_instance
      set_access_ip=set_access_ip)
    File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 360, in decorated_function
      return function(self, context, *args, **kwargs)
    File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1476, in _spawn
      LOG.exception(_('Instance failed to spawn'), instance=instance)
    File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__
      six.reraise(self.type_, self.value, self.tb)
    File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1473, in _spawn
      block_device_info)
    File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2237, in spawn
      block_device_info)
    File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3572, in _create_domain_and_network
      domain = self._create_domain(xml, instance=instance, power_on=power_on)
    File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3513, in _create_domain
      domain.XMLDesc(0))
    File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__
      six.reraise(self.type_, self.value, self.tb)
    File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3508, in _create_domain
      domain.createWithFlags(launch_flags)
    File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 187, in doit
      result = proxy_call(self._autowrap, f, *args, **kwargs)
    File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 147, in proxy_call
      rv = execute(f,*args,**kwargs)
    File "/usr/lib/python2.6/site-packages/eventlet/tpool.py", line 76, in tworker
      rv = meth(*args,**kwargs)
    File "/usr/lib64/python2.6/site-packages/libvirt.py", line 708, in createWithFlags
      if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
  libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/5
  -append only allowed with -kernel option

  ----------------------------------------------------------------------------

  Is this the correct behaviour or should the instance be booted with a
  log warning that the os_command_line isn't considered since it only
  applies to ami images in qemu?

  The easiest and least painful solution I could think of is to move the
  code in the kernel_id check, but I don't know how that would affect
  other hypervisors. Any comments by people with greater experience with
  the other hypervisors are more than welcome.

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


Follow ups

References