yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #25390
[Bug 1400784] [NEW] Cold migration fails when using vnic_type=direct
Public bug reported:
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/pci/devices/0000:05:11.5/config: No such file or directory"
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-nova-common-2014.2-2.el7ost.noarch
openstack-nova-compute-2014.2-2.el7ost.noarch
python-nova-2014.2-2.el7ost.noarch
** 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/1400784
Title:
Cold migration fails when using vnic_type=direct
Status in OpenStack Compute (Nova):
New
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/pci/devices/0000:05:11.5/config: No such file or directory"
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-nova-common-2014.2-2.el7ost.noarch
openstack-nova-compute-2014.2-2.el7ost.noarch
python-nova-2014.2-2.el7ost.noarch
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1400784/+subscriptions
Follow ups
References