Terminal output is: jerry@ubuntu:~$ qemu-img create x.img 10G Formatting 'x.img', fmt=raw size=10737418240 jerry@ubuntu:~$ kvm -m 512 -cdrom /host/Jerry/.cache/testdrive/iso/khostname_precise-mobile-i386.iso -hda x.img -boot d Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory Back to tcg accelerator. kvm: -cdrom /host/Jerry/.cache/testdrive/iso/khostname_precise-mobile-i386.iso: could not open disk image /host/Jerry/.cache/testdrive/iso/khostname_precise-mobile-i386.iso: No such file or directory jerry@ubuntu:~$ kvm -m 512 -cdrom /host/Jerry/.cache/testdrive/iso/khostname_precise-mobile-i386.iso -hda x.img -boot d lubuntu_precise-desktop-i386.iso xubuntu_precise-desktop-i386.iso jerry@ubuntu:~$ kvm -m 512 -cdrom /host/Jerry/.cache/testdrive/iso/lubuntu_precise-desktop-i386.iso -hda x.img -boot d Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory Back to tcg accelerator. kvm: pci_add_option_rom: failed to find romfile "pxe-rtl8139.rom"
================ seems like before and still no apport so not crashing but maybe running so long or slow I'm not patient enough to tell... It's an EeePC so maybe I'm expecting to much from it... On Wed, Dec 14, 2011 at 9:54 PM, jerry w <[email protected]> wrote: > after I get the Lubuntu filename right, > lots of little windows flash up > (presumably boot stuff > a install and language dropdown type dialog > overlaying it > and lots of CPU usage noticed in gkrellm > .... > and seems like nothing > until I have to kill it > > > On Wed, Dec 14, 2011 at 9:02 AM, jerry w <[email protected]> wrote: >> I'll let you know, hopefully later today, as it's on another machine. >> Not sure where I'll get 10G >> >> I'm guessing it is something else, but until I get it working, >> this may be leverage to get there... ;-/ >> >> >> On Wed, Dec 14, 2011 at 3:43 AM, Serge Hallyn <[email protected]> >> wrote: >>> What happens when you simply run >>> >>> qemu-img create x.img 10G >>> kvm -m 512 -cdrom >>> /host/Jerry/.cache/testdrive/iso/khostname_precise-mobile-i386.iso -hda >>> x.img -boot d >>> >>> ? >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/901401 >>> >>> Title: >>> qemu-system-x86_64 crashed with SIGABRT >>> >>> Status in “qemu-kvm” package in Ubuntu: >>> Incomplete >>> >>> Bug description: >>> testdrive-gtk >>> on Kubuntu Mobile >>> crashed on launch, and I lost the hour long iso download too... >>> >>> not sure why it's using 64 bit on an EeePC, >>> but that is what it seems to be doing... >>> >>> Tried running a Sugar On A Stick >>> (Fedora based with KVM and installed a >>> bunch of virtualization stuff to try to make that work) >>> so maybe package issues too? >>> >>> ProblemType: Crash >>> DistroRelease: Ubuntu 12.04 >>> Package: qemu-kvm 0.15.0+noroms-0ubuntu8 >>> ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 >>> Uname: Linux 3.2.0-3-generic i686 >>> ApportVersion: 1.90-0ubuntu1 >>> Architecture: i386 >>> Date: Wed Dec 7 15:36:24 2011 >>> ExecutablePath: /usr/bin/qemu-system-x86_64 >>> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) >>> KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code >>> 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD >>> MachineType: ASUSTeK Computer INC. 1005HA >>> ProcCmdline: kvm -m 1024 -smp 2 -cdrom >>> /host/Jerry/.cache/testdrive/iso/khostname_precise-mobile-i386.iso -drive >>> file=/host/Jerry/.cache/testdrive/img/testdrive-disk-0EXMAX.img,if=virtio,cache=writeback,index=0,boot=on >>> -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 >>> -vga cirrus >>> ProcEnviron: >>> SHELL=/bin/bash >>> PATH=(custom, user) >>> LANG=en_US.UTF-8 >>> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-generic >>> root=UUID=6C648DAC648D7A1A loop=/hostname/disks/root.disk ro quiet splash >>> vt.handoff=7 >>> Signal: 6 >>> SourcePackage: qemu-kvm >>> Stacktrace: >>> #0 0x00110416 in ?? () >>> No symbol table info available. >>> #1 0x1516bc8f in ?? () >>> No symbol table info available. >>> Backtrace stopped: Not enough registers or memory available to unwind >>> further >>> StacktraceTop: >>> ?? () >>> ?? () >>> Title: qemu-system-x86_64 crashed with SIGABRT >>> UpgradeStatus: Upgraded to precise on 2011-11-25 (11 days ago) >>> UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare >>> dmi.bios.date: 02/26/2010 >>> dmi.bios.vendor: American Megatrends Inc. >>> dmi.bios.version: 1401 >>> dmi.board.asset.tag: To Be Filled By O.E.M. >>> dmi.board.name: 1005HA >>> dmi.board.vendor: ASUSTeK Computer INC. >>> dmi.board.version: x.xx >>> dmi.chassis.asset.tag: 0x00000000 >>> dmi.chassis.type: 10 >>> dmi.chassis.vendor: ASUSTeK Computer INC. >>> dmi.chassis.version: x.x >>> dmi.modalias: >>> dmi:bvnAmericanMegatrendsInc.:bvr1401:bd02/26/2010:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: >>> dmi.product.name: 1005HA >>> dmi.product.version: x.x >>> dmi.sys.vendor: ASUSTeK Computer INC. >>> >>> To manage notifications about this bug go to: >>> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/901401/+subscriptions >> >> >> >> -- >> Jerry W > > > > -- > Jerry W -- Jerry W -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/901401 Title: qemu-system-x86_64 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/901401/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
