On 8/1/05, Mars G. Miro <[EMAIL PROTECTED]> wrote:
> On 7/30/05, Mars G. Miro <[EMAIL PROTECTED]> wrote:
> > On 7/30/05, Jung-uk Kim <[EMAIL PROTECTED]> wrote:
> > > Okay. I finally found a fix. It was actually quite simple. Newer
> > > FreeBSD and Linux ATA drivers check whether the PCI ATA co
On 7/30/05, Mars G. Miro <[EMAIL PROTECTED]> wrote:
> On 7/30/05, Jung-uk Kim <[EMAIL PROTECTED]> wrote:
> > Okay. I finally found a fix. It was actually quite simple. Newer
> > FreeBSD and Linux ATA drivers check whether the PCI ATA controller is
> > in legacy ATA mode (aka PATA mode). The t
I've used both -hda /dev/sda and -hdc /dev/sda for
booting from and just accessing a flashdrive
respectively on linux. Probably -hdc \\.\E: would
work for accessing the flashdrive from qemu running on
MS
Regards,
Brad Watson
__
Hi there...
This is probably already in the works, but just in case it hadn't been reported
yet, I think the latest versions of "windows qemu" and "windows kqemu" may be
out of sync.
Using qemu 0.7.1-3 from:
http://qemu.dad-answers.com/download/win32/
and the latest kqemu I could find...
On Wednesday 27 July 2005 15:00, [EMAIL PROTECTED] wrote:
> Your membership in the mailing list Qemu-devel has been disabled due
> to excessive bounces The last bounce received from you was dated
> 13-Jul-2005. You will not get any more messages from this list until
> you re-enable your membership
At 17:25 +0200 2005-07-31, Rudi Lippert wrote:
Looks like there really is an SDL problem. I'm not capable of writing a test
program, but I tried sdlroids. It hangs in status S+ right after starting
it.
After I found out about this, I rebuilt libsdl (Gentoo package), but it
didn't help.
What's nex
Hi,
On Sun, 31 Jul 2005, Rudi Lippert wrote:
> Looks like there really is an SDL problem. I'm not capable of writing a test
> program, but I tried sdlroids. It hangs in status S+ right after starting
> it.
> After I found out about this, I rebuilt libsdl (Gentoo package), but it
> didn't help.
>
> Mark Williamson wrote:
> > If only one machine (host or guest) has mounted the device then it should
> > always be safe to do this. You may get away with read only mounting in
> > one and writing in the other but it's not a reliable solution. Never
> > allow more than one writer to the filesyst
Mark Williamson wrote:
If you're using a file-based disk and it's partitioned you'll need to use
lomount http://www.dad-answers.com/qemu/utilities/QEMU-HD-Mounter/lomount/ to
mount the right partition in the host.
this works great for some of the partitions but not the last one. For
some rea
On 31/07/05, Rudi Lippert <[EMAIL PROTECTED]> wrote:
> Hey!
> Looks like there really is an SDL problem. I'm not capable of writing a test
> program, but I tried sdlroids. It hangs in status S+ right after starting
> it.
> After I found out about this, I rebuilt libsdl (Gentoo package), but it
> di
Hey!
Looks like there really is an SDL problem. I'm not capable of writing a test
program, but I tried sdlroids. It hangs in status S+ right after starting
it.
After I found out about this, I rebuilt libsdl (Gentoo package), but it
didn't help.
What's next?
Johannes Schindelin wrote:
> Hi,
>
> O
> one more question on this theme. How do I know when the guest OS has
> finished booting? The reason I ask is I am planning on using ssh to
> perform various operations on the guest OS once it's up.
Just like a real machine, you don't. You need to configure the guest to tell
the host when it's
Hi,
On Sun, 31 Jul 2005, Rudi Lippert wrote:
> Is there anything else that might help understanding the problem?
Do you have other programs running, which use SDL? Sorry, the configure
output does not help here.
> Btw: Qemu is not even taking up CPU.
That's right. It hangs in a select() when w
Mark Williamson wrote:
If only one machine (host or guest) has mounted the device then it should
always be safe to do this. You may get away with read only mounting in one
and writing in the other but it's not a reliable solution. Never allow more
than one writer to the filesystem - this does
I'm trying to boot the latest Darwin (8.0.1) as guest of a qemu 0.7.1
(with kqemu 0.7.1-1) running on a FC4 (AMD Athlon 2600+). The guest
hangs right after booting, on a blank screen on graphics mode or at
Starting Darwin/x86
while on text mode. Any ideas?
__
Thanks for your reply.
I only created the bt because someone said it might help.
configure output looks fairly good to me, but I don't know much about those
things.
Is there anything else that might help understanding the problem?
Btw: Qemu is not even taking up CPU.
Install prefix/usr
BIOS d
Hi,
actually it looks more like the program was compiled with
"-fomit-frame-pointer". For that reason, you only get correct names (and
EIPs) for library calls.
Since QEmu uses as many physical registers as it can get, it is sensible
to omit the frame pointer, because it has no meaning anyway once
On Sunday 31 July 2005 13:47, Rudi Lippert wrote:
> Should a qemu backtrace be 411 lines long?
> Actually, when I start qemu 0.7.1 (kqemu enabled, but makes no difference),
> it doesn't do anything. I hit CTRL-C to get a backtrace of the situation.
> Qemu has never worked on this setup, and the pro
Should a qemu backtrace be 411 lines long?
Actually, when I start qemu 0.7.1 (kqemu enabled, but makes no difference),
it doesn't do anything. I hit CTRL-C to get a backtrace of the situation.
Qemu has never worked on this setup, and the problem has always been the
same.
Any ideas?
Cheers,
Rudi
Hi,
What do you think about checking if a VGA bios was found (and if so, if
it has a valid size)?
Reasoning is that on pristine machines (i.e. without a VGA bios ROM
available) starting qemu fails without giving any helpful error message.
I'm attaching a simple patch which adds such a check.
Co
Hi,
- fix some commentary typos in exec.c.
Thank you,
Bernhard
diff -X excl -rduNp qemu.oorig/exec.c qemu/exec.c
--- qemu.oorig/exec.c 2005-07-28 17:54:37.0 +0200
+++ qemu/exec.c 2005-07-31 13:30:30.0 +0200
@@ -2168,7 +2168,7 @@ void cpu_physical_memory_rw(target_phys_
targ
Hi,
On Sun, 31 Jul 2005, Mark Williamson wrote:
> If only one machine (host or guest) has mounted the device then it should
> always be safe to do this. You may get away with read only mounting in one
> and writing in the other but it's not a reliable solution.
You almost certainly get not away
Add: clock=pit
to the fedora core GRUB kernel boot parameters .
Hetz
On 7/31/05, Mulyadi Santosa <[EMAIL PROTECTED]> wrote:
> Hello everybody
>
> Yesterday I tried to install Fedora Core 2 guest using qemu 0.7.1 (no
> kqemu) on top of FC 2 host. Both guest and host are running 2.6.5-1.358
> (the
On 31/07/05, Mulyadi Santosa <[EMAIL PROTECTED]> wrote:
> Hello everybody
>
> Yesterday I tried to install Fedora Core 2 guest using qemu 0.7.1 (no
> kqemu) on top of FC 2 host. Both guest and host are running 2.6.5-1.358
> (the default kernel of FC2). I experienced slower boot speed and slower
>
Hello everybody
Yesterday I tried to install Fedora Core 2 guest using qemu 0.7.1 (no
kqemu) on top of FC 2 host. Both guest and host are running 2.6.5-1.358
(the default kernel of FC2). I experienced slower boot speed and slower
keyboard typing (the delay between a key a pressed and the actual
You can probably also set up an ftp or smb (via Samba) server to
transfer files within the guest OS. HTTP should also work with
Apache, but remember the protocol wasn't originally designed for
uploads, and not all clients (eg, web browsers) support it.
--
Mike
__
26 matches
Mail list logo
