Re: [Qemu-devel] qemu-arm user mode
> 1) Paul's patch for NLS. You mean TLS and/or NPTL. NLS is something completely different :-) Paul ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu/target-i386 helper.c
>> Then lots of 'timeout: reset bus, target=0, lun=0' and other warnings >> with: >> >> Error for command 'read sector' Error Level: informational >> Sense Key: aborted command >> Vendor 'Gen-ATA' error code: 0x3 > > That's a new problem. It seems that the updated bios.bin doesn't setup > the ide disk for DMA mode any more, or something like that. I'm seeing > the same problem after a qemu cvs update. When I replace > qemu/share/qemu/bios.bin with an older version the problem is gone. You could also try adding '-B ata-dma-enabled=0' to boot the kernel as another alternate workaround. The Solaris ATA driver assumes that all devices of ATA4 or greater support and are configured for DMA. - Eric ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu-arm user mode
I have now managed to run a null program and a helloworld, (both eabi, linked statically, and without any thread calls), using the qemu-arm user mode, both inside and outside of scratchbox. To do this with qemu-0.8.2 I needed the following: 1) Paul's patch for NLS. http://lists.gnu.org/archive/html/qemu-devel/2006-09/msg00194.html Note that you will need to remove your object directory, reconfigure, and rebuild after patching. The patch changes configuration data which will not be updated from a simple rebuild so you will need to remove your object and reconfigure before building again. I didn't notice and this held me up for several days. 2) to build a qemu that can be debugged, you'll need to build it statically. To do this, you can configure qemu using "--static". 3) qemu cannot be built with gcc-4, (due to a problem I don't understand), nor with gcc-3 using -O0, (due to an apparent collision between register allocation and inlining). You'll need to use a gcc-3, with at least -O1 if you want to debug. I changed the -O values by editing the Makefiles directly, but this change isn't really necessary if you don't plan to debug qemu. 4) Configure using "--enable-uname-revision=2.6.16". Paul partially explained this recently. Glibc, (the one your target program linked against when it was compiled), runs a check to see what kernel version it's running over. When qemu-user emulates this call, by default, it asks the underlying host kernel what version the underlying host kernel is and then tells gdb that the emulated kernel version is the same. While there's an argument that this is reasonable, in the case of arm eabi, it's a problem for many people. Since eabi support was only added to the kernel in 2.6.16, earlier kernels can't handle eabi kernel calls. Glibc knows this and will fail out if it believes itself to be running on an older kernel. The fix, then, is to either run qemu-arm with the command line option, "-r 2.6.16" or to configure using "--enable-uname-revision=2.6.16" which will ask qemu to simply report these version numbers rather than querying the underlying host kernel. (Note: if your underlying (x86) host kernel happens to be 2.6.16 or later, then you probably don't need this workaround.) None of these are new issues or fixes. It just took me a few days to collect, run into them, and sort through them all. So I'm posting my results here. --rich ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] windows compile error fix
--- /d/qemu/block-raw.c Mon Oct 2 13:55:48 2006
+++ block-raw.c Mon Oct 2 13:42:55 2006
@@ -1134,6 +1134,10 @@
{
}
+void qemu_aio_flush(void)
+{
+}
+
void qemu_aio_wait_start(void)
{
}
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Brad Cambell's -no-reboot patch.
On Mon, 2006-10-02 at 13:21 -0700, Luke Crawford wrote: > what needs to happen to get this patch committed? I think it was just committed to CVS if I'm not mistaken. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Brad Cambell's -no-reboot patch.
Hi, On Mon, 2 Oct 2006, Luke Crawford wrote: > re-sending because I wasn't paying attention and posted this as a reply to > another thread. sorry. No need to. It has just been applied. Ciao, Dscho ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Brad Cambell's -no-reboot patch.
re-sending because I wasn't paying attention and posted this as a reply to another thread. sorry. -- I have a client that has an existing systemimager infrastructure management system; I am helping them virtualize their computer systems using Xen. The version of systemimager they use uses a heavily modified 2.4 linux kernel on a floppy to boot new computers. I set them up with QEMU to do the same thing from the dom0 to install domUs. (that is, they run qemu in the master (driver) domain, and it installs into the unprivileged domain, or the virtual server) The problem is that once the install finishes, the system reboots; the idea being that with the floppy, you boot and then take the floppy out, and the system reboots into the installed system. With qemu, this just infinitely loops. (I'm sure this could be fixed in systemimager, but frankly I am more comfortable playing with qemu than with systemimager.) Anyhow, I did some googling, and found Brad Cambell's -no-reboot patch, and it solves the problem nicely. http://www.mail-archive.com/qemu-devel@nongnu.org/msg06327.html the patch applies cleanly to the current stable qemu release, but it sure would be nice if it were included in the base qemu distribution; most of my clients are a little uncomfortable compiling their own software, and patch is right out. What needs to happen to get this patch committed? I'd be willing to spend some time on it if required. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] qemu qemu-doc.texi vl.c
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/10/02 19:44:22 Modified files: . : qemu-doc.texi vl.c Log message: no-reboot option CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/qemu-doc.texi?cvsroot=qemu&r1=1.110&r2=1.111 http://cvs.savannah.gnu.org/viewcvs/qemu/vl.c?cvsroot=qemu&r1=1.216&r2=1.217 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Brad Cambell's -no-reboot patch.
I have a client that has an existing systemimager infrastructure management system; I am helping them virtualize their computer systems using Xen. The version of systemimager they use uses a heavily modified 2.4 linux kernel on a floppy to boot new computers. I set them up with QEMU to do the same thing from the dom0 to install domUs. (that is, they run qemu in the master (driver) domain, and it installs into the unprivileged domain, or the virtual server) The problem is that once the install finishes, the system reboots; the idea being that with the floppy, you boot and then take the floppy out, and the system reboots into the installed system. With qemu, this just infinitely loops. (I'm sure this could be fixed in systemimager, but frankly I am more comfortable playing with qemu than with systemimager.) Anyhow, I did some googling, and found Brad Cambell's -no-reboot patch, and it solves the problem nicely. http://www.mail-archive.com/qemu-devel@nongnu.org/msg06327.html the patch applies cleanly to the current stable qemu release, but it sure would be nice if it were included in the base qemu distribution; most of my clients are a little uncomfortable compiling their own software, and patch is right out. What needs to happen to get this patch committed? I'd be willing to spend some time on it if required. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] qemu/pc-bios bios.diff bios.bin
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/10/02 18:35:39 Modified files: pc-bios: bios.diff bios.bin Log message: do not generate MP table if one CPU (no APIC in QEMU in this case) - added wbinvd (ignored in QEMU but useful on real hardware) CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/pc-bios/bios.diff?cvsroot=qemu&r1=1.15&r2=1.16 http://cvs.savannah.gnu.org/viewcvs/qemu/pc-bios/bios.bin?cvsroot=qemu&rev=1.18 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] qemu/hw acpi.c
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/10/02 18:25:40 Modified files: hw : acpi.c Log message: SMI enable bit support CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/hw/acpi.c?cvsroot=qemu&r1=1.6&r2=1.7 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] qemu kqemu.c
CVSROOT:/sources/qemu Module name:qemu Changes by: Fabrice Bellard06/10/02 17:58:33 Modified files: . : kqemu.c Log message: 32 bit syscall fix (Juergen Keil) CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/kqemu.c?cvsroot=qemu&r1=1.12&r2=1.13 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu/target-i386 helper.c
> > Try to boot with the kernel debugger enabled, so that you can read > > the panic message (I guess it reboots because of a panic). > > D'oh, I should have known that ;). It's not able to mount root. One > thing it says on IDE init is: > > ata_set_feature: (0x66,0x0) failed Harmless. > Then lots of 'timeout: reset bus, target=0, lun=0' and other warnings > with: > > Error for command 'read sector' Error Level: informational > Sense Key: aborted command > Vendor 'Gen-ATA' error code: 0x3 That's a new problem. It seems that the updated bios.bin doesn't setup the ide disk for DMA mode any more, or something like that. I'm seeing the same problem after a qemu cvs update. When I replace qemu/share/qemu/bios.bin with an older version the problem is gone. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu/target-i386 helper.c
On Mon, 2 Oct 2006, Juergen Keil wrote: ... seems to indicate that it is trying to find an unused portion of 256 bytes of I/O space (for the NIC (?) at pci bus/device/func 0/3/0, according to the command "info pci" in qemu's monitor), and has failed. Yeah, seems to be for the NIC. I also get this warning from time to time. Sometimes the reason is that clock is "stalled", sometimes it has "skipped". Ditto. It seems to be a harmless warning, though. Try to boot with the kernel debugger enabled, so that you can read the panic message (I guess it reboots because of a panic). D'oh, I should have known that ;). It's not able to mount root. One thing it says on IDE init is: ata_set_feature: (0x66,0x0) failed Then lots of 'timeout: reset bus, target=0, lun=0' and other warnings with: Error for command 'read sector' Error Level: informational Sense Key: aborted command Vendor 'Gen-ATA' error code: 0x3 Is that the host OS or the guest OS? SNV as guest. Are you running qemu or qemu-system-x86_64? 32bit Qemu. With or without kqemu? Without. Are you trying to install open solaris, or are you trying to boot from an installed qemu hdd image? I had installed it with qemu from a few weeks ago (or maybe 0.8.2 release - sorry, can't remember). Something very recent in CVS seems to have broken booting it. There shouldn't be any difference between install and boot really. I'm using a raw block device as Qemu 'hda'. I'll try dig further. regards, -- Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 64A2FF6A Fortune: "I shall expect a chemical cure for psychopathic behavior by 10 A.M. tomorrow, or I'll have your guts for spaghetti." -- a comic panel by Cotham ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] hosting the forum
Hi, It really depends if this is a shared host or a dedicated host. The previous QEMU forum was hosted on a shared host and the response time was awfully slow. Furthermore, you'll need MySQL 3.x (thats what I have on the server) and a bit knowledge of PHPBB in order to modify the configs to setup things correctly. The speed access from here (Israel) seems to be very good to your site. Thanks, Hetz On 10/2/06, Damien Mascord <[EMAIL PROTECTED]> wrote: Hetz Ben Hamo wrote: > Hi, > > Due to some personal problems (related to financial situations) I'm no > longer being able to keep paying the server which hosts the QEMU > forum. > > Therefore, I'm looking for someone who can host the QEMU forum (and, > if possible, the nightly snapshots). If anyone would want to host it, > please contact me offline. > > Thanks, > Hetz Hi Hetz, I would be more than willing to host it. Would the latency/transfer rate to http://node6503.gplhost.com be OK for most people? Cheers, Damien ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Visit my blog (hebrew) for things that (sometimes) matter: http://wp.dad-answers.com ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] hosting the forum
Hetz Ben Hamo wrote: Hi, Due to some personal problems (related to financial situations) I'm no longer being able to keep paying the server which hosts the QEMU forum. Therefore, I'm looking for someone who can host the QEMU forum (and, if possible, the nightly snapshots). If anyone would want to host it, please contact me offline. Thanks, Hetz Hi Hetz, I would be more than willing to host it. Would the latency/transfer rate to http://node6503.gplhost.com be OK for most people? Cheers, Damien ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] hosting the forum
Hi, Due to some personal problems (related to financial situations) I'm no longer being able to keep paying the server which hosts the QEMU forum. Therefore, I'm looking for someone who can host the QEMU forum (and, if possible, the nightly snapshots). If anyone would want to host it, please contact me offline. Thanks, Hetz -- Visit my blog (hebrew) for things that (sometimes) matter: http://wp.dad-answers.com ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu/target-i386 helper.c
> On Fri, 29 Sep 2006, Fabrice Bellard wrote: > > > Log message: > > 32 bit RSP update fix (aka Open Solaris x86_64 bug) > > I've been getting the following errors the last while. > > Very early in kernel init: > > WARNING: failed to program IO space [0/3/0] [EMAIL PROTECTED] length 0x100 I've not yet seen this. A quick look at the source... http://cvs.opensolaris.org/source/xref/on/usr/src/uts/i86pc/io/pci/pci_boot.c#12 41 ... seems to indicate that it is trying to find an unused portion of 256 bytes of I/O space (for the NIC (?) at pci bus/device/func 0/3/0, according to the command "info pci" in qemu's monitor), and has failed. > Later: > > WARNING: Time of Day clock error: reason [Stalled]. -- Stopped tracking Time of Day clock I also get this warning from time to time. Sometimes the reason is that clock is "stalled", sometimes it has "skipped". It seems to be a harmless warning, though. > Solaris then reboots itself before (AIUI) starting userspace. Try to boot with the kernel debugger enabled, so that you can read the panic message (I guess it reboots because of a panic). In the GRUB boot menu, type "e" twice to edit the boot commands, and add options "-kv" at the end of the "kernel" command line. and "b" boots with the kernel debugger and verbose kernel messages enabled. > This is with SNV_46 and with a fresh Qemu from CVS about 30 minutes > ago. Is that the host OS or the guest OS? Are you running qemu or qemu-system-x86_64? With or without kqemu? Are you trying to install open solaris, or are you trying to boot from an installed qemu hdd image? ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
