On the other hand, I think the starting point for a generic in-place
converter would be a loop that does something like bdrv_is_allocated()
but translates the guest position in the block device into an offset
into the image file. That, together with some sort of free map or
space allocation
1. header_size: variable in qed, equals to cluster size in qcow2:
When will it be larger than 1 cluster in qed? So, what will happen to
that extra data on qed-qcow2 conversion.
If you have an feature that is used in the original image, but cannot be
represented in the new format, I think
Nice that qemu-img convert isn't that far out by default on raw :).
About Google Summer of Code, I have posted my take on applying and
want to share that with you and qemu-devel:
http://blog.vmsplice.net/2011/03/advice-for-students-applying-to-google.html
Thanks for sharing your
On Saturday 05 March 2011 04:30 PM, Mahesh Shivhare wrote:
Hi all,
Is there any way by which we can run qemu on android-x86 OS.does qemu needs any
modification to run on android-x86
I'm trying to build QEMU with --static option but when m trying to run on
android it's getting stuck with the
On Sunday 27 February 2011 04:19 PM, Stefan Hajnoczi wrote:
On Sat, Feb 26, 2011 at 9:50 PM, Dushyant Bansal
cs5070...@cse.iitd.ac.in wrote:
Disk block size is usually 512 bytes and in qemu-img, sector size is also
512B. And, this change would copy n sectors even if only one of them
In cp, it just copies all the disk blocks actually occupied by the file.
And, with qemu-img convert, it checks all the sectors and copy those, which
contains atleast one non-NUL byte.
The better performance of cp over qemu-img convert is the result of overhead
of this checking.
How did
On Sunday 27 February 2011 03:45 AM, Frans de Boer wrote:
Hi all,
This is the only QEMU list, so I put my question her.
How can I copy the contents of a *.raw image to a real HD partition
or vice versa.
I often use a virtual image using qemu/kvm to test some OS's and want
to migrate them to a
On Wednesday 16 February 2011 02:39 PM, Avi Kivity wrote:
On 02/15/2011 05:59 PM, Dushyant Bansal wrote:
2. How to configure makefiles to get output of printk statements
inside kvm/arch/powerpc/kvm/trace.h
Better don't make them printks - just use the tracing framework. I'd
write up a small
On Saturday 29 January 2011 04:20 PM, Dushyant Bansal wrote:
Or this: which is faster, qemu-img convert -fformat -Oformat
src-image dst-image or cpsrc-image dst-image? What about for
raw images, shouldn't that be the same speed as cp(1)? Poke around
the source code, profile it, understand
On Thursday 17 February 2011 04:03 PM, Marco Boni wrote:
Hi all,
I am pretty new to QEMU development. To get involved in this, I have
been asked by my supervisor to do a simple modification to QEMU.
We would like to count the number of instructions the virtual machine
processes. In other
Hrm. This means that your kernel headers in /usr/include/linux are too old. Can
you try and find out which kernel version they are from please
Yes, kernel headers version is 2.6.32. For the time being, I copied some of the
header files from kvm/arch/powerpc/include/asm/ to kernel
On Tuesday 15 February 2011 08:03 PM, Alexander Graf wrote:
On 15.02.2011, at 15:21, Dushyant Bansal wrote:
Hrm. This means that your kernel headers in /usr/include/linux are too old. Can
you try and find out which kernel version they are from please
Yes, kernel
Hi,
I am trying to install kvm on ppc64 system (imac G5). I have built
kernel with kvm module. When I try to install qemu, I am getting this
error
$ ./configure --enable-kvm --target-list=ppc-softmmu
$ make
[...]
CCslirp/tftp.o
CClibdis/ppc-dis.o
GEN config-target.h
CC
On Friday 04 February 2011 08:13 PM, Alexander Graf wrote:
On 04.02.2011, at 14:25, Dushyant Bansalcs5070...@cse.iitd.ernet.in wrote:
Hi,
I am trying to install kvm on ppc64 system (imac G5). I have built
kernel with kvm module. When I try to install qemu, I am getting this
error
$
http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline
I'd like to see an in-place QCOW2- QED image converter with tests.
I'm interested in mentoring this year.
Stefan
Hi,
I am interested in working on this project as part of gsoc. I have prior
experience
On Monday 24 January 2011 08:26 PM, Stefano Bonifazi wrote:
On 01/24/2011 03:32 PM, Peter Maydell wrote:
Being a JIT doesn't prohibit counting target instructions executed.
It just means that counting them generally requires generating
code to do the counting at runtime, so it's a more
You should see this pdf
(www.ecs.syr.edu/faculty/yin/Teaching/TC2010/Proj4.pdf). It talks
about tracing the instructions.
--
Dushyant
Wow thank you! It sounds incredibly interesting!!
What we really need is to insert a function call into the
translated code, so when each instruction is
Hi all,
I have configured and built qemu with device tree support.
qemu-version: 0.13.50
I have built kernel image (uImage) for bamboo using powerpc-440 toolchain.
kernel-version: 2.6.37-rc6+
When I try to run this command,
# qemu-system-ppcemb -nographic -m 128 -M bamboo -kernel uImage
On Monday 24 January 2011 12:12 AM, Rob Landley wrote:
On 01/23/2011 06:59 AM, Dushyant Bansal wrote:
Hi all,
I have configured and built qemu with device tree support.
qemu-version: 0.13.50
I have built kernel image (uImage) for bamboo using powerpc-440 toolchain.
kernel-version: 2.6.37
Those are board emulations. Does it have a 440 _cpu_ emulation?
./qemu-system-ppc -cpu ? | grep 440
This is the output.
PowerPC 440-Xilinx PVR 7ff21910
Is this right for my requirement?
This is qemu version 0.13.50. And, it seems this support has been added
recently. It is
On Monday 24 January 2011 01:22 AM, Andreas Färber wrote:
Am 23.01.2011 um 19:42 schrieb Rob Landley:
On 01/23/2011 06:59 AM, Dushyant Bansal wrote:
When I try to run this command,
# qemu-system-ppcemb -nographic -m 128 -M bamboo -kernel uImage
-append
I get the following output
Hi,
I have installed qemu on x86 system. I downloaded debian-powerpc image
from http://people.debian.org/~aurel32/qemu/powerpc/ and used it with
qemu-system-ppc.
This is the cpuinfo of the guest os (debian-507-powerpc (2.6.26-1-powerpc) )
processor: 0
cpu: 740/750
temperature
22 matches
Mail list logo
