PXE don’t start

I need a solution

Hi all,

I have all tutorials and all videos read and watch but I don’t have a solution for my problem. I have no idea what to do in my case.

I have GSS Suite on a Server 2012R2 in a VM ESXI and on the same VM machina a windows 7 prof. Client. If I want to boot PXE

I become the following screen and after this my Win7 boot normaly but don’t boot PXE. Is there anyone who have the same problem?

Thanks for your help



  • No Related Posts

[API detection for Developer appliance] Unable to import license.

I need a solution


API appliance ovf: dlp_Scorpio-VA-1 (ARCHITECTURE: x86_64)

Enforce Server : 15.5 (Licensed)

ESXI : 6.5

[Issue Description]

– Noticed that currently license site has been renewed. Due to this reason, lost a way to apply license via “URL” and passphrase according to DLP API guide.

– Received bcl file instead.

– Tried to import the file into the API appliance but failed. 

– Custom linux of the API appliance does not seem to allow importing the bcl file as CLI is very limited, and I am not that familiar with CLI “licensing inline.”

– Tired to copy the file by using ssl & scp, connecting putty & WINscp which seems to be blocked by custom linux of API appliance.

I need assistance for importing license on the appliance properly. Any advice will be much appreciated.





  • No Related Posts

Reporter | Please help to confirm information

I need a solution

Dear  All,

  I have got question from customer as  below. please help to recommend.

1. Does a reporter support ESXi hypervisor (free edition) ?

2. In case a customer using ProxySG-VA, is it possible to install on shared storage ? [SAN, NAS]
3. For management center, does it has a feature likes admin over-write protect ?
4. Can we set delegate user for reporter via management center ?
5. For management center, is it possible to set delegate user per ASG/Proxy-SG device ?

Best Regards,




  • No Related Posts

VxRail: PTAgent upgrade failure, ESXi error “Can not delete non-empty group: dellptagent”[3]

Article Number: 516314 Article Version: 6 Article Type: Break Fix

VxRail 460 and 470 Nodes,VxRail E Series Nodes,VxRail P Series Nodes,VxRail S Series Nodes,VxRail V Series Nodes,VxRail Software 4.0,VxRail Software 4.5

VxRail upgrade process fails when upgrading PTAgent from older version 1.4 (and below) to newer 1.6 (and above).

Error message


Error in running [‘/etc/init.d/DellPTAgent’, ‘start’, ‘upgrade’]:

Return code: 1

Output: ERROR: ld.so: object ‘/lib/libMallocArenaFix.so’ from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object ‘/lib/libMallocArenaFix.so’ from LD_PRELOAD cannot be preloaded: ignored.

ERROR: ld.so: object ‘/lib/libMallocArenaFix.so’ from LD_PRELOAD cannot be preloaded: ignored.


Can not delete non-empty group: dellptagent

It is not safe to continue. Please reboot the host immediately to discard the unfinished update.

Please refer to the log file for more details.

Dell ptAgent upgrade failed on target: <hostname> failed due to Bad script return code:1

PTAgent can’t be removed without ESXi asking for a reboot, due to earlier version of PTAgent (lower than 1.6) had problem dealing with process signals, ESXi is unable to stop it no matter what signal is sent or what method is attempted to kill the process. Rebooting ESXi si required to kill the defunct process so the upgrade can proceed.

PTAgent 1.6 (and above) had this issue fixed, but upgrading from 1.4 to 1.6 can’t be done without human intervene once the issue is encountered.

Impacted VxRail versions (Dell platform only):

  • 4.0.x: VxRail 4.0.310 and below
  • 4.5.x: VxRail 4.5.101 and below

This issue is fixed in recent VxRail releases, but upgrade from earlier VxRail releases are greatly impacted. It’s strongly suggested customer to contact Dell EMC Technical Support to upgrade to PTAgent 1.7-4 which is included in below VxRail releases:

  • VxRail 4.0.500 for customer who stays on vSphere 6.0
  • VxRail 4.5.211 or above for customers who choose vSphere 6.5

