> with some kind of time stamp to correlate the data from the command
> line and the last updated time of the primary image file.
If there have to be separate files I'd prefer a weak hash to timestamps
to avoid the common problems with unexpected drift and no way to
calculate which ch
tates so I moved to exit(1).
I think (can someone correct me here?) there is another reason to call
atexit() for portable programs, and that is that Microsoft OSs aren't as
fussy about cleaning up after a program has exited.
--
Dan Shearer
[EMAIL PROTECTED]
n a device
language? :-)
--
Dan Shearer
[EMAIL PROTECTED]
t the images (not a difficult problem, I think) but VMware can.
I'll try other free virtualisation systems at some point.
See http://shearer.org/Microsoft_Demo_VMs for my notes so far.
--
Dan Shearer
[EMAIL PROTECTED]
ecial-purpose language for describing CPUs at this level) but I now
think your work is a very good solution for bootstrapping QEMU to the
next level of users.
--
Dan Shearer
[EMAIL PROTECTED]
On Fri, Jul 27, 2007 at 05:50:05PM +0200, Sunil Amitkumar Janki wrote:
> Dan Shearer wrote:
> >You do also have the architectures provided to you by QEMU :-) :-)
>
> Maybe in the future where we have all kinds of cheap multicore processors
> this will not matter much but for
On Fri, Jul 27, 2007 at 04:58:19PM +0200, Sunil Amitkumar Janki wrote:
> Dan Shearer wrote:
> >
> >I see this as a different class of testing to the tinderbox-style
> >testing Natalia Portillo was talking about, checking out and compiling
> >under different circumst
o the tinderbox-style
testing Natalia Portillo was talking about, checking out and compiling
under different circumstances. That's very valuable, and will help
address a problem that drives away a lot of potential QEMU users - they
just can't compile it.
--
Dan Shearer
[EMAIL PROTECTED]
emu
> to take the screenshot, compares the took one with the last one, stops qemu,
> sends the last screenshot by email, compresses all took screenshots, goes to
> next VM, so on. (Preferibly without X11 running, as the machine is a mostly
> headless P2P and File server)
I think this can be simplified. Care to send a copy offlist of what
you've done and i'll have a look at it?
--
Dan Shearer
[EMAIL PROTECTED]
ause
that isn't the only bad thing you can do with QEMU as root by accident.
The user's intention can be (more or less) detected with a parameter
like "-force-run-as-root". Since once of QEMU's main points is to avoid
the need f
ively. Here is where things
get hairy: The guest only thinks it's running ring-0 code, but VirtualBox has
fooled the guest OS to instead enter ring 1 (which is normally unused with x86
operating systems).
--- end quote
--
Dan Shearer
[EMAIL PROTECTED]
___
Ok ok, so the list archives give no result for "Virtualbox" and I only
just rejoined... yes I now realise everyone else knwos all about
VirtualBox. Sorry for the noise :-)
--
Dan Shearer
[EMAIL PROTECTED]
___
Qemu-devel mailing list
#x27;s a licensing bug; the Linux kernel module says "GPL2 as per COPYING",
but COPYING is in fact GPL2+.
So far looks like a very tidy piece of work. Now to compile it and try
it out... the debugger looks like it might have a nice id
13 matches
Mail list logo
