Quoting James Hunt ([email protected]):
> @Serge: what was your storage configuration when you saw the problem
> without LVs? I think I've seen the problem a couple of times simply by
> providing 2 extra raw disks to the system but at that point my udevd
> debug wasn't helpful. I have tried modifying udevd to continue
> processing events but it then hangs. I really need to be able to
> recreate the problem more reliably on a system I've got control over
> before fathoming this one out.
Here is the xml for that domain, for what it's worth. disk0.img is
raw format:
serge@sergelap:~/vms/kvm/c$ qemu-img info disk0.img
image: disk0.img
file format: raw
virtual size: 8.0G (8589934592 bytes)
disk size: 3.3G
serge@sergelap:~/vms/kvm/c$ virsh dumpxml c
<domain type='kvm' id='2'>
<name>c</name>
<uuid>15405141-d078-c266-ae6f-8ca6b72a08e8</uuid>
<memory>524288</memory>
<currentMemory>524288</currentMemory>
<vcpu>1</vcpu>
<os>
<type arch='x86_64' machine='pc-0.14'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/home/serge/vms/kvm/c/disk0.img'/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<alias name='ide0-1-0'/>
<address type='drive' controller='0' bus='1' unit='0'/>
</disk>
<controller type='ide' index='0'>
<alias name='ide0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x1'/>
</controller>
<interface type='network'>
<mac address='00:16:3e:26:26:74'/>
<source network='default'/>
<target dev='vnet0'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/4'/>
<target port='0'/>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/4'>
<source path='/dev/pts/4'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='5900' autoport='yes'/>
<video>
<model type='vmvga' vram='9216' heads='1'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</memballoon>
</devices>
<seclabel type='dynamic' model='apparmor'>
<label>libvirt-15405141-d078-c266-ae6f-8ca6b72a08e8</label>
<imagelabel>libvirt-15405141-d078-c266-ae6f-8ca6b72a08e8</imagelabel>
</seclabel>
</domain>
The host is a core i7 laptop with 8G ram and showing 8 cpus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/818177
Title:
boot failures caused by udev race
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818177/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
