Eric Lowe wrote: > Roland Mainz wrote: > > problem more closely because both QEMU and VMware suffer from extensive > > performace problems (contributing a lot to install times of more than 40 > > hours on QEMZ/AMD64 (the native machine is an Intel P4M 2GHz laptop with > > 2GB main memory)) when running Solaris while SuSE Linux 10.0 and 10.1 > > just work fine... > > QEMU 0.8.2 doesn't support ATAPI DMA but the latest CVS sources do, so > I'm trying those now. In the end I suspect the solution will be 'use the > latest qemu so DMA works' instead of trying to workaround this in the > driver. > > I'm still curious why the ATA driver is this way. The BSD ATA driver > still uses the capability bits, so FreeBSD figures out there isn't DMA > support and just works. > > As far as the install times, I think you'll see it is a lot better with > the kernel accelerator module. I just installed Ubuntu Dapper Drake > under QEMU on my AMD64 machine and it took about 20 minutes. I'm hoping > we can get the OpenSolaris accelerator into the next kqemu release.
What about security in this case ? Does the kernel accelerator module execute any native code within the kernel context ? > DMA works fine for me under VMWare, which supports UDMA2 for the CD-ROM, > though it still took a couple of hours to install SXCR 44 for me (1.5GHz > Pentium-M). It certainly wasn't on the order of 40 hours... Please correct me if I am wrong: I cannot use the kernel accelerator module for AMD64 on a 32bit x86 CPU, right ? The problem is that AFAIK the kernel accelerator works similar to VMware - it parses the code and intercepts/rewrites some commands to call the emulation layer but mainly executes the code natively. I've seen the 40h+ install time because I was using QEMU/AMD64 on a 32bit machine in the normal, "unaccerlated" interpreter mode AND QEmu suffers extensively from bugs in the ATA driver, kernel and other parts of Solaris. Examples include busy-loops after starting DMA, that the kernel doesn't call the x86 "HTL" instruction (which can damage emulator performance a lot - normal hardware just stops any execution until the next interrupt is hit, but an emulator than stops interpreting of the native instructions and does other stuff (including looking at I/O registers MUCH earlier (this is also a problem on laptops because it wastes energy))) very often and that Solaris has insane memory consumtion (or better: The "working set" during several 5-15min samples showed that the working set is sometimes beyond 100MB and that more or less kills emulator performance, too (unless the underlying host system has enougth spare bandwidth)) during install time (who had the idea to run JAVA duing installation ?!) ... At some point I really really wish Sun would allow others to ship preinstalled Solaris Nevada disk images for VMware (QEmu and other emulators understand that disk format, too). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
