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] NetBSD DomU don't boot anymore

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] NetBSD DomU don't boot anymore
From: Niels Dettenbach <nd@xxxxxxxxxxxx>
Date: Mon, 22 Feb 2010 07:32:25 +0100
Delivery-date: Sun, 21 Feb 2010 22:33:54 -0800
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Syndicat IT&Internet
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.0 (Linux/2.6.32-gentoo-r1; KDE/4.4.62; i686; ; )
Dear all,


after upgrading from Xen 3.2.1 32bit (on Xen QC E5440) to 3.4.2 64bit - 
2.6.31-xen-r10 ebuild sources (Dom0 is a Gentoo Linux) i have problems to get 
my NetBSD DomU (still 32bit PAE) get running.

The "crazy" thing is that the DomU got running over several days (after 
bringing up some things by hand after first boot of the new system like the 
loop module width max_loop=64 and a rebuild of udev-151-r1).

After a reboot i've found that all my linux based DomUs are starting well 
without problems (32bit PAE too) but my netbsd hangs during boot because some 
devices are going "away" - netbsd stops there and must be shutdown.

I tried several NetBSD kernels (32bit PAE) with the same results.

I have here two boot console logs - one from the working version and one from 
the non working. It seems the xennet0 (vif), xbd0 (virtual disks) are detaching:

        xennet0: detached
        xbd0: detached
        xbd1: detached
        xbd2: detached
[netbsd domu stops / hangs here, there is no further CPU time counted]

 and i can't find any "event channel" outputs comparing to the working version 
- i.e.:
        timecounter: Timecounters tick every 10.000 msec
        ...
        debug virtual interrupt using event channel 3
        ...
        xbd0: using event channel 5
        ...


working version:
============
- 32bit nonPAE DomU on
- 64bit 3.4.2 Xen Dom0 
- 2.6.18 ebuild kernel

--- snip ---
NetBSD 4.99.73 (XEN3_DOMU_NIELS) #1: Sat Oct 25 11:23:38 CEST 2008
        root@xen:/root/netbsd/obj/sys/arch/i386/compile/XEN3_DOMU_NIELS
