Re: [qubes-users] Q 4.0 updates took my sys-net off line

2018-05-07 Thread Coleman, Steve L. 
I am still offline since that faitful dom0 update/reboot for whatever reason, 
but have been unable to find the time to resolve this, due mostly to being 
off-line. I got a few minutes before work today to try a few things, without 
any luck. I switched back to hvm mode since pv didn't buy me anything. Trying 
random things is obviously not the best methodology.


I had noticed that qvm-prefs was displaying network information (IP address) 
that the qube-manager did not. But I would not think that the gateway should be 
equal to its own IP address though. I just wish I had a working system so I 
could compare configurations.  After playing with qvm-prefs --set the 
qube-manager seems to at least be finally displaying the same information. Not 
that it helped anything.


$ qvm-prefs sys-net

autostart -  False
backup_timestamp  -  1525126185
debug -  True
default_dispvmD  fedora-26-dvm
default_user  D  user
gateway   D  10.137.0.5
gateway6  D
include_in_backupsD  True
installed_by_rpm  D  False
ipD  10.137.0.5
ip6   D
kernelD  4.14.18-1
kernelopts-  nopat iommu=soft swiotlb=8192
klass D  AppVM
label -  red
mac   D  00:16:3E:5E:6C:00
maxmem-  8000
memory-  800
name  -  sys-net
netvm -  None
provides_network  -  True
qid   -  5
qrexec_timeoutD  60
start_timeD  1525698772.6
stubdom_mem   U
stubdom_xid   D  16
template  -  fedora-26-net
template_for_dispvms  D  False
updateableD  False
uuid  -  e7332e9f-b252-47e4-a997-b62f8310441d
vcpus D  2
virt_mode -  hvm
visible_gateway   D
visible_gateway6  D
visible_ipD  10.137.0.5
visible_ip6   D
visible_netmask   D
xid   D  15


The nic interface name also seems to have changed, again. It used to be eth0 
back when everything was working, before that dom0 update, then the IF was 
missing entirely,  then it first showed up as enp0s0, and now showing up as 
"ens5", but there is still no dhcp happening on that interface to obtain an IP 
address from the real network.


Q: What property/action in dom0 is supposed to cause this dhcp to happen in 
sys-net?

Q: Why would the if name be changing like this? Is it a HVM vs PV interface 
driver convention? If so, what causes it to change to eth0 which used to work?


thanks,


Steve



From: qubes-users@googlegroups.com <qubes-users@googlegroups.com> on behalf of 
Coleman, Steve L. <steve.cole...@jhuapl.edu>
Sent: Thursday, May 3, 2018 9:42 AM
To: Franz
Cc: qubes-users@googlegroups.com
Subject: Re: [qubes-users] Q 4.0 updates took my sys-net off line




From: Franz <169...@gmail.com>
Sent: Wednesday, May 2, 2018 5:12 PM
To: Coleman, Steve L.
Cc: qubes-users@googlegroups.com
Subject: Re: [qubes-users] Q 4.0 updates took my sys-net off line



On Wed, May 2, 2018 at 4:03 PM, Coleman, Steve L. 
<steve.cole...@jhuapl.edu<mailto:steve.cole...@jhuapl.edu>> wrote:



From: Franz <169...@gmail.com<mailto:169...@gmail.com>>
Sent: Wednesday, May 2, 2018 2:58 PM
To: Coleman, Steve L.
Cc: qubes-users@googlegroups.com<mailto:qubes-users@googlegroups.com>
Subject: Re: [qubes-users] Q 4.0 updates took my sys-net off line

Have you tried using a different template to generate sys-net?

Yes, I have tried my fedora-26-net, fedora-26-minimal, and generic fedora-26 
templates with both the old sys-net and the one I re-created.  None of that 
helped.



It is always Fedora, perhaps Debian...

The thing is that the updates were patches on the Dom0 side of the world that 
broke it. The template used by sys-net was not even changed and fedora should 
just work, as it is the default for the Qubes system.

At first the enp0s0 interface did not appear in sys-net at all, and I have been 
struggling to try to bring the if up, and nothing I have tried so far seems to 
work.  I managed to get the network card assigned to sys-net but I don't know 
what dom0 invokes within sys-net to tell it to do the dhcp stuff.

