similar to: ESXi, CentOS 7 guest, CPU disabled

On Mon, November 24, 2014 15:49, Jack Bailey wrote: > Hello, > > Over the last several weeks I've had a couple of CentOS 7 guests running > in ESXi freeze because the CentOS halted the CPU. The problem is > described here: > > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000542 > > My CentOS 6 VMs are not

> 2016-08-18 12:39 GMT-04:00 correomm <correomm at gmail.com>: > >> This bug is reported only on the VM's with CentOS 7 running on on VMware >> ESXi 5.1. >> The vSphere performance graph shows high CPU consume and disk activity only >> on VM's with CentOS 7. Sometimes I can not connect remotely with ssh >> (timeout error). >> > I'm

Hi BTRFS community I have a problem using btrfs/nfs to store my vmware images. - following setup :(debian wheezy + backports) Linux sncubetest02 3.14-0.bpo.1-amd64 #1 SMP Debian 3.14.12-1~bpo70+1 (2014-07-13) x86_64 GNU/Linux > btrfs --version Btrfs v3.14.1 > btrfs fi show Label: none uuid: 8e37c8d0-e0ef-4857-ae9f-9a1be21901ed Total devices 2 FS bytes used 210.27GiB

All,This happens on all of our CentOS 7 VMs.? but as stated in the email trail, the file softlockup_thresh does not exist.? Should it be added?? What is the best way to get rid of this behavior. Thanks in advance and sorry if I missed something along the way.KM From: correomm <correomm at gmail.com> To: CentOS mailing list <centos at centos.org> Sent: Thursday, August 18,

2016-08-18 12:39 GMT-04:00 correomm <correomm at gmail.com>: > This bug is reported only on the VM's with CentOS 7 running on on VMware > ESXi 5.1. > The vSphere performance graph shows high CPU consume and disk activity only > on VM's with CentOS 7. Sometimes I can not connect remotely with ssh > (timeout error). > I'm also seeing those errors in several

Not sure if this was the last email on this.? If not ignore me. However I found a post for new operating systems that says to set the watchdog_thresh value instead of softlockup_thresh.? http://askubuntu.com/questions/592412/why-is-there-no-proc-sys-kernel-softlockup-thresh this is an Ubuntu post, but on my CentOS 7 system this parameter exists, and softlockup_thresh does not.??I have set it but

Never saw this email....Did anyone get it?? anyone know how to fix this?thanks again. From: KM <info4km at yahoo.com> To: CentOS mailing list <centos at centos.org> Sent: Monday, August 7, 2017 11:26 AM Subject: Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0] All,This happens on all of our CentOS 7 VMs.? but as stated in the email trail, the file

Hi there, Is there a way to prevent Windows HVM guests from seeing passed through devices like graphics cards as being ejectable? i.e. you pass through a graphics adapter to an HVM guest which happens to be Windows. Windows sees this as a device with hotplug capability. Therefore it shows up in "safely remove hardware" option in the windows system tray. VMWare provides an option to

Hi all, while fiddling with VmWare View without being able to join windows7 client to samba4 domain, we stumbled on the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028164 which says, should we run MS Windows 2008R2 AD, we should enable the "Allow cryptography algorithms compatible with Windows NT 4.0"

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

Hi. I used VMware Standalone converter 5.5 to convert a CentOS 5.3 machine from a Physical server to a Virtaul Machine on ESXi 5.1 . Thus far with every attempt to convert this machine I get a "Kernel panic" mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc failed: No such file or directory

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections

Hello, I know, often asked, often discussed .. No recommendation from Citrix. What is the better solution? 1) use ntp in the XEN host and synchronize the guests with the clock running on the control domain (independent_wallclock=0, what the default is) 2) or use ntp in host and guest (and independent_wallclock=1) I ask, because the XEN host (bare metal) has a more stable clock and if the ntp

Hello All, First of all I want say thanks for all the info I see every time in this list. Second, sorry for my basic english. I writting this because I'm experiencing an issue with a Centos over a VPS. Every saturday (I have installed this vps since 3 weeks ago) I check the status of the server I found that the file system is in read-only mode #touch test touch: cannot touch `test':

This bug is reported only on the VM's with CentOS 7 running on on VMware ESXi 5.1. The vSphere performance graph shows high CPU consume and disk activity only on VM's with CentOS 7. Sometimes I can not connect remotely with ssh (timeout error). The details of last issues was reported to retrace.fedoraproject.org. ?Do you have a hint? [root at vmguest ~]# abrt-cli list id

On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM:

I run VMware vSphere 4 Essentials with three almost identically configured ESXi 4.1 hosts and a mix of 32 and 64 bit guests including Windows 2003 and 2008 as well as CentOS 5 and 6. Recently I updated one of the hosts to build 800380. The new build runs Windows and CentOS 5 VMs fine, but CentOS 6 guests won't come up. I tried two different CentOS 6 VMs. Both have the latest standard kernel

I am experiencing a strange problem that I hope someone out there has experience withf. We have a large fileserver running samba 3.6 backed by a 12T ext4 filesystem. We keep lots of VMware VMs on the filestore and I am trying to make some improvements to how we manage/launch/use the VMs. To that end, I've been trying to launch the VMs via the VMware VIX API by UNC path (not mapped drive).

(sorry about the top-posting) I did a killall on blazer_usb and nutdrv_qx, then did a lsusb, got the following: $ lsusb -d 0665: Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Then I started the driver in DDD mode, log attached, beyond the point where communication fails (591.465153). Lastly, I did the lsusb again and got this: $ lsusb -d 0665: Bus 002 Device 005: ID

On Jan 2, 2015, at 3:33 PM, Mike Raath <raathm at gmail.com> wrote: > Sorry, I messed up my reply a bit. > > The output of the lsusb command is the same before and after the data goes stale. > > $ lsusb -d 0665: > Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial > OK. That usually means that the VM kernel doesn't see that the device is