total memory = 2548 MB
avail memory = 2496 MB
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 3.2
vcpu0 at hypervisor0: Intel 686-class, 2833MHz, id 0x1067a
debug virtual interrupt using event channel 3
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
xencons0: console major 143, unit 0
xencons0: using event channel 2
npx0 at hypervisor0: using exception 16
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
Xen clock: using event channel 4
timecounter: Timecounter "xen_system_time" frequency 1000000000 Hz quality 10000
xenbus0: using event channel 1
xbd0 at xenbus0 id 2048: Xen Virtual Block Device Interface
xbd0: using event channel 5
xbd1 at xenbus0 id 2064: Xen Virtual Block Device Interface
xbd1: using event channel 6
xbd2 at xenbus0 id 2080: Xen Virtual Block Device Interface
xbd2: using event channel 7
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address 00:0c:6e:40:59:a4
xennet0: using event channel 8
unknown type console at xenbus0 id 0 not configured
xbd0: 19808 MB, 512 bytes/sect x 40566784 sectors
xbd1: 32000 MB, 512 bytes/sect x 65536000 sectors
xbd2: 2000 MB, 512 bytes/sect x 4096000 sectors
raidattach: Asked for 8 units
Kernelized RAIDframe activated
Searching for RAID components...
unknown type console at xenbus0 id 0 not configured
unknown type console at xenbus0 id 0 not configured
unknown type console at xenbus0 id 0 not configured
unknown type console at xenbus0 id 0 not configured
boot device: xbd0
root on xbd0a dumps on xbd0b
dump_misc_init: max_paddr = 0x9f500000
mountroot: trying lfs...
mountroot: trying ffs...
root file system type: ffs
init: copying out path `/sbin/init' 11
--- snap ---



non working version
===============
 - 32bit PAE DomU on 
 - 32bit 3.2.1 XEN Dom0
 - 2.6.31-xen-r10 ebuild kernel

--- snip ---
NetBSD 5.0.2 (XEN3PAE_DOMU) #0: Sat Feb  6 17:52:02 UTC 2010
        
builds@xxxxxxxxxxxxx:/home/builds/ab/netbsd-5-0-2-RELEASE/i386/201002061851Z-obj/home/builds/ab/netbsd-5-0-2-RELEASE/src/sys/arch/i386/compile/XEN3PAE_DOMU
total memory = 3500 MB
avail memory = 3427 MB
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 3.4
vcpu0 at hypervisor0: Intel 686-class, 2833MHz, id 0x1067a
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
xencons0: using event channel 2
npx0 at hypervisor0: using exception 16
xbd0 at xenbus0 id 2048: Xen Virtual Block Device Interface
xbd1 at xenbus0 id 2064: Xen Virtual Block Device Interface
xbd2 at xenbus0 id 2080: Xen Virtual Block Device Interface
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address 00:0c:6e:40:59:a4
xennet0: detached
xbd0: detached
xbd1: detached
xbd2: detached
--- snap ---

This is the configuration of the DomU. Because the 64bit Dom0 just accepts 
32bit PAE kernels i have to "switch" the kernel within old and new dom0.

--- snip ---
kernel = "/xen/netbsd/netbsd-XEN3_DOMU_NIELS"
# ^ works on 32bit Dom0

#kernel = "/xen/netbsd/netbsd502-XEN3PAE_DOMU"
# ^worked on 64bit Dom0
#kernel = "/xen/netbsd/netbsd-XEN3_DOMU_NIELS"
#kernel = "/xen/netbsd/netbsd-XEN3PAE_DOMU_NIELS"
#kernel = "/xen/netbsd/netbsd-XEN3_DOMU"

memory = 2800
memory = 2548
#memory = 2200
#memory = 2048
#maxmem = 3800
#memory = 3400

name = "netbsd"
disk = [ 
        'file:/xen/netbsd/disk1neu2.disk,sda,w', 
        'file:/xen/netbsd/var2.disk,sdb,w', 
        'file:/swaps/netbsd1.swap22,sdc,w', ]
boot='cda'

# worked without before:
root = "xbd0

# I needed to add this because the installer couldn't find a network card 
without it
vif = [ 'mac=00:0C:6E:40:59:A4, bridge=pwan1' ]

#pae=1
keymap='de'
vcpus=1
# List of which CPUS this domain is allowed to use, default Xen picks
cpus = "1-7" # run on cpus 1-7 (of 0-7)

on_reboot = 'restart'
on_crash = 'restart'
--- snap ---

hint:
Same happens when i try to use "tap:io:" instead of "file:.".

I can't find any really useful within the logs - but here is some output:

--- snip ---
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:92) 
XendDomainInfo.create(['vm', ['name', 'netbsd'], ['memory', 2548], 
['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], 
['on_xend_start', 'ignore'], ['on_xend_stop', 
'ignore'], ['cpus', '0-7'], ['image', ['linux', ['kernel', 
'/xen/netbsd/netbsd-XEN3PAE_DOMU_NIELS'], ['videoram', 4]]], ['s3_integrity', 
1], ['device', ['vbd', ['uname', 'file:/xen/netbsd/disk1neu2.disk'], ['dev', 
'sda'], ['mode', 'w']]], 
['device', ['vbd', ['uname', 'file:/xen/netbsd/var2.disk'], ['dev', 'sdb'], 
['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/swaps/netbsd1.swap22'], 
['dev', 'sdc'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'pwan1'], 
['mac', 
'00:0C:6E:40:59:A4']]]])
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:2304) 
XendDomainInfo.constructDomain
[2010-02-22 05:56:40 4813] DEBUG (balloon:166) Balloon: 3601256 KiB free; need 
4096; done.
[2010-02-22 05:56:40 4813] DEBUG (XendDomain:453) Adding Domain: 4
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:2505) 
XendDomainInfo.initDomain: 4 256
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:2529) 
_initDomain:shadow_memory=0x0, memory_static_max=0x9f400000, 
memory_static_min=0x0.
[2010-02-22 05:56:40 4813] DEBUG (balloon:166) Balloon: 3601140 KiB free; need 
2619392; done.
[2010-02-22 05:56:40 4813] INFO (image:173) buildDomain os=linux dom=4 vcpus=1
[2010-02-22 05:56:40 4813] DEBUG (image:663) domid          = 4
[2010-02-22 05:56:40 4813] DEBUG (image:664) memsize        = 2548
[2010-02-22 05:56:40 4813] DEBUG (image:665) image          = 
/xen/netbsd/netbsd-XEN3PAE_DOMU_NIELS
[2010-02-22 05:56:40 4813] DEBUG (image:666) store_evtchn   = 1
[2010-02-22 05:56:40 4813] DEBUG (image:667) console_evtchn = 2
[2010-02-22 05:56:40 4813] DEBUG (image:668) cmdline        = 
[2010-02-22 05:56:40 4813] DEBUG (image:669) ramdisk        = 
[2010-02-22 05:56:40 4813] DEBUG (image:670) vcpus          = 1
[2010-02-22 05:56:40 4813] DEBUG (image:671) features       = 
[2010-02-22 05:56:40 4813] DEBUG (image:672) flags          = 0
[2010-02-22 05:56:40 4813] INFO (XendDomainInfo:2168) createDevice: vbd : 
{'uuid': '5ac18aa1-6f3d-bae2-b5dc-82f997141139', 'bootable': 1, 'driver': 
'paravirtualised', 'dev': 'sda', 'uname': 'file:/xen/netbsd/disk1neu2.disk', 
'mode': 'w'}
[2010-02-22 05:56:40 4813] DEBUG (DevController:95) DevController: writing 
{'virtual-device': '2048', 'device-type': 'disk', 'protocol': 'x86_32-abi', 
'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/4/2048'} 
to /local/domain/4/device/vbd/2048.
[2010-02-22 05:56:40 4813] DEBUG (DevController:97) DevController: writing 
{'domain': 'netbsd', 'frontend': '/local/domain/4/device/vbd/2048', 'uuid': 
'5ac18aa1-6f3d-bae2-b5dc-82f997141139', 'bootable': '1', 'dev': 'sda', 
'state': '1', 'params': '/xen/netbsd/disk1neu2.disk', 'mode': 'w', 'online': 
'1', 'frontend-id': '4', 'type': 'file'} to /local/domain/0/backend/vbd/4/2048.
[2010-02-22 05:56:40 4813] INFO (XendDomainInfo:2168) createDevice: vbd : 
{'uuid': '6df9160c-58e4-952f-7fff-df240fddf12e', 'bootable': 0, 'driver': 
'paravirtualised', 'dev': 'sdb', 'uname': 'file:/xen/netbsd/var2.disk', 'mode': 
'w'}
[2010-02-22 05:56:40 4813] DEBUG (DevController:95) DevController: writing 
{'virtual-device': '2064', 'device-type': 'disk', 'protocol': 'x86_32-abi', 
'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/4/2064'} 
to /local/domain/4/device/vbd/2064.
[2010-02-22 05:56:40 4813] DEBUG (DevController:97) DevController: writing 
{'domain': 'netbsd', 'frontend': '/local/domain/4/device/vbd/2064', 'uuid': 
'6df9160c-58e4-952f-7fff-df240fddf12e', 'bootable': '0', 'dev': 'sdb', 'state': 
'1', 'params': '/xen/netbsd/var2.disk', 'mode': 'w', 'online': '1', 
'frontend-id': '4', 'type': 'file'} to /local/domain/0/backend/vbd/4/2064.
[2010-02-22 05:56:40 4813] INFO (XendDomainInfo:2168) createDevice: vbd : 
{'uuid': '008aaa85-a6b9-9a8c-ccbf-dffad1876e84', 'bootable': 0, 'driver': 
'paravirtualised', 'dev': 'sdc', 'uname': 'file:/swaps/netbsd1.swap22', 
'mode': 'w'}
[2010-02-22 05:56:40 4813] DEBUG (DevController:95) DevController: writing 
{'virtual-device': '2080', 'device-type': 'disk', 'protocol': 'x86_32-abi', 
'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/4/2080'} 
to /local/domain/4/device/vbd/2080.
[2010-02-22 05:56:40 4813] DEBUG (DevController:97) DevController: writing 
{'domain': 'netbsd', 'frontend': '/local/domain/4/device/vbd/2080', 'uuid': 
'008aaa85-a6b9-9a8c-ccbf-dffad1876e84', 'bootable': '0', 'dev': 'sdc', 
'state': '1', 'params': '/swaps/netbsd1.swap22', 'mode': 'w', 'online': '1', 
'frontend-id': '4', 'type': 'file'} to /local/domain/0/backend/vbd/4/2080.
[2010-02-22 05:56:40 4813] INFO (XendDomainInfo:2168) createDevice: vif : 
{'bridge': 'pwan1', 'mac': '00:0C:6E:40:59:A4', 'uuid': 
'8d1686ab-9a3d-074f-73ae-6c90ed3cc7f6'}
[2010-02-22 05:56:40 4813] DEBUG (DevController:95) DevController: writing 
{'mac': '00:0C:6E:40:59:A4', 'handle': '0', 'protocol': 'x86_32-abi', 
'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/4/0'} 
to 
/local/domain/4/device/vif/0.
[2010-02-22 05:56:40 4813] DEBUG (DevController:97) DevController: writing 
{'bridge': 'pwan1', 'domain': 'netbsd', 'handle': '0', 'uuid': 
'8d1686ab-9a3d-074f-73ae-6c90ed3cc7f6', 'script': 
'/etc/xen/scripts/vif-bridge', 'mac': 
'00:0C:6E:40:59:A4', 'frontend-id': '4', 'state': '1', 'online': '1', 
'frontend': '/local/domain/4/device/vif/0'} to /local/domain/0/backend/vif/4/0.
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:3060) Storing VM details: 
{'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': 
'55e1c792-94e2-4a83-712b-501b4ae5f10b', 'on_reboot': 'restart', 'start_time': 
'1266814600.82', 'on_poweroff': 'destroy', 'bootloader_args': '', 
'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 
'vcpus': '1', 'vcpu_avail': '1', 'bootloader': '', 'image': '(linux (kernel 
/xen/netbsd/netbsd-
XEN3PAE_DOMU_NIELS) (videoram 4) (keymap de-de) (notes))', 'name': 'netbsd'}
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:1622) Storing domain details: 
{'console/ring-ref': '2220265', 'console/port': '2', 'name': 'netbsd', 
'console/limit': '1048576', 'vm': 
'/vm/55e1c792-94e2-4a83-712b-501b4ae5f10b', 'domid': '4', 'store/port': '1', 
'cpu/0/availability': 'online', 'memory/target': '2609152', 
'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': 
'2220266', 
'console/type': 'xenconsoled'}
[2010-02-22 05:56:40 4813] DEBUG (DevController:95) DevController: writing 
{'protocol': 'x86_32-abi', 'state': '1', 'backend-id': '0', 'backend': 
'/local/domain/0/backend/console/4/0'} to /local/domain/4/device/console/0.
[2010-02-22 05:56:40 4813] DEBUG (DevController:97) DevController: writing 
{'domain': 'netbsd', 'frontend': '/local/domain/4/device/console/0', 'uuid': 
'165264f7-c04f-3889-9fc8-14fdbcc8e24c', 'frontend-id': '4', 'state': '1', 
'location': '2', 'online': '1', 'protocol': 'vt100'} to 
/local/domain/0/backend/console/4/0.
[2010-02-22 05:56:40 4813] DEBUG (XendDomainInfo:1709) 
XendDomainInfo.handleShutdownWatch
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices vif.
[2010-02-22 05:56:40 4813] DEBUG (DevController:144) Waiting for 0.
[2010-02-22 05:56:40 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vif/4/0/hotplug-status.
[2010-02-22 05:56:40 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vif/4/0/hotplug-status.
[2010-02-22 05:56:40 4813] DEBUG (DevController:643) hotplugStatusCallback 1.
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices vkbd.
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices 
ioports.
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices tap.
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices 
console.
[2010-02-22 05:56:40 4813] DEBUG (DevController:144) Waiting for 0.
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices vscsi.
[2010-02-22 05:56:40 4813] DEBUG (DevController:139) Waiting for devices vbd.
[2010-02-22 05:56:40 4813] DEBUG (DevController:144) Waiting for 2048.
[2010-02-22 05:56:40 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vbd/4/2048/hotplug-status.
[2010-02-22 05:56:41 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vbd/4/2048/hotplug-status.
[2010-02-22 05:56:41 4813] DEBUG (DevController:643) hotplugStatusCallback 1.
[2010-02-22 05:56:41 4813] DEBUG (DevController:144) Waiting for 2064.
[2010-02-22 05:56:41 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vbd/4/2064/hotplug-status.
[2010-02-22 05:56:42 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vbd/4/2064/hotplug-status.
[2010-02-22 05:56:42 4813] DEBUG (DevController:643) hotplugStatusCallback 1.
[2010-02-22 05:56:42 4813] DEBUG (DevController:144) Waiting for 2080.
[2010-02-22 05:56:42 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vbd/4/2080/hotplug-status.
[2010-02-22 05:56:43 4813] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vbd/4/2080/hotplug-status.
[2010-02-22 05:56:43 4813] DEBUG (DevController:643) hotplugStatusCallback 1.
[2010-02-22 05:56:43 4813] DEBUG (DevController:139) Waiting for devices irq.
[2010-02-22 05:56:43 4813] DEBUG (DevController:139) Waiting for devices vfb.
[2010-02-22 05:56:43 4813] DEBUG (DevController:139) Waiting for devices pci.
[2010-02-22 05:56:43 4813] DEBUG (DevController:139) Waiting for devices vtpm.
[2010-02-22 05:56:43 4813] INFO (XendDomain:1182) Domain netbsd (4) unpaused.

...
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2207) Destroying device model
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2214) Releasing devices
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2227) Removing vif/0
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:1134) 
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2227) Removing console/0
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:1134) 
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2227) Removing vbd/2048
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:1134) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2048
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2227) Removing vbd/2064
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:1134) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2064
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2227) Removing vbd/2080
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:1134) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2080
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2212) No device model
[2010-02-22 05:59:14 4813] DEBUG (XendDomainInfo:2214) Releasing devices
[2010-02-22 06:00:28 4813] DEBUG (XendDomainInfo:2212) No device model
[2010-02-22 06:00:28 4813] DEBUG (XendDomainInfo:2214) Releasing devices
[2010-02-22 06:00:28 4813] DEBUG (XendDomainInfo:2212) No device model

--- snap ---

i can't figure out more here:
--- snip ---
Xend started at Mon Feb 22 06:08:22 2010.
cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such file or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory
/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:544: DeprecationWarning: 
object.__new__() takes no parameters
  return object.__new__(cls, *args, **kwds)
Xend started at Mon Feb 22 06:10:03 2010.
cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such file or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory
/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:544: DeprecationWarning: 
object.__new__() takes no parameters
  return object.__new__(cls, *args, **kwds)
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendMonitor.py", line 230, 
in run
    for domid, cputimes in self._get_cpu_stats().items():
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendMonitor.py", line 213, 
in _get_cpu_stats
    vcpu_info = self.xc.vcpu_getinfo(domid, i)
Error: (3, 'No such process')

--- snap ---

and from messages:
--- snip ---
Feb 22 06:13:49 xen kernel: blkback: ring-ref 9, event-channel 7, protocol 2 
(x86_32-abi)
Feb 22 06:13:49 xen kernel: blkback: ring-ref 10, event-channel 8, protocol 2 
(x86_32-abi)
Feb 22 06:13:49 xen kernel: blkback: ring-ref 11, event-channel 9, protocol 2 
(x86_32-abi)
Feb 22 06:13:53 xen logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/6/2048
Feb 22 06:13:53 xen logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/6/2064
Feb 22 06:13:53 xen logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/6/2080
Feb 22 06:13:53 xen logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/6/0
Feb 22 06:13:53 xen kernel: device vif6.0 entered promiscuous mode
Feb 22 06:13:53 xen kernel: pwan1: port 3(vif6.0) entering forwarding state
Feb 22 06:13:53 xen logger: /etc/xen/scripts/vif-bridge: iptables setup failed. 
This may affect guest networking.
Feb 22 06:13:53 xen logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge 
online for vif6.0, bridge pwan1.
Feb 22 06:13:53 xen logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/6/0/hotplug-status connected to xenstore.
Feb 22 06:13:54 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2048/node /dev/loop11 to xenstore.
Feb 22 06:13:54 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2048/physical-device 7:b to xenstore.
Feb 22 06:13:54 xen kernel: (cdrom_add_media_watch() 
file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/6/2048
Feb 22 06:13:54 xen kernel: (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, 
line=95) type:0
Feb 22 06:13:54 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2048/hotplug-status connected to xenstore.
Feb 22 06:13:54 xen kernel: vif5.0: no IPv6 routers present
Feb 22 06:13:55 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2064/node /dev/loop12 to xenstore.
Feb 22 06:13:55 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2064/physical-device 7:c to xenstore.
Feb 22 06:13:55 xen kernel: (cdrom_add_media_watch() 
file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/6/2064
Feb 22 06:13:55 xen kernel: (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, 
line=95) type:0
Feb 22 06:13:55 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2064/hotplug-status connected to xenstore.
Feb 22 06:13:56 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2080/node /dev/loop13 to xenstore.
Feb 22 06:13:56 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2080/physical-device 7:d to xenstore.
Feb 22 06:13:56 xen kernel: (cdrom_add_media_watch() 
file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/6/2080
Feb 22 06:13:56 xen kernel: (cdrom_is_type() file=drivers/xen/blkback/cdrom.c, 
line=95) type:0
Feb 22 06:13:56 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/6/2080/hotplug-status connected to xenstore.
Feb 22 06:14:04 xen kernel: vif6.0: no IPv6 routers present

--- snap ---

there seems nothing related in dmesg.

For the future i plan to migrate my DomUs to 64bit too, but for several 
purposes this can't be done at this stage - i need the 64bit Dom0 working with 
the 32bit PAE guests first.

I assume it is something related to the Dom0 kernel config (i.e. udev, usb 
o.o.), because:
         - i got same 32bit PAE netbsd kernels (the full system) running a 
while / before
         - i had to change some kernel configuration to get my USB remote 
keyboard running (HP ILo). 

Many thanks in advance for any hint...
best regards,


Niels.
-- 

---

  Niels Dettenbach
  ---
  Syndicat IT&Internet
  http://www.syndicat.com
  T.-Muentzer.-Str. 2, 37308 Heilbad Heiligenstadt - DE
  ---
  Kryptoinfo: 
  PGP public key ID 651CA20D
  Fingerprint: 55E0 4DCD B04C 4A49 1586  88AE 54DC 4465 651C A20D
  https://syndicat.com/pub_key.asc
  ---

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] NetBSD DomU don't boot anymore, Niels Dettenbach <=