[Qemu-devel] qemu warnings and errors

[Qemu-devel] qemu warnings and errors

[James Barrett]

I keep getting these warnings with a message to send email to
qemu-devel@nongnu.org

here is the command I am using:

qemu-system-i386 -hda bbs.hd -fda bbs.fd -hdb fat:rw:dist


Host OS is Ubunti 17.10, guest OS is MS-DOS 6.22



WARNING: Image format was not specified for 'bbs.hd' and probing guessed
raw.
         Automatically detecting the format is dangerous for raw images,
write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.
WARNING: Image format was not specified for 'bbs.fd' and probing guessed
raw.
         Automatically detecting the format is dangerous for raw images,
write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.
vvfat dist chs 1024,16,63
WARNING: Image format was not specified for 'json:{"fat-type": 0, "dir":
"dist", "driver": "vvfat", "floppy": false, "rw": true}' and probing
guessed raw.
         Automatically detecting the format is dangerous for raw images,
write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.
unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org

Re: [Qemu-devel] qemu warnings and errors

[John Snow]

On 02/19/2018 10:24 AM, James Barrett wrote:
> I keep getting these warnings with a message to send email to
> qemu-devel@nongnu.org
> 
> here is the command I am using:
> 
> qemu-system-i386 -hda bbs.hd -fda bbs.fd -hdb fat:rw:dist
> 
> 
> Host OS is Ubunti 17.10, guest OS is MS-DOS 6.22
> 

What version of QEMU?

> 
> 
> WARNING: Image format was not specified for 'bbs.hd' and probing guessed
> raw.
>          Automatically detecting the format is dangerous for raw images,
> write operations on block 0 will be restricted.
>          Specify the 'raw' format explicitly to remove the restrictions.
> WARNING: Image format was not specified for 'bbs.fd' and probing guessed
> raw.
>          Automatically detecting the format is dangerous for raw images,
> write operations on block 0 will be restricted.
>          Specify the 'raw' format explicitly to remove the restrictions.
> vvfat dist chs 1024,16,63
> WARNING: Image format was not specified for 'json:{"fat-type": 0, "dir":
> "dist", "driver": "vvfat", "floppy": false, "rw": true}' and probing
> guessed raw.
>          Automatically detecting the format is dangerous for raw images,
> write operations on block 0 will be restricted.
>          Specify the 'raw' format explicitly to remove the restrictions.

All of the above is "fine," but occurs because you use the -hda and -fda
shorthands to load raw files.

The more explicit syntax looks like this:

-drive if=none,format=raw,file=bbs.hd,id=foo
-device ide-hd,drive=foo

with that "format=raw" parameter there you'll avoid all those warnings.

> unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
> 

This part is the only part that urges you to report the error, but I
don't know much about what's going on here.

Maybe Gerd knows?

--js

Re: [Qemu-devel] qemu warnings and errors

[Gerd Hoffmann]

  Hi,

> What version of QEMU?
> 
> > unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
> 
> This part is the only part that urges you to report the error, but I
> don't know much about what's going on here.
> 
> Maybe Gerd knows?

We had lots of keymap/keycode changes recently, most likely this will be
fixed in 2.12, maybe it already is in 2.11.  So, when using something
older, try upgrading first (or just ignore it in case it happes to be a
key you don't need).

cheers,
  Gerd

Re: [Qemu-devel] qemu warnings and errors

[Eric Blake]

On 02/20/2018 02:38 AM, Gerd Hoffmann wrote:
>    Hi,
> 
>> What version of QEMU?
>>
>>> unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
>>
>> This part is the only part that urges you to report the error, but I
>> don't know much about what's going on here.
>>
>> Maybe Gerd knows?
> 
> We had lots of keymap/keycode changes recently, most likely this will be
> fixed in 2.12, maybe it already is in 2.11.  So, when using something
> older, try upgrading first (or just ignore it in case it happes to be a
> key you don't need).

The error message doesn't mention a numeric code or other way to figure 
out which key is problematic.  While this particular message may 
disappear when you upgrade, it would also be worth investigating if this 
message can give more details to figure out which keycode is problematic 
in case of future mismatches, other than just "unnamed".

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

Re: [Qemu-devel] qemu warnings and errors

[Daniel P. Berrangé]

On Tue, Feb 20, 2018 at 08:45:00AM -0600, Eric Blake wrote:
> On 02/20/2018 02:38 AM, Gerd Hoffmann wrote:
> >    Hi,
> > 
> > > What version of QEMU?
> > > 
> > > > unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
> > > 
> > > This part is the only part that urges you to report the error, but I
> > > don't know much about what's going on here.
> > > 
> > > Maybe Gerd knows?
> > 
> > We had lots of keymap/keycode changes recently, most likely this will be
> > fixed in 2.12, maybe it already is in 2.11.  So, when using something
> > older, try upgrading first (or just ignore it in case it happes to be a
> > key you don't need).
> 
> The error message doesn't mention a numeric code or other way to figure out
> which key is problematic.  While this particular message may disappear when
> you upgrade, it would also be worth investigating if this message can give
> more details to figure out which keycode is problematic in case of future
> mismatches, other than just "unnamed".

It isn't about a specific key. This message is basically saying we don't
know what keymapping the X server is using, so we've given up. Historically
QEMU could only identify evdev and/or kbd key mappings. With the newly
merged code, we can now detect many more especially including Windows and
OS-X X11 server mappings. So git master hopefully removed the most common
cases that would trigger this particular error message. There's probably
still some remaining though, as there's a huge range of X11 servers impls
in the world.  With current git master this message will instruct the user
to provide us a list of relevant info to help us diagnose it - see the
end of ui/x_keymap.c file.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|