Germano,
Many helps for your tips.
Looks like I'm running even if latest master branch, some kind of old
version as all I have is:
grep CONF_KEY_ /usr/lib/xapi/sm/blktap2.py
CONF_KEY_ALLOW_CACHING = "vdi_allow_caching"
CONF_KEY_MODE_ON_BOOT = "vdi_on_boot"
CONF_KEY_CACHE_SR = "local_ca
Hi Dawid,
For what concerns your build I do not know how it maps to storage
manager and blktap versions.
If in /opt/xensource/sm/blktap2.py there is a line like
CONF_KEY_O_DIRECT = "o_direct"
then you can disable o_direct.
About your frustration I can understand but it is a long shot
to say xe
Thanks Germano,
I'm running latest master branch taken from here:
git clone git://github.com/xenserver/buildroot.git
as per:
https://github.com/xenserver/buildroot
If you could recommend me any good working branch I might be keen to try it.
btw. slightly off topic...
I've to admit that during
Thanks Carlos.
Interesting info on ZFS O_DIRECT :)
Regards,
Dawid
2014-12-31 2:03 GMT+01:00 Carlos Reategui :
> Glad you got it to work.
>
> BTW DirectIO support in ZFS on Linux is on the roadmap for 0.6.4 (
> https://github.com/zfsonlinux/zfs/issues/224). However don't know when
> that is sche
Hi Dawid,
Which sm or XS version are you using?
If you are using 6.2 or earlier, yes the fs need to support direct IO.
In the master branch and xs64bit there is code to disable o_direct.
Those changes go hand in hand with corresponding blktap changes.
Cheers,
Germano
On 12/30/2014 05:45 PM, D
Glad you got it to work.
BTW DirectIO support in ZFS on Linux is on the roadmap for 0.6.4 (
https://github.com/zfsonlinux/zfs/issues/224). However don't know when
that is scheduled for.
On Tue, Dec 30, 2014 at 4:04 PM, Dawid Kowalski wrote:
> Hi Carlos,
>
> Thanks for hint!
> This one worked.
Hi Carlos,
Thanks for hint!
This one worked.
So what worked:
zpool -> zfs block device fomatted as ext4 and mounted as folder
storage repository created with ffs driver.
The other drivers, meaning :
- file, fileSR on mounted ext4 FS,
- ext/lvm pointed to /dev/zd0
- ffs directly on ZFS.
Failed.
Have you tried using ext4 on a ZVOL and putting your VHDs there?
Scroll down to the "Ext4 on a ZVOL" section:
https://pthree.org/2012/12/21/zfs-administration-part-xiv-zvols/
On Tue, Dec 30, 2014 at 9:45 AM, Dawid Kowalski wrote:
> Just as a form of an update. I'm stuck trying to get NFS worki
Just as a form of an update. I'm stuck trying to get NFS working as no
other way to use ZFS in background seems to be available for me. iSCSI
share option for ZFS is not available on Linux. Should I try to enable
it I'd need to add third-party daemon.
I'm looking forward for your help in NFS c
> On 30 Dec 2014, at 17:24, Dawid Kowalski wrote:
>
> I'll answer myself.
>
> Modifying td.c line 258 to skip O_DIRECT and recompiling doesn't help.
> For some unexplained reasons, it calls O_DIRECT flag still:
Hm. As an experiment you could try an LD_PRELOAD wrapper like this:
http://www.mcg
I'll answer myself.
Modifying td.c line 258 to skip O_DIRECT and recompiling doesn't help.
For some unexplained reasons, it calls O_DIRECT flag still:
strace ./td-util create vhd 2048 /path/to/file
open("/path/to/file", O_WRONLY|O_CREAT|O_TRUNC|O_DIRECT, 0644) = -1
EINVAL (Invalid argument)
ex
Hi Guys,
Just wanted to report that file based Storage Repository won't work on
Linux systems as td-util is required O_DIRECT when creating image file
not supported on ZFS (Linux).
When creating vm, i.e. vm-import it calls td-util similar to below:
td-util create vhd 2048 /path/to/file
Strac
12 matches
Mail list logo
