I'm running the VMware ESXi 5.5 hypervisor and see a lot of error messages like below in its /var/log/vmkernel.log file:
<timestamp> cpu11:34032 opID=1ad4dfbe)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
The SCSI operation with code 0x9e is SERVICE ACTION IN (16), which is 16-byte command. So, why does the server complains about the max=12 limitation? What might be a reason to get these messages? What should I change to get rid of them?
Related
Since past two days, rsyslogd is using 100% CPU Utilization on all RHEL EC2 Instances in my environment. I Stopped and started rsyslog service but still issue persists.
This is first time we are facing this kind of behaviour in multiple servers.
There is sufficient disk space/memory exists in all servers.
I checked kernel logs (/var/log/kernel) and server messages( /var/log/messages),but not find any useful info.
Following is the OS and Kernal versions of all servers.
Operating System: Red Hat Enterprise Linux Server 7.2 (Maipo)
Kernel: Linux 3.10.0-1160.42.2.el7.x86_64
Can someone please suggest on this.
Issue is due to cert expiry for rsyslog. Observed a lot of connection retry errors in system messages for all clients. Post renewing certs in rsyslog, cpu went down.
I am installing a Linux guest on my computer. It supports VT-x, I've enabled it in the BIOS, I've turned off Hyper-V, but I haven't turned off Windows Hypervisor Platform. And, when I checked the enable VT-x for the guest, it always show an error: VT-x is not supported on this platform, continue without VT-x? Whether I clicked Yes or No, it always lead to an error. If I click Yes, it will pop up a dialog, said: VMware Workstation does not support nested virtualization on this host.
Module 'HV' power on failed.
Failed to start the virtual machine. If I click No, it will said: Failed to turn on this VM. The only thing I can do is turn off the: Virtualize VT-x for this guest, but I need VT-x turn on for this guest. Can anyone help me? Thanks! [My error][My error]
P/S: I'm a newbie to the VMWare. I don't know so much of this.
I had the same problem on my Windows 10 System with VMWare 16. It was caused by the "Container" windows feature. After switching this feature off, it worked correctly. You can verify your settings with the ones I use. Hope that it helps you to fix the problem.
When attempting to forcely uninstall a software from the server, I switched off these two components from MSCONFIG.EXE:
MSConfig Screenshot
After rebooting the server, it doesn't respond anymore to RDP connections.
The Google Cloud Panel shows that the server is running, has an internal and external IP Address, but I cannot access it by any means. I already rebooted, stopped and started it many times.
This is the output for SERIAL PORT #1:
SeaBIOS (version 1.8.2-20181112_143635-google)
Total RAM Size = 0x00000000f0000000 = 3840 MiB
CPUs found: 1 Max CPUs supported: 1
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=104857600 = 51200 MiB
drive 0x000f2a30: PCHS=0/0/0 translation=lba LCHS=1024/255/63 s=104857600
Booting from Hard Disk 0...
I am able to connect to SERIAL PORT #2, to try a deeper troubleshooting, but the first message after connection is this:
Computer is booting, SAC started and initialized
And when trying to open CMD command, this is the response:
SAC>cmd
Error: Unable to launch a Command Prompt. The service responsible for launching
Command Prompt channels has not yet registered. This may be because the
service is not yet started, is disabled by the administrator, is
malfunctioning or is unresponsive.
Does anyone know how to recover this server?
Thanks!
You unselected "Load system services". This means that nothing is loaded in Windows. The services that are required so that you can access the system remotely are not running.
You have two options:
Mount the disk on another Windows system, mount the registry and change the settings for these two items (I don't rember but this information is on the Internet). Then unmount the registry and create another VM with the disk.
Create a new instance and attach this disk as the second disk drive. Copy all the data from the second drive to the first drive. You will loose system settings, applications, etc but at least you can save your data.
I am trying to create a new VM on ESXI 6.0 using a Windows Server 2012 R2 .iso file.
After selecting all VM options and when finalizing the creation, the process fails with the following extremely informative message:
Failed - Invalid configuration for device '5'.
Any help would be highly appreciated.
My only concern is that ESXI by default does not offer the very specific option of selecting Windows 2012 R2 Server as OS (check attached image) - so I dont' know if this is causing the failure.
(I am selecting just Windows Server 2012, without the R2 since it doesn't exist)
Device 5 stands for IDE controller.
I managed to solve the similar issue by creating the VM without attached HDD and SCSI controller (WinServ 2016 in my case). Then you can try to attach a HDD and Controller lately.
I'm having a really strange problem. I have 2 virtual machines running ubuntu 11.4 in VMware player. These virtual machines have a bridged connection to my network. Since they use DHCP it would be more easy to let them talk to each other using hostnames instead of IP addresses.
That is where the it becomes a strange situation.
ping 192.168.0.10 //this is machine 1
ping 192.168.0.11 //this is machine 2
both work like a charm
ping machine1.local
ping machine2.local
work great on their own system. but ping machine1.local on machine 2 results in a "ping: unknown host machine1.local"
After trying and checking everything and getting nothing but the local machine in the avahi-browse, I installed wireshark to get to know what's really going on.
I ran wireshark, and then ran avahi-browse. In wireshark I saw all the responses to the MDNS message AND I GOT machine1.local AND machine2.local!!!
GREAT! but when I turned off wireshark the avahi-browse cache went empty again...
Why is it that when I have wireshark on in the virtual machine, the avahi-daemon gets the MDNS messages, and when I turn it off, the messages get lost again...
You may need to switch to the e1000 network adapter to (fully) support multicast. To switch to the e1000, open your vmx file in an editor and find the entry for the virtual ethernet adapters. Change or add this line:
ethernet0.virtualDev = "e1000"
(If you have more than one adapter, change it for each of ethernet0, ethernet1, etc.)
This thread details some of the multicast issues that seem similar to yours:
http://communities.vmware.com/message/1549658
This document describes the various possible virtual adapters and their limitations and capabilities:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1001805