On Wednesday 05 May 2010 14:11:04 Paul Leeming wrote: > 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 got the same problem as you when trying to boot a RAW image with QEMU. However, I was able to boot a CD image. > I run the command below: > > #> sudo qemu-kvm -m 512 -boot c -hda > meego-0.90-meego-preview-netbook-core-201005041355-sda.raw I have been doing my QEMU testing on Windows. I use the following command line: qemu.exe -L . -m 512 -hda meego.cow -hdb home.dsk -localtime -net nic,model=rtl8139 -net user -no-acpi (that is to boot the disk image I created after booting the cdrom -- to boot the cdrom I used "-cdrom meego.iso" instead of the -hda and -hdb options). The -no-acpi seems to be important (at least in my case). Note that the "install to disk" option does not work. > 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? That was my experience with the RAW image as well. > open /dev/kvm: No such file or directory > Could not initialize KVM, will disable KVM support As I mentioned, I am currently using Windows for my QEMU testing (because I started it when I was stuck due to an ash cloud and only had my work laptop with me). But from my previous experience with qemu on my Debian system, the kvm support makes a significant difference to the performance of qemu but it shouldn't change the functionality. > Perhaps I should try Meego vmware image instead I suggest trying the CD image as well. Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
