On Wed, Dec 10, 2014 at 11:30:30PM +, KY Srinivasan wrote:
+ {Msft, Virtual Disk, 1.0, BLIST_TRY_VPD_PAGES},
Is that version field meaningful or is it safe for us to inquire about
VPD pages without problems on older versions?
This version is used in all current Hyper-V
On Mon, Dec 08, 2014 at 06:04:35AM +, KY Srinivasan wrote:
Greg has not committed these patches yet. One of the patches changes the
balloon floor.
This means that the guest will not be ballooned down below the floor. Is this
what you are
seeing? In our testing we did not see anything
On Wed, Dec 10, 2014 at 12:38:25AM -0800, Long Li wrote:
MSFT targets currently claim SPC-2 compliance while they implement
post SPC-2 features. With this patch we can correctly handle
WRITE_SAME_16 issues.
This patch fixes an issue where the flag is setup too late in drive
initialization
the status.
This will address the inconsistent lock state that Sitsofe Wheeler
sits...@gmail.com
reported:
Sorry I didn't follow up on this. Things looked better after the patch
but I was seeing a strange issue where the memory was being reduced to
some minimum and the balloon would never shrink so
I've been trying to use the Hyper-V balloon driver to allow the host to
reclaim unused memory but have been hitting issues. With a Hyper-V 2012
R2 guest with 4GBytes of RAM, dynamic memory on, 1GByte minimum 10GByte
maximum, 8 vcpus, running a 3.18.0-rc3 kernel with no swap configured
the
On 23 October 2014 02:50, Martin K. Petersen martin.peter...@oracle.com wrote:
Sitsofe == Sitsofe Wheeler sits...@gmail.com writes:
Sitsofe 2. On top of the above, when a disk is small (has less than
Sitsofe2^32 sectors which is typically 2 TBytes in size) READ
SitsofeCAPACITY(16
On 21 October 2014 18:13, Long Li lon...@microsoft.com wrote:
Thanks Sitsofe. This should have been fixed by this patch:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f88e67149f97d73c704d6fe6f492edde97463025
Can you give it a try?
Ah this one went mainline a few
On Tue, Oct 14, 2014 at 09:06:37PM -0400, Martin K. Petersen wrote:
Sitsofe == Sitsofe Wheeler sits...@gmail.com writes:
Sitsofe A previous patch attempted to add a quirk to workaround this
Sitsofe but the quirk was only enabled after the features had been
Sitsofe scanned for, wouldn't work
On Tue, Oct 14, 2014 at 09:08:28PM -0400, Martin K. Petersen wrote:
Sitsofe == Sitsofe Wheeler sits...@gmail.com writes:
Sitsofe Microsoft Hyper-V virtual disks currently only claim SPC-2
Sitsofe compliance causing the kernel skip checks for features such as
Sitsofe thin provisioning even
On Sun, Oct 12, 2014 at 01:21:01AM +, KY Srinivasan wrote:
-Original Message-
From: Jeff Leung [mailto:jle...@v10networks.ca]
Sent: Saturday, October 11, 2014 1:22 PM
On the current release of Windows (windows 10), we are advertising
SPC3 compliance.
We are ok with
[mailto:driverdev-devel-boun...@linuxdriverproject.org] On Behalf
Of Sitsofe Wheeler
Sent: Thursday, October 09, 2014 6:32 AM
To: David Miller
Cc: o...@aepfle.de; net...@vger.kernel.org; jasow...@redhat.com;
linux-ker...@vger.kernel.org; a...@canonical.com;
de...@linuxdriverproject.org Subject
virtual disks and work on small
virtual disks.
Sitsofe Wheeler (3):
Revert Drivers: add blist flags
scsi: add try_rc16 blacklist flag
scsi: Use try_rc16 and try_vpd_pages quirks on Hyper-V virtual disks
drivers/scsi/scsi_devinfo.c | 1 +
drivers/scsi/scsi_scan.c| 3 +++
drivers/scsi
This reverts commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6 (Drivers:
add blist flags) as it does not enable thin provisioning for my Hyper-V 2012 R2
virtual disks.
Signed-off-by: Sitsofe Wheeler sits...@yahoo.com
---
drivers/scsi/storvsc_drv.c | 10 --
1 file changed, 10 deletions
-by: Sitsofe Wheeler sits...@yahoo.com
---
drivers/scsi/scsi_scan.c| 3 +++
drivers/scsi/sd.c | 3 +++
include/scsi/scsi_device.h | 1 +
include/scsi/scsi_devinfo.h | 1 +
4 files changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
index ba3f1e8..d3f6267
impacts Hyper-V's VHD/VHDX virtual disks and not passthrough devices.
Signed-off-by: Sitsofe Wheeler sits...@yahoo.com
---
drivers/scsi/scsi_devinfo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/scsi_devinfo.c b/drivers/scsi/scsi_devinfo.c
index 49014a1..3eadcb1 100644
On Sun, Oct 05, 2014 at 09:11:29PM -0400, David Miller wrote:
From: K. Y. Srinivasan k...@microsoft.com
Date: Sun, 5 Oct 2014 10:42:51 -0700
After the packet is successfully sent, we should not touch the packet
as it may have been freed. This patch is based on the work done by
Long Li
- not syncing: Fatal exception in interrupt
Kernel Offset: 0x0 from 0x8100 (relocation range:
0x8000-0x9fff)
---[ end Kernel panic - not syncing: Fatal exception in interrupt
So
Tested-by: Sitsofe Wheeler sits...@yahoo.com
But I'm still seeing oopses like the following
On Tue, Sep 23, 2014 at 09:56:10AM +0200, Olaf Hering wrote:
On Tue, Sep 23, Thomas Shao wrote:
In current hyper-v time sync service,it only gets the initial clock time
from the host. It didn't process the following time samples. This change
introduced a module parameter called
On Thu, Sep 25, 2014 at 09:40:42AM +, Thomas Shao wrote:
On Tue, Sep 23, Thomas Shao wrote:
with the host clock using host time sample. By default it is
disabled, because we still recommend user to configure NTP for time
-Original Message-
From: Sitsofe Wheeler
On Thu, Sep 04, 2014 at 10:40:14PM -0700, Christoph Hellwig wrote:
Looks good to me.
Olaf, Hannes - can I get another review for this (and the older hyperv
scanning patch set)?
I agree this looks useful because on a
59753a805499f1ffbca4ac0a24b3dff67bf1 3.17rc2 kernel with
92578ea
of BUG_ON crashes I was hitting on
Hyper-V while booting a kernel with verification options on. With these
I can complete a 3.17.0-rc2 boot on an SMP setup although patches from
Drivers: hv: vmbus: Miscellaneous cleanup are needed to resolve other
non-crash issues.
Tested-by: Sitsofe Wheeler sits
: Properly protect calls to smp_processor_id()
These patches (on top of the Drivers: hv: vmbus: Eliminate calls to
BUG_ON() series) resolve an issue I was seeing where the Hyper-V
framebuffer driver would fail when booting a 3.17.0-rc2 verification
kernel on a UP system.
Tested-by: Sitsofe Wheeler
On Thu, Aug 28, 2014 at 06:29:52PM -0700, K. Y. Srinivasan wrote:
Minimize failures in this function by pre-allocating the buffer
for posting messages. The hypercall for posting the message can fail
for a number of reasons:
snip
Cc: sta...@vger.kernel.org
Is this patch useful for all
While booting a 10 vcpu system with a post v3.17-rc2 kernel with the
Drivers: hv: vmbus: Eliminate calls to BUG_ON(), Drivers: hv: vmbus:
Miscellaneous cleanup patches and debugging/verification config options
on I'm seeing the following:
[ 31.570860] EXT4-fs (sdb1): mounted filesystem with
On Fri, Aug 29, 2014 at 01:24:11PM +0300, Dan Carpenter wrote:
On Fri, Aug 29, 2014 at 10:16:32AM +, Dexuan Cui wrote:
Section 4.11.3 of Hypervisor Top Level Functional Specification(available at
On Fri, Aug 29, 2014 at 05:18:51PM +, KY Srinivasan wrote:
-Original Message-
From: Sitsofe Wheeler [mailto:sits...@gmail.com]
Sent: Friday, August 29, 2014 2:32 AM
To: Dexuan Cui
Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang;
de...@linuxdriverproject.org; linux
Hi Dexuan,
On Thu, Aug 28, 2014 at 03:21:59AM +, Dexuan Cui wrote:
First let me thank you guys for looking into this issue. Looking at
Feel free to add
Reported-by: Sitsofe Wheeler sits...@yahoo.com
to your patches (it's useful too me because it makes it easier for me to show
what I've
On Tue, Aug 26, 2014 at 12:05:22PM -0700, K. Y. Srinivasan wrote:
Cleanup the channel management code and eliminate calls to BUG_ON()
K. Y. Srinivasan (4):
Drivers: hv: vmbus: Cleanup vmbus_post_msg()
Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()
Drivers: hv: vmbus: Cleanup
On Mon, Aug 25, 2014 at 09:48:31PM +, KY Srinivasan wrote:
There is also a case of the BUG_ON at line 460 being hit (from
https://lkml.org/lkml/2014/8/19/708 ):
457ret = vmbus_post_msg(msg,
458 sizeof(struct
On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote:
What is baffles me is the whole UP vs SMP thing - why would UP
make this show up consistently? Perhaps some assertions could be added
to check that rbi-ring_buffer still has sane values in it after
operations on it are finished?
On Wed, Aug 27, 2014 at 11:30:54AM +, Dexuan Cui wrote:
-Original Message-
From: Sitsofe Wheeler
On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote:
Actually I found the direct cause of the panic: sometimes
vmbus_post_msg() can return 4
On Wed, Aug 27, 2014 at 02:14:02PM +, Dexuan Cui wrote:
-Original Message-
From: Sitsofe Wheeler
Sent: Wednesday, August 27, 2014 20:16 PM
I'm making a patch for this.
Please see the end of the mail for the inline patch and try it.
(the patch hasn't been rebased against
On Wed, Aug 27, 2014 at 06:45:55PM +, KY Srinivasan wrote:
-Original Message-
From: Sitsofe Wheeler [mailto:sits...@gmail.com]
Sent: Wednesday, August 27, 2014 9:19 AM
BTW, with the patch below, hyperv_fb can work now, BUT,
*occasionally*,
storvsc_probe
Hi Dexuan,
On Mon, Aug 25, 2014 at 02:02:21PM +, Dexuan Cui wrote:
-Original Message-
From: Sitsofe Wheeler
Sent: Wednesday, August 20, 2014 17:27 PM
While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was
triggered while registering hyperv_fb which in turn
On Tue, Aug 19, 2014 at 12:40:53PM +0100, Sitsofe Wheeler wrote:
On Tue, Aug 19, 2014 at 10:57:30AM +0200, Daniel Borkmann wrote:
On 08/19/2014 10:15 AM, Sitsofe Wheeler wrote:
After a variety of issues on Hyper-V (host is running Windows 2012 R2) I
updated to the latest kernel (3.17-rc1
On Mon, Aug 25, 2014 at 12:36:48PM +0300, Dan Carpenter wrote:
The code here is:
drivers/hv/channel.c
460 BUG_ON(ret != 0);
461 t = wait_for_completion_timeout(info-waitevent, 5*HZ);
462 BUG_ON(t == 0);
There is also a case of the BUG_ON at line 460
Hi,
On Wed, Aug 20, 2014 at 11:15:39AM +, Dexuan Cui wrote:
-Original Message-
From: Sitsofe Wheeler
Sent: Wednesday, August 20, 2014 17:27 PM
To: Dexuan Cui
Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang;
de...@linuxdriverproject.org; linux-ker...@vger.kernel.org
After a variety of issues on Hyper-V (host is running Windows 2012 R2) I
updated to the latest kernel (3.17-rc1
7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9), turned on a bunch of kernel
validation options and booted which has resulted in a BUG being
triggered (IP claims to be at netvsc_select_queue),
On Tue, Aug 19, 2014 at 10:57:30AM +0200, Daniel Borkmann wrote:
On 08/19/2014 10:15 AM, Sitsofe Wheeler wrote:
After a variety of issues on Hyper-V (host is running Windows 2012 R2) I
updated to the latest kernel (3.17-rc1
7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9), turned on a bunch of kernel
While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was
triggered in drivers/hv/channel.c:504 which in turn caused a panic:
[ 11.367472] Non-volatile memory driver v1.3
[ 11.395587] Linux agpgart interface v0.103
[ 11.425034] loop: module loaded
[ 11.446046] Loading iSCSI
Now we get to the issue I've been meaning to report: changing the MTU of
a Hyper-V network interface while traffic is flowing through it triggers
a BUG. I've seen this happen on a variety of kernels but the trace below
is from 3.17.0-rc1.
Steps to reproduce:
(Guests were customised Fedora 20
On Tue, Aug 19, 2014 at 09:29:44PM +, Haiyang Zhang wrote:
-Original Message-
From: Sitsofe Wheeler [mailto:sits...@gmail.com]
Sent: Tuesday, August 19, 2014 8:37 AM
To: KY Srinivasan
Cc: Greg Kroah-Hartman; Haiyang Zhang; de...@linuxdriverproject.org;
linux-ker
features.
With this patch we can correctly handle WRITE_SAME_16 issues.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
Reviewed-by: Hannes Reinecke h...@suse.de
On Wed, Jul 23, 2014 at 09:13:41PM +0100, Sitsofe Wheeler wrote:
On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig
On Wed, Jul 23, 2014 at 09:13:41PM +0100, Sitsofe Wheeler wrote:
On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig wrote:
On Wed, Jul 23, 2014 at 03:10:28PM +0100, Sitsofe Wheeler wrote:
I'm not sure this alone will work - won't sdev_bflags/bflags have
already been built
a blacklist flag that allows the forcing of the paths leading
to logical block provisioning tests.
See https://lkml.org/lkml/2014/7/13/59 for the previous version.
Reported-by: K. Y. Srinivasan k...@microsoft.com
Original-patch-by: Martin K. Petersen martin.peter...@oracle.com
Signed-off-by: Sitsofe
for the previous version of this
patch and https://lkml.org/lkml/2014/7/23/615 for example devices.
Original-patch-by: K. Y. Srinivasan k...@microsoft.com
Signed-off-by: Sitsofe Wheeler sits...@yahoo.com
---
drivers/scsi/storvsc_drv.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff
On Thu, Jul 24, 2014 at 08:47:39AM +0100, Sitsofe Wheeler wrote:
On Wed, Jul 23, 2014 at 09:13:41PM +0100, Sitsofe Wheeler wrote:
On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig wrote:
On Wed, Jul 23, 2014 at 03:10:28PM +0100, Sitsofe Wheeler wrote:
I'm not sure this alone
On Thu, Jul 24, 2014 at 09:54:24AM -0400, Martin K. Petersen wrote:
Sitsofe == Sitsofe Wheeler sits...@gmail.com writes:
Sitsofe Fix incorrectly named variable. Some block devices (such as
Sitsofe Hyper-V passthrough SSDs) support logical block provisioning
Sitsofe (e.g. via UNMAP
On Thu, Jul 24, 2014 at 08:35:13AM -0700, Christoph Hellwig wrote:
On Thu, Jul 24, 2014 at 08:34:19AM -0700, Christoph Hellwig wrote:
I agree - I'd like to pull in KY's simple fix as soon as I get a second
review for it.
Ok, looks like I just got that from Hannes. Let's see if there's
On Thu, Jul 24, 2014 at 02:09:11PM +, James Bottomley wrote:
On Thu, 2014-07-24 at 08:56 +0100, Sitsofe Wheeler wrote:
Microsoft Hyper-V targets currently only claim SPC-2 compliance / no
compliance indicated even though they implement post SPC-2 features
which means those features
On Mon, Jul 21, 2014 at 04:06:01PM -0700, K. Y. Srinivasan wrote:
Add blist flags to permit the reading of the VPD pages even when
the target may claim SPC-2 compliance. MSFT targets currently
claim SPC-2 compliance while they implement post SPC-2 features.
With this patch we can correctly
On Wed, Jul 23, 2014 at 04:51:28AM -0700, Christoph Hellwig wrote:
On Wed, Jul 23, 2014 at 11:04:48AM +0100, Sitsofe Wheeler wrote:
OK I've just seen this as I was about to post a similar patch to get
discard going on Hyper-V. Will your patches handle Hyper-V pass through
devices
On Mon, Jul 21, 2014 at 04:06:01PM -0700, K. Y. Srinivasan wrote:
Add blist flags to permit the reading of the VPD pages even when
the target may claim SPC-2 compliance. MSFT targets currently
claim SPC-2 compliance while they implement post SPC-2 features.
With this patch we can correctly
On Wed, Jul 23, 2014 at 07:10:14AM -0700, Christoph Hellwig wrote:
On Wed, Jul 23, 2014 at 01:54:43PM +0100, Sitsofe Wheeler wrote:
That's good to know (I was worried the device would not be detected as
supporting discard because it doesn't report lbpme and doesn't declare a
conformance
On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig wrote:
On Wed, Jul 23, 2014 at 03:10:28PM +0100, Sitsofe Wheeler wrote:
I'm not sure this alone will work - won't sdev_bflags/bflags have
already been built at this point?
They've been built up, but we can still or new values
On Fri, Jul 11, 2014 at 03:25:11PM +, Haiyang Zhang wrote:
-Original Message-
From: Sitsofe Wheeler [mailto:sits...@gmail.com]
Sent: Friday, July 11, 2014 1:53 AM
To: Haiyang Zhang
Cc: KY Srinivasan; David S. Miller; de...@linuxdriverproject.org; linux-
ker
On Mon, Jul 14, 2014 at 10:39:48PM +, Haiyang Zhang wrote:
-Original Message-
From: Sitsofe Wheeler [mailto:sits...@gmail.com]
Sent: Monday, July 14, 2014 5:31 PM
To: Haiyang Zhang
Cc: KY Srinivasan; David S. Miller; de...@linuxdriverproject.org; linux-
ker
On Mon, Jul 07, 2014 at 07:13:41PM +0100, Sitsofe Wheeler wrote:
On Mon, Jul 07, 2014 at 04:54:20PM +, Haiyang Zhang wrote:
-Original Message-
From: Sitsofe Wheeler [mailto:sits...@gmail.com]
Sent: Sunday, July 6, 2014 4:18 PM
To: Haiyang Zhang
Cc: KY Srinivasan
With the 3.14 kernel Hyper-V no longer reliably enables its networking
devices in time on cloud images leading to network devices permanently
remaining offline.
After a painful round of bisection I've narrowed this down to commit
b679ef73edc251f6d200a7dd2396e9fef9e36fc3 :
# bad:
59 matches
Mail list logo
