Software Archive
Read-only legacy content
17061 Discussions

Host OS Ubuntu 14.04 Virtual Centos 7.1

Eric_B_1
New Contributor I
‎09-10-2015 07:59 AM
1,089 Views

So I am trying to start a virtual machine on ubuntu 14.04 using virtual machine manager.

I used the following instructions:

https://software.intel.com/en-us/articles/getting-kernel-based-virtual-machine-kvm-to-work-with-intel-xeon-phi-coprocessors

Minus the kernel patch part. (Which may be the issue).

When the virtual machine starts this is the status:

  • sudo service mpss status
  • mpss is stopped
  • dmesg | less 
    • [    3.130504] mic: module verification failed: signature and/or required key missing - tainting kernel
[    3.134219] vnet: mode: dma, buffers: 62
[    3.137954] mic 0000:00:08.0: irq 42 for MSI/MSI-X
[    3.138639] mic0: Transition from state ready to resetting
[    5.855699] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    5.856552] SELinux: initialized (dev nfsd, type nfsd), uses genfs_contexts
[   13.141207] mic_probe 0:8:0 as board #0
[   13.141231] mic: number of devices detected 1
[   14.143051] mic0: Resetting (Post Code 12)
[   14.143077] mic0: Transition from state resetting to ready
[   23.680495] mic0: Transition from state ready to booting
[   23.680503] mic image: /usr/share/mpss/boot/bzImage-knightscorner
[   23.680504] MIC 0 Booting
[   36.427086] Waiting for MIC 0 boot 5
[   41.437068] Waiting for MIC 0 boot 10
[   46.447080] Waiting for MIC 0 boot 15
[   50.891492] systemd-journald[552]: Received request to flush runtime journal from PID 1
[   51.457041] Waiting for MIC 0 boot 20
[  212.779045] Fail booting MIC 0. Wait time execeed 180 seconds

  • sudo micctrl –s

    • mic0: boot failed

  • sudo vim /var/log/mpssd

    • Thu Sep 10 05:32:05 2015: MPSS Daemon start
Thu Sep 10 05:32:05 2015: mic0: Command line: quiet root=ramfs console=hvc0 cgroup_disable=memory highres=off
Thu Sep 10 05:32:06 2015: mic0: Debug log buffer addr ffffffff818a3320 len @ ffffffff81724cc0
Thu Sep 10 05:32:06 2015: mic0: Generate /var/mpss/mic0.image.gz
Thu Sep 10 05:32:09 2015: mic0: State ready -> booting
Thu Sep 10 05:32:17 2015: mic0: Booting /usr/share/mpss/boot/bzImage-knightscorner initrd /var/mpss/mic0.image.gz

  • Vim /var/logs/messages

    • Sep  9 07:53:42 localhost NetworkManager[1000]: <info>  parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Sep  9 07:53:42 localhost NetworkManager[1000]: <info>  parsing /etc/sysconfig/network-scripts/ifcfg-mic0 ...
Sep  9 07:53:42 localhost NetworkManager[1000]: <info>      read connection 'System mic0'
Sep  9 07:53:42 localhost NetworkManager[1000]: <warn>      Ignoring connection 'System mic0' / device 'mic0' due to NM_CONTROLLED=no.
Sep  9 07:53:42 localhost NetworkManager[1000]: <info>  (mic0): new Generic device (driver: 'micvnet' ifindex: 4)
Sep  9 07:53:42 localhost NetworkManager[1000]: <info>  (mic0): exported as /org/freedesktop/NetworkManager/Devices/3

  • On host OS (Ubuntu 14.04) lspci 09:00.0 Co-processor: Intel Corporation Xeon Phi coprocessor 3120 series (rev 20)

  • On VM (Centos 7.1) lspci 00:08.0 Co-processor: Intel Corporation Xeon Phi coprocessor 3120 series (rev 20)

  • Miccheck

    • Test 0: Check number of devices the OS sees in the system ... pass
  Test 1: Check mic driver is loaded ... pass
  Test 2: Check number of devices driver sees in the system ... pass
  Test 3: Check mpssd daemon is running ... fail
    mpssd daemon not running

  • sudo service mpss start

    • Starting mpss (via systemctl):  Job for mpss.service failed. See 'systemctl status mpss.service' and 'journalctl -xn' for details.                                                    [FAILED]

  • systemctl status mpss.service

    • mpss.service - Intel(R) MPSS control service
   Loaded: loaded (/etc/systemd/system/mpss.service; enabled)
   Active: failed (Result: exit-code) since Thu 2015-09-10 06:27:55 EDT; 27s ago
  Process: 6058 ExecStart=/etc/init.d/mpss start (code=exited, status=1/FAILURE)

