All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Johansson" <esj@eggo.org>
To: Hans de Goede <hdegoede@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, kvm <kvm@vger.kernel.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: can I make this work… (Foundation for accessibility project)
Date: Thu, 20 Nov 2014 11:28:19 -0500	[thread overview]
Message-ID: <546E16A3.9060608@eggo.org> (raw)
In-Reply-To: <546B5E6F.9030007@eggo.org>


On 11/18/2014 9:57 AM, Eric S. Johansson wrote:
>
> That's great to know. I will spin up a version of Windows 7 and give 
> it a try given that I'm not looking at it, I can strip it down to the 
> barest user interface elements and improve performance significantly.

I tried it and it took me approximately 10 to 12 hours to install 
Windows 7 twice and I didn't even finish installing the last time.

Here's what happened. The first time I installed it, it was a naïve 
install. Took all the defaults just set up the ISO and let the install 
run. Then I installed all the updates. Hours went by and it kind of came 
up and ran but then I tried to install the virt I/O drivers and the 
Windows installation lost its mind. Did some reading on how to make 
performance better and on using the virtio drivers in windows.

So I start of the second install, same size disk 25 GB, same amount of 
RAM, 1 GB and installed the ethernet, disk and balloon drivers at the 
right time. I also changed the cache to none, I/O something to native 
and I think that's about it. Anyway, that was not really any 
improvement. It's still was incredibly slow and this time it was 
complaining about running out of memory and packages install never 
finished. Just kept going and going going.  iptraf reported network io 
ranging from 3kbit to 100kbit range when the updates were running.

I'm accustomed to lesser performance on virtual machines. That's the 
hazard of a running on old and slow laptop  (dell e6400 (2.2ghz core 
duo, 8gb ram)[1]) but even virtual box is not this slow.  So what am I 
doing wrong? It would be nice to use a slow machine like this as many 
handcrips don't have a whole lot of resources for buying newer/faster 
machines. On the other hand, many of them use desktops and work from one 
place whereas someone like me is all over the map (quite literally).

--- eric
[1] Part of the reason I don't bother upgrading machines all that often 
is because it no matter how fast the CPU runs or how much memory I have, 
Windows always runs about the same speed.



  reply	other threads:[~2014-11-20 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  6:48 can I make this work… (Foundation for accessibility project) Eric S. Johansson
2014-11-18 13:50 ` Paolo Bonzini
2014-11-18 13:53   ` Hans de Goede
2014-11-18 14:57     ` Eric S. Johansson
2014-11-20 16:28       ` Eric S. Johansson [this message]
2014-11-20 21:48         ` Paolo Bonzini
2014-11-20 22:22           ` Eric S. Johansson
2014-11-21 14:06             ` Paolo Bonzini
2014-11-21 16:52               ` Eric S. Johansson
2014-11-21 18:22                 ` Paolo Bonzini
2014-11-21 18:24                 ` next puzzle: " Eric S. Johansson
2014-11-21 18:47                   ` Eric S. Johansson
2014-11-18 14:51   ` Eric S. Johansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=546E16A3.9060608@eggo.org \
    --to=esj@eggo.org \
    --cc=hdegoede@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.