[Bug 450267] New: provide proper named devices for xen
https://bugzilla.novell.com/show_bug.cgi?id=450267 Summary: provide proper named devices for xen Product: openSUSE 11.0 Version: Final Platform: IA64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: estellnb@gmail.com QAContact: qa@suse.de Found By: Community of Practice Desktop users will decide from time to time to boot either via kernel-xen or kernel-default. * there should be a udev-rule establishing /dev/dvd pointing either to /dev/sr0(default-kernel) or to /dev/hdx(xen-kernel) * at the moment no xenbridge-device is available after startup /etc/xen/scripts/network-bridge start does not seem to create a xenbridge; instead ppeth0 appears and network access via peth0 is disabled -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c1 James Fehlig <jfehlig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbendixs@novell.com, jfehlig@novell.com, | |jbeulich@novell.com Status|NEW |NEEDINFO Info Provider| |estellnb@gmail.com QAContact|qa@suse.de |jdouglas@novell.com --- Comment #1 from James Fehlig <jfehlig@novell.com> 2008-12-01 10:47:35 MST --- Sounds like this should really be two bugs - one for dvd naming and one for the network-bridge issue. Could you open a different bug for the bridge issue? Include output of 'brctl show', any output from network-bridge script, and whether you are using network manager or ifup scripts in the report. You mentioned "desktop users" so I assume network manager is being used. NB there are known issues with network manager and xen networking scripts. This bug can be used for the dvd naming issue. For that one, can you provide boot messages from both default and xen kernels? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c2 --- Comment #2 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-02 11:29:32 MST --- The issue with the xen-bridge has most likely been a fallacy of mine (may have executed 'rcnetwork restart' by accident, which is not allowed prior to shutting the xen-bridge down). Concerning the name of /dev/dvd this annoys when it comes to use zypper. Perhaps zypper should be configured to use a mount point like /media/dvd by default in order to allow the user to circumvent this without modifying the repo. Nevertheless this will not save us from creating a proper device link as /dev/dvd pointing to /dev/sr0 or /dev/hdx respectively. Similar links should be created for all devices with different naming convention under xen.
zypper in open-iscsi Lendo os pacotes instalados...
O seguinte pacote NOVO será instalado: open-iscsi Tamanho total do download: 157,0 K. Após a operação, 505,0 K adicionais serão utilizados. Continuar? [SIM/não]: Sim Baixando pacote open-iscsi-2.0.869-8.1.x86_64 (1/1), 157,0 K (505,0 K descomprimido) Falha ao montar cd:///?devices=/dev/sr0 em .: Mounting media failed Cancelar, repetir ou ignorar? [C/r/i]: c Falha ao montar cd:///?devices=/dev/sr0 em .: Mounting media failed Cancelar, repetir ou ignorar? [C/r/i]: C Exceção não esperada. Falha ao montar cd:///?devices=/dev/sr0 em .: Mounting media failed Por favor registre um relatório de bug sobre isto. Veja em http://en.opensuse.org/Zypper#Troubleshooting para obter instruções. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c3 Elmar Stellnberger (AT/K) <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|estellnb@gmail.com | --- Comment #3 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 00:03:25 MST --- . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c4 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |estellnb@gmail.com --- Comment #4 from Jan Beulich <jbeulich@novell.com> 2008-12-03 02:28:10 MST --- You didn't provide the information asked for: You say hat you get different device names for your DVD drive depending on what kernel you boot. That I could only explain by different drivers being picked (which seems rather unlikely, but I can't see any alternative) for the controller the drive is connected to, and in order to verify this we need (as asked for above) the kernel boot messages for both the native and the Xen kernel to compare. Also supplying the output of "ll /dev/[sh][dr]*" under both kernels would be desirable. Note that creating a /dev/dvd node is certainly out of question - that sort of abstraction is what /media/dvd is for. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c5 --- Comment #5 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 03:09:45 MST --- Created an attachment (id=257632) --> (https://bugzilla.novell.com/attachment.cgi?id=257632) ll /dev/[sh][dr]*, kernel-xen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c6 --- Comment #6 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 03:14:39 MST --- Created an attachment (id=257636) --> (https://bugzilla.novell.com/attachment.cgi?id=257636) grep hda /var/log/messages |grep -vi alsa -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c7 --- Comment #7 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 05:11:28 MST --- Created an attachment (id=257670) --> (https://bugzilla.novell.com/attachment.cgi?id=257670) ll /dev/[sh][dr]* -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c8 --- Comment #8 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 05:12:31 MST --- Created an attachment (id=257671) --> (https://bugzilla.novell.com/attachment.cgi?id=257671) grep --before 10 --after 2 sr0 /var/log/messages -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c9 Elmar Stellnberger (AT/K) <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|estellnb@gmail.com | --- Comment #9 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 05:16:53 MST --- The earlier we can make the abstraction the better because this will save us from additional case destinctions later on. A udev rule for /dev/dvd is all we need, or are we going to put two mount points for /media/dvd into fstab? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c10 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |estellnb@gmail.com --- Comment #10 from Jan Beulich <jbeulich@novell.com> 2008-12-03 05:35:57 MST --- I'm sorry, it doesn't really help to provide information you weren't asked for. We really need the kernel boot messages (and those unfiltered, i.e. just the raw /var/log/boot.msg files). /var/log/messages may help, but then it should also be unfiltered (but ideally reduced to just the relevant session's portion). I don't understand what you try to say with #9 - the goal must be for the device to get the same name no matter what kernel flavor (it may change with kernel version, but that's not the topic here), which makes the discussion about having an extra udev rule pointless. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c11 --- Comment #11 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 07:32:42 MST --- Created an attachment (id=257719) --> (https://bugzilla.novell.com/attachment.cgi?id=257719) boot-default.msg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c12 --- Comment #12 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 09:31:40 MST --- Created an attachment (id=257770) --> (https://bugzilla.novell.com/attachment.cgi?id=257770) boot-xen.msg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c13 Elmar Stellnberger (AT/K) <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|estellnb@gmail.com | --- Comment #13 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-03 09:35:50 MST --- reasons to create a /dev/dvd symlink by a udev-rule * practical issue: it should be possible to create a mount point for any block device in /etc/fstab * design issue: early unification will save unnecessary case destinctions later on (at the level of zypper f.e.) * all necessary information is available at the level of udev -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jfehlig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c14 --- Comment #14 from James Fehlig <jfehlig@novell.com> 2008-12-03 11:28:05 MST --- (In reply to comment #2 from Elmar Stellnberger (AT/K))
The issue with the xen-bridge has most likely been a fallacy of mine (may have executed 'rcnetwork restart' by accident, which is not allowed prior to shutting the xen-bridge down).
Right, can't do that in openSUSE < 11.1 or SLE < 11. FYI network-bridge is no longer used so you will be able to do "rcnetwork start|stop|restart" in 11.1 and SLE11. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c15 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |estellnb@gmail.com --- Comment #15 from Jan Beulich <jbeulich@novell.com> 2008-12-04 03:11:59 MST --- As suspected, the drivers controlling the individual devices differ between native and Xen. To further narrow this we'll need - lspci -nn output - lsmod output - initrd each for native and Xen. Also, I assume the two initrd-s were created at the same time (and hence in the same environment). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c16 --- Comment #16 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-04 06:05:54 MST --- Created an attachment (id=258011) --> (https://bugzilla.novell.com/attachment.cgi?id=258011) xen-env -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c17 --- Comment #17 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-04 08:25:19 MST --- Created an attachment (id=258047) --> (https://bugzilla.novell.com/attachment.cgi?id=258047) default-env.tar -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c18 --- Comment #18 from Jan Beulich <jbeulich@novell.com> 2008-12-04 09:08:30 MST --- The attachment in #16 looks broken (initrd-xen is garbage). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c19 --- Comment #19 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-04 09:26:34 MST --- Created an attachment (id=258069) --> (https://bugzilla.novell.com/attachment.cgi?id=258069) initrd-xen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c20 --- Comment #20 from Jan Beulich <jbeulich@novell.com> 2008-12-04 09:28:31 MST ---
From looking at the order modules got loaded, I'd conclude that indeed the Xen initrd is incomplete - did you customize /etc/sysconfig/kernel in any way? What is INITRD_MODULES in that file set to?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c21 --- Comment #21 from Jan Beulich <jbeulich@novell.com> 2008-12-04 09:41:02 MST --- RESOLVED_INITRD_MODULES in the Xen initrd has only xennet and xenblk, which would indicate it was created for a DomU rather than for Dom0. As the two initrd-s definitely were not created at the same time, you'd need to clarify how the Xen one was in fact generated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c22 --- Comment #22 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-12-04 10:30:08 MST --- No, I have not customized /etc/sysconfig/kernel in any way. Xen was installed later on by YaST. kernel:INITRD_MODULES="processor thermal pata_jmicron ahci sata_sil24 ata_piix fan reiserfs edd" kernel:DOMU_INITRD_MODULES="xennet xenblk" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c23 --- Comment #23 from Jan Beulich <jbeulich@novell.com> 2008-12-05 01:40:49 MST --- I'd recommend you simply force a re-install of kernel-xen. If you do this from the command line (using rpm -if ...) you would at once get shown the list of modules included in the initrd. If any of ahci, pata_jmicron, or sata_sil24 aren't listed, just copy-and-paste the whole command output here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cgriffin@novell.com |jbeulich@novell.com Status|NEEDINFO |ASSIGNED Info Provider|estellnb@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |estellnb@gmail.com Platform|IA64 |x86-64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c24 Elmar Stellnberger (AT/K) <estellnb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|estellnb@gmail.com | --- Comment #24 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2009-02-03 12:50:26 MST --- Reinstalling kernel-xen via YaST has not helped, but interestingly adding all modules found in INITRD_MODULES to DOMU_INITRD_MODULES of /etc/sysconfig/kernel has resolved the issue. It seems as if xen uses the DOMU_INITRD_MODULES list for dom0 as well. INITRD_MODULES="processor thermal pata_jmicron ahci sata_sil24 ata_piix fan reiserfs edd" DOMU_INITRD_MODULES="xennet xenblk processor thermal pata_jmicron ahci sata_sil24 ata_piix fan reiserfs edd" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c25 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Xen |Basesystem AssignedTo|jbeulich@novell.com |hare@novell.com QAContact|jdouglas@novell.com |qa@suse.de --- Comment #25 from Jan Beulich <jbeulich@novell.com> 2009-02-04 02:49:46 MST --- DOMU_INITRD_MODULES is definitely not intended to be used standalone, but indeed the way /lib/mkinitrd/scripts/setup-start.sh sets RESOLVED_INITRD_MODULES seems wrong. I wonder how nobody else ran into that issue so far. It seems to be done better (but still not optimal) in SLE11 - there the construct says if is_xen_kernel $kernel_version; then RESOLVED_INITRD_MODULES="$modules $domu_modules" else RESOLVED_INITRD_MODULES="$modules" fi But in a DomU it could really just use $domu_modules, it's just that that case isn't being considered (perhaps because it depends on running mkinitrd inside the VM, whereas the current approach does not use this run-time characteristic - otoh, other run-time characteristics are being considered when constructing the module list, so that apparently is not the issue). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com