This bug affects JeOS too. Should I report it as a seperate bug against JeOS ?
I used the ISO with MD5(ubuntu-7.10-jeos-i386.iso)= 341ca65a187c71643079a2f9ee5523b5 to create an image from it.
I created the image like this : qemu-img create -f qcow jeos.img 10G qemu -m 512 -cdrom ubuntu-7.10-jeos-i386.iso -boot d jeos.img -no-acpi -std-vga I needed this workaround to create the QEMU image : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316/comments/7
This bug affects JeOS too. Should I report it as a seperate bug against JeOS ?
I used the ISO with MD5(ubuntu- 7.10-jeos- i386.iso) = 341ca65a187c716 43079a2f9ee5523 b5 to create an image from it.
I created the image like this : 7.10-jeos- i386.iso -boot d jeos.img -no-acpi -std-vga /bugs.launchpad .net/ubuntu/ +source/ linux-source- 2.6.22/ +bug/120316/ comments/ 7
qemu-img create -f qcow jeos.img 10G
qemu -m 512 -cdrom ubuntu-
I needed this workaround to create the QEMU image : https:/