On Wed, May 2, 2018 at 3:46 PM, Coleman, Steve L. 
<steve.cole...@jhuapl.edu<mailto:steve.cole...@jhuapl.edu>> wrote:

Yesterday I pulled some Dom0 updates and rebooted to complete the install, and 
since then had no luck at getting it back online. My sys-net is not properly 
configuring the network card so that eth0 never gets configured properly and 
assigned an address.


I have tried switching between HVM/PV modes with no luck. I created a new 
sys-net and assigned the controller over with no joy either. Any advice on what 
to look at next would be very much apprec

Re: [qubes-users] Q 4.0 updates took my sys-net off line

2018-05-03 Thread Coleman, Steve L. 


From: Franz <169...@gmail.com>
Sent: Wednesday, May 2, 2018 5:12 PM
To: Coleman, Steve L.
Cc: qubes-users@googlegroups.com
Subject: Re: [qubes-users] Q 4.0 updates took my sys-net off line



On Wed, May 2, 2018 at 4:03 PM, Coleman, Steve L. 
<steve.cole...@jhuapl.edu<mailto:steve.cole...@jhuapl.edu>> wrote:



From: Franz <169...@gmail.com<mailto:169...@gmail.com>>
Sent: Wednesday, May 2, 2018 2:58 PM
To: Coleman, Steve L.
Cc: qubes-users@googlegroups.com<mailto:qubes-users@googlegroups.com>
Subject: Re: [qubes-users] Q 4.0 updates took my sys-net off line

Have you tried using a different template to generate sys-net?

Yes, I have tried my fedora-26-net, fedora-26-minimal, and generic fedora-26 
templates with both the old sys-net and the one I re-created.  None of that 
helped.



It is always Fedora, perhaps Debian...

The thing is that the updates were patches on the Dom0 side of the world that 
broke it. The template used by sys-net was not even changed and fedora should 
just work, as it is the default for the Qubes system.

At first the enp0s0 interface did not appear in sys-net at all, and I have been 
struggling to try to bring the if up, and nothing I have tried so far seems to 
work.  I managed to get the network card assigned to sys-net but I don't know 
what dom0 invokes within sys-net to tell it to do the dhcp stuff.

On Wed, May 2, 2018 at 3:46 PM, Coleman, Steve L. 
<steve.cole...@jhuapl.edu<mailto:steve.cole...@jhuapl.edu>> wrote:

Yesterday I pulled some Dom0 updates and rebooted to complete the install, and 
since then had no luck at getting it back online. My sys-net is not properly 
configuring the network card so that eth0 never gets configured properly and 
assigned an address.


I have tried switching between HVM/PV modes with no luck. I created a new 
sys-net and assigned the controller over with no joy either. Any advice on what 
to look at next would be very much appreciated.


