SR - IOV

Similar Questions

• Alias of IOV Distributed System Manager

  Is it possible to see the IOV alias name and the name of the physical channel

  a cRIO channel?  The Project Explorer displays cRIO channels in this way and

  would be nice if the DSM would do that also.  Otherwise if you track down

  a bad transducer on a high lane count module, you will need to list the

  channels in your head.

  One possibility is to look into the following file stored on the cRIO system and extract the information from there.

  C:\NI-RT/config/variables. XML

  This file contains simple XML code, listing all the IOVs in the current configuration of the cRIO system.

  The attached sample project shows how you can read and analyze the information directly on the cRIO system. Of course, you can also copy (FTP) this file to the host and analyzed it.

  Note: Scan Engine Channel Info Plus.vi included in the sample, download its own bitstream on the FPGA to determine which modules of series C are located in the cRIO chassis. So this VI cancels and replaces any current FPGA VI running on the cRIO chassis. Use this VI cautiously because it can cause serious problem in your application due to the interruption of the FPGA.

  This example uses the reference for the CRY component library to retrieve information about cRIO current of the system hardware.

• Is it possible to MOS engine tuner to search for words with a hyphen (SR - IOV / SRIOV)?

  Hello

  SR - IOV allows to create virtual functions on Ethernet or FC HBA card,

  If new virtual ports can be created and assigned to logical domains with Oracle LMOS.

  Documentation Oracle talk SR - IOV, IE:

  http://docs.Oracle.com/CD/E38405_01/HTML/E38406/sriovoverview.html

  but in may other scenarios (bugs, mos docs, patches) can be read SRIOV

  So, there is a huge difference in MOS looking with the word "SR - IOV" (with hyphen) against the word "SRIOV" (without hyphen)

  Q. is possible to set this specific word (SR - IOV / SRIOV) search engine MOS

  so when you search for this word SR - IOV or SRIOV, he would do an effective search for SR - IOV and SRIOV?

  Thanks in advance,

  Miguel Angel

  Hello Miguel.

  Yes, it is possible.  We will grant so that when your search query contains sr - iov or sriov, it will do an effective search on both.

  Thank you

  Debbie Sta. Iglesia

• SR - IOV and VXLN

  Hello

  Is SR - IOV support VXLAN?

  This KB shows virtual VXLAN son not being supported witih SR - IOV in vSphere 5.1 and 5.5: VMware KB: SR - IOV FAQ support status

  Page 139 of the vSphere network guide also lists 6, VXLAN virtual son as features not available for virtual machines configured wit SR - IOV.

• Can not do the ping test with to assign a VF SR - IOV for an operating system called window 2008.

  Hello

  I am very confused on below question:

  When I using a 2008 guest operating system window, can't do the test of ping with a pc.

  But if I'm using a linux guest OS, it doesn't.

  NIC: x 540 - at2

  ESXi:5.5 u2

  Steps to follow:

  1. install ESXI.

  2. create VFs and create the guest operating system.

  3. assign to guest operating system.

  4. install the driver on the windows of the guest operating system 2008.

  5 make the test ping with a pc.                < = problem

  Maybe need a configuration on the guest operating system or ESXI?

  or maybe it's a limitation of vmware?

  Update intel IGB driver to 3.21.4 on the ESX host and try...

