IT技術情報 – ページ 50 – ぷすぅ～ぷすぅ～

Ubuntu 側でアップデートすると度々動かなくなる。
で、 VMwareTools を再インストールしてもダメ。
ここで、VMwareToolsのインストール時のトラブルを報告したが、今回もアップデートに伴う問題の別件。

VMwareTools を入れ直してももうまくいかないので、注意深くログをみていたら以下のようなエラーが。


Using kernel build system.
make: Entering directory `/tmp/modconfig-0s8m4m/vmci-only'
/usr/bin/make -C /lib/modules/3.2.0-77-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-77-generic'
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-0s8m4m/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-0s8m4m/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-0s8m4m/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-0s8m4m/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-77-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-0s8m4m/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-0s8m4m/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-0s8m4m/vmci-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-0s8m4m/vmhgfs-only'
/usr/bin/make -C /lib/modules/3.2.0-77-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
	  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-77-generic'
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/backdoor.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/backdoorGcc64.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/bdhandler.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/cpName.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/cpNameLinux.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/cpNameLite.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/dentry.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/dir.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/file.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/filesystem.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/fsutil.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/hgfsBd.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/hgfsEscape.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/hgfsUtil.o
  CC [M]  /tmp/modconfig-0s8m4m/vmhgfs-only/inode.o
/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c: In function ‘HgfsPermission’:
/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: error: ‘struct dentry’ has no member named ‘d_alias’
/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: warning: initialization from incompatible pointer type [enabled by default]
/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: warning: (near initialization for ‘dentry’) [enabled by default]
/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: error: ‘struct dentry’ has no member named ‘d_alias’
make[2]: *** [/tmp/modconfig-0s8m4m/vmhgfs-only/inode.o] Error 1
make[1]: *** [_module_/tmp/modconfig-0s8m4m/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-77-generic'
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/modconfig-0s8m4m/vmhgfs-only'

The filesystem driver (vmhgfs module) is used only for the shared folder 
feature. The rest of the software provided by VMware Tools is designed to work 
independently of this feature.

If you wish to have the shared folders feature, you can install the driver by 
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine. 
These packages are available on your distribution's installation CD.

Using kernel build system.

make: Entering directory `/tmp/modconfig-0s8m4m/vmci-only'

/usr/bin/make -C /lib/modules/3.2.0-77-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.2.0-77-generic'

CC [M] /tmp/modconfig-0s8m4m/vmci-only/linux/driver.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/linux/vmciKernelIf.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciContext.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciDatagram.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciDoorbell.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciDriver.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciEvent.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciHashtable.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciQPair.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciQueuePair.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciResource.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/common/vmciRoute.o

CC [M] /tmp/modconfig-0s8m4m/vmci-only/driverLog.o

LD [M] /tmp/modconfig-0s8m4m/vmci-only/vmci.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-0s8m4m/vmci-only/vmci.mod.o

LD [M] /tmp/modconfig-0s8m4m/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-77-generic'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-0s8m4m/vmci-only'

make[1]: `postbuild' is up to date.

make[1]: Leaving directory `/tmp/modconfig-0s8m4m/vmci-only'

cp -f vmci.ko ./../vmci.o

make: Leaving directory `/tmp/modconfig-0s8m4m/vmci-only'

Using kernel build system.

make: Entering directory `/tmp/modconfig-0s8m4m/vmhgfs-only'

/usr/bin/make -C /lib/modules/3.2.0-77-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.2.0-77-generic'

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/backdoor.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/backdoorGcc64.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/bdhandler.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/cpName.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/cpNameLinux.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/cpNameLite.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/dentry.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/dir.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/file.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/filesystem.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/fsutil.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/hgfsBd.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/hgfsEscape.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/hgfsUtil.o

CC [M] /tmp/modconfig-0s8m4m/vmhgfs-only/inode.o

/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c: In function ‘HgfsPermission’:

/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: error: ‘struct dentry’ has no member named ‘d_alias’

/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: warning: initialization from incompatible pointer type [enabled by default]

/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: warning: (near initialization for ‘dentry’) [enabled by default]