Sep 10 06:27:49 localhost.localdomain systemd[1]: Starting Intel(R) MPSS control service...
Sep 10 06:27:55 localhost.localdomain mpss[6058]: Starting Intel(R) MPSS: [FAILED]
Sep 10 06:27:55 localhost.localdomain systemd[1]: mpss.service: control process exited, code=exited status=1
Sep 10 06:27:55 localhost.localdomain systemd[1]: Failed to start Intel(R) MPSS control service.
Sep 10 06:27:55 localhost.localdomain systemd[1]: Unit mpss.service entered failed state

  • sudo journalctl -xn

    • -- Logs begin at Thu 2015-09-10 05:31:46 EDT, end at Thu 2015-09-10 06:28:54 EDT. --
Sep 10 06:28:52 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 2 of 5 (Device Configure) complete.
Sep 10 06:28:53 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Sep 10 06:28:53 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 3 of 5 (IP Configure Start) started...
Sep 10 06:28:53 localhost.localdomain NetworkManager[1001]: <info>  (ens9): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 10 06:28:53 localhost.localdomain NetworkManager[1001]: <info>  Activation (ens9) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 10 06:28:53 localhost.localdomain NetworkManager[1001]: <info>  dhclient started with pid 6137
Sep 10 06:28:53 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 3 of 5 (IP Configure Start) complete.
Sep 10 06:28:53 localhost.localdomain dhclient[6137]: DHCPDISCOVER on ens9 to 255.255.255.255 port 67 interval 8 (xid=0x42983a6f)
Sep 10 06:28:54 localhost.localdomain avahi-daemon[824]: Registering new address record for fe80::5054:ff:fe4f:8e4 on ens9.*.
Sep 10 06:28:54 localhost.localdomain sudo[6141]: ##### : TTY=pts/0 ; PWD=/home/#### ; USER=root ; COMMAND=/bin/journalctl –xn

  • Reboot card sudo micctrl –rw

    •  mic0: resetting

    • mic0: ready

  • ​start mpss sudo service mpss start

  • sudo micctrl –s

    • mic0: booting (mode: linux image: /usr/share/mpss/boot/bzImage-knightscorner)

  • ifconfig

    • mic0: flags=3<UP,BROADCAST>  mtu 64512
        inet 172.31.1.254  netmask 255.255.255.0  broadcast 172.31.1.255
        inet6 fe80::4e79:baff:fe30:53  prefixlen 64  scopeid 0x20<link>
        ether 4c:79:ba:30:00:53  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  carrier 0  collisions 0

  • miccheck

    • MicCheck 3.5.2-r1
Copyright (c) 2015, Intel Corporation.

Executing default tests for host
  Test 0: Check number of devices the OS sees in the system ... pass
  Test 1: Check mic driver is loaded ... pass
  Test 2: Check number of devices driver sees in the system ... pass
  Test 3: Check mpssd daemon is running ... fail
    mpssd daemon not running

  • sudo mpssd

  • miccheck

    • MicCheck 3.5.2-r1
Copyright (c) 2015, Intel Corporation.

Executing default tests for host
  Test 0: Check number of devices the OS sees in the system ... pass
  Test 1: Check mic driver is loaded ... pass
  Test 2: Check number of devices driver sees in the system ... pass
  Test 3: Check mpssd daemon is running ... pass
Executing default tests for device: 0
  Test 4 (mic0): Check device is in online state and its postcode is FF ... fail
    device is not online: boot failed

Status: FAIL
Failure: A device test failed

  • Using this: https://software.intel.com/sites/default/files/managed/fa/ac/Intel_MPSS_Debugging_Linux_MPSS3.pdf

    • Everything looks good until

    • dmesg | less

    • and there is a code 12

    • sudo service micras start

      • ​Thu Sep 10 06:45:51 2015 MICRAS INFO    : MCA filter log file not existed, create a new filter log file.

      • Thu Sep 10 06:45:51 2015 MICRAS ERROR   : No MIC device detected!

  • ​​sudo service mpss unload

    • ​[sudo] password for ###:

    • Shutting down Intel(R) MPSS:

    • Removing MIC Module: modprobe: FATAL: Module mic is in use.                                                         [FAILED]

 

​​Now im stuck any ideas?

 

0 Kudos

Link Copied

7 Replies
Frances_R_Intel
Employee
‎09-10-2015 04:34 PM
1,089 Views

Two things -

