My guess is that vmbuilder is writing 'hwcap 0 nosegneg' is written by vmbuilder because of bug 246625 and other similar/duplicate bugs there. However, as far as I can tell there is no affect of writing that file other than that it breaks the upgrade as I reported here.
Ie: $ sudo rm /etc/ld.so.conf.d/libc6-xen.conf $ sudo /sbin/ldconfig $ sudo reboot ... $ sudo do-release-upgrade -d The reboot are just to show a generally functional system after removal of that file (also shown by the ablility to do-release-upgrade). The do-release-upgrade finished successfully. A reboot of the system is a bad idea, though on ec2 as the old kernel simply isn't going to work for upstart/mountall/udev of lucid. -- hardy2lucid: hwcap index 0 already defined https://bugs.launchpad.net/bugs/562787 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
