Hi,
On 03/03/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
andrzej zaborowski wrote:
> Hi,
>
> On 20/02/07, Christopher Olsen <[EMAIL PROTECTED]> wrote:
> >Ok FreeBSD Support round one..
> >
> >Be gentle this is my first attempt at working with the rest of this
> >community..
> >
> >Files it modi
On Sun, 2007-03-04 at 19:18 +0100, Fabrice Bellard wrote:
> OK. Except that I would prefer "-cpu" instead of "-C".
OK; I choosed -C for "symetry" with the machine selection option (-M)
but -cpu is OK for me...
> J. Mayer wrote:
> > Here's a patch that allow the user to specify a specific CPU
> >
Hi,
I wrote a patch to automatically eject a physical CD-ROM disk when:
* Issue "eject" command in monitor console, or
* Issue "eject" command in Linux guest system, or
* In Windows guest system, press the right mouse button above CD-ROM
icon, then select "eject".
This is patch is based
Hi,
On 3/4/07, Hetz Ben Hamo <[EMAIL PROTECTED]> wrote:
Hmm, What guest platform/OS supports it? Not XP or Vista iirc...
MacIntels all have EFI BIOS. All Itanium machines have them too, so
all OS that support Itanium support EFI.
Guillaume
___
Qem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hetz Ben Hamo wrote:
> Hmm, What guest platform/OS supports it? Not XP or Vista iirc...
Linux and MacOSX for sure; I suppose BSD too.
- --
Flavio Visentin
GPG Key: http://www.zipman.it/gpgkey.asc
There are only 10 types of people in this world:
thos
Hmm, What guest platform/OS supports it? Not XP or Vista iirc...
Thanks,
Hetz
On 3/5/07, Fabrice Bellard <[EMAIL PROTECTED]> wrote:
Hi,
There is now an EFI BIOS for QEMU thanks to Tristan Gingold. It is
available from the download section of the web site
(http://bellard.org/qemu/efi-bios.tar.b
Hi,
There is now an EFI BIOS for QEMU thanks to Tristan Gingold. It is
available from the download section of the web site
(http://bellard.org/qemu/efi-bios.tar.bz2). It can only be used with the
CVS version of QEMU.
Fabrice.
___
Qemu-devel maili
On Sun, Mar 04, 2007 at 11:11:15AM -0600, Anthony Liguori wrote:
> Avi Kivity wrote:
> >Anthony Liguori wrote:
> >>This option helps differentiate between guests when running more than
> >>one instance of QEMU. It adds a string to the SDL window title and
> >>to the VNC server title.
> >>
> >>Ha
OK. Except that I would prefer "-cpu" instead of "-C".
Regards,
Fabrice.
J. Mayer wrote:
Here's a patch that allow the user to specify a specific CPU
model/variant on the command line.
This makes different CPU tests less painfull, as the current code need a
recompilation for this.
This patch o
Chris Wilson wrote:
Hi Avi,
On Sun, 4 Mar 2007, Avi Kivity wrote:
Anthony Liguori wrote:
I think we should still provide the ability to set the most common
options via the command line. I'm also fine with specifying single
options on the command line. I suspect though that being able to
Anthony Liguori wrote:
So right now we have:
QEMU
QEMU - Press Ctrl+Alt to exit grab
My patch would add:
QEMU (WinXP Home)
QEMU (WinXP Home) - Press Ctrl+Alt to exit grab
You're suggesting:
WinXP Home - QEMU
WinXP Home - QEMU - Press Ctrl+Alt to exit grab
I like yours for the first title b
Avi Kivity wrote:
Anthony Liguori wrote:
This option helps differentiate between guests when running more than
one instance of QEMU. It adds a string to the SDL window title and
to the VNC server title.
Having a name associated with a guest is also terribly useful for
management tools as it
Avi Kivity wrote:
Anthony Liguori wrote:
1. Any option should be settable either in the config file or
command line. In other words, the user should not be forced to use
a config file. This is useful for management programs who keep all
options in an internal database, and for users who c
Hi Avi,
On Sun, 4 Mar 2007, Avi Kivity wrote:
Anthony Liguori wrote:
I think we should still provide the ability to set the most common
options via the command line. I'm also fine with specifying single
options on the command line. I suspect though that being able to do
-config - is mor
On Sunday 04 March 2007 11:52, Kirill A. Shutemov wrote:
> I want to help qemu project, but some patches which I post to the mail
> list have ignored. I guess that a open source project should have faster
> feedback.
Giving some description of the patches might help. Patches with no explanation
o
I want to help qemu project, but some patches which I post to the mail
list have ignored. I guess that a open source project should have faster
feedback.
Subject of posts which have still ignored:
[PATCH] syscall mincore
[PATCH] syscall uselib
[BUG] [PATCH] Syscall gethostname fix
[BUG] [PATCH] S
On Sunday 04 March 2007 11:48, Avi Kivity wrote:
> Paul Brook wrote:
> >> Out of curiosity, why? If the options are store in some database, as is
> >> likely, surely it is easier to generate a longish command line than to
> >> generate a unique name for a file, remove it if it already exists, writ
Paul Brook wrote:
Out of curiosity, why? If the options are store in some database, as is
likely, surely it is easier to generate a longish command line than to
generate a unique name for a file, remove it if it already exists, write
out the data, launch qemu, and clean up the file later? And f
On Sunday 04 March 2007 09:28, Avi Kivity wrote:
> Anthony Liguori wrote:
> >> 1. Any option should be settable either in the config file or
> >> command line. In other words, the user should not be forced to use a
> >> config file. This is useful for management programs who keep all
> >> option
Here's a patch that allow the user to specify a specific CPU
model/variant on the command line.
This makes different CPU tests less painfull, as the current code need a
recompilation for this.
This patch only has an actual effect when using the PowerPC target, as I
don't want to break other targets
> Hi,
> I have successfully integrated the statistical simulation package
> SimPoint with QEMU.
> I am curious where I would edit QEMU to look for such commands, some
> point in the code where I can see what command is passed to QEMU, and
> do something such as
> "if strcmp(command, "start
Anthony Liguori wrote:
This option helps differentiate between guests when running more than
one instance of QEMU. It adds a string to the SDL window title and to
the VNC server title.
Having a name associated with a guest is also terribly useful for
management tools as it gives a standard w
Anthony Liguori wrote:
1. Any option should be settable either in the config file or
command line. In other words, the user should not be forced to use a
config file. This is useful for management programs who keep all
options in an internal database, and for users who can experiment via
23 matches
Mail list logo
