Programmingkid writes:
> On Sep 10, 2015, at 1:15 PM, Markus Armbruster wrote:
>
>> Programmingkid writes:
>>
>>> On Sep 10, 2015, at 3:21 AM, Markus Armbruster wrote:
>>>
Programmingkid writes:
> Does this look about right?
>
> QDict *qdict;
> Error *errp;
>>>
On Sep 10, 2015, at 1:15 PM, Markus Armbruster wrote:
> Programmingkid writes:
>
>> On Sep 10, 2015, at 3:21 AM, Markus Armbruster wrote:
>>
>>> Programmingkid writes:
>>>
Does this look about right?
QDict *qdict;
Error *errp;
QObject **ret_data;
static
Programmingkid writes:
> On Sep 10, 2015, at 3:21 AM, Markus Armbruster wrote:
>
>> Programmingkid writes:
>>
>>> Does this look about right?
>>>
>>>QDict *qdict;
>>>Error *errp;
>>>QObject **ret_data;
>>>static int counter;
>>>char *idString, *fileName;
>>>
>>> // The
On Sep 10, 2015, at 3:21 AM, Markus Armbruster wrote:
> Programmingkid writes:
>
>> Does this look about right?
>>
>>QDict *qdict;
>>Error *errp;
>>QObject **ret_data;
>>static int counter;
>>char *idString, *fileName;
>>
>> // The file variable is objective-c, left t
Programmingkid writes:
> Does this look about right?
>
> QDict *qdict;
> Error *errp;
> QObject **ret_data;
> static int counter;
> char *idString, *fileName;
>
> // The file variable is objective-c, left that code out
>
> fileName = g_strdup_printf("%s",
>
Programmingkid writes:
> On Sep 9, 2015, at 6:25 PM, Eric Blake wrote:
>
>> On 09/09/2015 03:37 PM, Programmingkid wrote:
>>
>>>
>>> Thank you very much for caring. I appreciate all the help I can
>>> receive. I so like my idea of
>>> sending a command to QEMU as if the user typed it himself. I
Does this look about right?
QDict *qdict;
Error *errp;
QObject **ret_data;
static int counter;
char *idString, *fileName;
// The file variable is objective-c, left that code out
fileName = g_strdup_printf("%s",
[file cStringUsingEnc
On Sep 9, 2015, at 6:31 PM, Eric Blake wrote:
> On 09/09/2015 04:25 PM, Eric Blake wrote:
>
>>> That leaves QMP. I am trying to figure it out. This is my attempt so far:
>>>
>>> Error **errp;
>>> char *commandBuffer;
>>> commandBuffer = g_strdup_printf("{ \"execute\": \"quit\" }");
>>> qmp_quer
On Sep 9, 2015, at 6:25 PM, Eric Blake wrote:
> On 09/09/2015 03:37 PM, Programmingkid wrote:
>
>>
>> Thank you very much for caring. I appreciate all the help I can receive. I
>> so like my idea of
>> sending a command to QEMU as if the user typed it himself. It is so easy to
>> maintain. So
On 09/09/2015 04:25 PM, Eric Blake wrote:
>> That leaves QMP. I am trying to figure it out. This is my attempt so far:
>>
>> Error **errp;
>> char *commandBuffer;
>> commandBuffer = g_strdup_printf("{ \"execute\": \"quit\" }");
>> qmp_query_command_line_options(false, commandBuffer, errp);
>> prin
On 09/09/2015 03:37 PM, Programmingkid wrote:
>> On 2 September 2015 at 01:56, Programmingkid
>> wrote:
It's okay to trim your reply, to make it easier for others to quickly
skip to the relevant part of your emails.
>
> Thank you very much for caring. I appreciate all the help I can r
is
>>>>> (and there might not even be a human monitor to talk to)...
>>>>
>>>> Under what situation is the human monitor not available?
>>>>
>>>> Would you know what function I should use in place of the commands the
>>>&g
org/archive/html/qemu-devel/2015-09/msg8.html
>>
>> The mapping from HMP to the C interfaces can be more complex. Going
>> from QMP to C is easier.
>
> The problem with QMP is that it is so difficult to use. It could be
> made to be more
> user-friendly. I will
On Sep 8, 2015, at 2:46 PM, Markus Armbruster wrote:
> Programmingkid writes:
>
>> On Sep 8, 2015, at 12:17 PM, Peter Maydell wrote:
>>
>>> On 2 September 2015 at 01:56, Programmingkid
>>> wrote:
Add "Mount Image File..." and a "Eject Image File" menu items to
cocoa interface. This
Programmingkid writes:
> On Sep 8, 2015, at 12:17 PM, Peter Maydell wrote:
>
>> On 2 September 2015 at 01:56, Programmingkid
>> wrote:
>>> Add "Mount Image File..." and a "Eject Image File" menu items to
>>> cocoa interface. This patch makes sharing files between the
>>> host and the guest user-
On 8 September 2015 at 17:39, Programmingkid wrote:
> Under what situation is the human monitor not available?
It might be connected to a TCP port, or to stdio, rather than to
a QEMU console, for instance. If you're running a -nodefaults
command line then there won't be a monitor at all unless yo
On Sep 8, 2015, at 12:17 PM, Peter Maydell wrote:
> On 2 September 2015 at 01:56, Programmingkid
> wrote:
>> Add "Mount Image File..." and a "Eject Image File" menu items to
>> cocoa interface. This patch makes sharing files between the
>> host and the guest user-friendly.
>>
>> The "Mount Ima
On 2 September 2015 at 01:56, Programmingkid wrote:
> Add "Mount Image File..." and a "Eject Image File" menu items to
> cocoa interface. This patch makes sharing files between the
> host and the guest user-friendly.
>
> The "Mount Image File..." menu item displays a dialog box having the
> user p
Cc'ing the maintainers you forgot. scripts/get_maintainer.pl is your
friend.
Programmingkid writes:
> Add "Mount Image File..." and a "Eject Image File" menu items to
> cocoa interface. This patch makes sharing files between the
> host and the guest user-friendly.
>
> The "Mount Image File..."
Add "Mount Image File..." and a "Eject Image File" menu items to
cocoa interface. This patch makes sharing files between the
host and the guest user-friendly.
The "Mount Image File..." menu item displays a dialog box having the
user pick an image file to use in QEMU. The image file is setup as
a U
20 matches
Mail list logo
