similar to: SCSI driver for VMware's virtual HBA - V6.

Forgot to copy the virtualization list.. On Wed, 2009-09-30 at 11:53 -0700, Alok Kataria wrote: > Hi James, > > Given that their are no more modification requests, I think this driver > should be ready for prime time now. I have incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me

Forgot to copy the virtualization list.. On Wed, 2009-09-30 at 11:53 -0700, Alok Kataria wrote: > Hi James, > > Given that their are no more modification requests, I think this driver > should be ready for prime time now. I have incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me

>> > vmware esxi 5.5.0 (free, using vsphere client to manage), vm is minimal > centos 7 64bit. I added a 16gb vdisk and immediately see this in dmesg... > > [155484.386792] vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5) > [155484.386796] vmw_pvscsi: msg: device added at scsi0:1:0 > [155484.388250] scsi 0:0:1:0: Direct-Access VMware Virtual disk > 1.0 PQ: 0 ANSI:

On 11/4/2015 11:36 AM, Boris Epstein wrote: > Absolutely, I see your point. This was the starting point - you add the > device on the ESXi server, you reboot the VM, the VM sees the device, no > problem. Now, I ask - do I have to reboot the VM? Logically I hope there > ought to be a way for me not to have to do that - but I have yet to figure > out how to get there. > vmware

Update the maintainers file to include maintainers for the VMware vmci driver, af_vsock, and the vsock vmci transport. Signed-off-by: Jorgen Hansen <jhansen at vmware.com> --- MAINTAINERS | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index e17ebf7..b9714fc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -16630,6 +16630,14 @@ S: Maintained

Howdy, I've got a CentOS 7 VM that occasionally becomes unresponsive. There's a "list_add corruption" entry in /var/log/messages, included below. This is on VMware. We have lots of other VMs which are running just fine. Only a few are CentOS 7 VMs, though, so I can't rule out some kind of environment issue. It's up-to-date on OS patches, and running kernel

__CHECK_ENDIAN__ isn't on by default presumably because it triggers too many sparse warnings for correct code. But virtio is now clean of these warnings, and we want to keep it this way - enable this for sparse builds. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- It seems that there should be a better way to do it, but this works too. drivers/block/Makefile | 1

Boris Epstein wrote: >> >> My turn for a dumb question: from not paying a lot of attention to this >> thread, the answer isn't clear to me: has the *host* recognized the >> disk? If not, the guest's not going to see it. > > IMO your question is not dumb at all. Unfortunately, I don't have an > answer to it. > > All I know is, you reboot the VM and

All non-kms driver fields are now located in struct drm_legacy_state. A driver-wide instance is available via struct drm_driver.legacy. The call sites test if the driver is marked with DRIVER_LEGACY before accessing the fields. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/drm_bufs.c | 10 +++++----- drivers/gpu/drm/drm_context.c | 9

Hi, I created an HVM type virtual machine and installed RHEL5U7 guest in it. I have assigned 7 scsi disks to the virtual machine in physical mode (using phy:), however, I see those disks are xvd and not as scsi. Is anyone aware what the problem might be ? Please let me know what kind of information do I need to post in order to narrow down to the problem. Thanks, K

Hi Zachary: I was able to reproduce the greendragon results locally (OSX), and fix the problem by excluding 'debuginfo-tests' from check-clang -- this prevents them from being added twice, once for check-clang and again for check-debuginfo. Below are the minimized patches I used to reproduce and fix the problem -- based on your originals. I've verified these patches work when

> On Dec 6, 2017, at 10:10 AM, Zachary Turner <zturner at google.com> wrote: > > Adrian, Mike, Chris? Any update on this? I've temporarily switched to working on something different, but I plan to be back on this in a couple of weeks. It's been a month since my first revert of this CL, which seems like a reasonable amount of lead-time to deal with issues surrounding

> On Dec 6, 2017, at 10:21 AM, Zachary Turner <zturner at google.com> wrote: > > Can I have some assurance that if it fails again, someone will look into who has access to the builders so I don't have to keep doing speculative commits? Sure. I did this last time and I promise to also do it this time. -- adrian > > On Wed, Dec 6, 2017 at 10:13 AM Adrian Prantl

Hi all, I have updated my Centos 6.5 KVM host to kernel 2.6.32-431.23.3 this morning ... After 2 hours working, the following kernel error appears and all vm guests goes slowly .... device monif4 entered promiscuous mode monif: port 5(monif4) entering forwarding state INFO: task cgroup:83 blocked for more than 120 seconds. Not tainted 2.6.32-431.23.3.el6.x86_64 #1 "echo 0 >

I run latest sparse from git on virtio drivers (turns out the version I had was rather outdated). This patchset fixes a couple of bugs this uncovered, and adds some annotations to make it sparse-clean. In particular, endian-ness is often tricky, so this patchset enabled endian-ness checks for sparse builds. Michael S. Tsirkin (10): virtio_console: drop unused config fields drm/virtio: fix

I run latest sparse from git on virtio drivers (turns out the version I had was rather outdated). This patchset fixes a couple of bugs this uncovered, and adds some annotations to make it sparse-clean. In particular, endian-ness is often tricky, so this patchset enabled endian-ness checks for sparse builds. Michael S. Tsirkin (10): virtio_console: drop unused config fields drm/virtio: fix

I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure

<<insert bug report here>> ------------------------------------------------------ Error: R : Copyright 2002, The R Development Core Team Version 1.5.1 (2002-06-17) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type `license()' or `licence()' for distribution details. R is a collaborative project with

This patchset moves legacy, non-KMS driver state from struct drm_driver into struct drm_legacy_state. Only non-KMS drivers provide an instance of the latter structure. One special case is nouveau, which supports legacy interfaces. It also provides an instance of the legacy state if the legacy interfaces have been enabled (i.e., defines the config option CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT) I

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to