/tmp/modconfig-0s8m4m/vmhgfs-only/inode.c:1978:34: error: ‘struct dentry’ has no member named ‘d_alias’

make[2]: *** [/tmp/modconfig-0s8m4m/vmhgfs-only/inode.o] Error 1

make[1]: *** [_module_/tmp/modconfig-0s8m4m/vmhgfs-only] Error 2

make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-77-generic'

make: *** [vmhgfs.ko] Error 2

make: Leaving directory `/tmp/modconfig-0s8m4m/vmhgfs-only'

The filesystem driver (vmhgfs module) is used only for the shared folder

feature. The rest of the software provided by VMware Tools is designed to work

independently of this feature.

If you wish to have the shared folders feature, you can install the driver by

running vmware-config-tools.pl again after making sure that gcc, binutils, make

and the kernel sources for your running kernel are installed on your machine.

These packages are available on your distribution's installation CD.

問題は、 ‘struct dentry’ has no member named ‘d_alias’ だ。
また、ヘッダファイルか。変数名の名前が変わったのだろう。

ヘッダファイルの場所を変えるなどいろいろ試したがダメで、以下のような記述を発見

VMwareTools入れるときにエラー

ソースをいじって解決だ。

まず、VMwareToolsを展開したディレクトリから以下に移動


cd vmware-tools-distrib/lib/modules/source

cd vmware-tools-distrib/lib/modules/source

vmhgfs.tar を展開して移動


tar xvf ./vmhgfs.tar
cd vmhgfs-only/

tar xvf ./vmhgfs.tar

cd vmhgfs-only/

inode.c にある、d_alias を、d_u.d_alias に変更


chmod u+w ./inode.c

chmod u+w ./inode.c

で、先ほどのサイトにあるように、


vi ./inode.c

vi ./inode.c

で、開いて
:%s/d_alias/d_u.d_alias/ で変換するか。
sedで変換する。


sed -i -e "s/d_alias/d_u.d_alias/g" inode.c

sed -i -e "s/d_alias/d_u.d_alias/g" inode.c

vmhgfs.tar を削除して、再び、vmhgfs.tar を作る


rm ./vmhgfs.tar 
tar cvf vmhgfs.tar ./vmhgfs-only

rm ./vmhgfs.tar

tar cvf vmhgfs.tar ./vmhgfs-only

そして、VMwareTools を再インストールして、エラーなく終わり、共有ができていることを確認する。

以下のように projections を使って集計した結果を取った場合


def result = Domain.createCriteria().list {
    projections {
        sum("price", "priceSum")          // sum(price) as priceSum
        groupProperty("field1", "field1") // group by field1 
    }
}

def result = Domain.createCriteria().list {

projections {

sum("price", "priceSum") // sum(price) as priceSum

groupProperty("field1", "field1") // group by field1

}

戻り値のListの各要素は Object の配列(Object[])になっている。

なので、 Data Binding を使って new できない


result.each {
    SumDomain sumDomain = new SumDomain(it)
}

result.each {

SumDomain sumDomain = new SumDomain(it)

}

以下のように resultTransformer(CriteriaSpecification.ALIAS_TO_ENTITY_MAP) を付け加えるとうまくいく


def result = Domain.createCriteria().list {

    resultTransformer(CriteriaSpecification.ALIAS_TO_ENTITY_MAP)
    projections {
        sum("price", "priceSum")
        groupProperty("field1", "field1")
    }
}

result.each {
    SumDomain sumDomain = new SumDomain(it)
}

def result = Domain.createCriteria().list {

resultTransformer(CriteriaSpecification.ALIAS_TO_ENTITY_MAP)

projections {

sum("price", "priceSum")

groupProperty("field1", "field1")

}

result.each {

SumDomain sumDomain = new SumDomain(it)

}

Listの各要素は Map で受け取れるので Data Binding が使える

カテゴリー: IT技術情報

VMware Player 上のUbuntu。 Software の update 時に共有フォルダが使えなくなる

[Grails] projections で取得したデータに名前を付けて(Map形式)でデータを取得する