>> Thanks for your response. I have actually built a RAW image (I put the wrong command line into my original email) My attempts >> to run the RAW image have not fully worked. I run the command below: >> #> sudo qemu-kvm -m 512 -boot c -hda meego-0.90-meego-preview-netbook-core-201005041355-sda.raw
No probs. I think RAW is much more versatile. >> I see some boot information, and a grey QEMU window which very briefly flashes 'Starting Meego....' , but no Meego command >> line. Is this similar to your experience? >> Also some output in the terminal, as follows >> open /dev/kvm: No such file or directory >> Could not initialize KVM, will disable KVM support I think the output on the terminal is okay. It just says that QEMU is not running in KVM mode and would use SW only virtualization. I also get the same error message but that is because I am running Ubuntu in VBox. I haven't enabled any virtualization features in Vbox. I got to the starting MeeGo screen and then am stuck at the boot: prompt. I try to put in various values but nothing happens. I guess either the mic2 is broken or there is something wrong in the .ks file. I changed the keyboard type, timezone and --timeout arguments. I also removed the --append="quiet". The compilation and everything worked out pretty fine. I got some errors regarding closing file handles after running mic2. I guess that is because of some invalid (already deleted temporary files) handles. But I assume the image creation worked fine. > > > After some digging I found that I have the right modules installed, but > dmesg shows that kvm is disabled by the bios. My bios settings have no > options to allow me to change it. Not sure if my processor can support it? > or perhaps I need to update my bios so I might be able to change the > setting? Still searching around the subject. > > Perhaps I should try Meego vmware image instead > > Paul > > Do keep updating on if it worked with the VMDK image instead. I guess it will be the same problem since I suspect the image creation is messing up somehow (.ks is a definite suspect). BTW, I used 0.17 tag for my mic2 compilation. 0.9 was giving a lot of compile errors as well as errors wrt yum version (it wanted .24 whereas the latest is .23). I tried the USB image instead. Am able boot but am stuck at ACPI startup. BR; Naresh
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