Manual workaround if experiencing the PTAgent upgrade failure

  • Enter maintenance mode and reboot the host mentioned in error message
  • Wait until the host is available and showing proper state in vCenter, click retry button in VxRail Manager to retry upgrade.


  • No Related Posts

App Layering : Unable to create an image

Check to see if you have hosts in maintenance mode or otherwise in trouble.


Add the following permissions to the service account either at the DataCenter level or the vSphere level.

Basically, the service account doesn’t have enough vSphere account permissions, or user doesn’t have them set at the right level.

Virtual Machine / Interaction / Device Connection

Virtual Machine / Interaction / VMware Tools install

Virtual Machine / Provisioning / Clone template

Virtual Machine / Provisioning / Clone virtual machine

For required permissions refer :



  • No Related Posts

Virtualize SMP Server

I need a solution

I’m considering virtualizing my SMP server that has 2 CPUs with 12 cores each to a VMware infrastructure.  VCenter Converter will set the cores to 24 like the physical box but for those who’ve gone through this P2V, did you decrease, say, the cores per processor so as not to utilize too much of the resources on the ESXi host?  I know memory tends to have more of an impact on an ESX host where my physical box has 24 gigs which the host can handle.

Anyhow, I’m more concerned about CPU usage on the host should I leave the cores as-is or the performance impact it’ll have on the VM by reducing the total number of cores.  I don’t believe we have a VM with 24 cores in our VMware environment so not sure if leaving it at “24” is reasonable.  Also, thought the more cores you specify in a VM could have a negative impact as the ESX host needs to wait to grab ALL of the CPU resources from the host when needed.  Just not sure what to set the number of CPUs and cores to in Converter which makes sense.



  • No Related Posts

Operating System Fixup in XenCenter 5.6 or later OVF Appliance Plug-in

This article describes the Open Virtualization Format (OVF) Appliance Plug-in feature of XenCenter 5.6 and later. The OVF includes advanced hypervisor interoperability option Run Operating System Fixups.


The OVF standard is composed of metadata and file elements that describe Virtual Machines (VMs), and additional information that is important to the deployment and operation of the applications in the OVF package.

Using OVF as a method of packaging does not guarantee cross hypervisor compatibility of the virtual machines. An OVF package created on one hypervisor might not automatically work on a different hypervisor. This happens for a variety of reasons including; different interpretations of the OVF specification, guest operating system devices, drivers, and implementations inherent to a hypervisor.

The Operating System Fixup feature in XenCenter 5.6 creates a basic level of interoperability for OVF packages that are imported to XenServer 5.6. The Fixup process addresses the operating system device and driver issue inherent when moving from one hypervisor to another. This is not designed to perform conversions from one platform to another.

Operating System Fixup Option

The Operating System Fixup is included with the XenCenter 5.6 installer as an automatically booting ISO image.

It can be enabled from the Advanced Options screen of the Appliance Import and Disk Image Import wizards in XenCenter.

The Operating System Fixup attempts to repair boot device related problems with the imported virtual system that might prevent the operating system within the virtual machine from booting.

It is important to understand how an appliance or disk image was created when deciding to use if the operating system fixup, or when diagnosing problems with booting a VM after import has completed.

Requirements for Operating System Fixup

An ISO Storage Repository (SR) for the OVF Appliance wizard to copy the Fixup ISO from the XenCenter administrative client machine to a location where XenServer can use it.

The ISO Storage Repository can be CIFS or NFS share with read/write permissions.

What does Operating System Fixup do to the Virtual Machine?

The Operating System Fixup option is designed to make the minimal changes possible to enable a virtual system to boot. Depending on the guest operating system and original hypervisor host, additional configuration changes, driver installation, or other actions might be required following using the fixup option.

During the Fixup process, an ISO is copied to an ISO SR. This ISO is attached to a virtual machine; the boot order is set to boot from the virtual DVD drive, and that virtual machine boots into the ISO. The environment within the ISO then checks each disk of the virtual machine to determine if it is a Linux or a Windows system.

