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-bugs

[Xen-bugs] [Bug 807] New: Error: Device 0 not connected

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 807] New: Error: Device 0 not connected
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 04 Nov 2006 23:34:36 -0800
Delivery-date: Sat, 04 Nov 2006 23:35:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=807

           Summary: Error: Device 0 not connected
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: hskupin@xxxxxxxxx


I'm running Xen 3.0-unstable-1-amd64 under Debian Etch for a week now. I'm
using network routing with an own vif-bridge to get a private network. After a
couple of minutes or hours all domU cannot be reached from outside. When
running 'xm list' afterwards I get the message: "Error: Device 0 not
connected". Actually I cannot figure out how to reactivate dom0 and the network
connections to have a running system without rebooting the whole machine.

Opening the log file 'xend-debug.log' shows following entry:

Traceback (most recent call last):
  File "SocketServer.py", line 463, in process_request_thread
    self.finish_request(request, client_address)
  File "SocketServer.py", line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "SocketServer.py", line 521, in __init__
    self.handle()
  File "BaseHTTPServer.py", line 316, in handle
    self.handle_one_request()
  File "BaseHTTPServer.py", line 310, in handle_one_request
    method()
  File "/usr/lib/xen-3.0-unstable-1/lib/python/xen/util/xmlrpclib2.py", line
66, in do_POST
    self.send_response(200)
  File "BaseHTTPServer.py", line 367, in send_response
    self.wfile.write("%s %d %s\r\n" %
  File "socket.py", line 248, in write
    self.flush()
  File "socket.py", line 235, in flush
    self._sock.sendall(buffer)
error: (32, 'Broken pipe')


dmesg dom0:

Bridge firewalling registered
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
device vif2.0 entered promiscuous mode
audit(1162689220.872:2): dev=vif2.0 prom=256 old_prom=0 auid=4294967295
xenintbr: port 1(vif2.0) entering learning state
eth0: no IPv6 routers present
xenintbr: no IPv6 routers present
device vif3.0 entered promiscuous mode
audit(1162689227.948:3): dev=vif3.0 prom=256 old_prom=0 auid=4294967295
xenintbr: port 2(vif3.0) entering learning state
xenintbr: topology change detected, propagating
xenintbr: port 1(vif2.0) entering forwarding state
xenintbr: topology change detected, propagating
xenintbr: port 2(vif3.0) entering forwarding state
device vif2.0 left promiscuous mode
audit(1162704280.839:4): dev=vif2.0 prom=0 old_prom=256 auid=4294967295
xenintbr: port 1(vif2.0) entering disabled state

xm dmesg:

Xen version 3.0-unstable-1 (Debian 3.0-unstable+hg11561-1) (waldi@xxxxxxxxxx)
(gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) Fri Sep 22 18:04:24
UTC 2006
 Latest ChangeSet: Thu Sep 21 17:56:14 2006 +0100

(XEN) Command line: /xen-3.0-unstable-1-amd64.gz
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009f000 (usable)
(XEN)  000000000009f000 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000003fef0000 (usable)
(XEN)  000000003fef0000 - 000000003fef3000 (ACPI NVS)
(XEN)  000000003fef3000 - 000000003ff00000 (ACPI data)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 1022MB (1047100kB)
(XEN) Xen heap: 14MB (14468kB)
(XEN) found SMP MP-table at 000f4f10
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 VIAK8T                                ) @
0x00000000000f8d70
(XEN) ACPI: RSDT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x000000003fef3040
(XEN) ACPI: FADT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x000000003fef30c0
(XEN) ACPI: MADT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x000000003fef8000
(XEN) ACPI: DSDT (v001 VIAK8T AWRDACPI 0x00001000 MSFT 0x0100000e) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:7 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2199.826 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 1024K (64 bytes/line)
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: AMD Athlon(tm) 64 Processor 3700+ stepping 02
(XEN) Total of 1 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 1 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000000f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (230590 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff80566e88
(XEN)  Init. ramdisk: ffffffff80567000->ffffffff81575800
(XEN)  Phys-Mach map: ffffffff81576000->ffffffff817485f0
(XEN)  Start info:    ffffffff81749000->ffffffff8174949c
(XEN)  Page tables:   ffffffff8174a000->ffffffff81759000
(XEN)  Boot stack:    ffffffff81759000->ffffffff8175a000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81800000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Initrd len 0x100e800, start at 0xffffffff80567000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) Xen trace buffers: disabled
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
Xen).

xm info:

host                   : hskupin.info
release                : 2.6.17-2-xen-amd64
version                : #1 SMP Wed Sep 13 18:35:45 CEST 2006
machine                : x86_64
nr_cpus                : 1
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2199
hw_caps                :
078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:00000001
total_memory           : 1022
free_memory            : 0
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable-1
xen_caps               : xen-3.0-x86_64
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Thu Sep 21 17:56:14 2006 +0100
cc_compiler            : gcc version 4.1.2 20060901 (prerelease) (Debian
4.1.1-13)
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Fri Sep 22 18:04:24 UTC 2006
xend_config_format     : 2

dmesg dom1:

device vif2.0 entered promiscuous mode
audit(1162689220.872:2): dev=vif2.0 prom=256 old_prom=0 auid=4294967295
xenintbr: port 1(vif2.0) entering learning state
eth0: no IPv6 routers present
xenintbr: no IPv6 routers present
device vif3.0 entered promiscuous mode
audit(1162689227.948:3): dev=vif3.0 prom=256 old_prom=0 auid=4294967295
xenintbr: port 2(vif3.0) entering learning state
xenintbr: topology change detected, propagating
xenintbr: port 1(vif2.0) entering forwarding state
xenintbr: topology change detected, propagating
xenintbr: port 2(vif3.0) entering forwarding state
device vif2.0 left promiscuous mode
audit(1162704280.839:4): dev=vif2.0 prom=0 old_prom=256 auid=4294967295
xenintbr: port 1(vif2.0) entering disabled state


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

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