Hi, I'm interested about the option -writeconfig/-readconfig.
I'm looking for some documentation about the format of the file, the
syntax of all possible options and if there's a library that helps to
read and write this file from external applications.
I've been writing a sort of a cli to manage
On 10/27/15 10:11 AM, Markus Armbruster wrote:
[...]
Eduardo, I did try this approach. It takes 2 line changes in exec.c:
comment the unlink out, and making sure MAP_SHARED is used when
-mem-path and -mem-prealloc are given. It works beautifully, and
libvmi accesses are fast. However, the VM is
On 10/27/15 9:00 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/26/15 11:52 AM, Eduardo Habkost wrote:
I was trying to advocate the use of a shared mmap'ed region. The sharing
would be two-ways (RW for both) between the QEMU virtualizer and the libvmi
process. I envision
On 10/27/15 9:18 AM, Valerio Aimale wrote:
I did not try to mmap'ing to a file on a RAMdisk. Without physical
disk I/O, the VM might run faster.
I did try with the file on a ramdisk
$ sudo mount -o size=3G -t tmpfs none /ramdisk
$ /usr/local/bin/qemu-system-x86_64 -name Windows
On 10/26/15 11:52 AM, Eduardo Habkost wrote:
I was trying to advocate the use of a shared mmap'ed region. The sharing
would be two-ways (RW for both) between the QEMU virtualizer and the libvmi
process. I envision that there could be a QEMU command line argument, such
as "--mmap-guest-memory "
On 10/26/15 3:09 AM, Markus Armbruster wrote:
[...]
Eduardo, I think it would be a common rule of politeness not to pass
any judgement on a person that you don't know, but for some texts in a
mailing list. I think I understand how mmap() works, and very well.
Participating is this discussion h
On 10/23/15 12:55 PM, Eduardo Habkost wrote:
On Thu, Oct 22, 2015 at 03:51:28PM -0600, Valerio Aimale wrote:
On 10/22/15 3:47 PM, Eduardo Habkost wrote:
On Thu, Oct 22, 2015 at 01:57:13PM -0600, Valerio Aimale wrote:
On 10/22/15 1:12 PM, Eduardo Habkost wrote:
On Wed, Oct 21, 2015 at 12:54
On 10/23/15 8:56 AM, Eric Blake wrote:
On 10/23/2015 08:44 AM, Valerio Aimale wrote:
Libvmi dependence on virsh is so strict, that libvmi does not even know
if the QEMU VM has an open qmp unix socket or inet socket, to send
commands through. Thus, libvmi sends qmp commands (to query
o let QEMU send the open file descriptor to a QMP
client.
Valerio, would an command line option to share guest memory suffice, or
does it have to be a monitor command? If the latter, why?
IIUC, libvmi wants to be able to connect to arbitrary pre-existing
running KVM instances on the host. As such I
On 10/23/15 12:35 AM, Markus Armbruster wrote:
Eduardo Habkost writes:
On Wed, Oct 21, 2015 at 12:54:23PM +0200, Markus Armbruster wrote:
Valerio Aimale writes:
[...]
There's also a similar patch, floating around the internet, the uses
shared memory, instead of sockets, as inter-pr
On 10/22/15 3:47 PM, Eduardo Habkost wrote:
On Thu, Oct 22, 2015 at 01:57:13PM -0600, Valerio Aimale wrote:
On 10/22/15 1:12 PM, Eduardo Habkost wrote:
On Wed, Oct 21, 2015 at 12:54:23PM +0200, Markus Armbruster wrote:
Valerio Aimale writes:
[...]
There's also a similar patch, flo
On 10/22/15 2:03 PM, Eric Blake wrote:
On 10/22/2015 01:57 PM, Valerio Aimale wrote:
pmemmap would return the following json
{
'success' : 'true',
'map_filename' : '/tmp/QEM_mmap_1234567'
}
In general, it is better if the client controls the
On 10/22/15 1:12 PM, Eduardo Habkost wrote:
On Wed, Oct 21, 2015 at 12:54:23PM +0200, Markus Armbruster wrote:
Valerio Aimale writes:
[...]
There's also a similar patch, floating around the internet, the uses
shared memory, instead of sockets, as inter-process communication
between l
On 10/21/15 4:54 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/19/15 1:52 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/16/15 2:15 AM, Markus Armbruster wrote:
vale...@aimale.com writes:
All-
I've produced a patch for the current QEMU HEAD, for libv
On 10/22/15 5:50 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/21/15 4:54 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/19/15 1:52 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/16/15 2:15 AM, Markus Armbruster wrote:
vale...@aimale.com writes
On 10/21/15 4:54 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/19/15 1:52 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/16/15 2:15 AM, Markus Armbruster wrote:
vale...@aimale.com writes:
All-
I've produced a patch for the current QEMU HEAD, for libv
re.
If and when we decide that this patch belongs in the QEMU source tree, I
will clean up grammar, documentation and code. However, as per
discussion with Markus, that is still up in the air. So I'll hold of on
those for now.
Below discussions of two issues only, endianness and fprintf.
On 10/19/15 1:52 AM, Markus Armbruster wrote:
Valerio Aimale writes:
On 10/16/15 2:15 AM, Markus Armbruster wrote:
vale...@aimale.com writes:
All-
I've produced a patch for the current QEMU HEAD, for libvmi to
introspect QEMU/KVM VMs.
Libvmi has patches for the old qeum-kvm fork, i
arting at
'addr' of size 'size'
(qemu) pmemsave 0 8589934591 "/tmp/memorydump"
(qemu) quit
However I just noticed that the dump is just about 4GB in size, so there
might be more changes needed to snapshot all physical memory of a 64 but
VM. I did not investigate any further.
ls -l /tmp/memorydump
-rw-rw-r-- 1 libvirt-qemu kvm 4294967295 Oct 16 08:04 /tmp/memorydump
hmp-commands.hx and qmp-commands.hx should be edited accordingly. I
did not make the above pmemsave changes part of my patch.
Let me know if you have any questions,
Valerio
From: Valerio Aimale
---
Makefile.target | 2 +-
hmp-commands.hx | 14
hmp.c| 9 +++
hmp.h| 1 +
memory-access.c | 206 +++
memory-access.h | 21 ++
qapi-schema.json | 28
qmp-commands.hx
x27;pmemsave',
'data': {'val': 'int64', 'size': 'int64', 'filename': 'str'} }
---
hmp-commands.hx and qmp-commands.hx should be edited accordingly. I did not
make the above pmemsave changes part of my patch.
Let me know if you have any questions,
Valerio
have you tried with "-cpu kvm64,+nx" ?
The additional parameter enables the No eXecute (NX) bit.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/921208
Title:
win7/x64 installer hangs on startup wit
22 matches
Mail list logo