• Shared variables, analysis engine and multiple targets

  I'm looking for some general tips on my LabVIEW project structure.

  The project consists of a laptop with LabVIEW, a connected joystick and a CompactRIO connected via ethernet. I ran the cRIO mode Interface FPGA, but a change in some things causes the project to have be moved to scan mode.

  From now on, the code on the portable computer updates the shared variables on the cRIO and bed from the variables shared on the cRIO for surveillance. I want to shared variables on the cRIO because he will also need to work without the connected laptop. Before moving the cRIO for scan mode, I found that I had to first run the code of the laptop and then run the code cRIO, or shared variables would not release properly. Now that I spent to scan mode, I have to run the code cRIO first, and even then the shared vars do not properly communicate for more than a few seconds and are well laggier.

  My ideal project solution is a system that can operate with or without the connected laptop and obviously do not have these questions shared variable. I would like the autostart code on the cRIO and ask the user to execute the code of the computer laptop, if necessary, but in the past, it doesn't seem to work with shared variables.

  I'm really confused about why this is happening. I hope I explained my problem well enough. I really don't want to display the entire project here, but I can email to people if they are willing to take a look. Thank you for taking the time to read this.

  I'm under LabVIEW 2010 SP1 with FPGA, DSC modules and robotic in real time. I have the updated Feb 11 driver and NOR-RIO 3.6.0 installed and completed all updated on my RT cRIO.

  I do this kind of thing all the time...

  Move all your NSV libraries on the cRIO.  Of the project, you must deploy on the cRIO and then they are persistent until you reformat.

  Your windows GUI application, you can set static NSV tags on the block schema or use the API SV dynamic R / w.  Also you can bind GUI controls and

  indicators directly to the NSV cRIO (it's what I do) also I create a library of 'mirror' in the PC HMI that is linked to the library of cRIO.  This library has DSC Citadel

  data record enable and automatically records the historical traces of all my important data - very nice.  Libraries hosted PC can be set to autodeploy in the version of the app.

  the project also has an option of autodeploy to the development environment that normally, I turned off.  If you have a PC at the cRIO binding configuration so be careful

  on any kind of autodeployment because this will eventually force the cRIO app stop when you deploy.  To work around this problem, you can use the PSP (IP address rather than project binding

  process name) and use of the DSC deploy library s vi in your HMI application.  Once you use the scan engine, you can use the app DSM (Distributed System Manager) to view, DIF and

  each of you IOV and NSV graphic on your network.

• deploy the project with Ethercat

  Hi all!

  I need help. I created a project that consists of two parts. The host to run on a Standard PC (HMI display...), that the second part is working on a controller PXI (RT) linked to an Ethercat 9144. I have my project debugging and everything works perfectly, I am able to read variable Ethercat of host, send data to the RT using shared variables...

  To complete my project, I wanted to create an exe for the RT. This is the beginning of my problems. I built the executable, set it as start and deploy the exe to the target. After rebotting target, I started the application on the host... Now, it is impossible to read Ethercat variables and variable shared. If I try to set up the shared variable or the Ethercat for the project, it stops the executable that runs on the target...

  I have not found any documents that describe how to deploy variable Ethercat in an executable... Does anyone have an idea about this problem? any suggestion is welcome...

  When running a windows project, libraries RT SV are usually defined to deploy automatically when the application of the RT is deployed.  Also you can manually deploy libraries SV yourself project.

  Once a SV belonging is deployed on an RT target that it will stay there until eliminated.  You can verify your deployment with Distributed System Manager (DSM) If you see it then you're good.

  Your RT exe cannot deploy its own libraries, they should be deployed in advance.  In addition, you should be able to use the DSM to see the IOV engine on the 9144 chassis analysis even if your RT application is not running.  Check this first.  Also check the on your target RT .alias file to make sure it has the appropriate IP addresses to resolve any URL NSV.

• T420 Graphics support?

  I recently received a T420 for virtualization in a lab environment.  I do not VDI, but I don't want to run several virtual machines at once, which will be my daily VM.  I have no need of a GPU for thousands of dollars more but I want graphics better than the edge [] most of the servers are given.  No crazy game, but some GPU functions would be nice.  That's the problem.  It seems that ONLY cards that this guy supports are the Q4000 and Q6000 Nvidia cards?  Seriously?  Is this really the case? I don't care about Dell support but I am not allowed to use my graphics for a $100 Best Buy card?  I really hope I'm just something missing.  The T420 allows graphics cards Nvidia Q4000 or Q6000?  If not, what is someone knows why?  What is a bios limitation?  Is this some other limitations of the technique?

  Hi Zanzaboo,

  I'm not aware of what we have done to disable not taken in charge specifically video cards, although we certainly cannot guarantee their compatibility or we tested or them validated in all configurations and for this reason, do not recommend. For graphics supported on the T420 (as you correctly identified as the Q4000 and Q6000), you must disable video output shipped from the BIOS/system setup under embedded devices (pg 30-31, support.dell.com/.../T420OMen.pdf ) to get the video output. Note that when you do so, the video output of iDRAC virtual console will not be available until the embedded video is again enabled. I don't know of any reason you can not follow the same steps with an unsupported graphics card but I must stress we do not test or validate it and if it does not you would have any recourse under the guarantee (i.e. not replace us the motherboard for a defective PCI-e port for example). I don't know if PCI-e video passthrough works here, but you may need to configure the SR - IOV (just below the embedded video setting), by the needs of your hypervisor. Let us know how it goes and good luck!

• DELL PowerEdge T710 support for 2012 Windows

  Hello

  I was reading this document on the support Windows 2012:

  http://en.community.Dell.com/TechCenter/OS-applications/w/wiki/4149.Dell-PowerEdge-server-support-for-Windows-Server-2012-and-its-features.aspx

  If I understand correctly T710 is supported for the installation of Windows 2012 as:

  Support Dell - qualified.

  And 'X' means that the long-term 2012 Windows: error memory consumed, Collaborative processor performance counters, logic processor idling, compatible device name are not supported on this server. Only SR-IOV future is supported?

  Thank you

  That is right.  Consumed memory error, the processor performance counters Collaborative, idling logical processor and compatible device Naming are only available on generation servers 12.   Server 2012 will take place on the T710.

  Kind regards

• Fabric 6248 with MDS

  Hi all

  We are at the stage of inter-connecting simple IBM V3700 SAN box with double FI 6248 (redundant) via unique Cisco MDS 9000 SAN Switch with single UCS 5108 chasis.

  We have four blades B200 M3 in UCS 5108. The blades have no local hard disks. Our requirement is to install hyperV/Windows on IBM storage.

  I did the physical connections between IBM and MDS & MDS FI 6248 and FI 6248 dual Core 6509 VSS enabled.

  I don't have issues with part FI 6248 and LAN, I have doubts about FI 6248 with SAN kindly advise.

  6248 FI are default mode (Host End). I need to change FI on switch mode?
  I change ports Uplink FC, unified FI ports connected to the MDS are configured as storage CF?
  How vNIC, vSAN (vSAN how do I need), vHBA & Service profile works to each other? can any advise please?
  What steps do we need to set up in FI & MDS so that we can use SAN storage for hyperV/Windows installation?

  It's my first deployment of the UCS 5108, to apologize to ask fundamental questions.

  Kind regards

  1. what would be the impact of multiple VSANS vs default vSAN, I plan to use default vSan in the two FI-6248 & I can't find any problem with this, please advise.

  Please do not use default vsan (vsan nr or 1); best practices: create different VSAN fabric A and B; e.g. vsan 10A, vsan 20 b

  2 - pool WWPN, should I create two different WWPN pool 1 for FI-6248-A & others for FI-6248-B? I have only a UCS 5108 chasis, we cannot set an unique WWPN for the two FI-6248 Pool? What is the best practice? I can't find any problem with single WWPN pool. Please advise.

  Best practices: use pools of different pwwn to fabric A and B; useful for troubleshooting; in General: all pools must also encode a field id UCS (your starting with 1). just in case in the future, you have another! See attachment.

  3 - incase, if I will configure 1 WWPN pool would I face any problem in mapping the area in MDS? According to my understanding there will be no problem because the area is just the initiator (Server Blade) mapping & target (IBM Storage). Keep in mind, I only Cisco MDS SAN Switch NOT redundant. Please advise.

  Even with an SDM, you create a virtual double fabric with 10 and 20 VSANs. zoning is done by VSANs, zones and activation as well!

  what adapter policy 4 - Creating Service profile should I choose in the menu Dynamics vNIC? I want to install Windows on Hyper V environment, but I'm not hyper V option. It has linux, VMWare, VMWare passthrough, window, default & some HyperV more but not?

  You do not create dynamic vNIC! This only applies to the VM - FEX, resp. SR - IOV. Hyper-V means political adapter = window

  Good luck

  Walter.

• Is it Possible to access only bypassed FC HBA to multiple virtual machines

  Hello

  I have a FC HBA on my 5.5 ESX. Server. It does not support the function of SR - IOV. Is it possible to access this FC HBA across multiple virtual machines?

  If possible, please provide as follows to go further.

  Kind regards

  Aashish

  It is not possible. The basic material underlying PCI specification does not have a single shared between several independent operating systems PCI device.

  SR - IOV solves by creating the virtual function peripheral PCI, but as you mentioned, that he can't stand not and first of all, ESXi supports that SR - IOV for Ethernet network devices and not for native FC HBA (excluded FCoE) functions.

• Separate VSANS / Mgmt / Vmotion traffic on different switches

  Hello

  I want to build a hybrid Cluster VSAN 4 knots (6.x).

  I have 2 x 10GE switches dedicated for Taffic VSAN

  also 2 * 1GBE switches for management / VM / Vmotion traffic

  Each host has 2 10 GbE NIC, 1 uplink for each of 10GBE switches

  Each host also has 4 * rising 1GBE, 2 for each of the switches 1GBE

  My idea is to use 10GBE just for VSAN traffic (separate DVSWitch, an asset, a standby) on each 10GBE switch

  Also to use 2 Ports on the management traffic (separate DVSWitch, an asset, a standby) on each 1GBE switch

  And use 2 Ports on traffic VM (separate DVSWitch, an asset, a standby) on each 1GBE switch

  VMotion traffic would be on the same rising as management, but active / standby vice versa

  Question: is - this possiuble / useful to connect vmotion for 10 GbE uplink ports (active standby vice versa VSAN traffic)

  I appreciate any useful comment on my scheduled install (I have no boy networking)

  Couple thoughts.  You can run several vKernels to VSAN and vMotion (allowing one on each switch).  To VSAN, use of VLANS / subnets (one on each switch offers you a pleasant has / B space) while vMotion must have all the vkernel on the same subnet 2 ideally layer.  This allows for maximum reliability, in theory faster failover and access flow.  This also has the advantage of if your cluster is not big (bigger that say 48 ports) you can avoid having multicasting, leaving the switch (usually requires more quarrels with the cats of network) as each switch TOR will have its own VSAN network.    Then use the NIOC for butterfly and protect the traffic between them.  Now the NIOC is not as effective as SR - IOV (but its good enough) to 100% and you will maximize your investment 10 Gbps without swamping the things.

  • Network management interface VMkernel = explicit order of Fail-over = active P1 / P2 ensures 10.1.1.1/24 VLAN 100
  • vMotion VMkernel - an explicit order of Fail-over = interface = active P1 / P2 ensures 10.1.2.1/24 VLAN 101
  • vMotion VMkernel-B interface = explicit Fail-over order active = P2 / P1 ensures 10.1.2.2/24 VLAN 101
  • Machine virtual Portgroup = explicit Fail-over order = active P1 / P2 ensures 10.1.2.1/22 VLAN 102
  • Virtual VMkernel-A SAN interface = explicit order of Fail-over = active P1 / P2 in standby (or not use) * 10.1.3.1/24 VLAN 103
  • Virtual interface of SAN VMkernel-B = explicit Fail-over order active = P2 / P1 Eve (or not use) * 10.1.4.1/24 VLAN 104

  In this case, VLAN, 100, 101 and 102 will be on all switches.

  * 103 and 104 could be configured to only exist on each switch (has / B isolation, failover do not switch on the value and set up on both) or exist on both (and use standby) as described.  This design will focus on maintaining the communications host-to-host on the same switch (decreases complications with multicasting and reduces its lag time as VSAN traffic does not have to jump to another switch unless you run out of switch ports, but now with dense 40Gbps past using 10 Gbps break out in theory you could hit the limit of 64 nodes on a single switch).

  I'm curious of anyone thoughts on just disable the failover and forcing them to each core sticking to its switch (and accepting loss of communication) on this vKernel in the event of a switch failure.  I want to do some tests with both laboratory and to test the failover of the switch/path between both of these configurations (compared to a configuration unique vkernel).

  However, some people prefer a 'simpler' configuration if (and I'm not opposed to that).

  Duncan drawn active passive failover configuration with of the vKernel unique for each host.

  In theory not being not not as dependent on the NIOC for insulation of storage should help the latency for the short bursts it takes to NIOC launch design active active vs.

  Control IO SAN and virtual network

  • Network management interface VMkernel = explicit order of Fail-over = active P1 / P2 ensures
  • vMotion VMkernel interface = explicit Fail-over order = active P1 / P2 ensures
  • Machine virtual Portgroup = explicit Fail-over order = active P1 / P2 ensures
  • SAN VMkernel virtual interface = explicit order of Fail-over = P2 active / standby P1

• SRIOV support for FreeBSD 8.4/10.1 VM with ESX 6?

  Hello experts,

  Question

  Would like to know if the SRIOV VF drivers are supported on FreeBSD 8.4/10.1 VM with ESX 6?

  Configuration information:

  In my setup, I have Intel 82599 NIC with VF interfaces configured and assigned to a virtual 10.1 FreeBSD computer.

  But claim fails with the following error message:

  ix0: Intel (r) PRO/10GbE Virtual Function Network Driver, Version - 1.1.4 > mem 0xebaf8000-0xebafbfff, 0xebafc000-0xebafffff to the 0,0 on pci3 device

  ix0: MSIX config error

  ix0: failure of PCI resource allocation

  device_attach: ix0 attach returned 6

  pcib4: < ACPI PCI - PCI bridge > camera 21.1 on pci0

  To probe further, pci_alloc_msix() call returns-1, which is unexpected.

  The PF IGB driver on esx 5.5 is 3.21.5

  The ESX version is: ESXi 5.5.0 (Build 1331820)

  If I have a Ubuntu VM affected with a VF of the same physical NETWORK adapter interface, he claims as expected.

  If I live of e/s configured for the Intel 82599 NIC, the 10.1 FreeBSD VM calls for the interface as expected

  Guidance on the support above on ESX 6.0 help.

  Kind regards

  Nirmal

  We do not have a supported guest in 6.0 OS documentation. assuming that since the previous version is not one supported. You can provide your comments to article KB KB VMware: support of the only guest operating system Root i/o Virtualization (SR - IOV).

• B2496824 Player 7.1 + Win 10 (split volume) error: not enough space on the disk

  Hello!

  I have the following configuration:

  Host: Windows 7 x 64 professional

  Host: Samsung 840 EVO 240 GB SSD with 48 GB of free

  Comments: Overview of Windows 10

  Comments: 60 GB VMDK, spread across 30 x 2 GB vmdk, which are NOT previously affected

  Description of the problem:

  I do upgrade from Windows in the Win10 system, and then at one point I had a warning of VMware Player, which is not accessible VMDK #009

  It's the NEWSPAPER, which States that vmdk #009 running out of space... which is very strange, considdering that I have 40 GB free in the guest OS and 48 GB free in the HOME... and the VMDK is an expansion of volume

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug response = 2

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: DISKLIB-LIB: RWv failed ioId: #46815 (13) (13).

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: DISK: drive e/s on scsi0:0 failed: there is not enough space on the file system for the selected operation (13)

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: # dumping contents of iov #.

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: WRITE

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: startSector = 37601304

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: numSectors = 8

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: numBytes = 4096

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: numEntries = 1

  2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: entries [0] = F53A8000 / 4096

  2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

  2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

  2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

  2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

  2015 04-15 T 10: 47:20.844 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

  2015 04-15 T 10: 47:20.844 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

  2015 04-15 T 10: 47:20.844 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

  2015 04-15 T 10: 47:20.845 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

  2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

  2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

  2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

  2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

  2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

  2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

  2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

  2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

  2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

  2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

  2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

  2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

  2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

  2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

  2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

  2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

  After copying VMDK #009 in a new file

  and after running the tool of restoration Performance of Samsung,

  Windows 10 VM is now back in business!

• VMWare Tools shared folder code does not compile on VMWare Fusion 7, Ubuntu asked 14.10, and Clipboard sharing does not work.

  Hello

  After the upgrade to a guest of 14.04 to 14.10 Ubuntu, I tried to reinstall the VMWare tools.  The problems I've come across so far:

  Shared folder code will not compile.  I get the following result:

  do: enter the directory "/ tmp/modconfig-ElOCTG/vmhgfs-only.

  Using the kernel build system.

  / usr/bin/make /lib/modules/3.16.0-23-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.16.0-23-generic'

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/message.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/dir.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/request.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/hgfsUtil.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/cpName.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/rpcout.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/stubs.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/hgfsEscape.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/link.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/transport.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/module.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/file.o

  CC [M] /tmp/modconfig-ElOCTG/vmhgfs-only/super.o

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c: in function 'HgfsAioRead ':

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c:714:4: error: implicit declaration of function 'generic_file_aio_read' [-Werror-implicit-function-declaration =]

  result = generic_file_aio_read (iocb, iov, numSegs, offset);

  ^

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c: in function 'HgfsAioWrite ':

  /tmp/modconfig-ElOCTG/vmhgfs-only/file.c:786:4: error: implicit declaration of function 'generic_file_aio_write' [-Werror-implicit-function-declaration =]

  result = generic_file_aio_write (iocb, iov, numSegs, offset);

  ^

  Cc1: some warnings are treated as errors

  scripts / Makefile.build:257: recipe for target ' / tmp/modconfig-ElOCTG/vmhgfs-only/file.o' failed

  make [2]: * [/ tmp/modconfig-ElOCTG/vmhgfs-only/file.o] error 1

  make [2]: * waiting unfinished...

  Makefile:1345: recipe for target ' _module_/tmp/modconfig ElOCTG/vmhgfs-only' failed

  make [1]: * [_module_/tmp/modconfig ElOCTG/vmhgfs-only] error 2

  make [1]: leaving directory ' / usr/src/linux-headers-3.16.0-23-generic'

  Makefile:120: doesn't have a recipe for target 'vmhgfs.ko '.

  make: * [vmhgfs.ko] error 2

  make: leaving directory ' / tmp/modconfig-ElOCTG/vmhgfs-only.

  The filesystem (vmhgfs module) driver is used only for the shared folder

  feature. The rest of the software provided by VMware Tools is designed to work

  regardless of this function.

  If you want the shared folders feature, you can install the driver of

  running vmware-config - tools.pl again after making sure that gcc, binutils, make

  and your kernel sources are installed on your computer.

  These packages are available on the installation of your distribution CD.

  [Press the Enter key to continue]

  In addition, the shared clipboard does not work.

  I'm under VMWare 7.0.0 on OS X 10.10.

  Any help or advice will be greatly appreciated.

  
  Thank you

  Jonathan Morgan

  The VMWare Tools included with fusion 7.0.1 solved this problem for me (and without any serious regressions I noticed so far, at least, which is nice but not something I intend on with vmware), so probably the next update of each VMware product should include the updated tools.  Don't know how long updates to other products are coming, however.  Wonder if there is a separate place to get just the tools to day?