qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] KQEMU error, unable to get major 254
@ 2005-02-11  1:19 Darryl Dixon
  2005-02-11  1:41 ` [Qemu-devel] [PATCH] " Darryl Dixon
  2005-02-11  1:47 ` [Qemu-devel] " Hetz Ben Hamo
  0 siblings, 2 replies; 3+ messages in thread
From: Darryl Dixon @ 2005-02-11  1:19 UTC (permalink / raw)
  To: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

Hi Fabrice,

    I have managed to download the latest cvs and tried it out on Fedora
Core 3 (kernel 2.6.10).  It seems that for some reason the kqemu module
is unable to be assigned major device number 254.  Below are the errors:
[root@localhost ~]# modprobe kqemu
FATAL: Error inserting kqemu
(/lib/modules/2.6.10-1.760_FC3/misc/kqemu.ko): Device or resource busy
[root@localhost ~]# tail /var/log/messages
Feb 11 14:14:07 localhost kernel: QEMU Accelerator Module version 1.0.0,
Copyright (c) 2005 Fabrice Bellard
Feb 11 14:14:07 localhost kernel: This is a proprietary product. Read
the LICENSE file for more information
Feb 11 14:14:07 localhost kernel: Redistribution of this module is
prohibited without authorization
Feb 11 14:14:07 localhost kernel: kqemu: could not get major 254


Regards,
-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 1390 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Qemu-devel] [PATCH]   Re: KQEMU error, unable to get major 254
  2005-02-11  1:19 [Qemu-devel] KQEMU error, unable to get major 254 Darryl Dixon
@ 2005-02-11  1:41 ` Darryl Dixon
  2005-02-11  1:47 ` [Qemu-devel] " Hetz Ben Hamo
  1 sibling, 0 replies; 3+ messages in thread
From: Darryl Dixon @ 2005-02-11  1:41 UTC (permalink / raw)
  To: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

I have worked around this temporarily with the following patch:

diff -ru qemu/kqemu/install.sh qemu_major250/kqemu/install.sh
--- qemu/kqemu/install.sh       2005-02-11 11:10:28.000000000 +1300
+++ qemu_major250/kqemu/install.sh      2005-02-11 14:24:04.000000000
+1300
@@ -20,5 +20,5 @@
 # Create the kqemu device. No special priviledge is needed to use
kqemu.
 device="/dev/kqemu"
 rm -f $device
-mknod $device c 254 0
+mknod $device c 250 0
 chmod 666 $device
Only in qemu_major250/kqemu: .kmod.o.cmd
diff -ru qemu/kqemu/kqemu.h qemu_major250/kqemu/kqemu.h
--- qemu/kqemu/kqemu.h  2005-02-11 11:10:28.000000000 +1300
+++ qemu_major250/kqemu/kqemu.h 2005-02-11 14:23:46.000000000 +1300
@@ -1,7 +1,7 @@
 #ifndef KQEMU_H
 #define KQEMU_H

-#define KQEMU_MAJOR 254
+#define KQEMU_MAJOR 250

 #define KQEMU_VERSION 0x010000



Cheers,
D




On Fri, 2005-02-11 at 14:19 +1300, Darryl Dixon wrote:

> Hi Fabrice,
> 
>     I have managed to download the latest cvs and tried it out on
> Fedora Core 3 (kernel 2.6.10).  It seems that for some reason the
> kqemu module is unable to be assigned major device number 254.  Below
> are the errors:
> [root@localhost ~]# modprobe kqemu
> FATAL: Error inserting kqemu
> (/lib/modules/2.6.10-1.760_FC3/misc/kqemu.ko): Device or resource busy
> [root@localhost ~]# tail /var/log/messages
> Feb 11 14:14:07 localhost kernel: QEMU Accelerator Module version
> 1.0.0, Copyright (c) 2005 Fabrice Bellard
> Feb 11 14:14:07 localhost kernel: This is a proprietary product. Read
> the LICENSE file for more information
> Feb 11 14:14:07 localhost kernel: Redistribution of this module is
> prohibited without authorization
> Feb 11 14:14:07 localhost kernel: kqemu: could not get major 254
> 
> 
> Regards,
> -- 
> Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 3268 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] KQEMU error, unable to get major 254
  2005-02-11  1:19 [Qemu-devel] KQEMU error, unable to get major 254 Darryl Dixon
  2005-02-11  1:41 ` [Qemu-devel] [PATCH] " Darryl Dixon
@ 2005-02-11  1:47 ` Hetz Ben Hamo
  1 sibling, 0 replies; 3+ messages in thread
From: Hetz Ben Hamo @ 2005-02-11  1:47 UTC (permalink / raw)
  To: esrever_otua, qemu-devel

Earlier in IRC someone mentioned that changing the code to work with
major 253 solved this issue...

Can someone tell where do you "officially" can request a major number
these days? (if it's possible)..

Thanks,
Hetz

On Fri, 11 Feb 2005 14:19:59 +1300, Darryl Dixon
<esrever_otua@pythonhacker.is-a-geek.net> wrote:
>  Hi Fabrice,
>  
>      I have managed to download the latest cvs and tried it out on Fedora
> Core 3 (kernel 2.6.10).  It seems that for some reason the kqemu module is
> unable to be assigned major device number 254.  Below are the errors:
>  [root@localhost ~]# modprobe kqemu
>  FATAL: Error inserting kqemu (/lib/modules/2.6.10-1.760_FC3/misc/kqemu.ko):
> Device or resource busy
>  [root@localhost ~]# tail /var/log/messages
>  Feb 11 14:14:07 localhost kernel: QEMU Accelerator Module version 1.0.0,
> Copyright (c) 2005 Fabrice Bellard
>  Feb 11 14:14:07 localhost kernel: This is a proprietary product. Read the
> LICENSE file for more information
>  Feb 11 14:14:07 localhost kernel: Redistribution of this module is
> prohibited without authorization
>  Feb 11 14:14:07 localhost kernel: kqemu: could not get major 254
>  
>  
>  Regards,
>  
>  -- 
>  Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 
> 
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-02-11  2:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-11  1:19 [Qemu-devel] KQEMU error, unable to get major 254 Darryl Dixon
2005-02-11  1:41 ` [Qemu-devel] [PATCH] " Darryl Dixon
2005-02-11  1:47 ` [Qemu-devel] " Hetz Ben Hamo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).