On Tue, 14 Aug 2018 08:09:34 +0800
Ed Greshko wrote:
> 1. You won't be able to make a connection between the host and the guest.
> virt-manager warns you about this.
That isn't the case if you setup the bridge as described
in the linux kvm web page. A device on the bridge is just
another device
On Mon, 2018-08-13 at 19:38 -0400, Tom Horsley wrote:
> On Mon, 13 Aug 2018 17:54:20 -0400
> Bob Goodwin wrote:
>
> > Is this the result of my having made a wrong selection when creating the
> > VM from virt-manager? If so, I could go through the process again and
> > see what the new network[sc
On 08/14/18 07:38, Tom Horsley wrote:
> On Mon, 13 Aug 2018 17:54:20 -0400
> Bob Goodwin wrote:
>
>> Is this the result of my having made a wrong selection when creating the
>> VM from virt-manager? If so, I could go through the process again and
>> see what the new network[scripts should look li
On Mon, 13 Aug 2018 17:54:20 -0400
Bob Goodwin wrote:
> Is this the result of my having made a wrong selection when creating the
> VM from virt-manager? If so, I could go through the process again and
> see what the new network[scripts should look like since if I understand
> what I've read tha
On 08/13/2018 02:54 PM, Bob Goodwin wrote:
> On 08/13/18 14:00, Tom Horsley wrote:
>>> Can anyone suggest what I might have wrong?
>> Is the VM using NAT networking or a bridge? If it is NAT, the VM probably
>> won't be on the 192.168.1.0 subnet. You could see what the VM thinks its
>> IP address i
On 08/13/2018 04:04 PM, Rick Stevens wrote:
> On 08/13/2018 02:54 PM, Bob Goodwin wrote:
>> On 08/13/18 14:00, Tom Horsley wrote:
Can anyone suggest what I might have wrong?
>>> Is the VM using NAT networking or a bridge? If it is NAT, the VM probably
>>> won't be on the 192.168.1.0 subnet. Yo
On 08/13/18 14:00, Tom Horsley wrote:
Can anyone suggest what I might have wrong?
Is the VM using NAT networking or a bridge? If it is NAT, the VM probably
won't be on the 192.168.1.0 subnet. You could see what the VM thinks its
IP address is.
+
"using NAT networking or a bridge?"
Is this the
On 08/13/2018 11:26 AM, Bob Goodwin wrote:
On 08/13/18 13:53, Rick Stevens wrote:
On 08/13/2018 10:08 AM, Bob Goodwin wrote:
I have an Fedora 28 computer with Fedora 27 running in virtual manager.
My NFS server refuses its connection although the Fedora28 computer
itself connects routinely. Pin
On 08/13/2018 11:26 AM, Bob Goodwin wrote:
> On 08/13/18 13:53, Rick Stevens wrote:
>> On 08/13/2018 10:08 AM, Bob Goodwin wrote:
>>> I have an Fedora 28 computer with Fedora 27 running in virtual manager.
>>> My NFS server refuses its connection although the Fedora28 computer
>>> itself connects r
El 13/8/18 a las 20:26, Bob Goodwin escribió:
> On 08/13/18 13:53, Rick Stevens wrote:
>> On 08/13/2018 10:08 AM, Bob Goodwin wrote:
>>> I have an Fedora 28 computer with Fedora 27 running in virtual manager.
>>> My NFS server refuses its connection although the Fedora28 computer
>>> itself connec
On 08/13/18 13:53, Rick Stevens wrote:
On 08/13/2018 10:08 AM, Bob Goodwin wrote:
I have an Fedora 28 computer with Fedora 27 running in virtual manager.
My NFS server refuses its connection although the Fedora28 computer
itself connects routinely. Ping and ssh can connect to the NFS server
from
On Mon, 13 Aug 2018 13:08:25 -0400
Bob Goodwin wrote:
> Can anyone suggest what I might have wrong?
Is the VM using NAT networking or a bridge? If it is NAT, the VM probably
won't be on the 192.168.1.0 subnet. You could see what the VM thinks its
IP address is.
___
Den 2018-08-13 kl. 19:08, skrev Bob Goodwin:
>
> I have an Fedora 28 computer with Fedora 27 running in virtual manager.
> My NFS server refuses its connection although the Fedora28 computer
> itself connects routinely. Ping and ssh can connect to the NFS server
> from the VM. Stopping Firewalld a
On 08/13/2018 10:08 AM, Bob Goodwin wrote:
>
> I have an Fedora 28 computer with Fedora 27 running in virtual manager.
> My NFS server refuses its connection although the Fedora28 computer
> itself connects routinely. Ping and ssh can connect to the NFS server
> from the VM. Stopping Firewalld and
I have an Fedora 28 computer with Fedora 27 running in virtual manager.
My NFS server refuses its connection although the Fedora28 computer
itself connects routinely. Ping and ssh can connect to the NFS server
from the VM. Stopping Firewalld and setenforce 0 in the VM make no
difference.
NF
15 matches
Mail list logo
