Re: [Qemu-devel] x86 emulation on ARM host (Samsung Chromebook)
On Wed, May 21, 2014 at 12:57:59PM +, Violaine V. wrote: Hi everyone, I’m trying to use QEMU (qemu-system-x86_64) to emulate an x86 virtual machine on an ARM host : a Samsung Chromebook with Cortex-A15 CPU. The Chromebook only has 2 GB of RAM and a relatively slow 32 bit processor, and you're using an SD card which means all I/O is going to be slow. Emulation of x86 is going to be very slow and painful. Anyway I think what you need to do is attach a debugger to find out what the guest is doing. http://wiki.qemu.org/Documentation/Debugging I've no idea if an ARM-compiled gdb will be able to debug an x86 guest however ... You may need to cross-compile it somehow. I'm kind of interested in making this work, but only on 64 bit ARM hardware where this is more feasible. People using libguestfs on aarch64 want to inspect and run commands in their x86 VMs. There was a request for this on the mailing list only a couple of weeks ago. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
[Qemu-devel] x86 emulation on ARM host (Samsung Chromebook)
Hi everyone, I’m trying to use QEMU (qemu-system-x86_64) to emulate an x86 virtual machine on an ARM host : a Samsung Chromebook with Cortex-A15 CPU. My Chromebook boots a Linux (kernel version 3.13) from an SD card. I have tried to create a new Debian virtual machine, by using a netinst iso file, but after the ‘Debian install menu’, nothing happens, the VM screen stays black forever, and gives no error outputs… I have also tried with an Ubuntu iso, and with qemu-system-i386, but no more success. I am using QEMU 2.0, which I compiled on my Chromebook. Beside, I have tried to boot an x86 VM previously created with an x86 host. So i pass to QEMU the kernel image, the initrd file and kernel boot options. I didn’t succeed in that either, but I am not sure if this is even possible ? My concern is that QEMU has quite a strange behaviour : Sometimes it’s having a Segmentation fault (core dumped) really early in the execution, sometimes it starts to boot the kernel, and has the segmentation fault later. Also sometimes when booting the kernel, it hangs with some errors (udev, timer).. but this is not reproducible easily. I would like to have any thoughts or ideas you may have on what i am doing. And also, what are the ways to have more debug information from QEMU ? Thanks ! Violaine.
