Am Sonntag, 1. Mai 2011, 05:22:03 schrieb Cristian Rodríguez:
Hi:
When you build in either xen or KVM, the mount command seems to use host's mount options instead of the VM's one.
for example in my SSD drive
fsck from util-linux 2.19 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/vda /dev/vda: clean, 19024/262144 files, 187334/1048576 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/vda mount -o rw,noatime,data=writeback,acl,user_xattr,barrier=0,commit=100 -t ext4 /dev/vda /root
or in the OBS
fsck from util-linux 2.19-rc3 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda1 /dev/hda1: Superblock last write time is in the future. (by less than a day, probably due to the hardware clock being incorrectly set). FIXED. /dev/hda1: clean, 2621/897600 files, 123116/3584000 blocks fsck succeeded. Mounting root device read-only. Mounting root /dev/hda1 mount -o ro,defaults -t ext3 /dev/hda1 /root
This doesnt sound like the expected behavior to me, or am I missing something here ?
The reason is probably the initrd you created for kvm (and xen) is tailored at your host. That works 90% also wor the workers. The 10% are cases like your encryption and filesystems like btrfs atm. So we need to think on how to generate the needed initrd's in a better way. Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org