- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Nimble+KVM+New Linux Kernels
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 05:27 AM
12-03-2015 05:27 AM
Hey everyone! New to nimble, we just got two CS300's a few months ago. We are looking to run them in a KVM environment (Proxmox 4 to be exact). The latest version of Proxmox is based on the 4.2.x kernel branch and we are running into all kinds of issues with installing VM's and filesystem errors within VM's. We are using simple LVM backed raw disks. Whats really interesting is the issue seems to only occur when using the default cache setting of "cache=none". This is the recommended/default cache settings and ensure writes are committed to the cache of the storage.
The issue does not happen in 2.6.32 kernels or 3.10.x kernels (Proxmox3) .
The Proxmox dev's have been digging into this now for a few weeks and havn't been able to pin the issue down. I am the only user reporting the issue and the issue only exists when using a disk backed by the nimble storage.
Just hoping there are some other community members using a newer kernel or looking to.
I appreciate the input!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2016 03:56 AM