quite impossible: the hardware inside qemu guest would be different
with the real hardware of the laptop.
worst case: error 7b and blue screen. it will not go further, and it
means you need to reinstall everything.
best case: it moves further in safe mode, but then you'll need the
xp cdrom for
Embedded PowerPC have the need of implementing 3 timers in the core
area:
- a fixed interval timer
- a programable interval timer
- a watchdog timer
Those 3 timers are fully independant and can raise different exceptions
(eventually at the same time). For this reason, they cannot be
implemented
It appears that some targets may need more than the 2 standard
execution modes.
For example, PowerPC 64 has 3 execution modes: hypervisor, supervisor
and problem state.
Another example is alpha which has 4 execution modes (even if Linux
seems to use only two of them).
My proposal is to increase
On 3/25/07, Christian MICHON [EMAIL PROTECTED] wrote:
On 3/26/07, Kyle Hubert [EMAIL PROTECTED] wrote:
Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
having 1600x1200 working in the virtual machine, so I looked at using
the -std-vga option with the vesa X driver.
While
It does work in cirrus mode for 1024x768. I was under the impression
that it was all the cirrus driver would support. However, the std-vga
mode supports vga 799 and 798 in the console. (1600x1200:24bpp and
1600x1200:16bpp respectively)
Here is the output from dmesg showing the console working:
On 3/26/07, Kyle Hubert [EMAIL PROTECTED] wrote:
It does work in cirrus mode for 1024x768. I was under the impression
that it was all the cirrus driver would support. However, the std-vga
mode supports vga 799 and 798 in the console. (1600x1200:24bpp and
1600x1200:16bpp respectively)
The X
1) go into the monitor of qemu (ctrl-alt-2)
2) key in:
sendkey ctrl-alt-f1
3) go back to the emulated screen (ctrl-alt-1)
it should have swapped back to text mode.
sorry for the late reply, but your email just made it now
to the mailing list.
On 3/14/07, Halim Sahin [EMAIL PROTECTED] wrote:
you could use sendkey in the monitor console of qemu.
This is the only way on xp host to send a ctrl-alt-delete to
a xp guest to login...
On 2/10/07, Georg Schlomka [EMAIL PROTECTED] wrote:
Hi!
We use Qemu un an Ubuntu host and want to run XP guests. No problems
there. But the most important
no obvious problem in the xf86config file.
when all fails, use the framebuffer :) and Xfbdev (fbdev driver instead
of vesa)
The framebuffer seems to miss every other vertical scan line. I'm not
sure if I make sense, but the video wraps around the screen onto
itself vertically. Thus rendering
J. Mayer wrote:
It appears that some targets may need more than the 2 standard
execution modes.
For example, PowerPC 64 has 3 execution modes: hypervisor, supervisor
and problem state.
Another example is alpha which has 4 execution modes (even if Linux
seems to use only two of them).
My
On 3/26/07, Kyle Hubert [EMAIL PROTECTED] wrote:
I tried using the newer video appendage and it didn't seem to work. I
had to use the older vga=. I believe you are talking about the kernel
boot param, yes?
yes. normally the vesafb-tng is supposed to address missing functions
or resolutions of
Am Sat, 24 Mar 2007 12:55:16 +
schrieb Julian Seward [EMAIL PROTECTED]:
The problems of the gcc backend to qemu have already been discussed
extensively on this list. Stealing 3+ registers from gcc on x86 really
is asking for trouble, and I believe it is generally understood that the
The Intel manual states for LTR and 64-Bit Exceptions:
#GP(selector)
If the descriptor type of the upper 8-byte of the 16-byte descriptor
is non-zero.
Qemu currently does not check this. The attached patch fixes the bug.
Bernhard Kauer
--- helper.c.orig 2007-03-26
Does this fix some specific bug you encountered?
J
On Monday 26 March 2007 14:53, Bernhard Kauer wrote:
The Intel manual states for LTR and 64-Bit Exceptions:
#GP(selector)
If the descriptor type of the upper 8-byte of the 16-byte descriptor
is non-zero.
Qemu currently
On Mon, Mar 26, 2007 at 01:54:43PM +, Julian Seward wrote:
Does this fix some specific bug you encountered?
I have some code here that runs on Qemu but not on real hardware
due to this missing check.
Bernhard
On Monday 26 March 2007 14:53, Bernhard Kauer wrote:
The Intel manual
By now (more than two months after I sent it) this patch is less relevant, as
it is already included in Anthony's updated qemu-live-migration patch.
Is live migration going to be accepted soon ?
Regards,
Uri.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Uri Lublin
Sent:
Hi Avi,
On Sunday 25 March 2007 15:40, Avi Kivity wrote:
Axel Zeuner wrote:
A full featured converter (cvtasm) has a lot of dependencies: it has to
support all hosts (M) (with all assembler dialects M') and all targets N,
i.e. in the worst case one would end with M'x N variants of it, or M
Hi
I intend to extract program counter streams from QEMU as a program executes.
Can you please point me to the hooks that I may have to insert into the QEMU
source code in order to extract the PC values?
Also, since I'm new to QEMU, I'd appreciate if somebody can point me to some
documents
Hi,
On 26/03/07, Anthony Liguori [EMAIL PROTECTED] wrote:
andrzej zaborowski wrote:
Hi, sorry for late reply.
On 21/03/07, Anthony Liguori [EMAIL PROTECTED] wrote:
Do you think using the SDL cursor is all that useful? As soon as gtk
widgets get involved, the cursor becomes ARGB so in
Hi,
File eepro100.tar.bz2 (added to this mail) contains everything
needed to add 3 new PCI network device (all similar to EEPRO100):
eepro100.patch:
Makefile.target:
added two binaries needed for EEPRO100
split entries for PCI network devices (1 line / entry, better
merging
On 26/03/07, Marc Lörner [EMAIL PROTECTED] wrote:
On Monday 26 March 2007 00:08, andrzej zaborowski wrote:
On 26/03/07, andrzej zaborowski [EMAIL PROTECTED] wrote:
snip
+# warning non-optimized CPU
+#include sys/time.h
+#include time.h
+
static inline int64_t cpu_get_real_ticks
I don't have the current source repository, I'm running off of the
0.9.0 source release. However, I felt that there was a bug with having
the VM in fullscreen mode and still allowing the ctrl-alt modifiers to
release the mouse. With SDL, this is rather useless and only requires
the user to grab
Hi,
kqemu doesn't trap the rdtsc instruction for performance reasons.
This is mostly okay on a uniprocessor host, but on a dual core CPU
there are effectively two TSCs and there's no warranty that they are
in sync. On my Linux desktop there happens to be about 17 seconds
difference between
I moved to helper2.c because AFAICT helper.c is compiled with the same
sort of restrictions as op.c which leads to the compile failure.
Yes, helper.c is compiled with the global register variables and the code
is called directly from the op_xxx functions, but one needs the global
register
If you've been running QEMU on SPARC Solaris 10 and using it for anything
including RTEMS development, you can now upgrade to the latest, bleeding
edge build of QEMU 0.9.0
http://www.thoughtwave.com/downloads.html
Have fun!
Jonathan
--
--
Jonathan Kalbfeld
+1 323 620 6682
Hi Paul,
On Tuesday 27 March 2007 00:53, Paul Brook wrote:
I moved to helper2.c because AFAICT helper.c is compiled with the same
sort of restrictions as op.c which leads to the compile failure.
Yes, helper.c is compiled with the global register variables and the code
is called
On Monday 26 March 2007 22:37, andrzej zaborowski wrote:
On 26/03/07, Marc Lörner [EMAIL PROTECTED] wrote:
On Monday 26 March 2007 00:08, andrzej zaborowski wrote:
On 26/03/07, andrzej zaborowski [EMAIL PROTECTED] wrote:
snip
+# warning non-optimized CPU
+#include sys/time.h
27 matches
Mail list logo
