<br><br><div><span class="gmail_quote">On 8/6/07, <b class="gmail_sendername">Jarom McDonald</b> <<a href="mailto:jarom_mcdonald@byu.edu">jarom_mcdonald@byu.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The problem with Myth in the virtual machine may not be VMWare at all;<br>it may be Vista, which takes an enormous amount of resources. A few<br>things to check:<br>1) make sure that you have the VMWare settings to reserve the entire 1GB
<br>of RAM for the virtual machine. This isn't the default; by default,<br>VMware shares all the memory, so Vista may be hogging too much of it,<br>causing your VM to start swapping.<br>2) Additionally, even if you've got a full 1GB reserved for the virtual
<br>machine, there's also about 100 MB of overhead, so if Vista is left with<br>only 900MB of ram it may be doing some swapping itself, clogging up your<br>disk I/O. Try creating your virtual machine on a separate physical disk,
<br>if that's possible.<br>3) Try it on XP, as others have suggested, which is a far less<br>resource-intensive OS.<br><br>Let me know if your have any luck with Parallels instead. I know that<br>for Mac OS X, it's really a bastardized virtualization option, as it
<br>can't even access both cores of a Duo Core machine. I don't know what<br>its track record on Windows is, though.<br><br>Jarom McDonald<br><br>David Whyte wrote:<br>> On 8/6/07, Matt Emmott <<a href="mailto:memmott@gmail.com">
memmott@gmail.com</a>> wrote:<br>>> I think he's actually rolling back his Vista install to a clean XP install,<br>>> so it might be an option. :)<br>><br>><br>> A couple of points:<br>><br>
> - I had myth running in VMware just fine. Using XP host, Ubuntu 7.04<br>> (pre-release) guest on a 2GHz laptop (old Pentium M chip, not dual<br>> core). I made the move to linux on the laptop though so I blew the
<br>> client away, sorry!<br>> - I don't think winmyth works with the latest version of mythTV. I<br>> never got it to work good *ever* regardless of the mythTV version.<br>> - There was another client called Tapeworm or something. I had some
<br>> good success with that but I have no idea where it is up to now. Try<br>> searching the mailing list for the web page.<br>><br>> HTH's<br>> Whytey<br>> _______________________________________________
<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a></blockquote><div><br>Thanks for all the tips so far. To respond to your emails:<br><br>1 & 2) I've set it to reserve the GB of RAM. The host OS never used more than 1.6GB RAM total, including the VM, which means it never went into true pagefile territory. I'm only on one physical disk, but it is SATA 3 GB/sec. I'll take a look at the disk activity and see if it's really being hammered. I'll probably fire up perfmon and look at the queue length, for starters.
<br><br>3) I don't have the resources to try XP on this machine, without messing with dual booting and the like. Unfortunately it's a Dell machine with no IDE controllers, and both SATA ports are taken up by the disk and DVD drives.
<br><br>I haven't done much testing with Parallels yet, but from what I understand it uses a different hypervisor than VMWare, one that my BIOS supports, so it _should_ be able to access hardware directly. Unfortunately my first load results in Mythdora freaking out and not being able to boot after install. That's on Mythdora
3.2 / FC5, so I'm going to try MythDora 4 / FC 6 tonight and see what happens.<br><br> <br></div><br></div><br>