As I understand it, not installing the patches is like not enabling large bar in the BIOS. My understanding could be faulty but - look in drivers/pci/pci.h - if the type of pci_resource_alignment is int, you are going to have problems.

NetworkManager makes some assumptions about non-hardwired network interfaces, like the virtual Ethernet over PCI, and can cause problems for the coprocessor. It is recommended that you use the older network service (see the Users Guide that came with your release of MPSS).

0 Kudos
Copy link
Eric_B_1
New Contributor I
‎09-11-2015 04:37 AM
1,089 Views

So where might i find this:

drivers/pci/pci.h - if the type of pci_resource_alignment

There are two on my VM that link to each other: in /usr/include/linux

From Page 23:

service NetworkManager status

Redirecting to /bin/systemctl status  NetworkManager.service
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Fri 2015-09-11 03:22:52 EDT; 8min ago
 Main PID: 1001 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─1001 /usr/sbin/NetworkManager --no-daemon
           ├─1330 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-ens3.pid -lf /var/lib/NetworkManager/dhclient-3f3067f8-42ee-4554-af5f-6711f772501b-...
           └─4021 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-ens9.pid -lf /var/lib/NetworkManager/dhclient-876a9ecf-13b6-4dd7-a1a9-9a1087c42faf-...

Sep 11 03:31:37 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 2 of 5 (Device Configure) complete.
Sep 11 03:31:38 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Sep 11 03:31:38 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 3 of 5 (IP Configure Start) started...
Sep 11 03:31:38 localhost.localdomain NetworkManager[1001]: <info>  (ens9): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 11 03:31:38 localhost.localdomain NetworkManager[1001]: <info>  Activation (ens9) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 11 03:31:38 localhost.localdomain NetworkManager[1001]: <info>  dhclient started with pid 4021
Sep 11 03:31:38 localhost.localdomain NetworkManager[1001]: <info>  (ens9): Activation: Stage 3 of 5 (IP Configure Start) complete.
Sep 11 03:31:38 localhost.localdomain dhclient[4021]: DHCPDISCOVER on ens9 to 255.255.255.255 port 67 interval 3 (xid=0x2a5312e5)
Sep 11 03:31:41 localhost.localdomain dhclient[4021]: DHCPDISCOVER on ens9 to 255.255.255.255 port 67 interval 4 (xid=0x2a5312e5)
Sep 11 03:31:45 localhost.localdomain dhclient[4021]: DHCPDISCOVER on ens9 to 255.255.255.255 port 67 interval 8 (xid=0x2a5312e5)

 

service network start
Starting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details. [FAILED]

systemctl status network.service
network.service - LSB: Bring up/down networking

   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: failed (Result: exit-code) since Fri 2015-09-11 03:34:05 EDT; 1min 19s ago
  Process: 4217 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Sep 11 03:34:05 localhost.localdomain network[4217]: Bringing up loopback interface:  [  OK  ]
Sep 11 03:34:05 localhost.localdomain network[4217]: Bringing up interface eth0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device  does not seem to be pre...alization.
Sep 11 03:34:05 localhost.localdomain network[4217]: [FAILED]
Sep 11 03:34:05 localhost.localdomain network[4217]: Bringing up interface mic0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device mic0 does not seem to be...alization.
Sep 11 03:34:05 localhost.localdomain network[4217]: [FAILED]
Sep 11 03:34:05 localhost.localdomain systemd[1]: network.service: control process exited, code=exited status=1
Sep 11 03:34:05 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
Sep 11 03:34:05 localhost.localdomain systemd[1]: Unit network.service entered failed state.

May be onto something with the eth0

 

 

0 Kudos
Copy link
Surya_Narayanan_N_
Beginner
‎10-27-2015 09:38 AM
1,089 Views

is this issue resolved? @Eric where you able to get the MPSS latest version working without patch? I would like to install similar thing.

0 Kudos
Copy link
Eric_B_1
New Contributor I
‎10-29-2015 08:37 AM
1,089 Views

I am still working this:

I may have an updated post later today.

0 Kudos
Copy link
Eric_B_1
New Contributor I
‎10-29-2015 08:50 AM
1,089 Views

By the way is you want to do:

Centos 7, RHEL 7, openSuse , Suse 

Virtual manager works great out of the box.

0 Kudos
Copy link
Surya_Narayanan_N_
Beginner
‎10-29-2015 08:55 AM
1,089 Views

@Eric, did you mean the procedure given in the KVM document works well without the patch in Centos7?

0 Kudos
Copy link
Eric_B_1
New Contributor I
‎11-02-2015 06:30 AM
1,089 Views

Yes

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.