On 12/16/06, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:
On Sat, Dec 16, 2006 at 07:42:46PM -0800, Diwaker Gupta wrote:
> o do these changes seem correct? As in, do they actually track the
> read/write memory accesses done by the guest? I was concerned because
> when I start a guest, I see a who
bout 4x faster when
> it comes to memory access. You can view my results at:
>
> http://www.calcmaster.net/qemu/benchmarks-20061216/
Two things:
1. http://www.vmware.com/download/eula/player.html
(Restrictions - Section 3.3 - "You may use the Software to ...")
stand waiting
around for hours and hours while Qemu translates code, sorry. At this
particular time, I'm really only interested in this particular case
because I use it for production use and many non-developer users are
wanting to do the same thing. The only major differenc
On Sat, Dec 16, 2006 at 07:42:46PM -0800, Diwaker Gupta wrote:
> o do these changes seem correct? As in, do they actually track the
> read/write memory accesses done by the guest? I was concerned because
> when I start a guest, I see a whole lot of writes and not as many
> reads, which seems a litt
Hi list,
I've searched the archives and the forums, but couldn't get a specific
solution (I think my search terms might have been too general).
Anyways, I think what I'm trying to do should be relatively easy and
hopefully experts here will be able to quickly point me in the right
direction :)
S
If you expose the monitor on a character device that support
reconnecting, it becomes difficult to deterministically execute
commands. For instance, one person may connect and send a partial
command in which case reconnecting may result in your command not being
what you expect.
Furthermore,
info block is impossible to parse reliably because there is no escaping
done on the filename. A really unfortunately name like "Ugly
backing_file=foo" would result in:
hda: type=hd removable=0 file=Ugly backing_file=foo ro=0 drv=qcow
Which is ambiguous when compared to a file named "Ugly" wit
This is a short patch series to make the monitor a bit more friendly to
external programs.
This series is independent of my previous series but may apply with fuzz
if the other series isn't applied.
Regards,
Anthony Liguori
___
Qemu-devel mailing
David Woodhouse wrote:
> > However, it is probably easier to use the host's, than to write the
> > equivalent (basically duplicating the kernel's futex code in qemu, the
> > hashed locks and wait queues etc.).
>
> The kernel's implementation is a _whole_ lot more complicated than ours
> needs to b
This adds a -daemonize option. This option is mostly useful for
front-ends as it provides a deterministic way to connect to QEMU's
various devices. For instance, if you wanted to execute:
qemu -hda ~/win2k.img -monitor telnet:localhost:1024,server &
telnet localhost:1024
Occasionally, you wi
The following patch allows a user to restrict which interface the VNC
server will listen on. It also adds unix domain socket support to VNC.
N.B. The old syntax of:
qemu -vnc 1
Is now:
qemu -vnc :1
Also, the syntax between the unix char devices and VNC is a bit
different. This is because
This patch introduces a unix: domain socket. It reuses the tcp: code so
it will behave almost identically.
An example usage would be:
qemu -hda ~/win2k.img -monitor unix:/home/anthony/monitor.sock,server,nowait
Regards,
Anthony Liguori
diff -r 01fafeaa2f64 qemu_socket.h
--- a/qemu_socket.h T
Howdy,
I've been working on a QEMU front end for a bit now. The following
patch introduces a number of things to make writing front ends in
general a bit easier. This includes making the char devices exposable
as unix sockets and adding a daemonize option.
Unix sockets are useful for a fro
Atsushi Nemoto wrote:
> On Sun, 3 Dec 2006 21:35:18 +, Ralf Baechle <[EMAIL PROTECTED]> wrote:
> > > It seems this commit break QEMU kernel ... or QEMU can not interpret
> > > the TNE instruction correctly?
> >
> > Thiemo says that's indeed a possibility. Probably that feature has not
> > be
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 06/12/16 16:45:18
Modified files:
target-mips: translate.c
Log message:
Fix erraneous fallthrough in MIPS trap implementation, thanks Atsushi
Nemoto.
CVSWeb URLs:
http://cvs.savannah.gnu.o
> > On the other hand, using the host's makes it hard to run Linux guest
> > binaries on non-Linux hosts (those which don't have futex), or newer
> > Linux guest binaries on older Linux hosts which have fewer futex ops,
> > or none at all.
>
> I don't think we care. You can't run qemu-i386 on a non
On Thu, 2006-12-14 at 02:16 +, Jamie Lokier wrote:
> David Woodhouse wrote:
> > - sys_futex():
> >
> > We have to translate these into calls to the host's sys_futex() anyway.
>
> I don't think it's necessary to translate to the host's sys_futex(),
> unless the guest will be doing futex operat
17 matches
Mail list logo
