yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-2

-- 
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/1188517

Title:
  Use tap2 instead of tap for Xen disks

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Hi.

  I am running Xen-4.1.3 + Libvirt-1.0.2 on a Grizzly installation and
  the machines are not able to view their disk anymore:

       XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
      XENBUS: Timeout connecting to device: device/vbd/51712 (local state 1, remote state 1)
      XENBUS: Device not ready: device/vbd/51712

  This is because blktap has been substituted by blktap2 [1]  so we
  should use "tap2" for the driver name, instead of "tap". I do not know
  if this is also true with older (i.e. 4.0) versions of Xen, so at
  least it should be configurable.

  I will submit a patch later today.

  [1] http://wiki.xenproject.org/wiki/Blktap2

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