i wait a long time for this driver but vmware find this is not useful or whatever... i don't know why
for mac user using esxi, fusion etc. the driver would be welcome !
i wait a long time for this driver but vmware find this is not useful or whatever... i don't know why
for mac user using esxi, fusion etc. the driver would be welcome !
Sounds promising but I cant test it. I do not have a Development ESXi Server available at this moment so I will have to wait for another client to make tests before getting it on production.
I found a script that does the job to make versions of the log but the old versions are not removed so the log will not grow indefinitely but the count of files will. This is OK but not enough as cant let the ESXi unattended. I am not a bash programmer so I do not know ho to modify it to remove the old files after a certain number of them.
dingo and djciaro are you guys doing the below steps assuming your server is running HP Hardware:
1. Update the firmware using the last HP SPP 2016.04 (864794_001_spp-2016.04.0-SPP2016040.2016_0317.20.iso) ?
2. Upgrade or install the ESXi using the HPE latest ESXi (VMware-ESXi-5.5.0-Update3-3568722-HPE-550.9.5.0.33-Apr2016.iso) ?
There is no support for thin-print in Mac OS X guest, but you can add the printer in the VM manually.
It would be convenient to have a "Add Device ..." selection.
I have been searching the internet for an hour and I cannot find any information about how to switch from a parallels 9.0 virtual machine to a vmware virtual machine using a mac pro. I am thinking about switching but I need to have directions before I will make the switch. Teresa
Good evening,
I am using VMware vSphere 5.5 (no update) with Windows 10 Pro, connected to the host server vmware ESXi 5.5, but when you connect a VM by vshpere console, the screen does not fit as it should (attached).
Could someone please help me?
Thank you!
Setup: VMWare ESXi 6.0 Update 2, with a Centos 7 guest VM using vmic1
Problem: Centos 7 cannot ping default gateway, but can ping other hosts on the same network. As seen from the output below (both Centos and Windows10) these hosts all report the same MAC for the FW (default gateway) in their ARP tables. The Centos host pings the Windows box with no problem and vice-versa. Win10 has no issues pinging the default gateway either. Furthermore, the mac address for the Centos box is also listed in the FW's ARP table at the bottom. Can someone help identify the problem here?
!===============Centos
[root@cloud ~]# ifconfig
eno16777984: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.255.10 netmask 255.255.255.0 broadcast 192.168.255.255
inet6 fe80::20c:29ff:fe0f:5e8b prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:0f:5e:8b txqueuelen 1000 (Ethernet)
RX packets 12 bytes 1410 (1.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 62 bytes 6726 (6.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@cloud ~]# arp -n
Address HWtype HWaddress Flags Mask Iface
192.168.255.1 ether 84:b5:9c:2c:40:50 C eno16777984
[root@cloud ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.255.1 0.0.0.0 UG 0 0 0 eno16777984
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eno16777984
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
192.168.255.0 0.0.0.0 255.255.255.0 U 0 0 0 eno16777984
[root@cloud ~]# ping 192.168.255.101
PING 192.168.255.101 (192.168.255.101) 56(84) bytes of data.
64 bytes from 192.168.255.101: icmp_seq=1 ttl=128 time=0.544 ms
64 bytes from 192.168.255.101: icmp_seq=2 ttl=128 time=0.474 ms
64 bytes from 192.168.255.101: icmp_seq=3 ttl=128 time=0.436 ms
[root@cloud ~]# firewall-cmd --state
not running
[root@cloud ~]#
[root@cloud ~]# cat /etc/sysconfig/network-scripts/ifcfg-eno16777984
TYPE=Ethernet
BOOTPROTO=static
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=eno16777984
UUID=c6a00e9f-ab1f-4a5b-92fa-13b15aff8cb8
DEVICE=eno16777984
ONBOOT=yes
HWADDR=00:0c:29:0f:5e:8b
IPADDR=192.168.255.10
NETMASK=255.255.255.0
GATEWAY=192.168.255.1
NETWORK=192.168.255.0
DNS1=8.8.8.8
[root@cloud ~]#
!============= Windows 10
Windows IP Configuration
Ethernet adapter INET:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::3ca2:6e9d:7a95:c9fc%28
IPv4 Address. . . . . . . . . . . : 192.168.255.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.255.1
C:\Users\admin>arp -a
Interface: 192.168.255.101 --- 0x1c
Internet Address Physical Address Type
192.168.255.1 84-b5-9c-2c-40-50 dynamic
192.168.255.10 00-0c-29-0f-5e-8b dynamic
192.168.255.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
<ping from Win10 to Centos>
C:\Users\admin>ping 192.168.255.10
Pinging 192.168.255.10 with 32 bytes of data:
Reply from 192.168.255.10: bytes=32 time<1ms TTL=64
Reply from 192.168.255.10: bytes=32 time<1ms TTL=64
<ping from Win10 to gateway>
C:\Users\admin>ping 192.168.255.10
Pinging 192.168.255.10 with 32 bytes of data:
Reply from 192.168.255.10: bytes=32 time<1ms TTL=64
Reply from 192.168.255.10: bytes=32 time<1ms TTL=64
!================Firewall (default gateway)
root@MyDoorMat> show arp
MAC Address Address Name Interface Flags
00:0c:29:0f:5e:8b 192.168.255.10 192.168.255.10 vlan.255 none
bc:5f:f4:ea:28:64 192.168.255.101 192.168.255.101 vlan.255 none
Same problem here. I never had this problem with Workstation 11 and earlier. Now, with both Workstation 12 and 12.5 it's a constant battle to try and avoid "Building Menu". If it works, it works, otherwise I have to reboot the VM and try Unity again. This stinks.
It seems that you can override the policy (per vRealize Automation 7.1 Information Center).
I wonder if you could create a blank policy? I've not tried that.
Yes, this is by design so far.
<ping from Win10 to gateway>
C:\Users\admin>ping 192.168.255.10
Pinging 192.168.255.10 with 32 bytes of data:
Reply from 192.168.255.10: bytes=32 time<1ms TTL=64
Reply from 192.168.255.10: bytes=32 time<1ms TTL=64
above, you pinged to CentOS from Win10 not gateway.
can you ping to gateway 192.168.255.1 from win10 and centOS and share output?
-
Haridas
!======Centos
[root@cloud ~]# ping 192.168.255.1
PING 192.168.255.1 (192.168.255.1) 56(84) bytes of data.
^C
--- 192.168.255.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms
!======Windows
C:\Users\admin>ping 192.168.255.1
Pinging 192.168.255.1 with 32 bytes of data:
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Reply from 192.168.255.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.255.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
!=========Firewall
root@MyDoorMat> ping 192.168.255.101
PING 192.168.255.101 (192.168.255.101): 56 data bytes
64 bytes from 192.168.255.101: icmp_seq=0 ttl=128 time=1.636 ms
64 bytes from 192.168.255.101: icmp_seq=1 ttl=128 time=1.724 ms
64 bytes from 192.168.255.101: icmp_seq=2 ttl=128 time=1.635 ms
^C
--- 192.168.255.101 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.635/1.665/1.724/0.042 ms
root@MyDoorMat> ping 192.168.255.10
PING 192.168.255.10 (192.168.255.10): 56 data bytes
^C
--- 192.168.255.10 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
root@MyDoorMat>
no, you have to take 3rd party app backup separately.
I have SUSE Linux Enterprise Server 12.x virtual machines currently running from HyperV2012 R2, with UEFI Firmware Interface.
As per the VMWARE converter user guide, its not listed as supported. SLES 12 is not listed at all, and as for the UEFI in SLES 11 version itself is listed not supported in the userguide. Would that mean it would not support the offline migrations as well ?
any feedback is much appreciated.
Apologies for delay , was on vacation .
Just downloaded the new version and retried , no noticeable change . Still no access to any redirected drives.
Still suspicious of server side configuration possible inhibiting .
Were about to upgrade the server side to Horizon 7 so will see if that has any affect.
I had same issue with VMware Horizon View Agent 7.x and I wasted entire day looking for some solution.
Finally my findings are "sometimes we look at the bigger things and forget the smaller things and mess up everything".
Let me ask you, have you tried to disable the Anti-Virus protection from your machine?
AntiVirus tries to stop everything and everybody to make sure the system is protected and sometimes its pain.
I had McAfee and I had to go to VirusScan Console and had to Disable below things:
Access Protection
On-Delivery Email Scanner (which I don't think is required, for 1-2 minutes there is no harm in disabling this)
On-Access Scanner
And the problem got resolved.
Now in version 6 i have observed SRM is integrated with PSC not vCenter. My question is If multiple vCenter Servers are connected with the PSC, then will SRM be integrated wth both the vCenters?
Hi
After deleteing the core.vpxd-worker files they keep getting generated causing vCentre issues. Does anyone know a known cause of large core.vpxd-worker file being generated?
have you installed VMware tools in that VM? from VM console --> Click on View from top menu bar --> select either Fit Guest Now / Fit Window / Auto Fit Window.
In one of the KB, It is clearly mentioned about VM disk resizing challenge with vsphere replication but i am unable to find any KB where same challenge is mentioned with ABR. Is it same with ABR replicated VM? Is it supported by VMware to modify the disk size of ABR replicated VM.