While using mkinitrd on debian sarge, it gives the following error: mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen /usr/sbin/mkinitrd: illegal option -- v $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] Options: -d confdir Specify an alternative configuration directory. -k Keep temporary directory used to make the image. -m command Set the command to make an initrd image. -o outfile Write to outfile. -r root Override ROOT setting in mkinitrd.conf. See mkinitrd(8) for further details. It looks like the syntax for mkinitrd is different from the ones used in RH based distros. I have been trying different combinations however haven''t had any luck generating the initrd image. Can anyone please tell me how to use this under debian to generate the image ?? -- regards, Anand Gupta
On Tuesday 03 October 2006 23:12, Anand Gupta wrote:> While using mkinitrd on debian sarge, it gives the following error: > > mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod > initrd-2.6.16-xen.img 2.6.16-xen > /usr/sbin/mkinitrd: illegal option -- v > > $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ > > Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] > > Options: > -d confdir Specify an alternative configuration directory. > -k Keep temporary directory used to make the image. > -m command Set the command to make an initrd image. > -o outfile Write to outfile. > -r root Override ROOT setting in mkinitrd.conf. > > See mkinitrd(8) for further details. > > > It looks like the syntax for mkinitrd is different from the ones used in RH > based distros. I have been trying different combinations however haven''t > had any luck generating the initrd image. Can anyone please tell me how to > use this under debian to generate the image ??Hi, In debian you can just use mkinitrd -o=/boot/initrd.img-2.6.16-xen initrd.img-2.6.16-xen the command tries to guess the necessary modules. If you need to specify any module just edit the file /etc/mkinitrd/modules and add any necessary modules. hope it help regards hugo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 03 October 2006 23:52, Hugo Brites wrote:> On Tuesday 03 October 2006 23:12, Anand Gupta wrote: > > While using mkinitrd on debian sarge, it gives the following error: > > > > mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod > > initrd-2.6.16-xen.img 2.6.16-xen > > /usr/sbin/mkinitrd: illegal option -- v > > > > $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ > > > > Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] > > > > Options: > > -d confdir Specify an alternative configuration directory. > > -k Keep temporary directory used to make the image. > > -m command Set the command to make an initrd image. > > -o outfile Write to outfile. > > -r root Override ROOT setting in mkinitrd.conf. > > > > See mkinitrd(8) for further details. > > > > > > It looks like the syntax for mkinitrd is different from the ones used in > > RH based distros. I have been trying different combinations however > > haven''t had any luck generating the initrd image. Can anyone please tell > > me how to use this under debian to generate the image ?? > > Hi, > > In debian you can just use > mkinitrd -o=/boot/initrd.img-2.6.16-xen initrd.img-2.6.16-xen > > the command tries to guess the necessary modules. If you need to specify > any module just edit the file > /etc/mkinitrd/modules > and add any necessary modules. > > hope it help > regards > hugo >Sorry it''s mkinitrd -o /boot/initrd.img-2.6.16-xen initrd.img-2.6.16-xen the = was wrong regards hugo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John Paul Walters
2006-Oct-03 23:13 UTC
[Xen-users] Error: Device 0 (vif) could not be connected
I''m new to Xen and am trying to get a VM set up. I''ve built
Xen 3.0.2-2
from source on a dual core AMD Opteron machine. I''m able to boot into
the new kernel without any trouble.
Everything seems fine until I issue "xm create ttylinux". At this
point, I''m told:
"Error: Device 0 (vif) could not be connected. Backend device not
found." is returned.
Looking at ifconfig''s output, this is no surprise:
eth1 Link encap:Ethernet HWaddr 00:E0:81:59:1C:A7
inet addr:10.1.1.101 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::2e0:81ff:fe59:1ca7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5942 errors:0 dropped:0 overruns:0 frame:0
TX packets:3562 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:915225 (893.7 KiB) TX bytes:467674 (456.7 KiB)
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3128 errors:0 dropped:0 overruns:0 frame:0
TX packets:3128 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3969380 (3.7 MiB) TX bytes:3969380 (3.7 MiB)
So my question is, how can I get this interface created? Should this
have been done automatically or is there some script that I have to run?
thanks,
JP
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users