On 06/17/2014 08:47 AM, Peter Teoh via smartos-discuss wrote: > Not sure where is "qemu-kvm", but after downloading qemu from git:// > git.qemu.org/qemu.git, and after building it, the "qemu-system-x86_64" is > used to bootup smartos-latest.iso (as downloaded from SmartOS site):
In Ubuntu, I would simply install the qemu-kvm package in Ubuntu. In the past these packages had something called qemu-kvm, but qemu-system-x86_64 should be similar assuming your qemu is built with kvm support and the kernel module exists. > qemu-img create qemu_smartos.img 3500M > qemu-system-x86_64 -m 512M -boot d -cdrom smartos-latest.iso -hda > qemu_smartos.img > > And after booting, I used mdb to get the crashdump, and analyse the > registers etc: > > https://drive.google.com/file/d/0B1hg6_FvnEa8LUNvYl9aYmF3VjA/edit?usp=sharing > https://drive.google.com/file/d/0B1hg6_FvnEa8MEdMT3M1dU1xWTQ/edit?usp=sharing > https://drive.google.com/file/d/0B1hg6_FvnEa8NlpUZEgtYTFVMzg/edit?usp=sharing > https://drive.google.com/file/d/0B1hg6_FvnEa8UERUOWg3RVlEcFk/edit?usp=sharing In general, I would probably stick with 1 Gb of memory as a minimum. That might be the problem, but it may not, because I was able to successfully launch a 512 Mb VM at my end, despite 200Mb of that being used by the live image. Unfortunately your vga device has lost all the relevant information I also would disable the vga device and instead use a serial device, so you can actually get the backlog. In this case knowing what the panic message was will help us out a lot with making forward progress and knowing where to look, since unfortunately, I'm not able to reproduce it at this moment. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
