Since it's now possible to use the -drive option, the test for something
in the index 0 of the IDE bus is too restrictive.
A better idea, IMHO, is to check if the user specified any bootable device,
and only if not, fallback to the default, compatible behaviour of checking
hda regardless of the pr
Hello,
this patch to sdl.c (qemu 0.9.1) changes the behavior of -alt-grab to be
similar to VirtualBox.
The reason for this is to have an easy way for sending ctrl-alt-Fn and
ctrl-alt-backspace to the guest. Since ctrl-alt-Fn and
ctrl-alt-backspace are intercepted by X11 new shortcuts are add
On Friday 08 February 2008, Rob Landley wrote:
> Grepping through the source code, I can find 3 places where this global
> variable is set (it's initialized to a default value of 1, there's
> a "no-code-copy" command line option that sets it to zero, and then it
> shows up in the test suite once).
Grepping through the source code, I can find 3 places where this global
variable is set (it's initialized to a default value of 1, there's
a "no-code-copy" command line option that sets it to zero, and then it shows
up in the test suite once). What I can't find is any code ever actually
checki
This version is still a bit chatty when -name isn't specified so
attached is an updated version of the patch which is less chatty when
-name isn't specified.
Regards,
Anthony Liguori
Anthony Liguori wrote:
Modern DNS clients (like vinagre) support mDNS/DNS-SD discovery of VNC servers.
VNC se
Modern DNS clients (like vinagre) support mDNS/DNS-SD discovery of VNC servers.
VNC servers like Vino link directly against libavahi to publish themselves.
Fitting libavahi into QEMU though would be pretty hairy and not as flexible as
simply calling out to a helper script and using the avahi utilit
On Thu, 7 Feb 2008, Ian Jackson wrote:
Johannes Schindelin writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
LIST_* macros"):
Read what you wrote. By that reasoning you cannot use _any_ name in qemu,
because qemu should bend over to be mixable with other code.
No, not at all. Jus
Hello,
I'm getting acquainted with QEMU's internals because I'll need to know them
very well for the next few months. I've reached a point where I want to
debug QEMU with gdb in order to better understand the code flux related to
some things that are still not clear after just looking at the code.
This patch will make an .rc file that will put the version info as well as a
brief discription of the app for Windows.
versionrc.diff
Description: Binary data
Johannes Schindelin writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
LIST_* macros"):
> Read what you wrote. By that reasoning you cannot use _any_ name in qemu,
> because qemu should bend over to be mixable with other code.
No, not at all. Just that when a clash happens something s
Hi,
On Thu, 7 Feb 2008, Ian Jackson wrote:
> Anthony Liguori writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
> LIST_* macros"):
> > Ian Jackson wrote:
> >
> > > qemu's audio subdirectory contains a copy of BSD's sys-queue.h,
> > > which defines a bunch of LIST_ macros. This makes i
Anthony Liguori writes ("Re: [Qemu-devel] [PATCH] check return value from
read() and write() properly"):
> Ian Jackson wrote:
> > The system calls read and write may return less than the whole amount
> > requested for a number of reasons. So the idioms
> >if (read(fd, &object, sizeof(object))
Anthony Liguori writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
LIST_* macros"):
> Ian Jackson wrote:
> > qemu's audio subdirectory contains a copy of BSD's sys-queue.h, which
> > defines a bunch of LIST_ macros. This makes it difficult to build a
> > program made partly out of qemu a
Hi,
-soundhw, -M, -cpu and -d options use the '?' to display the list of
possibilities, whereas -clock uses 'help'. This has to be made consistent.
Some debug output is shown when -clock option is specified, which
displays list of available clocks. In my opinion, interest is very
limited (as
14 matches
Mail list logo
