WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Problem with loopback device in xenU

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Problem with loopback device in xenU
From: "Jochen" <gerribaldi@xxxxxxxx>
Date: Wed, 10 Aug 2005 18:17:15 +0200
Delivery-date: Wed, 10 Aug 2005 16:14:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: gerribaldi@xxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWdxve55jBf9B1DR72jtOoZORSb/Q==
Hi!

I´m a newbie in xen, but get 2 guest machines to work ;). In generall
everything is working, and it´s a great thing to have different servers on
one hardware.
Unfortunally i have a problem in all my xen guest machines. The loopback
device don´t start automaticly on boot time. When i type ifconfig lo i get
the messages:

lo        Link encap:Local Loopback
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

With ifconfig add 127.0.0.1 the loopback device is starting to work.
Normally should it be started on boot timte, or? The linux is a Slackware
10.1, also in the guest machines. The network config in generall is working,
also the loopback device is compiled in the kernel (not as modul). Anybody
any idea about this?

Thanks 
Jochen 

The output of xend.log and xend-debug.log is here:

Xned.log:
[2005-08-10 18:03:59 xend] INFO (console:94) Created console id=12 domain=16
port=9616
[2005-08-10 18:03:59 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=16
uname=file:/xen/http_fs
[2005-08-10 18:03:59 xend] DEBUG (blkif:63) exception looking up device
number for sda5: [Errno 2] No such file or directory: '/dev/sda5'
[2005-08-10 18:03:59 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 16 0>
[2005-08-10 18:03:59 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=16
uname=file:/xen/http_swap_fs
[2005-08-10 18:03:59 xend] DEBUG (blkif:63) exception looking up device
number for sda6: [Errno 2] No such file or directory: '/dev/sda6'
[2005-08-10 18:03:59 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 16 0>
[2005-08-10 18:03:59 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=16
vif=0 mac=aa:00:00:38:93:2f
[2005-08-10 18:03:59 xend] INFO (XendRoot:112) EVENT> xend.console.create
[12, 16, 9616]
[2005-08-10 18:03:59 xend] INFO (XendRoot:112) EVENT> xend.domain.create
['http', '16']
[2005-08-10 18:03:59 xend] INFO (XendRoot:112) EVENT> xend.domain.unpause
['http', '16']
[2005-08-10 18:03:59 xend] DEBUG (blkif:203) Connecting blkif to event
channel <BlkifBackendInterface 16 0> ports=13:3




Xend-debug.log:
recv_fe_interface_connect {'tx_shmem_frame': 115361, 'rx_shmem_frame':
115360, 'handle': 0}
{}
VirqClient.virqReceived> 4
vif-bridge down vif=vif11.0 domain=http mac=aa:00:00:5f:1a:66 bridge=xen-br0
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c033a1c4
 Init. ramdisk: c033b000->c033b000
 Phys-Mach map: c033b000->c034b000
 Page tables:   c034b000->c034d000
 Start info:    c034d000->c034e000
 Boot stack:    c034e000->c034f000
 TOTAL:         c0000000->c0400000
 ENTRY ADDRESS: c0100000
/dev/loop: Is a directory
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
/dev/loop: Is a directory
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
vif-bridge up vif=vif12.0 domain=http mac=aa:00:00:40:c2:e1 bridge=xen-br0
recv_fe_driver_status> {'status': 1}

recv_fe_driver_status>

recv_fe_interface_connect {'tx_shmem_frame': 83545, 'rx_shmem_frame': 83544,
'handle': 0}
{}
{}
VirqClient.virqReceived> 4
vif-bridge down vif=vif12.0 domain=http mac=aa:00:00:40:c2:e1 bridge=xen-br0
VirqClient.virqReceived> 4
vif-bridge down vif=vif10.0 domain=kolab mac=aa:00:00:60:6a:b7
bridge=xen-br0
xend-debug.log lines 377-418/418 (END)


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>