On Thu, Apr 2, 2020 at 11:16 AM R C wrote:
> why not use dmidecode ipmi, things like that?
>
> On 4/1/20 11:40 PM, Thomas Stephen Lee wrote:
> > On Wed, Apr 1, 2020 at 12:33 PM Peter Kjellström wrote:
> >
> >> On Wed, 1 Apr 2020 10:01:04 +0530
> >> Thomas Stephen Lee wrote:
> >> ...
> >>> Than
On Tue, 31 Mar 2020, Divine Tanyingoh wrote:
On centos 6 I cannot ping the hostname and get a
reply without first resolving in the /etc/hosts file by adding a new entry:
192.168.0.47 server1.example.com.
But for centos 7 I am able to ping the hostname and get a reply even when I
have not made
why not use dmidecode ipmi, things like that?
On 4/1/20 11:40 PM, Thomas Stephen Lee wrote:
On Wed, Apr 1, 2020 at 12:33 PM Peter Kjellström wrote:
On Wed, 1 Apr 2020 10:01:04 +0530
Thomas Stephen Lee wrote:
...
Thanks for the information 😊.
Rented a new EPYC Rome Server from Hetzner, but
On Wed, Apr 1, 2020 at 12:33 PM Peter Kjellström wrote:
> On Wed, 1 Apr 2020 10:01:04 +0530
> Thomas Stephen Lee wrote:
> ...
> > Thanks for the information 😊.
> > Rented a new EPYC Rome Server from Hetzner, but sensors does not show
> > status of all cores in list, which is why I asked.
>
> Cur
OK I rebooted.
I changed the NIC from Bridge to Passthrough, hit apply, then changed it to
bridge and hit apply, then booted the VM.
My firewall looks better but still not working.
iptables -L FORWARD -v -n | egrep '(policy|virbr1)'
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
0 0 ACCE
>Sorry, have to correct myself. Had to much to do today on OpenShift.
>There is no Docker involved in what we discuss. The firewall rules for
>the host bridge devices get created by libvirtd.
Thanks I was using iptables and not converted to firewalld. I am doing so
now.
Will I need to delete the
Am 01.04.2020 um 22:07 schrieb Alexander Dalloz:
So looks like my IPTables is not correct.
What commands do you run for that ?
Simply firewalld. Docker acts by itself.
Sorry, have to correct myself. Had to much to do today on OpenShift.
There is no Docker involved in what we discuss. The fir
Am 01.04.2020 um 21:56 schrieb Jerry Geis:
Thanks for the info.
brctl show virbr0
bridge name bridge id STP enabled interfaces
virbr0 8000.525400fc34af yes virbr0-nic
brctl show virbr1
bridge name bridge id STP enabled inter
Thanks for the info.
brctl show virbr0
bridge name bridge id STP enabled interfaces
virbr0 8000.525400fc34af yes virbr0-nic
brctl show virbr1
bridge name bridge id STP enabled interfaces
virbr1 8000.5254009c3902
Am 01.04.2020 um 14:53 schrieb Jerry Geis:
I have CentOS 7 host. Two guests on bridge network setup by GUI and
virt-manager.
1 CentOS 8 guest
1 Win 10 guest
Both cannot access the host. They can other machines on the network. Guests
can access the internet just not the host.
I used virt-manager
I have CentOS 7 host. Two guests on bridge network setup by GUI and
virt-manager.
1 CentOS 8 guest
1 Win 10 guest
Both cannot access the host. They can other machines on the network. Guests
can access the internet just not the host.
I used virt-manager GUi to set up everything. Selected the eth0:m
On Wed, 1 Apr 2020 10:01:04 +0530
Thomas Stephen Lee wrote:
...
> Thanks for the information 😊.
> Rented a new EPYC Rome Server from Hetzner, but sensors does not show
> status of all cores in list, which is why I asked.
Curious what "sensors" you are referring to..
Like this:
$ cat /sys/device
12 matches
Mail list logo