Re: kqemu /dev node
On Tuesday 30 January 2007, debian-user-digest-request@lists.debian.org wrote:
> David Baron wrote:
> > This is being created, apparently by a /etc/qmeu-ifup.... (there are
> > several) with major 250, minor 0.
> >
> > kqemu.ko gets placed in misc. Implication is major==10? There is no entry
> > in /proc/devices (and this cannot be simply edited).
> >
> > kqemu has a minor value of 63 in /proc/misc.
> >
> > So what really should be going on here?
>
> Hi, David,
>
> I have Qemu installed on my Debian system. What I have looks like this:
>
> $ l /dev/kq*
> crw-rw-rw- 1 root root 10, 63 2007-01-29 15:55 /dev/kqemu
> $ ls /etc/*qemu*
> ls: /etc/*qemu*: No such file or directory
> $ find /lib/modules -name '*qemu*'
> /lib/modules/2.6.17-2-686/misc/kqemu.ko
> /lib/modules/2.6.18-3-686/misc/kqemu.ko
> $ lsmod | grep qemu
> kqemu 107620 0
> $ cat /etc/modules
> # /etc/modules: kernel modules to load at boot time.
> #
> # This file contains the names of kernel modules that should be loaded
> # at boot time, one per line. Lines beginning with "#" are ignored.
>
> loop
> sbp2
> kqemu major=0
>
> ===
>
> This last item is what makes /dev/kqemu with major number 10 (I believe
> that's because major 10 is available for use and is picked dynamically
> during the boot process, so it could be something different if some
> other driver loads first).
>
> The /etc/qemu-ifup file is part of the Qemu network setup when using the
> tun/tap devices (which I don't use, as yet) and so have nothing to do
> with the device node for kqemu itself.
>
> Hope this is helpful.
This makes more sense. However, I am running nothing to make that node 250,0
nor have I used kqemu with TAP. The mknod with 250,0 is in the if-up files I
mentioned.
Simply modpobe kqemu major=0 does not create the node (I am not using udev so
maybe that is why. I manually created it c 10 63 and the modprobe leaves that
alone.
Startup scripts usually remove their node and mknod it again so I will see
what happens on next bootup.
Reply to: