On 02/18/2014 03:46 PM, Dan Mossor wrote:
>
> However, everything would be much simpler if virt-manager wouldn't wig out on
> us when trying to create a bridge with it...
>
virt-manager 1.0.0 in updates-testing should fix a few issues with creating
bridge devices. Please try that version, and if
On 02/17/2014 10:32 PM, Jonathan Calloway wrote:
Dan,
You may want to dump that into a shell script, as all kernel updates moving
forward will “break” VMWare workstation again.
On Feb 17, 2014, at 8:41 PM, Dan Mossor wrote:
On 02/14/2014 07:56 PM, Jonathan Calloway wrote:
Lawrence,
Dan,
You may want to dump that into a shell script, as all kernel updates moving
forward will “break” VMWare workstation again.
On Feb 17, 2014, at 8:41 PM, Dan Mossor wrote:
>
>
> On 02/14/2014 07:56 PM, Jonathan Calloway wrote:
>> Lawrence,
>>
>> You know, now that I think about it,
On 02/14/2014 07:56 PM, Jonathan Calloway wrote:
Lawrence,
You know, now that I think about it, I used to run VMWare Player in Fedora. I
always had trouble getting it to compile. I found a thread somewhere that
provided a way of modifying a config file so that it thought the version of
Fe
Lawrence,
You know, now that I think about it, I used to run VMWare Player in Fedora. I
always had trouble getting it to compile. I found a thread somewhere that
provided a way of modifying a config file so that it thought the version of
Fedora it was running on was an older version, or somet
My guess is something didn’t get built right. . . you’re getting folder not
found errors. .
> 2014-02-14T18:30:06.184-07:00| vthread-3| I120:
> [msg.dictionary.load.openFailed] Cannot open file
> "/home/lawrence67/.vmware/config": No such file or directory.
On Feb 14, 2014, at 8:38 PM, Lawren
2014-02-14T18:30:06.188-07:00| vthread-3| I120: Log for VMware
Workstation pid=3421 version=10.0.1 build=build-1379776 option=Release
2014-02-14T18:30:06.188-07:00| vthread-3| I120: The process is 64-bit.
2014-02-14T18:30:06.188-07:00| vthread-3| I120: Host codepage=UTF-8
encoding=UTF-8
2014-02-
