I'm running VMware Workstation 10 on Mageia 4 with the latest updates. In VMware Workstation I'm running Mageia 5 Alpha 2. When I try to update I get the following messages: Serious error. A serrious error had occured: couldn't find any mirror server from mirrorlist $MIRRORLIST I have now found the reason why I can't get the MIRRORSERVER. It depends on the kernel 3.17.0 (and 3.17.0.rc6) that don't connect to internet. When I use kernel 3.15.0 it connects to internet and I can update Mageia 5 Alpha 2. With kernel 3.15.0 it is possible to connect to internet. With kernel 3.17.0 it is not possible to connect to internet.
Nothing changes after installing kernel 3.17.0-5 mga5 it is not possible to connect to internet.
Anything in the logs ? If you remove and reconfigure network access in the virtual machine, does it work then?
CC: (none) => tmb
This is the information I can find: Mageia 4 uname -a: 3.14.18-server-3.mga4 ifconfig: ifconfig ens33 Link encap:Ethernet HWaddr 00:0C:29:3D:DB:DC inet addr:172.16.215.132 Bcast:172.16.215.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe3d:dbdc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:195 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12558 (12.2 KiB) TX bytes:7444 (7.2 KiB) Interrupt:19 Base address:0x2000 ens: Advance Micro Device.Inc[AMD] 79c970[PCnet32 LANCE] Mageia 5 Alpha 2 First try: uname -a: 3.17.0-server-5.mga5 ifconfig: ifconfig eno16777736: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:0c:29:3a:4c:aa txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 frame 0 device interrupt 19 base 0x2000 The only interface to choose: eno16777736: Advance Micro Device.Inc[AMD] 79c970[PCnet32 LANCE] Second try uname -a: 3.15.6-server-1.mga5 ifconfig: ens33: flags=4163<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.16.215.133 netmask 255.255.255.0 broadcast 172.16.215.255 inet6 fe80::20c:29ff:fe3a:4caa prefixlen 64 scopeid (Ethernet) ether 00:0c:29:3a:4c:aa txqueuelen 1000 (Ethernet) RX packets 255 bytes 14084 (13.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 33 bytes 5965 (5.8 KiB) TX errors 0 dropped 0 carrier 0 collisions 0 device interupt 19 base 0x2000 Third try uname -a: 3.17.0-server-5.mga5 ifconfig: eno16777736: flags=4163<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.16.215.133 netmask 255.255.255.0 broadcast 172.16.215.255 inet6 fe80::20c:29ff:fe3a:4caa prefixlen 64 scopeid 0x20<link> ether 00:0c:29:3a:4c:aa txqueuelen 1000 (Ethernet) RX packets 171 bytes 10828 (10.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11 bytes 1386 (1.3 KiB) TX errors 0 dropped 0 carrier 0 collisions 0 device interupt 19 base 0x2000 Result: No internetconnection /var/log/net_monitor.log: eno16777736:DOWN:1413353640 eno16777736:DOWN:1413353640 eno16777736:UP:1413353644 eno16777736:DOWN:1413353954 eno16777736:DOWN:1413354134 eno16777736:DOWN:1413354277 eno16777736:DOWN:1413354329 eno16777736:DOWN:1413355356 I hope this will help.
Are you using a static IP address or DHCP ? The fact that you do not see an inet address in your first try with 17 but do in your second try is significant. It indicates that at some point you are connected on the second try. Please post the output of "route -n", "traceroute 23.194.116.205", and "host www.apple.com". "route -n" will indicate if your traffic is being misdirected, "traceroute" will indicate whether your traffic to that IP (www.apple.com) is getting off your VM host or not, and "host" will indicate whether your hostnames are getting successful DNS resolution.
CC: (none) => ftg
First I will point that with kernel 3.15.6-server-1.mga5 everything works OK. Here is what you asked for: 3.15.6-server-1.mga5 [root@localhost jan]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.16.215.2 0.0.0.0 UG 10 0 0 ens33 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 ens33 172.16.215.0 0.0.0.0 255.255.255.0 U 10 0 0 ens33 [root@localhost jan]# [root@localhost jan]# traceroute 23.194.116.205 traceroute to 23.194.116.205 (23.194.116.205), 30 hops max, 60 byte packets 1 172.16.215.2 (172.16.215.2) 0.832 ms 0.164 ms 0.149 ms 2 10.0.0.1 (10.0.0.1) 0.703 ms 0.860 ms 0.698 ms 3 192.168.1.254 (192.168.1.254) 3.614 ms 3.311 ms 8.662 ms 4 ua-213-114-128-1.cust.bredbandsbolaget.se (213.114.128.1) 8.514 ms 8.335 ms 8.163 ms 5 ti3001d400-xe6-0-1.ti.telenor.net (146.172.107.237) 15.630 ms 16.257 ms 16.766 ms 6 ti3001c400-ae1-0.ti.telenor.net (146.172.99.69) 11.095 ms 11.828 ms 12.639 ms 7 ti0001c360-ae18-0.ti.telenor.net (146.172.98.46) 13.031 ms 12.754 ms 13.340 ms 8 ti0001b400-ae1-0.ti.telenor.net (146.172.105.66) 14.168 ms 14.433 ms 14.916 ms 9 ti0300c360-ae7-0.ti.telenor.net (146.172.105.17) 21.856 ms 22.339 ms 22.610 ms 10 ti3003c400-ae6-0.ti.telenor.net (146.172.99.245) 26.904 ms 30.545 ms 30.439 ms 11 ti6000b400-ae1-0.ti.telenor.net (146.172.105.46) 19.238 ms 20.384 ms 19.618 ms 12 ae51.bar1.Copenhagen1.Level3.net (213.242.108.13) 19.733 ms 30.146 ms 29.956 ms 13 ae-0-10.bar1.Copenhagen2.Level3.net (4.69.137.154) 20.552 ms 21.117 ms 21.526 ms 14 Telia-Level3-10G.Copenhagen2.Level3.net (4.68.110.222) 38.458 ms 38.451 ms 39.194 ms 15 kbn-bb4-link.telia.net (62.115.142.210) 38.937 ms kbn-bb4-link.telia.net (62.115.142.208) 34.345 ms 34.273 ms 16 nyk-bb1-link.telia.net (62.115.141.101) 105.182 ms nyk-bb2-link.telia.net (80.91.247.119) 109.245 ms hbg-bb4-link.telia.net (213.155.135.122) 35.376 ms 17 ldn-bb2-link.telia.net (213.155.132.247) 118.041 ms 180.594 ms ldn-bb1-link.telia.net (80.91.245.62) 54.452 ms 18 akamai-ic-300848-chi-b21.c.telia.net (213.248.96.206) 130.887 ms 132.621 ms 129.077 ms 19 a23-194-116-205.deploy.static.akamaitechnologies.com (23.194.116.205) 134.620 ms 128.324 ms chi-b21-link.telia.net (62.115.140.107) 132.804 ms [root@localhost jan]# [root@localhost jan]# host www.apple.com www.apple.com is an alias for www.isg-apple.com.akadns.net. www.isg-apple.com.akadns.net is an alias for www.apple.com.edgekey.net. www.apple.com.edgekey.net is an alias for e3191.dscc.akamaiedge.net. e3191.dscc.akamaiedge.net has address 95.100.13.15 e3191.dscc.akamaiedge.net has IPv6 address 2a02:26f0:41:28a::c77 e3191.dscc.akamaiedge.net has IPv6 address 2a02:26f0:41:29d::c77 [root@localhost jan]# 3.17.0-server-5.mga5 [root@localhost jan]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.16.215.2 0.0.0.0 UG 10 0 0 eno16777736 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eno16777736 172.16.215.0 0.0.0.0 255.255.255.0 U 10 0 0 eno16777736 [root@localhost jan]# [root@localhost jan]# traceroute 23.194.116.205 traceroute to 23.194.116.205 (23.194.116.205), 30 hops max, 60 byte packets send: Operationen inte tillåten [root@localhost jan]# [root@localhost jan]# host www.apple.com name.c:2485: REQUIRE((((source) != ((void *)0)) && (((const isc__magic_t *)(source))->magic == ((('D') << 24 | ('N') << 16 | ('S') << 8 | ('n')))))) failed, back trace #0 0x81cad8c in ?? #1 0x81cac41 in ?? #2 0x8086c0a in ?? #3 0x8056f42 in ?? #4 0x8057014 in ?? #5 0x8057266 in ?? #6 0x805cc02 in ?? #7 0x81f01b7 in ?? #8 0xb7468386 in ?? #9 0xb71dbb5e in ?? Avbruten (SIGABRT) [root@localhost jan]#
You didn't say, but from the fact that you can't appear to communicate with your gateway, I'll guess that you're using a static IP. Are these two separate VMs, or the same VM booted first with 15 and then with 17 (i. e. just different choices from the grub menu) ? What about "journalctl -a -b | grep eno16777736" in each case ?
Sorry, in the 15 case use ens33 as the grep argument.
I use DHCP Yes, it is the same VM booteed with different kernel with different ckoises from the grub menu. 3.17.0-server-5.mga5 [root@localhost jan]# journalctl -a -b | grep eno16777736 okt 15 16:23:37 localhost.localdomain kernel: pcnet32 0000:02:01.0 eno16777736: renamed from eth0 okt 15 16:23:37 localhost.localdomain systemd-udevd[477]: renamed network interface eth0 to eno16777736 okt 15 16:23:40 localhost.localdomain kernel: pcnet32 0000:02:01.0 eno16777736: link up okt 15 16:23:40 localhost.localdomain ifplugd(eno16777736)[893]: ifplugd 0.28 initializing. okt 15 16:23:40 localhost.localdomain ifplugd(eno16777736)[893]: Using interface eno16777736/00:0C:29:3A:4C:AA with driver <pcnet32> (version: 1.35) okt 15 16:23:40 localhost.localdomain ifplugd(eno16777736)[893]: Using detection mode: SIOCETHTOOL okt 15 16:23:40 localhost.localdomain ifplugd(eno16777736)[893]: Initialization complete, link beat detected. okt 15 16:23:40 localhost.localdomain ifplugd(eno16777736)[893]: Executing '/etc/ifplugd/ifplugd.action eno16777736 up'. okt 15 16:23:42 localhost.localdomain network[743]: Sätter startad gränssnittet eno16777736: [ OK ] okt 15 16:23:43 localhost.localdomain avahi-daemon[610]: Registering new address record for fe80::20c:29ff:fe3a:4caa on eno16777736.*. okt 15 16:23:45 localhost.localdomain dhclient[979]: DHCPDISCOVER on eno16777736 to 255.255.255.255 port 67 interval 3 okt 15 16:23:48 localhost.localdomain dhclient[979]: DHCPREQUEST on eno16777736 to 255.255.255.255 port 67 okt 15 16:23:49 localhost.localdomain avahi-daemon[610]: Joining mDNS multicast group on interface eno16777736.IPv4 with address 172.16.215.133. okt 15 16:23:50 localhost.localdomain avahi-daemon[610]: New relevant interface eno16777736.IPv4 for mDNS. okt 15 16:23:50 localhost.localdomain avahi-daemon[610]: Registering new address record for 172.16.215.133 on eno16777736.IPv4. okt 15 16:23:50 localhost.localdomain avahi-daemon[610]: Withdrawing address record for 172.16.215.133 on eno16777736. okt 15 16:23:50 localhost.localdomain avahi-daemon[610]: Leaving mDNS multicast group on interface eno16777736.IPv4 with address 172.16.215.133. okt 15 16:23:50 localhost.localdomain avahi-daemon[610]: Interface eno16777736.IPv4 no longer relevant for mDNS. okt 15 16:23:50 localhost.localdomain avahi-daemon[610]: Joining mDNS multicast group on interface eno16777736.IPv4 with address 172.16.215.133. okt 15 16:23:51 localhost.localdomain ifplugd(eno16777736)[893]: client: Determining IP information for eno16777736... done. okt 15 16:23:51 localhost.localdomain ifplugd(eno16777736)[893]: Program executed successfully. okt 15 16:23:51 localhost.localdomain avahi-daemon[610]: New relevant interface eno16777736.IPv4 for mDNS. okt 15 16:23:51 localhost.localdomain avahi-daemon[610]: Registering new address record for 172.16.215.133 on eno16777736.IPv4. [root@localhost jan]# 3.15.6-server-1.mga5 [root@localhost jan]# journalctl -a -b | grep ens33 okt 15 16:31:58 localhost.localdomain systemd-udevd[472]: renamed network interface eth0 to ens33 okt 15 16:32:11 localhost.localdomain kernel: pcnet32 0000:02:01.0 ens33: link up okt 15 16:32:10 localhost.localdomain ifplugd(ens33)[1415]: ifplugd 0.28 initializing. okt 15 16:32:11 localhost.localdomain network[726]: Sätter startad gränssnittet ens33: [ OK ] okt 15 16:32:12 localhost.localdomain ifplugd(ens33)[1415]: Using interface ens33/00:0C:29:3A:4C:AA with driver <pcnet32> (version: 1.35) okt 15 16:32:12 localhost.localdomain ifplugd(ens33)[1415]: Using detection mode: SIOCETHTOOL okt 15 16:32:12 localhost.localdomain ifplugd(ens33)[1415]: Initialization complete, link beat detected. okt 15 16:32:12 localhost.localdomain ifplugd(ens33)[1415]: Executing '/etc/ifplugd/ifplugd.action ens33 up'. okt 15 16:32:13 localhost.localdomain avahi-daemon[609]: Registering new address record for fe80::20c:29ff:fe3a:4caa on ens33.*. okt 15 16:32:14 localhost.localdomain dhclient[1548]: DHCPDISCOVER on ens33 to 255.255.255.255 port 67 interval 5 okt 15 16:32:15 localhost.localdomain dhclient[1548]: DHCPREQUEST on ens33 to 255.255.255.255 port 67 okt 15 16:32:15 localhost.localdomain avahi-daemon[609]: Joining mDNS multicast group on interface ens33.IPv4 with address 172.16.215.133. okt 15 16:32:15 localhost.localdomain avahi-daemon[609]: New relevant interface ens33.IPv4 for mDNS. okt 15 16:32:15 localhost.localdomain avahi-daemon[609]: Registering new address record for 172.16.215.133 on ens33.IPv4. okt 15 16:32:15 localhost.localdomain avahi-daemon[609]: Withdrawing address record for 172.16.215.133 on ens33. okt 15 16:32:15 localhost.localdomain avahi-daemon[609]: Leaving mDNS multicast group on interface ens33.IPv4 with address 172.16.215.133. okt 15 16:32:16 localhost.localdomain avahi-daemon[609]: Interface ens33.IPv4 no longer relevant for mDNS. okt 15 16:32:16 localhost.localdomain avahi-daemon[609]: Joining mDNS multicast group on interface ens33.IPv4 with address 172.16.215.133. okt 15 16:32:16 localhost.localdomain avahi-daemon[609]: New relevant interface ens33.IPv4 for mDNS. okt 15 16:32:16 localhost.localdomain avahi-daemon[609]: Registering new address record for 172.16.215.133 on ens33.IPv4. okt 15 16:32:16 localhost.localdomain ifplugd(ens33)[1415]: client: Determining IP information for ens33... done. okt 15 16:32:17 localhost.localdomain ifplugd(ens33)[1415]: Program executed successfully. [root@localhost jan]#
(In reply to Jan Pihlgren from comment #5) > First I will point that with kernel 3.15.6-server-1.mga5 > everything works OK. > Thats because its old... > > [root@localhost jan]# host www.apple.com > name.c:2485: REQUIRE((((source) != ((void *)0)) && (((const isc__magic_t > *)(source))->magic == ((('D') << 24 | ('N') << 16 | ('S') << 8 | ('n')))))) > failed, back trace > #0 0x81cad8c in ?? > #1 0x81cac41 in ?? > #2 0x8086c0a in ?? > #3 0x8056f42 in ?? > #4 0x8057014 in ?? > #5 0x8057266 in ?? > #6 0x805cc02 in ?? > #7 0x81f01b7 in ?? > #8 0xb7468386 in ?? > #9 0xb71dbb5e in ?? > Avbruten (SIGABRT) > [root@localhost jan]# Are you sure your vmware version even supports kernel-3.17 + glibc 2.20 ? This above crash suggests some broken guest addons or something like that...
In both cases you can reach the DHCP server, so there's nothing wrong with the interface itself. I assume that "ping 172.16.215.2" fails on 17 ? So it's just your gateway it can't get to. Can you ping your DHCP server ? Can you ping any other server on your intranet (e. g. the system hosting the VM) ?
(In reply to Thomas Backlund from comment #9) > (In reply to Jan Pihlgren from comment #5) > > First I will point that with kernel 3.15.6-server-1.mga5 > > everything works OK. > > > > Thats because its old... > > > > > > [root@localhost jan]# host www.apple.com > > name.c:2485: REQUIRE((((source) != ((void *)0)) && (((const isc__magic_t > > *)(source))->magic == ((('D') << 24 | ('N') << 16 | ('S') << 8 | ('n')))))) > > failed, back trace > > #0 0x81cad8c in ?? > > #1 0x81cac41 in ?? > > #2 0x8086c0a in ?? > > #3 0x8056f42 in ?? > > #4 0x8057014 in ?? > > #5 0x8057266 in ?? > > #6 0x805cc02 in ?? > > #7 0x81f01b7 in ?? > > #8 0xb7468386 in ?? > > #9 0xb71dbb5e in ?? > > Avbruten (SIGABRT) > > [root@localhost jan]# > > > Are you sure your vmware version even supports kernel-3.17 + glibc 2.20 ? > This above crash suggests some broken guest addons or something like that... I use VMware Workstation 10.0.3 build-1895310 Host is Mageia 3.14.18-desktop-3.mga4 There is no new updates.
(In reply to Frank Griffin from comment #10) > In both cases you can reach the DHCP server, so there's nothing wrong with > the interface itself. > > I assume that "ping 172.16.215.2" fails on 17 ? So it's just your gateway > it can't get to. > > Can you ping your DHCP server ? Can you ping any other server on your > intranet (e. g. the system hosting the VM) ? I can't do any networkconnection from Mageia 5 Alpha 2 I can do what I want from other VMguests with no problem for example Windows 7, windows 8, CentOS and so on. For me it looks like that the problem is Mageia 5 Alpha 2 kernel that is the problem. Everything works with kernel 3.15.6 and stop working with 3.17.0.rc6 and so forth. So the some change done in kernel 3.17.0 is the reason for the errors
(In reply to Jan Pihlgren from comment #12) > (In reply to Frank Griffin from comment #10) > > In both cases you can reach the DHCP server, so there's nothing wrong with > > the interface itself. > > > > I assume that "ping 172.16.215.2" fails on 17 ? So it's just your gateway > > it can't get to. > > > > Can you ping your DHCP server ? Can you ping any other server on your > > intranet (e. g. the system hosting the VM) ? > > I can't do any networkconnection from Mageia 5 Alpha 2 > I can do what I want from other VMguests with no problem for example > Windows 7, windows 8, CentOS and so on. > For me it looks like that the problem is Mageia 5 Alpha 2 kernel that is the > problem. No. The problem is vmware not keeping up with kernel development. They Always lag behind ... > Everything works with kernel 3.15.6 and stop working with 3.17.0.rc6 and so > forth. > So the some change done in kernel 3.17.0 is the reason for the errors They dont officially support kernel 3.17 yet. I guess they will catch up eventually...
@Jan You miss the point. Your 17 boot is sending out a DHCPREQUEST broadcast, and it is getting a response back, or else you wouldn't have the IP address 172.16.215.133 assigned to the interface. That proves that the eth interface is not only up but functional. The problem is obviously related to 3.17, but it appears to have to do with whom you're trying to talk to, and not the actual network connectivity. @Thomas I don't know that much about VMWare. Are they really sensitive to Linux kernel versions ?
Yep, we get bugreports every release... a Quick google shows something like this needed: http://pastebin.com/t8gXaHSq
Good god, I knew there was some reason I used VBox besides just being cheap :-)
(In reply to Thomas Backlund from comment #13) > (In reply to Jan Pihlgren from comment #12) > > (In reply to Frank Griffin from comment #10) > > > In both cases you can reach the DHCP server, so there's nothing wrong with > > > the interface itself. > > > > > > I assume that "ping 172.16.215.2" fails on 17 ? So it's just your gateway > > > it can't get to. > > > > > > Can you ping your DHCP server ? Can you ping any other server on your > > > intranet (e. g. the system hosting the VM) ? > > > > I can't do any networkconnection from Mageia 5 Alpha 2 > > I can do what I want from other VMguests with no problem for example > > Windows 7, windows 8, CentOS and so on. > > For me it looks like that the problem is Mageia 5 Alpha 2 kernel that is the > > problem. > > No. > The problem is vmware not keeping up with kernel development. They Always > lag behind ... > > > > Everything works with kernel 3.15.6 and stop working with 3.17.0.rc6 and so > > forth. > > So the some change done in kernel 3.17.0 is the reason for the errors > > They dont officially support kernel 3.17 yet. I guess they will catch up > eventually... OK, I understand. Good to know this. Two things: First, the problem is between 3.17.0 and VMware. Second I will wait for Mageia 5 Beta and an update from VMware. Thanks for your patient and your work to clear for me where the problem seems to be. Thanks.
I now have update VMware Workstation to 10.0.4 (released 2014-10-30) and Mageia 5 Alpha 2 kernel to 3.17.2 with no success. But VirtualBox 4.3.16 works OK.
Yeah, well that changelog between 10.0.3 and 10.0.4 is short: * Fixes memory issue in Workstation on Microsoft Windows 8.1 and Windows Server 2012.
Today I installed Mageia 5 Beta 1, kernel 3.17.2-server-4.mga5 Now Mageia work with VMware Workstation 10.0.4 Now I'm really happy! Good work. For me you can close the case.
ok closing then
Status: NEW => RESOLVEDResolution: (none) => FIXED