If a Linux system is detected, then the location of the GRUB configuration file is determined and any pointers to SCSI disk boot devices are modified to point to IDE disks. For example, if GRUB contains an entry of /dev/sda1 representing the first disk on the first SCSI controller, this entry is changed to /dev/hda1 representing the first disk on the first IDE controller.

If a Windows system is detected, a generic critical boot device driver is extracted from the driver database of the installed operating system and registered with the operating system. This is especially important for older Windows operating systems when the boot device is changed between a SCSI and IDE interface. Also, if certain virtualization tool sets are discovered in the virtual machine, they are disabled to prevent performance problems and unnecessary event messages.

What Hypervisors has the OVF Appliance Wizard Imported Content From?

The hypervisors that the OVF Appliance Wizard has imported VMs from and applied the Operating System Fixup option to:

Tested Hypervisor VMs and Utilities



VMware Workstation


Delete VMware Tools from the VM to import if possible.

VMware ESX

3.5, 4.0

Delete VMware Tools from the VM to import if possible.

VMware OVF Tool


Delete VMware Tools from the VM to import if possible.

VMware Studio


Delete VMware Tools from the VM to import if possible.

Sun Virtual Box


Delete Virtual Box Tools from the VM to import if possible.

MS Virtual Server

2005 SP1

Delete MS Tools from the VM to import if possible.

MS Hyper-V

2008, 2008 R2

Operating Systems that has the Operating System Fixup been Tested With

The Operating System Fixup option has been tested with the following operating systems:

Windows Linux

Windows 2000 Advanced Server

Windows XP SP3

Windows 2003 R2 SP2

Windows Vista SP2

Windows 2008 SP2

Windows 2008 R2

Windows 7

Debian 4, 5

SuSE Linux Enterprise Server 10 SP2, 11

RedHat 4, 5

CentOS 4, 5

*WIM disk image imports have only been tested with Windows operating systems.

Does the Operating System Fixup Repair all Problems?

There are differences among operating systems that cannot be repaired by the Fixup. It is also important to note that this is not a conversion process.

One example is: CentOS 5.3. The primary distribution media for CentOS 5.3 contains kernel revision 18. This kernel contains a bug that prevents it from migrating between SCSI and IDE boot devices; the bug is not fixed until kernel revision 28. The appliance cannot be repaired by the fixup because a new kernel could break numerous applications within the virtual machine because of kernel dependencies.

Operating System Fixup Expected Behavior with Different Operating Systems

The following tables identify the expected behavior when choosing to use or not to use the Operating System Fixup option. Success indicates that the VM booted and could be logged in to.

Tested VM Imports with Fixups Version Comments
CentOS 4, 32 bit 4
CentOS 5, 32 bit 5 Known kernel incompatibility 1
CentOS 5, 64 bit 5 Known kernel incompatibility 1
Debian 3 and 4, 32 bit 4.0 (Etch) Hangs at USB device detection, requires user hitting <Enter> 2
Debian 5, 32 bit 5.0 (Lenny)
Red Hat Enterprise Linux, 32 bit 4.8 Fixups do not repair 3
Red Hat Enterprise Linux, 32 bit 5.3 Fixups are optional 4
Red Hat Enterprise Linux, 64 bit 5.3 Fixups are optional 4
SuSE Linux Enterprise Server, 32 bit 10 SP2
SuSE Linux Enterprise Server, 32 bit 11
SuSE Linux Enterprise Server, 64 bit 11
Oracle Enterprise Linux , 32 bit 5
Oracle Enterprise Linux 64 bit 5
Windows 2000 Advanced Server SP4
Windows XP Professional SP3
Windows Server 2003 Enterprise Edition SP2
Windows Server 2003 x64 Enterprise Edition SP2
Windows Vista Enterprise Edition SP2 Fixups are not necessary 5
Windows Vista x64 Enterprise Edition SP2 Fixups are not necessary 5
Windows Server 2008 Enterprise Edition SP2 Fixups are not necessary 5
Windows Server 2008 x64 Enterprise Edition SP2 Fixups are not necessary 5
Windows Server 2008 R2 (64 bit only) Enterprise Edition Fixups are not necessary 5
Windows 7 32 bit Ultimate Fixups are not necessary 5
Windows 7 64 bit Ultimate Fixups are not necessary 5


  • After importing a 64-bit CentOS 5.2 appliance to XenServer the appliance fails to boot with a repeating error that contains: “unable to read inode block”. There is a known problem with the CentOS kernel 2.6.18 that CentOS 5.x is based on causing this problem. Builds including and beyond 2.6.22 do not exhibit this problem. To upgrade the kernel, the appliance must be booted on the same type of hypervisor it was built on and the kernel must be updated to at least 2.6.22. Instructions can be found here.

  • A Debian based virtual machine guest imported from VMware will hang during the boot sequence loading the HID USB device. XenServer represents the keyboard and mouse as USB tablet devices. To resolve, install the XenServer Tools.

  • This contains a kernel that does not migrate to XenServer, nor handle hardware change. The recommendation is to not attempt import of this distribution but to build it on the hypervisor.

  • If the Red Hat distribution includes the Anaconda module; hardware change should be detected and device driver issues should be handled by the operating system.

  • Windows systems versions after Vista do not require fixups. Hardware detection within the operating system addresses device driver issues.

