ami-852718ec fails to come up with c3 and i2 instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on EC2 |
Won't Fix
|
High
|
Robert C Jennings |
Bug Description
ami-852718ec fails to come up with c3 and i2 instances with the console output below.
AWS support thinks this is happening because c3 and i2 instances want to run with SRIOV networking enabled
(possibly because ami-852718e had image-attribute sriov set to 'simple'?), but ixgbevf-2.11.3 drivers are not installed in the ami.
-------
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/
[ 2.112634] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/
done.
Begin: Running /scripts/
[ 11.425236] EXT4-fs (sda1): re-mounted. Opts: (null)
[ 12.922186] kjournald starting. Commit interval 5 seconds
[ 12.929710] EXT3-fs (xvdb): using internal journal
[ 12.932988] EXT3-fs (xvdb): mounted filesystem with ordered data mode
cloud-init start-local running: Tue, 28 Jan 2014 17:55:22 +0000. up 22.99 seconds
no instance data found in start-local
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
ci-info: lo : 1 127.0.0.1 255.0.0.0 .
ci-info: eth0 : 1 . . 12:c1:85:bb:da:87
route_info failed
-------
Changed in ubuntu-on-ec2: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Robert C Jennings (rcj) |
Changed in ubuntu-on-ec2: | |
status: | Confirmed → In Progress |
Eugene, thank you for the bug report.
I have recreated and am attaching console log. This is from ubuntu- precise- 12.04-amd64- server- 20131003 (ami-b93264d0). This ami boots without the sr-iov attribute which allows me to make changes prior to adding the 'simple' sriov attribute and recreating the problem you are seeing. Removal of the xen_emul_unplug kernel cmdline option and addition of the xen-platform-pci kernel module to the initramfs does not provide relief, therefore I do not believe tha this is related to bug #1268012.