Oh, Qemu performance is horrible, I don't know if there is any work being
done to make kqemu work, but I just use it more as a proof of concept, if
your wanting to run VM's for performance, this is not the route to go,
IMO...
J
On Tue, Feb 2, 2010 at 10:48 AM, Bryan <brakeb@gmail.com> wrote:
quoted text > On Tue, Feb 2, 2010 at 11:09, Vijay Sankar <vsankar@foretell.ca> wrote:
> >
> > I was running three instances of Windows 2000 Server and one Windows 2003
> > server on a Dell 2900 -- two IIS servers, and two SQL Servers for testing
> > purposes a while ago. Here is some info on how I was doing it at that
> time
> > --
> >
>
> > Each vm guest was started with a command similar to the following:
> >
> > sudo env ETHER=bnx1 qemu \
> > -net nic,vlan=0,model=rtl8139,macaddr=AA:BB:CC:DD:EE:XX \
> > -net tap,vlan=0 -m 384 -no-fd-bootchk -localtime \
> > -hda whatever.img -nographic
> >
> > XX was F1, F2, F3, and F4 w2k3, w2k, appint and appext images
> respectively
> >
> > I used nographic because it was easier to use rdesktop and rdp from other
> > systems to access the vm guests instead of being at the console.
> >
>
> Do you notice any performance gains by running them like this? I'm
> running one instance of XP on a dual-core box with 4GB of RAM, and
> it's slow as hell. I'd try running Windows 7, but the ACPI fails, and
> I can't allocate 1GB of RAM with the version we have in ports to do
> the initial install.
