http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c1 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | --- Comment #1 from Olaf Hering --- Also inst-sys has no /dev/disk -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c3 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmilasan@suse.com, | |thomas.blume@suse.com Flags| |needinfo?(thomas.blume@suse | |.com) --- Comment #3 from Robert Milasan --- Could be missing rules in the initrd. Try to boot with 'rd.udev.log-priority=debug', but this is only for udev. Thomas, whats the best idea to debug in the ISO, do you know? Will journalctl work? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c5 --- Comment #5 from Robert Milasan --- OK, the problems seems to be that we dont support 'hd*' :) We (probably upstream) seems to have drop the support for hda style of naming. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c7 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ohering@suse.com Flags| |needinfo?(ohering@suse.com) --- Comment #7 from Robert Milasan --- I'm thinking of this: 1. For IDE controllers device file name is - hda, hdb, hdc.. 2. For SCSI and SATA controllers device file name is - sda, sdb, sdc.. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c9 --- Comment #9 from Robert Milasan --- (In reply to Olaf Hering from comment #8)

The strings for a given block device are "free strings", that means a given block driver is free to pick any name. It just happend that IDE used to pick hd, SCSI picked "sd" and so on. In the early days the PV drivers used to claim the well known names and their major:minors to make it easier to install and run existing distros.

Not really, the device name is given based on what layer is used, for example SCSI/SATA/ATA usually can go thru SCSI or libata (I'm talking about kernel) and their naming will start with 'sd'. Xen has its own things and will be something like 'xvd', but you have 'hd' because you have a bit of a different setup, maybe not using Xen's own driver or layer or something, but the kernel and kernel sees it as an old device. I really dont know enough about Xen to comment too much. Here you are emulating an old machine, somehow.

Today the names can be still passed into the guest. For some reason I picked "hd" instead of "xvd" for my PV guests. So that part might be fixeable by adjusting both the domU.cfg and also the used devicenames within the VM. In the end I would call this a regression. "hd" per se has no relationship to IDE hardware anymore, as explained above. Please restore "hd" support, I'm sure such names are in use.

Not sure why the HVM guest fails. Here the "hd" in domU.cfg has additional meaning, it tells qemu to create an emulated IDE controller which is later driven by the SATA drivers. Have to see how to debug this.

'hd' is not really is use, because is not possible. A normal machine that is 64bit wont be using IDE, is too old. At least is what I know. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c11 --- Comment #11 from Olaf Hering --- Created attachment 655422 --> http://bugzilla.suse.com/attachment.cgi?id=655422&action=edit udev-hvm.txt HVM with emulated piix controller, required for booting. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c13 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@suse.com --- Comment #13 from Robert Milasan --- Try: grep ^KERNEL /usr/lib/udev/rules.d/60-persistent-storage.rules Adding 'hd*' to that line wont help, as the links are created by the rest of the lines looking like this: KERNEL=="sd*... NOTE: This is one of the rules involved, there are several of them. Lets add Hannes here too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c15 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ohering@suse.com) --- Comment #15 from Robert Milasan --- How does it look like? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c17 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ohering@suse.com) | --- Comment #17 from Olaf Hering --- Created attachment 655510 --> http://bugzilla.suse.com/attachment.cgi?id=655510&action=edit hd.patch Is there a reason why the by-label/by-uuid are skipped for everything which is not handled? It looks like this bug could have been easily avoided by creating the symlinks for on-disk content unconditionally. There is certainly no need for by-id or by-path, which could be handled by the whitelist as it is implemented now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c19 --- Comment #19 from Olaf Hering --- bug#954872 is an example that the prefix "hd" is still in use, perhaps just due to old habit. sle11sp2 required it to create an emulated disk from which qemu BIOS can boot. sle11sp3 turned also "xvd" into such emulated disk. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c21 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #21 from Franck Bui --- closing as invalid. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c23 --- Comment #23 from Franck Bui --- (In reply to Olaf Hering from comment #22)

(In reply to Franck Bui from comment #20)

...

I don't know Xen at all, ...

Then please dont close this bug as invalid... Instead apply the patch for the .rules file.

Then please explain why we should allow this hack whereas you can simply rename your device correctly ? I also suggest you to send your patch to upstream if you believe it as valid. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c25 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fbui@suse.com) | --- Comment #25 from Franck Bui --- (In reply to Robert Milasan from comment #24)

Franck, how would he rename his device(s)?

"xvd", it seems to be the "official" kernel name used by the xen virtual block devices. Apparently, Olaf choose "hd" for no good reason (see his comment #8), and I don't see any reason to add one more special handling for him. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c27 --- Comment #27 from Olaf Hering --- libxl supports the domU.cfg files from xend. Their syntax is equal anyway, but some aspects of the "old" disk=[] syntax needed an update to handle more use cases. In the end this translates to "existing domU.cfg files must be supported". This means that even the names of the devices (such as "hda") are accepted on the libxl side. I'm sure there are domU.cfg files with 'hd?' out there, and TW will simply breaks in those VMs. For no good reason. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c29 --- Comment #29 from Franck Bui --- (In reply to Olaf Hering from comment #27)

libxl supports the domU.cfg files from xend. Their syntax is equal anyway, but some aspects of the "old" disk=[] syntax needed an update to handle more use cases. In the end this translates to "existing domU.cfg files must be supported". This means that even the names of the devices (such as "hda") are accepted on the libxl side.

I'm sure there are domU.cfg files with 'hd?' out there, and TW will simply breaks in those VMs. For no good reason.

Currently your the first one reporting a bug for that, and if the name you're using is considered as a bad practice, then you should rename it instead of asking for us to support one more hack forever. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c31 --- Comment #31 from Olaf Hering --- (In reply to Franck Bui from comment #29)

Currently your the first one reporting a bug for that, and if the name you're using is considered as a bad practice, then you should rename it instead of asking for us to support one more hack forever.

Who said "hd?" is bad practice? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=954452 http://bugzilla.suse.com/show_bug.cgi?id=954452#c33 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX --- Comment #33 from Olaf Hering --- The pvops kernel enforces "/dev/xvd*" as device name. This issue happend only during the short timeframe when systemd was upgraded and Tumbleweed still had a xenlinux (instead of pvops) based domU kernel. -- You are receiving this mail because: You are on the CC list for the bug.