[user@sys-net ~]$ ifconfig -a
enp0s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
ether 18:03:73:be:70:17  txqueuelen 1000  (Ethernet)
RX packets 2033  bytes 193536 (189.0 KiB)
RX errors 132  dropped 0  overruns 0  frame 132
TX packets 7797  bytes 1484630 (1.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 26  memory 0xe160-e162

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 645  bytes 31721 (30.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 645  bytes 31721 (30.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif6.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
RX packets 16375  bytes 1014366 (990.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14967  bytes 1473500 (1.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


[user@sys-net ~]$ sudo dmesg | grep -i e1000e
[8.488338] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[8.488350] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[8.488565] e1000e :00:00.0: Xen PCI mapped GSI20 to IRQ26
[8.489625] e1000e :00:00.0: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[8.589599] e1000e :00:00.0 :00:00.0 (uninitialized): registered PHC 
clock
[8.684606] e1000e :00:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 
18:03:73:be:70:17
[8.684638] e1000e :00:00.0 eth0: Intel(R) PRO/1000 Network Connection
[8.684690] e1000e :00:00.0 eth0: MAC: 10, PHY: 11, PBA No: E041FF-0FF
[8.747515] e1000e :00:00.0 enp0s0: renamed from eth0
[   18.923186] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44053.103546] e1000e: enp0s0 NIC Link is Down
[44062.829234] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44103.730522] e1000e: enp0s0 NIC Link is Down
[44106.646419] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44119.384485] e1000e: enp0s0 NIC Link is Down
[44122.317273] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None

[@dom0 ~] lspci | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) (rev 04)


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
qubes-users+unsubscr...@googlegroups.com&l

Re: [qubes-users] Q 4.0 updates took my sys-net off line

2018-05-02 Thread Franz 
On Wed, May 2, 2018 at 4:03 PM, Coleman, Steve L. <steve.cole...@jhuapl.edu>
wrote:

>
> --
> *From:* Franz <169...@gmail.com>
> *Sent:* Wednesday, May 2, 2018 2:58 PM
> *To:* Coleman, Steve L.
> *Cc:* qubes-users@googlegroups.com
> *Subject:* Re: [qubes-users] Q 4.0 updates took my sys-net off line
>
> Have you tried using a different template to generate sys-net?
>
> Yes, I have tried my fedora-26-net, fedora-26-minimal, and generic
> fedora-26 templates with both the old sys-net and the one I re-created.
> None of that helped.
>
>
>
It is always Fedora, perhaps Debian...



> On Wed, May 2, 2018 at 3:46 PM, Coleman, Steve L. <
> steve.cole...@jhuapl.edu> wrote:
>
>> Yesterday I pulled some Dom0 updates and rebooted to complete the
>> install, and since then had no luck at getting it back online. My sys-net
>> is not properly configuring the network card so that eth0 never gets
>> configured properly and assigned an address.
>>
>>
>> I have tried switching between HVM/PV modes with no luck. I created a new
>> sys-net and assigned the controller over with no joy either. Any advice on
>> what to look at next would be very much appreciated.
>>
>>
>> [user@sys-net ~]$ ifconfig -a
>> enp0s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>> ether 18:03:73:be:70:17  txqueuelen 1000  (Ethernet)
>> RX packets 2033  bytes 193536 (189.0 KiB)
>> RX errors 132  dropped 0  overruns 0  frame 132
>> TX packets 7797  bytes 1484630 (1.4 MiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> device interrupt 26  memory 0xe160-e162
>>
>> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>> inet 127.0.0.1  netmask 255.0.0.0
>> inet6 ::1  prefixlen 128  scopeid 0x10
>> loop  txqueuelen 1000  (Local Loopback)
>> RX packets 645  bytes 31721 (30.9 KiB)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 645  bytes 31721 (30.9 KiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> vif6.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>> inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
>> inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
>> ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
>> RX packets 16375  bytes 1014366 (990.5 KiB)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 14967  bytes 1473500 (1.4 MiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>>
>>
>> [user@sys-net ~]$ sudo dmesg | grep -i e1000e
>> [8.488338] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
>> [8.488350] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
>> [8.488565] e1000e :00:00.0: Xen PCI mapped GSI20 to IRQ26
>> [8.489625] e1000e :00:00.0: Interrupt Throttling Rate (ints/sec)
>> set to dynamic conservative mode
>> [8.589599] e1000e :00:00.0 :00:00.0 (uninitialized):
>> registered PHC clock
>> [8.684606] e1000e :00:00.0 eth0: (PCI Express:2.5GT/s:Width x1)
>> 18:03:73:be:70:17
>> [8.684638] e1000e :00:00.0 eth0: Intel(R) PRO/1000 Network
>> Connection
>> [8.684690] e1000e :00:00.0 eth0: MAC: 10, PHY: 11, PBA No:
>> E041FF-0FF
>> [8.747515] e1000e :00:00.0 enp0s0: renamed from eth0
>> [   18.923186] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
>> Control: None
>> [44053.103546] e1000e: enp0s0 NIC Link is Down
>> [44062.829234] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
>> Control: None
>> [44103.730522] e1000e: enp0s0 NIC Link is Down
>> [44106.646419] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
>> Control: None
>> [44119.384485] e1000e: enp0s0 NIC Link is Down
>> [44122.317273] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
>> Control: None
>>
>> [@dom0 ~] lspci | grep Ethernet
>> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
>> Connection (Lewisville) (rev 04)
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "qubes-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to qubes-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to qubes-users@googlegroups.com.
>> To view this discussion on the web visit https://group

Re: [qubes-users] Q 4.0 updates took my sys-net off line

2018-05-02 Thread Coleman, Steve L. 


From: Franz <169...@gmail.com>
Sent: Wednesday, May 2, 2018 2:58 PM
To: Coleman, Steve L.
Cc: qubes-users@googlegroups.com
Subject: Re: [qubes-users] Q 4.0 updates took my sys-net off line

Have you tried using a different template to generate sys-net?

Yes, I have tried my fedora-26-net, fedora-26-minimal, and generic fedora-26 
templates with both the old sys-net and the one I re-created.  None of that 
helped.


On Wed, May 2, 2018 at 3:46 PM, Coleman, Steve L. 
<steve.cole...@jhuapl.edu<mailto:steve.cole...@jhuapl.edu>> wrote:

Yesterday I pulled some Dom0 updates and rebooted to complete the install, and 
since then had no luck at getting it back online. My sys-net is not properly 
configuring the network card so that eth0 never gets configured properly and 
assigned an address.


I have tried switching between HVM/PV modes with no luck. I created a new 
sys-net and assigned the controller over with no joy either. Any advice on what 
to look at next would be very much appreciated.


[user@sys-net ~]$ ifconfig -a
enp0s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
ether 18:03:73:be:70:17  txqueuelen 1000  (Ethernet)
RX packets 2033  bytes 193536 (189.0 KiB)
RX errors 132  dropped 0  overruns 0  frame 132
TX packets 7797  bytes 1484630 (1.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 26  memory 0xe160-e162

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 645  bytes 31721 (30.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 645  bytes 31721 (30.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif6.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
RX packets 16375  bytes 1014366 (990.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14967  bytes 1473500 (1.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


[user@sys-net ~]$ sudo dmesg | grep -i e1000e
[8.488338] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[8.488350] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[8.488565] e1000e :00:00.0: Xen PCI mapped GSI20 to IRQ26
[8.489625] e1000e :00:00.0: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[8.589599] e1000e :00:00.0 :00:00.0 (uninitialized): registered PHC 
clock
[8.684606] e1000e :00:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 
18:03:73:be:70:17
[8.684638] e1000e :00:00.0 eth0: Intel(R) PRO/1000 Network Connection
[8.684690] e1000e :00:00.0 eth0: MAC: 10, PHY: 11, PBA No: E041FF-0FF
[8.747515] e1000e :00:00.0 enp0s0: renamed from eth0
[   18.923186] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44053.103546] e1000e: enp0s0 NIC Link is Down
[44062.829234] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44103.730522] e1000e: enp0s0 NIC Link is Down
[44106.646419] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44119.384485] e1000e: enp0s0 NIC Link is Down
[44122.317273] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None

[@dom0 ~] lspci | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) (rev 04)


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
qubes-users+unsubscr...@googlegroups.com<mailto:qubes-users+unsubscr...@googlegroups.com>.
To post to this group, send email to 
qubes-users@googlegroups.com<mailto:qubes-users@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1525286811400.68924%40jhuapl.edu<https://groups.google.com/d/msgid/qubes-users/1525286811400.68924%40jhuapl.edu?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1525287841118.78183%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Q 4.0 updates took my sys-net off line

2018-05-02 Thread Franz 
Have you tried using a different template to generate sys-net?

On Wed, May 2, 2018 at 3:46 PM, Coleman, Steve L. 
wrote:

> Yesterday I pulled some Dom0 updates and rebooted to complete the install,
> and since then had no luck at getting it back online. My sys-net is not
> properly configuring the network card so that eth0 never gets configured
> properly and assigned an address.
>
>
> I have tried switching between HVM/PV modes with no luck. I created a new
> sys-net and assigned the controller over with no joy either. Any advice on
> what to look at next would be very much appreciated.
>
>
> [user@sys-net ~]$ ifconfig -a
> enp0s0: flags=4163  mtu 1500
> ether 18:03:73:be:70:17  txqueuelen 1000  (Ethernet)
> RX packets 2033  bytes 193536 (189.0 KiB)
> RX errors 132  dropped 0  overruns 0  frame 132
> TX packets 7797  bytes 1484630 (1.4 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 26  memory 0xe160-e162
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1000  (Local Loopback)
> RX packets 645  bytes 31721 (30.9 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 645  bytes 31721 (30.9 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> vif6.0: flags=4163  mtu 1500
> inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
> inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
> ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
> RX packets 16375  bytes 1014366 (990.5 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 14967  bytes 1473500 (1.4 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>
> [user@sys-net ~]$ sudo dmesg | grep -i e1000e
> [8.488338] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
> [8.488350] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
> [8.488565] e1000e :00:00.0: Xen PCI mapped GSI20 to IRQ26
> [8.489625] e1000e :00:00.0: Interrupt Throttling Rate (ints/sec)
> set to dynamic conservative mode
> [8.589599] e1000e :00:00.0 :00:00.0 (uninitialized):
> registered PHC clock
> [8.684606] e1000e :00:00.0 eth0: (PCI Express:2.5GT/s:Width x1)
> 18:03:73:be:70:17
> [8.684638] e1000e :00:00.0 eth0: Intel(R) PRO/1000 Network
> Connection
> [8.684690] e1000e :00:00.0 eth0: MAC: 10, PHY: 11, PBA No:
> E041FF-0FF
> [8.747515] e1000e :00:00.0 enp0s0: renamed from eth0
> [   18.923186] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: None
> [44053.103546] e1000e: enp0s0 NIC Link is Down
> [44062.829234] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: None
> [44103.730522] e1000e: enp0s0 NIC Link is Down
> [44106.646419] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: None
> [44119.384485] e1000e: enp0s0 NIC Link is Down
> [44122.317273] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: None
>
> [@dom0 ~] lspci | grep Ethernet
> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> Connection (Lewisville) (rev 04)
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/qubes-users/1525286811400.68924%40jhuapl.edu
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAPzH-qDzj0nM%3DeT66Dnryg%3DDT%2BtefXGxNziOB-YcuQDeWOXg7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Q 4.0 updates took my sys-net off line

2018-05-02 Thread Coleman, Steve L. 
Yesterday I pulled some Dom0 updates and rebooted to complete the install, and 
since then had no luck at getting it back online. My sys-net is not properly 
configuring the network card so that eth0 never gets configured properly and 
assigned an address.


I have tried switching between HVM/PV modes with no luck. I created a new 
sys-net and assigned the controller over with no joy either. Any advice on what 
to look at next would be very much appreciated.


[user@sys-net ~]$ ifconfig -a
enp0s0: flags=4163  mtu 1500
ether 18:03:73:be:70:17  txqueuelen 1000  (Ethernet)
RX packets 2033  bytes 193536 (189.0 KiB)
RX errors 132  dropped 0  overruns 0  frame 132
TX packets 7797  bytes 1484630 (1.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 26  memory 0xe160-e162

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 645  bytes 31721 (30.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 645  bytes 31721 (30.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif6.0: flags=4163  mtu 1500
inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
RX packets 16375  bytes 1014366 (990.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 14967  bytes 1473500 (1.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


[user@sys-net ~]$ sudo dmesg | grep -i e1000e
[8.488338] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[8.488350] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[8.488565] e1000e :00:00.0: Xen PCI mapped GSI20 to IRQ26
[8.489625] e1000e :00:00.0: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[8.589599] e1000e :00:00.0 :00:00.0 (uninitialized): registered PHC 
clock
[8.684606] e1000e :00:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 
18:03:73:be:70:17
[8.684638] e1000e :00:00.0 eth0: Intel(R) PRO/1000 Network Connection
[8.684690] e1000e :00:00.0 eth0: MAC: 10, PHY: 11, PBA No: E041FF-0FF
[8.747515] e1000e :00:00.0 enp0s0: renamed from eth0
[   18.923186] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44053.103546] e1000e: enp0s0 NIC Link is Down
[44062.829234] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44103.730522] e1000e: enp0s0 NIC Link is Down
[44106.646419] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[44119.384485] e1000e: enp0s0 NIC Link is Down
[44122.317273] e1000e: enp0s0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None

[@dom0 ~] lspci | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) (rev 04)

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1525286811400.68924%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.