Alright, seems like it was trying to use the full graphics boot by default and not working (possibly because it did not like my VMware Virtual Graphics Controller. Did we already introduce UI to meego, so we have a desktop?
I stepped into the boot menu and then removed all quiet options from the kernel command options and it booted to a prompt fine enough. If we have introduced desktop/UI, how do I use it in a VM (qemu/vmware are both fine with me)? Thanks, Adhyas -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Avasthi Adhyas (Nokia-NRC/PaloAlto) Sent: Thursday, May 13, 2010 6:47 PM To: [email protected] Subject: [MeeGo-dev] Issues with booting meego image on qemu/Vmware I am following instructions on the Image Creation wiki to create my own raw or vmdk image and boot it in qemu or vmware. I have fresh Fedora Core 12 in a VM (installed today) with all the required packages installed today as well. I pulled in the .ks file for netbook atom image and modified the Base and Core to Meego Base and Meego Core When I invoke mic-image-creator, it gets all the packages and builds the images. At the very end, it throws this error: 0+1 records in 0+1 records out 440 bytes (440 B) copied, 0.00308378 s, 143 kB/s /var/tmp/imgcreate-6AQArO/install_root/boot/extlinux is device /dev/mapper/loop0p1 Running scripts Finished Your new image can be found here: /home/adhyas/meego/meego-0.90-meego-preview-netbook-core-201005131818-vmdk/meego-0.90-meego-preview-netbook-core-201005131818-sda.vmdk /home/adhyas/meego/meego-0.90-meego-preview-netbook-core-201005131818-vmdk/meego-0.90-meego-preview-netbook-core-201005131818-sda.vmx Finished. close failed in file object destructor: Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/abrt_exception_handler.py", line 243, in <lambda> handleMyException((etype, value, tb)) TypeError: 'NoneType' object is not callable Original exception was: IOError: [Errno 9] Bad file descriptor I upgraded my Python but this issue is not going away. Just the most recent trace source changed in the error. The images are built, however. But when I try to boot using those images, meego does not come up. The screen (virtual) turns light gray and stays like that forever. If I build a livecd image, that does boot fine in vmware VM that I create for it (although if I choose to install, that does not work either). I would like to do either of two things: -> Be able to install meego (what format should I use if I want to do this?) -> Be able to boot meego in a VM using raw/vmdk/other virtual disk formats Any ideas what might be going wrong? Has anyone else seen this issue? Thanks, Adhyas _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
