Facing this problem 2 years go when bringing a customer from 4.x to 6.5. IIRC i "pull" the VMs rather than pushing them and i specify an old key algorythm/ cipher on command line for scp. Not sure about 6.5.
Regards,
Joerg
Facing this problem 2 years go when bringing a customer from 4.x to 6.5. IIRC i "pull" the VMs rather than pushing them and i specify an old key algorythm/ cipher on command line for scp. Not sure about 6.5.
Regards,
Joerg
I know I started with GB but then jumped on to TB, sorry for that but think the point I want to make is still clear, i.e. the vSAN storage migration should work as long as the LUN has available space that satisfies the data size that the Guest VM operating system sees.
Point1: vSAN Default Storage Policy (FTT=1)
Point2: Default Datastore policy
Point3: Not sure, will need to check further. (Yes think error is a pre-check failure) Are you meaning that if the 1.5TB LUN currently has a VM with 600GB disk (thin provisioned) it would not allow me to make to storage migration? (Since it has to make sure that the current VM can grow up to 600GB) thus 1.5 - .6 = .9 left
Point4: No am using the web client (Not the HTML5 one as not supported on the version am running of 6.0)
Point5: Not sure but doubt they are aligned as can see the decimal points
I will try to research further and get more information.
Thanks
my means is for example can i migrate 20vms+40vdisk in same time there is not any limitation ?
BR
Please show the driver and driver version in use as well as the firmware for this/these SSDs.
I downloaded gparted booted in vmware client . Asked it to refresh the HDDs. Yet the VMware HDD is not detected. I am really stuck up.
There is a limitation on how many concurrent vMotion and SvMotion can be performed per host. But, there is no limitation on the no. of vDisks with respect to migration -
https://www.vmware.com/pdf/vsphere6/r65/vsphere-65-configuration-maximums.pdf - Search for "Concurrent Operations"
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
Cheers,
Supreet
Thank you also that was the problem Many thanks
Hello,
I don't know why it doesn't show me the device firmware
Here is the output:
[root@ns3094269:~] esxcli nvme device get -A vmhba1
Adapter not found.
[root@ns3094269:~] esxcli nvme device get -A vmhba1:C0:T1:L0
Adapter not found.
And here are some other details:
"Runtime Name","Target","LUN","Status"
"vmhba1:C0:T1:L0","","0","Active (I/O)"
"vmhba1:C0:T0:L0","","0","Active (I/O)"
"Model","Adapter","Type","Status","Identifier","Targets","Devices","Paths"
"DC P3500 SFF","","","","","","",""
,"vmhba2","SCSI","Unknown","--","1","1","1"
,"vmhba3","SCSI","Unknown","--","1","1","1"
"iSCSI Software Adapter","","","","","","",""
,"vmhba64","iSCSI","Online","iqn.1998-01.com.vmware:ns3094269-251eeb57","0","0","0"
"Wellsburg AHCI Controller","","","","","","",""
,"vmhba0","Block SCSI","Unknown","--","0","0","0"
,"vmhba1","Block SCSI","Unknown","--","2","2","2"
General
Name vmhba1
Model Wellsburg AHCI Controller
"Name","LUN","Type","Capacity","Datastore","Operational State","Hardware Acceleration","Drive Type","Transport"
"Local ATA Disk (t10.ATA_____HGST_HUS726020ALA610____________________K5H3W36A____________)","0","disk","1.82 TB","datastore4","Attached","Not supported","HDD","Block Adapter"
"Local ATA Disk (t10.ATA_____HGST_HUS726020ALA610____________________K5H3TUVA____________)","0","disk","1.82 TB","datastore3","Attached","Unknown","Flash","Block Adapter"
None of this output shows either device firmware or ESXi driver and version.
oh Sorry,
How can I check it?
Dear all,
I need your help since I struggle with virtual machines after the upgrade.
I have upgraded my ESXi 6.0 to 6.7 using SSH commands (e.g. https://miketabor.com/how-to-upgrade-esxi-6-5-to-esxi-6-7/ ). Immediately after I have signed in to the "new" web based ESXi vSphere I have noticed that:
a) virtual machines (2) have not started and have red exclamation mark
b) there are no datastores
I have tried the data store browser but web app throws JS errors on me. When I run Linux commands these are shown normally.
I have subsequently tried to downgrade ESXi, but this does not seems to be an optiion (both 6.0 and 6.5).
What I suspect is some hard drive controller driver missing (deleted during the update proces), but I do not know which one since there are many of them in the update log. Another thing that could possibly happened is that 6.0 => 6.7 was a big jump and I need to change VMFS to something new, because its no longer supported.
Update log:
Kernel log:
This is DYI home server:
CPU Intel Pentium G620T (2,2GHz, 3MB, LGA1155) BOX
MB MSI H61MA-E35 (B3) - H61, s.1155, DDR3, mATX
+ 3 hard drives
Thanks in advance for any help.
As many of you may know, this Early Access sub-community provides you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want you discover the latest content that is in development and learn about the potential directions in these designs.
I'm please to share the work that William Lam and I had the pleasure to develop recently, VMware Pivotal Container Service for Workload Domains. This early access material covers the architecture and design elements for adding PKS 1.1.x to a VMware Validated Design workload domain for a new container services layer.
The container services layer enables enterprises and service providers to simplify the deployment and operations of Kubernetes-based container services within the VMware SDDC. In the container services layer, access to production-grade Kubernetes distribution with advanced networking, built-in private registry, and full lifecycle management support of the clusters is provided on top of and integrated with the SDDC.
Got feedback?
We want to hear from you. So dive into this latest early access content and share your feedback directly with our solutions architects and product managers!
Here is the detail from one of those virtual machines:
Compatibility
[missing "en-us.vm.hardwareVersion..label" translation]
VMware Tools
[missing "en-us.vm.tools.installed." translation]
As many of you may know, this Early Access sub-community provides you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want you discover the latest content that is in development and learn about the potential directions in these designs.
I'm please to share the work that we recently completed, Design and Deployment of VMware Skyline within the VMware Validated Design for SDDC. This early access material covers the architecture and design elements, plus deployment guidance, for adding Skyline Collector 1.4 to the VMware Validated Design and is applicable to single-region, dual-region, and multi-availability zones.
VMware Skyline is a technology for proactive support. VMware Skyline uses automation to securely collect data and perform environment-specific analytics on configuration, feature, and performance data. The resulting information improves visibility in your environment. As a result, VMware and your organization interact without extensive time and investment by support administrators. As a result, proactive, predictive, and prescriptive recommendations by VMware improve the stability and reliability of the environment. In addition, reactive support issues can be resolved more quickly.
Got feedback?
We want to hear from you. So dive into this latest early access content and share your feedback directly with our solutions architects and product managers!
what does this mean
Concurrent vMotion operations per VMFS volumes 128
vMotion operations per host (10 Gb/s network) 8
vMotion operations per datastore 128
Storage vMotion operations per host 2
Storage vMotion operations per datastore 8
In the vSphere web client
Actions > Compatibility > Upgrade VM Compatibility....
How old is this VM that it has the HW version set so low??
Here is a document talking about the hardware version upgrade: VMware Knowledge Base
Before you upgrade the virtual hardware:
Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.
Upgrading a white-box can always be a hit, or miss.
Anyway, please follow the upgrade steps again until step 4, but replace the command with the one below, and post the output.
esxcli software profile install -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-20180804001-standard --ok-to-remove --dry-run
Note: This command will not modify anything (--dry-run), but will show what's left over from the old installation.
André
What may be an option is https://www.virtuallyghetto.com/2012/06/how-to-copy-vms-directly-between-esxi.html
Hint: In case you want the target VMs being thin provisioned, insert the option --dm=thin behind the ovftool command.
André
hello everybody,
Using latest Esxi. But VMMachines time is not properly correct though I made those correct many times!
Do I have to make it correct from Esxi?
Thanks in Advance
Yes, you need to set the time properly within ESXi or use an NTP server as the source of clock sync.