>>> On 06.07.10 at 22:51, 0bo0 <[email protected]> wrote: > i've noted this new entry in my xen boot logs, > > > ---------------------------- > Boot logging started on /dev/char/../xvc0(/dev/console) at Tue Jul 6 > 13:46:40 2010 > Starting udevd: udevd[765]: can not read > '/etc/udev/rules.d/79-yast2-drivers.rules'
This one I can't say anything about. > [ 8.956190] udev: starting version 157 > > done > Loading drivers, configuring devices: udevd-work[780]: kernel-provided > name 'pci_iomul' and NAME= 'xen/pci_iomul' disagree, please use > SYMLINK+= or change the kernel to provide the proper name > ---------------------------- > > i haven't noticed any ill effects. is this known? a bug? just noise? This is known (there should be a few more of them) and represents a warning that things will break at some point in the future. With the Xen 4.0.0 tool stack (i.e. in 11.3) we can't do much about it (i.e. you should consider this just noise), going forward we'll have to change the kernel (assuming that a fixed tool stack is in place). Charles, this particularly implies that before I commit the respective kernel side changes (to properly prefix all devices names with xen/) trunk and Factory should be updated to current 4.0.1 or -unstable. Otherwise (with the old tools) the (correct) device nodes will get removed by libxc without it being able to re-create them. Jan -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
