qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Sebastian Herbszt" <herbszt@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Problem(s) with encrypted images
Date: Mon, 16 Jun 2008 20:14:36 +0200	[thread overview]
Message-ID: <006201c8cfdd$33247b10$0201a8c0@zeug> (raw)
In-Reply-To: 01f001c8cb07$28c41d90$0201a8c0@zeug

>>> 2. When I start qemu, it just hangs there waiting for (assumingly) the 
>>> password of the encrypted image. However I cannot find the place where the 
>>> prompt actually is.
>> 
>> qemu_key_check in vl.c does use monitor_readline, so you should see a "Password:"
>> prompt in the monitor window (press ctrl-alt-2 to get there).
> 
> The initialization order seems to be wrong in main() (vl.c):
> 
>    for(i = 0; i < nb_drives_opt; i++)
>        if (drive_init(&drives_opt[i], snapshot, machine) == -1)
>            exit(1);
>    ...
>    *_display_init();
>    ...
>    monitor_init();
> 
> drive_init() got
> ...
> if (bdrv_open2(bdrv, file, bdrv_flags, drv) < 0 || qemu_key_check(bdrv, file)) {
> 
> and qemu_key_check depends on the monitor:
> 
>    term_printf("%s is encrypted.\n", name);
>    for(i = 0; i < 3; i++) {
>        monitor_readline("Password: ", 1, password, sizeof(password));
> 

Can you try this patch? It will break monitor but should read the password.

- Sebastian

--- vl.c.orig Mon Jun 16 18:07:39 2008
+++ vl.c Mon Jun 16 17:47:44 2008
@@ -5307,7 +5307,7 @@ static int drive_init(struct drive_opt *
         bdrv_flags |= BDRV_O_SNAPSHOT;
     if (!cache)
         bdrv_flags |= BDRV_O_DIRECT;
-    if (bdrv_open2(bdrv, file, bdrv_flags, drv) < 0 || qemu_key_check(bdrv, file)) {
+    if (bdrv_open2(bdrv, file, bdrv_flags, drv) < 0 ) {
         fprintf(stderr, "qemu: could not open disk image %s\n",
                         file);
         return -1;
--- monitor.c.orig Mon Jun 16 17:56:17 2008
+++ monitor.c Mon Jun 16 18:06:23 2008
@@ -2642,10 +2642,12 @@ static void term_event(void *opaque, int
     if (event != CHR_EVENT_RESET)
  return;
 
+/*
     if (!hide_banner)
      term_printf("QEMU %s monitor - type 'help' for more information\n",
    QEMU_VERSION);
     monitor_start_input();
+*/
 }
 
 static int is_first_init = 1;

      parent reply	other threads:[~2008-06-16 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  3:18 [Qemu-devel] Problem(s) with encrypted images nuitari-qemu
2008-06-10 13:34 ` [Qemu-devel] " Sebastian Herbszt
2008-06-10 14:33   ` Sebastian Herbszt
2008-06-11 18:35     ` nuitari
2008-06-11 19:02     ` nuitari-qemu
2008-06-16 18:14     ` Sebastian Herbszt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006201c8cfdd$33247b10$0201a8c0@zeug' \
    --to=herbszt@gmx.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).