[Bug 893450] Re: KVM guest fails to autostart sometimes with virSecurityDACRestoreSecurityFileLabel error
Horacio
893450 at bugs.launchpad.net
Thu Nov 24 01:42:28 UTC 2011
apport-collect didn't worked (the server has not direct internet
connection).
-------------------------
lspci
-------------------------
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
05:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 02)
-------------------------
some of the dmesg output
-------------------------
[ 1.152651] Fusion MPT base driver 3.04.18
[ 1.152707] Copyright (c) 1999-2008 LSI Corporation
[ 1.157884] async_tx: api initialized (async)
[ 1.170812] Fusion MPT SAS Host driver 3.04.18
[ 1.170911] mptsas 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.171196] mptbase: ioc0: Initiating bringup
[ 1.330050] raid6: int64x1 1469 MB/s
[ 1.390018] Refined TSC clocksource calibration: 1866.732 MHz.
[ 1.390078] Switching to clocksource tsc
[ 1.500025] raid6: int64x2 1967 MB/s
[ 1.670042] raid6: int64x4 1418 MB/s
[ 1.840049] raid6: int64x8 1323 MB/s
[ 2.010011] raid6: sse2x1 3152 MB/s
[ 2.180022] raid6: sse2x2 3804 MB/s
[ 2.350016] raid6: sse2x4 5600 MB/s
[ 2.350070] raid6: using algorithm sse2x4 (5600 MB/s)
[ 2.351541] xor: automatically using best checksumming function: generic_sse
[ 2.400007] generic_sse: 6836.000 MB/sec
[ 2.400062] xor: using function: generic_sse (6836.000 MB/sec)
[ 2.405934] md: raid6 personality registered for level 6
[ 2.405994] md: raid5 personality registered for level 5
[ 2.406051] md: raid4 personality registered for level 4
[ 2.413276] md: raid10 personality registered for level 10
[ 3.670031] ioc0: LSISAS1064E B1: Capabilities={Initiator}
[ 3.670248] mptsas 0000:05:00.0: setting latency timer to 64
[ 9.833435] scsi2 : ioc0: LSISAS1064E B1, FwRev=01100000h, Ports=1, MaxQ=511, IRQ=16
[ 9.857778] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x455d3742e2bbac8f
[ 9.866008] scsi 2:0:0:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 5
[ 9.867787] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 9.868136] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 9.869384] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 1, phy 1, sas_addr 0x455d393cddc2ad95
[ 9.877777] scsi 2:0:1:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 5
[ 9.879545] sd 2:0:1:0: Attached scsi generic sg2 type 0
[ 9.879901] sd 2:0:1:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 9.886711] sd 2:0:0:0: [sda] Write Protect is off
[ 9.886771] sd 2:0:0:0: [sda] Mode Sense: 73 00 00 08
[ 9.894839] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9.897900] sd 2:0:1:0: [sdb] Write Protect is off
[ 9.897959] sd 2:0:1:0: [sdb] Mode Sense: 73 00 00 08
[ 9.905889] sd 2:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9.976991] sda: sda1 sda2 sda3 sda4
[ 9.988416] sdb: sdb1 sdb2 sdb3 sdb4
[ 10.003907] sd 2:0:0:0: [sda] Attached SCSI disk
[ 10.015535] sd 2:0:1:0: [sdb] Attached SCSI disk
[ 10.511656] md: bind<sda4>
[ 10.525609] md: bind<sda2>
[ 10.542465] md: bind<sdb4>
[ 10.544430] bio: create slab <bio-1> at 1
[ 10.544560] md/raid1:md1: active with 2 out of 2 mirrors
[ 10.544640] md1: detected capacity change from 0 to 1985396702208
[ 10.632182] md: bind<sdb2>
[ 10.632774] md1: unknown partition table
[ 10.634310] md/raid1:md0: active with 2 out of 2 mirrors
[ 10.634394] md0: detected capacity change from 0 to 9998877696
[ 10.728161] md0: unknown partition table
[ 15.876872] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 19.034769] <30>udev[374]: starting version 167
[ 19.043871] Adding 4882808k swap on /dev/sda3. Priority:-1 extents:1 across:4882808k
[ 19.059394] Adding 4882808k swap on /dev/sdb3. Priority:-2 extents:1 across:4882808k
-------------------------
/proc/mdstat
-------------------------
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb2[1] sda2[0]
9764529 blocks super 1.2 [2/2] [UU]
md1 : active raid1 sdb4[1] sda4[0]
1938863967 blocks super 1.2 [2/2] [UU]
unused devices: <none>
-------------------------
Disk layout
-------------------------
The disk are two 2TB sata. No multipath. No hardware raid (I thing the
controller supports hardware raid). I don't know any further detail of
the hardware, tell me if you need more information about that.
There are 2 raid partitions and 1 swap on each disk.
- md0 (raid1) -> root filesystem
- md1 (raid1) -> one LVM physical volume, one volume group, all the LV from here...
Some of the LV are PV for the guest machines. I've configured the
"filter" on lvm.conf, so now only /dev/sd? and /dev/md? are scanned (and
not the LV that are PV for the guests), but this doesn't fixed the
problem.
I've to say that I've some trouble with this server some time ago. The
server worked ok, but some times the boot process stopped with an error.
It seems that the raid took too many time to startup, and failed to
mount the filesystem. I workaround that adding file on /etc/initramfs-
tools/scripts/local-premount/waitbeforemount with a "sleep 5" line...
and with this pause we have no more boot problems.
Tell me if you need more information about something else...
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/893450
Title:
KVM guest fails to autostart sometimes with
virSecurityDACRestoreSecurityFileLabel error
Status in “libvirt” package in Ubuntu:
Incomplete
Status in “udev” package in Ubuntu:
New
Bug description:
Some times, one of the KVM guest failed to start. I've 3 guest, two
started OK and one failed (the two times the same has failed). After
rebooting the host two times, the KVM guest started OK, but this is a
server and found too risky this behavior. The host server is running
"Ubuntu 11.04 Server 64bits" and libvirt 0.8.8-1ubuntu6.5
The two times that failed, I've found this on syslog:
error : virSecurityDACSetOwnership:125 : unable to set user and group to '105:115' on '/dev/vg_default/lv_robot-pv0': No such file or directory
kernel: [ 200.354543] type=1400 audit(1321932141.068:11): apparmor="DENIED" operation="open" parent=2539 profile="/usr/lib/libvirt/virt-aa-helper" name="/dev/dm-7" pid=2638 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=105
kernel: [ 200.692255] type=1400 audit(1321932141.408:12): apparmor="STATUS" operation="profile_load" name="libvirt-7262201f-566b-d0b1-16ec-0b404ccd5336" pid=2639 comm="apparmor_parser"
libvirtd: 00:22:21.424: 2539: error : virSecurityDACRestoreSecurityFileLabel:143 : cannot resolve symlink /dev/vg_default/lv_robot-pv0: No such file or directory
libvirtd: 00:22:21.707: 2539: error : qemuAutostartDomain:275 : Failed to autostart VM 'robot': unable to set user and group to '105:115' on '/dev/vg_default/lv_robot-pv0': No such file or directory
The LVM device is on a software raid. Maybe this is taking too long to
come up?
FYI, running "aa-status" (after the reboots) gives me:
apparmor module is loaded.
9 profiles are loaded.
9 profiles are in enforce mode.
/sbin/dhclient
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/lib/libvirt/virt-aa-helper
/usr/sbin/libvirtd
/usr/sbin/tcpdump
libvirt-7262201f-566b-d0b1-16ec-0b404ccd5336
libvirt-c032ea0a-8c62-7730-fb4d-e1bf60c15a31
libvirt-f06ad419-f312-f002-444f-3e51f40d2291
0 profiles are in complain mode.
4 processes have profiles defined.
4 processes are in enforce mode :
/usr/sbin/libvirtd (2459)
libvirt-7262201f-566b-d0b1-16ec-0b404ccd5336 (2521)
libvirt-c032ea0a-8c62-7730-fb4d-e1bf60c15a31 (2551)
libvirt-f06ad419-f312-f002-444f-3e51f40d2291 (2582)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/893450/+subscriptions
More information about the foundations-bugs
mailing list