From: nuitari-qemu@nuitari.net
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Problem(s) with encrypted images
Date: Wed, 11 Jun 2008 15:02:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0806111439480.18515@anvil.nuitari.net> (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));
Just changing the order in vl.c doesn't work.
For example I get:
VM_Serveur_de_scripts.crypt.qcow2 is encrypted.
Password: QEMU 0.9.1 monitor - type 'help' for more information
(qemu) blahblahblahblah
unknown command: 'blahblahblahblah'
(qemu)
(qemu)
Also connecting to vnc results in a segmentation fault with the reordering
that I did.
next prev parent reply other threads:[~2008-06-11 18:58 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 [this message]
2008-06-16 18:14 ` Sebastian Herbszt
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=Pine.LNX.4.64.0806111439480.18515@anvil.nuitari.net \
--to=nuitari-qemu@nuitari.net \
--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).