Tested WIM Imports Disk Controller Selecting Fixups Not selecting Fixups
Windows 7 Enterprise, x86 and x64 SCSI Success Success
Windows 7 Enterprise, x86 and x64 IDE Success Success
Windows Server 2008 R2 SCSI Success Success
Windows Server 2008 R2 IDE Success Success
Windows Vista SP2, x86 SCSI Success Success
Windows Vista SP2, x86 IDE Success Success
Windows Server 2008 SP2, x86 and x64 SCSI Success Success
Windows Server 2008 SP2, x86 and x64 IDE Success Success
Windows XP SP3, x86 SCSI Success “Stop 0x0000007B” error
Windows 2003 R2, x86 SCSI Success “Stop 0x0000007B” error
Windows 2008 R2, x64

*See the workaround noted in the following section.
SCSI “Stop 0x0000007B” error “Stop 0x0000007B” error
Windows Server 2008 R2, x86 and x64 – Physical System SATA “Stop 0x0000007B” error Success
Windows XP SP2, x86 and x64 – Physical System SATA “Stop 0x0000007B” error Success

Known Issues with Operating System Fixup

Windows Server 2003 R2 64-bit might not boot following import. A WIM import of the 64-bit version of Server 2003 might result in a STOP 7B error when the VM is booted.

The following workaround is required to repair a virtual machine that meets this scenario:

  1. After importing the virtual appliance attach a WinPE x64 boot disk ISO to the VM (or use the Server 2003 installation media and drop to a command prompt).

  2. Boot the VM.

  3. At the WinPE console type the following command: chkdsk c: /f

  4. When chkdsk is finished shut down the VM.

  5. Eject the WinPE ISO.

  6. Attach the xenserver-linuxfixup-disk.iso to the VM.

  7. Start the VM.

The VM shuts down when the fixup process is complete and the ISO can be ejected.

CTX121908 – How to Enable Physical Volumes on HVM Linux Virtual Machines from VMware (SLES Debian)

CTX121737 – How to Use Kenso Open Virtualization Format Technology to Import VMware Appliances

CTX121616 – Error: Failed to start the X server (your graphical interface)

CTX121624 – How to Import Citrix Merchandising Server using XenConvert

CTX121621 – Repairing Debian after importing to XenServer from VMware

CTX121620 – Repairing X Windows on RedHat after importing to XenServer from VMware

CTX121619 – Repairing X Windows on CentOS after importing to XenServer from VMware

CTX124924 – How to Build a Reference Virtual Machine for Deployment from WIM

CTX124925 – Appliance Imported Virtual Machine Fails to Boot with STOP 7B or ‘Device Does Not Exist

Migrating VMs Between Hypervisors – the hypervisor


  • No Related Posts