Cold migration fails when using vnic_type=direct
Bug #1400784 reported by
Itzik Brown
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Medium
|
Charlotte Han |
Bug Description
When launching an instance with port with vnic_type direct and using nova migrate I get an error:
"Device 0000:05:11.5 not found: could not access /sys/bus/
How to Reproduce
===============
#neutron port-create tenant1-net1 --binding:vnic-type direct
#nova boot --flavor m1.small --image rhel7 --nic port-id=<port-id> vm1
#nova migrate <vm-id>
After a white run nova show <vm-id> and the error should be in the 'fault' entry.
Version
=======
RHEL7.0
openstack-
openstack-
python-
Changed in nova: | |
assignee: | nobody → Deliang Fan (vanderliang) |
Changed in nova: | |
status: | New → Confirmed |
tags: | added: network |
Changed in nova: | |
importance: | Undecided → Medium |
tags: |
added: pci-passthrough removed: network |
Changed in nova: | |
assignee: | Deliang Fan (vanderliang) → nobody |
Changed in nova: | |
assignee: | nobody → Yongli He (yongli-he) |
tags: |
added: pci removed: pci-passthrough |
Changed in nova: | |
assignee: | Yongli He (yongli-he) → nobody |
Changed in nova: | |
assignee: | nobody → Charlotte Han (hanrong) |
Changed in nova: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
this issue is related to the resize bug (https:/ /bugs.launchpad .net/nova/ +bug/1368201)
which may fix it.
if that is the case I will duplicate it to resize bug, for now it can be on hold.