Really? Last I knew it would not even run unless it found particular
raid adapters, or a fiber san connection. Must look into it again...
On 08/20/2010 11:58 PM, Christopher A. Williams wrote:
On Fri, 2010-08-20 at 21:24 -0400, Chris Kloiber wrote:
On 08/20/2010 12:15 AM, Christopher A. Willia
On Fri, 2010-08-20 at 21:24 -0400, Chris Kloiber wrote:
> On 08/20/2010 12:15 AM, Christopher A. Williams wrote:
>
> > Otherwise, you need to just run a Type 1 hypervisor, which leaves you
> > with VMware ESXi Free edition. It's limited in what it can do compared
> > to the full version, but it de
On 08/20/2010 12:15 AM, Christopher A. Williams wrote:
Otherwise, you need to just run a Type 1 hypervisor, which leaves you
with VMware ESXi Free edition. It's limited in what it can do compared
to the full version, but it definitely works, and works well.
I haven't looked into that much, but
On Fri, 2010-08-20 at 00:00 -0400, Kevin J. Cummings wrote:
> On 08/19/2010 11:40 PM, Christopher A. Williams wrote:
> > On Thu, 2010-08-19 at 21:50 -0500, Robert G. (Doc) Savage wrote:
> >> Krosh,
> >>
> >> Chris is correct. One of the important library packages (I don't recall
> >> which) changed
On Thu, 2010-08-19 at 21:50 -0500, Robert G. (Doc) Savage wrote:
> Krosh,
>
> Chris is correct. One of the important library packages (I don't recall
> which) changed in F13 and VMware hasn't caught up. You'll be much better
> off choosing an alternative like VirtualBox.
>
Really...? Which libra
On 08/19/2010 11:40 PM, Christopher A. Williams wrote:
> On Thu, 2010-08-19 at 21:50 -0500, Robert G. (Doc) Savage wrote:
>> Krosh,
>>
>> Chris is correct. One of the important library packages (I don't recall
>> which) changed in F13 and VMware hasn't caught up. You'll be much better
>> off choosi
Krosh,
Chris is correct. One of the important library packages (I don't recall
which) changed in F13 and VMware hasn't caught up. You'll be much better
off choosing an alternative like VirtualBox.
--Doc Savage
Fairview Heights, IL
On Thu, 2010-08-19 at 21:50 -0400, Chris Kloiber wrote:
> Use t
Use the following repo, and get VirtualBox-3.2. Free as in beer. For me,
it works well while VMWare does not support F13 (I could not even run
the installer)
# cat /etc/yum.repos.d/virtualbox.repo
[virtualbox]
name=Fedora $releasever - $basearch - VirtualBox
baseurl=http://download.virtualbox.o
Hi guys,
I've installed VMWare and its dependencies ( kernel-headers ). kernel-devel,
kernel-pae-devel and others are installed too, but it keeps asking for
kernel-headers. What path should I put in "Location" field for VMWare to
work?
Thanks
--
users mailing list
users@lists.fedoraproject.org
To
