Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Best practice for Linux proxy VM configuration in HotAdd transport (67757)

Last Updated: 3/2/2023Categories: Best PracticesTotal Views: 7840Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When there are multiple SCSI controllers in the Linux Proxy VM,

The disk open may fail due to exception

2018-03-28_09:07:34.633 INFO VDDK - 2018-03-28T05:07:34.633-04:00 error -[03497] [Originator@6876 sub=transport] Cannot use mode hotadd to access [sharedVmfs-0] RHELXfsTargetClone_src/RHELXfsTargetClone_src-000001.vmdk: Cannot mount using this method. (Mounting 4217d91d-6112-4412-2a1a-54caec2cf7aa using transport hotadd failed : HotAdd ManagerLoop caught an exception.)
2018-03-28_09:07:34.633 INFO VDDK - 2018-03-28T05:07:34.633-04:00 info -[03497] [Originator@6876 sub=ThreadPool] Thread delisted
2018-03-28_09:07:34.633 INFO VDDK - VixDiskLib: Unable to locate appropriate transport mode to open disk. Error 13 (You do not have access rights to this file) (Mounting 4217d91d-6112-4412-2a1a-54caec2cf7aa using transport hotadd failed : HotAdd ManagerLoop caught an exception.) at 5283.
2018-03-28_09:07:34.633 INFO VDDK - VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [sharedVmfs-0] RHELXfsTargetClone_src/RHELXfsTargetClone_src-000001.vmdk. Error 13 (You do not have access rights to this file) (Mounting 4217d91d-6112-4412-2a1a-54caec2cf7aa using transport hotadd failed : HotAdd ManagerLoop caught an exception.) at 5423.

The disk open may fail due to incorrect disk device open.

The target disk close may lead to other disk removal.

Cause

When there are multiple SCSI controllers in the Linux Proxy VM, the hotadd transport may not be able to recognize the disk correctly.

The cause of these errors is that SCSI controller ordering in the proxy VM must correspond one-to-one with SCSI controller ordering in the backed-up guest VM.

For example, SCSI initiator 0 in the guest VM corresponds to SCSI controller 0 in the proxy VM, SCSI initiator 3 in the guest VM corresponds to SCSI controller 1 in the proxy VM, SCSI initiator 4 in the guest VM corresponds to SCSI controller 2 in the proxy VM, and SCSI initiator 5 in the guest VM corresponds to SCSI controller 3 in the proxy VM.

[0:0:0:0]    disk    VMware   Virtual disk     2.0   /dev/sda
[1:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR00 1.00  /dev/sr0
[2:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR10 1.00  /dev/sr1
[3:0:0:0]    disk    VMware   Virtual disk     2.0   /dev/sdb
[4:0:0:0]    disk    VMware   Virtual disk     2.0   /dev/sdc
[5:0:0:0]    disk    VMware   Virtual disk     2.0   /dev/sdd

The first column I:C:T:L indicates initiator, controller, target, and LUN.
The root partition is assigned SCSI disk A, /dev/sda.
When SCSI devices are added, they will be /dev/sdb, /dev/sdc, etc

Resolution

This issue is fixed for Linux proxy since VDDK 7.0.3.2 and later.

Workaround

HotAdd backup has a strict requirement for SCSI controller correspondence: SCSI controller ordering in the proxy VM must match ordering in the backed-up VM. Previously this requirement was documented as requiring numeric order, but the actual requirement is for one-to-one correspondence.

To work around this problem when it occurs, follow these steps after every reboot of the proxy VM:

1, Power off the proxy VM
2, Move all the disks to SCSI controller #0 (so you can remove other controllers in the next step)
3, Remove SCSI controller #1, SCSI controller #2, SCSI controller #3
4, Power on the proxy VM and make sure the proxy VM can boot successfully
5, Add back SCSI controller #1
6, Add back SCSI controller #2
7, Add back SCSI controller #3
8, Confirm that SCSI controller ordering can match the SCSI order in the proxy VM.

It’s highly recommended to use SCSI controller of type (Paravirtualized SCSI) in proxy VM.

May refer to latest VDDK Programming Guide for more info.

Related Information

PDF document for version 6.7 is available here .

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Virtual Disk Development Kit

Related Versions:

Virtual Disk Development Kit 6.7

Virtual Disk Development Kit 6.5

Virtual Disk Development Kit 6.0

Virtual Disk Development Kit 5.5

Virtual Disk Development Kit 5.1

Virtual Disk Development Kit 5.0

Virtual Disk Development Kit 1.2.2

Virtual Disk Development Kit 1.2.1

Virtual Disk Development Kit 1.2

Virtual Disk Development Kit 1.1.1

Virtual Disk Development Kit 1.1.0

Virtual Disk Development Kit 1.0.1

view all

Take Our Survey

Support Assistant