[Bug 348987] New: kqemu module not loaded by default
https://bugzilla.novell.com/show_bug.cgi?id=348987 Summary: kqemu module not loaded by default Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: initialZero@gmail.com QAContact: qa@suse.de Found By: --- When one installs qemu amd kqemu. The kqemu module is not loaded by default. Can a group kqemu be created and the module loaded when kqemu is installed? Here are the warnings given by default. If modprobe kqemu is used the latter warning is not given. Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory -- 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=348987 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.provo.novell.com |uli@novell.com --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2008-01-02 13:40:19 MST --- These are two different bug reports. The RTC issue is because CONFIG_RTC=y is set. We couldn't enable modular RTCs in 10.3 due to serious last minute bug reports related to it. The problem is that there isn't any physical hardware that can be scanned for kqemu to load the module automatically. Loading a module such as kqemu just because the package is installed would be a bad policy. You could boot any number of times without needing the module, and it would just sit there wasting resources. Uli, it be beneficial for qemu to try to load kqemu. -- 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=348987 User uli@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c2 Ulrich Hecht <uli@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Ulrich Hecht <uli@novell.com> 2008-01-14 06:29:15 MST --- I guess we will need an udev rule 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=348987 User uli@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c3 Ulrich Hecht <uli@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kasievers@novell.com --- Comment #3 from Ulrich Hecht <uli@novell.com> 2008-01-21 03:41:19 MST --- Kay, what is the correct way to autoload the kqemu module? There are no triggers, except qemu trying to access /dev/kqemu. -- 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=348987 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c4 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com Status|NEEDINFO |ASSIGNED Info Provider|kasievers@novell.com | --- Comment #4 from Kay Sievers <kasievers@novell.com> 2008-01-21 23:22:25 MST --- You could drop the kqemu device node in /lib/udev/devices/ with the rpm, otherwise there is no way to trigger autoloading. -- 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=348987 Marc Benstein <initialZero@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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=348987 User initialZero@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c5 Marc Benstein <initialZero@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmeeks@novell.com --- Comment #5 from Marc Benstein <initialZero@gmail.com> 2008-09-23 11:32:16 MDT --- *** Bug 391287 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=391287 -- 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=348987 User initialZero@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c6 Marc Benstein <initialZero@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Priority|P3 - Medium |P1 - Urgent --- Comment #6 from Marc Benstein <initialZero@gmail.com> 2008-09-23 11:34:14 MDT --- This is still happening in 11.0 -- 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=348987 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=348987#c7 --- Comment #7 from Jeff Mahoney <jeffm@novell.com> 2008-09-24 09:35:23 MDT --- The fix suggested in comment #4 won't work since the module dynamically allocates its minor number. The device node can't be created before the module is loaded, since the device node isn't yet known. -- 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=348987 Ihno Krumreich <ihno@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P3 - Medium CC| |ihno@novell.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.
participants (1)
-
bugzilla_noreply＠novell.com