id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 3523,"SATA (ncq?) timeouts. works, then suddenly ceases: hangs guest.",Antryg Revok,,"VirtualBox 2.1.4, openSUSE 11.0 host, Gentoo AMD64 guest, no guest additions yet because I haven't got far enough in the Gentoo install to be able to boot into the guest directly. When I tried unpacking the portage tgz, it'd go for awhile ( seconds ), then suddenly hang. The error message was timeouts, and alternated between lines ending in ""ncq"" and lines ending in ""DRDY"". Remembering that the documentation had said that SATA shouldn't be relied-on, I tried again with a boot disk of IDE type ( lspci shows that SATA is likely to be *drastically* faster than IDE: SATA can move 8k per get/put, whereas IDE moves only a few bytes, it seems ) IDE works, but if IDE emulation is speed-crippled, and I'm needing a virtual machine for *video editing* then either I gotta get that fixed, or I gotta get that fixed, if you know what I mean. Current Host: AMD64 x2, 1GHz, 4GB, Raptor, ext3. Current Guest settings: 1 core ( I've no idea how to set this: NO documentation on it? ) 2560MB 128MB video CD, HD ACPI enabled IO APIC enabled AMD-V enabled 3D acceleration enabled ( at least it would be, if guest additions get installed ) VMDK 8GB ( 2GB swap, 6.whatever GB / ) ALSA/ICH PCnet-FASTIII no cereal ports 1 shared folder, that will work later when guest additions get in... no remote display. BTW, the *reason* I'm installing Gentoo is simple: repeated installation of MS Windows requires calling MS to explain oneself to 'em. I don't have a phone, nor do I ever want one again ( silence is glorious -- meditation & training are much easier without being continually interrupted ) Therefore, it makes sense to discover all the bugs & blockers, and their workarounds, *before* installing the OS I *have* to run in a virtual machine. ata1.00: status: { DRDY } ata1.00: cmd 64/20..stuff..changes..data?../40 tag 30[increases] ncq -number- -in||out- res 40/00:00:00:00:00...etc...00:00/00 Emask 0x4 (timeout) ACPI shutdown hangs, of course so killing the thing with the Big Red Switch becomes necessary... last line displaying is * Stopping syslog-ng ... Machine/Close hangs, destroying VirtualBox's windows ( the rectangles are still there, but they're blank ) using KDE to kill the machine window, now VirtualBox ( no longer blank ) says Gentoo was ""aborted"" BTW, seeing AMD Athlon on a 440FX is -shudder- odd... As an aside, SOMETHING in VirtualBox is deciding how many CPUs to present to the guest, but I can't find *any* indication of how to control that in the documentation, or through the VirtualBox.org search, and the Help section isn't a help-section, it's a Trac install that doesn't have any content except for the Trac help ( maybe it was intended that the Help section of VirtualBox.org be help for the Trac system, but if so, then where's the VirtualBox Help section? peculiar user-interface/information-design ) If someone could please document, in the manual, simply & quickly, how to set the number of presented CPUs, so one doesn't get hit with stupid Re-register Windows Or Else scenarios when one upgrades the CPU, or something? I dearly want this project to be the most configurable, fastest, solidest, and best, so I'll help however I can, but I can't code, so pls keep any requests simple and sysadmin-ey, eh? :)",defect,closed,other,VirtualBox 2.1.4,fixed,sata timeout hang crash,,Linux,Linux