Last modified: 2013-09-11 22:45:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T53473, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51473 - Vagrant very slow with two processor setting and IO-APIC conflict
Vagrant very slow with two processor setting and IO-APIC conflict
Status: RESOLVED FIXED
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ori Livneh
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-16 20:41 UTC by spage
Modified: 2013-09-11 22:45 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2013-07-16 20:41:56 UTC
My vagrant instance ran very slowly, 50 seconds to view any page. The vagrant box info in Oracle VM VirtualBox Manager (4.2.10_ubuntu) looks OK, but when I click Settings, it warns

Non-optimal settings detected. ... you have assigned more than one virtual CPU to this VM. This will not work unless the IO-APIC feature is also enabled. This will be done... [when you press OK].

One problem is VBox Manager actually doesn't change this setting if vagrant is running, it can't change it until you run `vagrant halt`.  After halting vagrant, VBox Manager > Settings does update it, and thereafter Vagrant runs about 9x faster!

Ori asked me to report a bug, mentioning that the Vagrantfile sets
   vb.customize ['modifyvm', :id, '--cpus', '2']

My Vagrant instance is months old, maybe this IO-APIC conflict doesn't occur any more.  If it does, perhaps this line should be commented out and users should be recommended in installation instructions to review settings in VirtualBox Manager.  I added a section https://www.mediawiki.org/wiki/MediaWiki-Vagrant/Troubleshooting#If_vagrant_is_slow
Comment 1 Matthew Flaschen 2013-07-16 21:18:48 UTC
Mine was re-created much more recently (maybe a week or so ago).  I haven't really noticed performance problems, but then again, I have nothing much to compare to.

When I opened VirtualBox, it showed 2 processors, but warned me that I had to check IO-APIC for that to take effect.  It seems IO-APIC should be automatically enabled by MediaWiki-Vagrant, or it should use 1 processor (it doesn't seem like it really uses 2 otherwise).
Comment 2 Gerrit Notification Bot 2013-07-16 21:20:10 UTC
Change 74061 had a related patch set uploaded by Ori.livneh:
Enable I/O APIC

https://gerrit.wikimedia.org/r/74061
Comment 3 Matthew Flaschen 2013-07-16 22:57:22 UTC
It actually is supposed to use IO-APIC regardless of the guest processor count, because it is 64-bit.  That's what the latest changeset does.  See http://www.virtualbox.org/manual/ch03.html#intro-64bitguests

See also https://bugs.launchpad.net/ubuntu/+bug/1201983 , an Ubuntu bug about the same thing.
Comment 4 Gerrit Notification Bot 2013-07-17 05:08:08 UTC
Change 74061 merged by jenkins-bot:
Enable I/O APIC

https://gerrit.wikimedia.org/r/74061
Comment 5 Andre Klapper 2013-09-11 22:45:35 UTC
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links