Unable to find root device. domU??

Unable to find root device. domU??

[Nicholas Lee]

[-- Attachment #1: Type: text/plain, Size: 4051 bytes --]

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo xm create breezy -c
Using config file "/etc/xen/breezy".
Started domain breezy
Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian
1:3.3.5-13)) #3 SMP Thu Oct 13 14:56:20 NZDT 2005
kernel direct mapping tables upto 10000000 @ 568000-5ea000
Built 1 zonelists
Kernel command line:  root=/dev/sda1 ro 4 lockd.udpport=32768
lockd.tcpport=32768
Unknown boot option `lockd.udpport=32768': ignoring
Unknown boot option `lockd.tcpport=32768': ignoring
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 2194.794 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 251904k/262144k available (2569k kernel code, 9752k reserved,
814k data, 160k init)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
Booting processor 1/1 rip ffffffff80100008 rsp ffff8800014f5f58
Initializing CPU#1
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
AMD Opteron(tm) Processor 248 stepping 01
Brought up 2 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: System does not support PCI
PCI: System does not support PCI
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
Grant table initialized
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with ACLs, security attributes, large block/inode numbers, no
debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
Failed to obtain physical IRQ 8
Real Time Clock Driver v1.12
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
WARNING: Failed to register Xen virtual console driver as 'tty1'
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda1" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)


nic@wuwei:/usr/src/xen/xen-unstable.hg$ hg tip
changeset:   7353:29db5bded574

nic@wuwei:/etc/xen$ cat breezy
kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 256
name = "breezy"
vcpus = 2
nics=1
vif = [ "mac=aa:00:00:88:02:40, bridge=xen-br0" ]
disk = [ 'phy:ww/breezy-fs,sda1,w', 'phy:ww/breezy-swap,sda2,w' ]

root = "/dev/sda1 ro"
extra = "4 lockd.udpport=32768 lockd.tcpport=32768"
restart = 'onreboot'

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo lvdisplay ww/breezy-fs
  --- Logical volume ---
  LV Name                /dev/ww/breezy-fs
  VG Name                ww
...


Can someone explain what I might be missing here.  Note I previously
got domU booting, but had problems with the net device. Now it looks
like the net device is initialising but the block device is having
issues.

Thanks.
--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

[-- Attachment #2: config --]
[-- Type: application/octet-stream, Size: 19478 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.12-xenU
# Thu Oct 13 14:49:14 2005
#
CONFIG_XEN=y
CONFIG_ARCH_XEN=y
CONFIG_NO_IDLE_HZ=y

#
# XEN
#
# CONFIG_XEN_PRIVILEGED_GUEST is not set
CONFIG_XEN_PHYSDEV_ACCESS=y
CONFIG_XEN_BLKDEV_BACKEND=y
# CONFIG_XEN_BLKDEV_TAP_BE is not set
CONFIG_XEN_NETDEV_BACKEND=y
# CONFIG_XEN_TPMDEV_FRONTEND is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_FRONTEND_PIPELINED_TRANSMITTER is not set
# CONFIG_XEN_BLKDEV_TAP is not set
# CONFIG_XEN_SHADOW_MODE is not set
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_X86 is not set
CONFIG_XEN_X86_64=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not set
# CONFIG_CPUSETS is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_XENARCH="x86_64"
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_GOOD_APIC=y
# CONFIG_HPET_TIMER is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
CONFIG_PREEMPT=y
CONFIG_MICROCODE=y
# CONFIG_X86_CPUID is not set
CONFIG_SWIOTLB=y
# CONFIG_NUMA is not set
# CONFIG_MTRR is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_X86_LOCAL_APIC is not set
# CONFIG_X86_IO_APIC is not set
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_SECCOMP=y

#
# X86_64 processor configuration
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_EARLY_PRINTK=y

#
# Processor type and features
#
# CONFIG_MPSC is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_L1_CACHE_BYTES=128
# CONFIG_X86_TSC is not set
CONFIG_X86_XEN_GENAPIC=y
# CONFIG_X86_MSR is not set
CONFIG_X86_HT=y
# CONFIG_K8_NUMA is not set
# CONFIG_NUMA_EMU is not set
# CONFIG_GART_IOMMU is not set
CONFIG_DUMMY_IOMMU=y
# CONFIG_X86_MCE is not set

#
# Power management options
#
# CONFIG_PM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI etc.)
#
# CONFIG_UNORDERED_IO is not set

#
# Executable file formats / Emulations
#
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_CT_ACCT=y
CONFIG_IP_NF_CONNTRACK_MARK=y
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
# CONFIG_IP_NF_MATCH_LIMIT is not set
CONFIG_IP_NF_MATCH_IPRANGE=m
# CONFIG_IP_NF_MATCH_MAC is not set
# CONFIG_IP_NF_MATCH_PKTTYPE is not set
# CONFIG_IP_NF_MATCH_MARK is not set
# CONFIG_IP_NF_MATCH_MULTIPORT is not set
# CONFIG_IP_NF_MATCH_TOS is not set
# CONFIG_IP_NF_MATCH_RECENT is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_DSCP is not set
# CONFIG_IP_NF_MATCH_AH_ESP is not set
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
# CONFIG_IP_NF_MATCH_HELPER is not set
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_MATCH_PHYSDEV=m
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_CONNMARK is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_ULOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
# CONFIG_IP_NF_TARGET_REDIRECT is not set
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_FTP=m
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set

#
# Bridge: Netfilter Configuration
#
# CONFIG_BRIDGE_NF_EBTABLES is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=y
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_NET_CLS_IND=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
# CONFIG_USB is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# InfiniBand support
#
CONFIG_INFINIBAND=y
CONFIG_INFINIBAND_MTHCA=y
CONFIG_INFINIBAND_MTHCA_DEBUG=y
CONFIG_INFINIBAND_IPOIB=y
CONFIG_INFINIBAND_IPOIB_DEBUG=y
CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y

#
# XFS support
#
CONFIG_XFS_FS=y
CONFIG_XFS_EXPORT=y
# CONFIG_XFS_RT is not set
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=m
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#

#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
# CONFIG_INIT_DEBUG is not set

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Unable to find root device. domU??

[Rob Gardner]

Nicholas Lee wrote:

>xen_blk: Initialising virtual block device driver
>xen_net: Initialising virtual ethernet driver.
>mice: PS/2 mouse device common for all mice
>NET: Registered protocol family 2
>IP: routing cache hash table of 1024 buckets, 16Kbytes
>TCP established hash table entries: 16384 (order: 6, 262144 bytes)
>TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
>TCP: Hash tables configured (established 16384 bind 16384)
>NET: Registered protocol family 1
>NET: Registered protocol family 17
>Bridge firewalling registered
>Root-NFS: No NFS server available, giving up.
>VFS: Unable to mount root fs via NFS, trying floppy.
>VFS: Cannot open root device "sda1" or unknown-block(2,0)
>Please append a correct "root=" boot option
>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
>  
>



Yep... exactly what I've been battling for days now!!

Rob

Re: Unable to find root device. domU??

[Sean Dague]

[-- Attachment #1.1: Type: text/plain, Size: 1116 bytes --]

On Thu, Oct 13, 2005 at 03:20:19PM +1300, Nicholas Lee wrote:
<snip>
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "sda1" or unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
                                                              ^^^^^^^^^^^^^^^^^^

I am seeing exactly this failure per the previous email thread.

> nic@wuwei:/usr/src/xen/xen-unstable.hg$ hg tip
> changeset:   7353:29db5bded574

Same change set.

	-Sean

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/13/05, Sean Dague <sean@dague.net> wrote:
> I am seeing exactly this failure per the previous email thread.

I'm not even seeing the first domU come up.  I'm distclean and trying
again with the default default kernal (plus XFS as I use that here.)

Otherwise is there a 'good' changeset to revert too?

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Keir Fraser]

On 13 Oct 2005, at 04:25, Nicholas Lee wrote:

>> I am seeing exactly this failure per the previous email thread.
>
> I'm not even seeing the first domU come up.  I'm distclean and trying
> again with the default default kernal (plus XFS as I use that here.)
>
> Otherwise is there a 'good' changeset to revert too?

There are some fixes for domU device probing waiting in the queue to 
get pushed to the public tree. Hopefully should fix some of these 
failures. I expect they'll get pushed out some time this morning after 
testing.

  -- Keir

Re: Re: Unable to find root device. domU??

[Rob Gardner]

Keir Fraser wrote:

>
> There are some fixes for domU device probing waiting in the queue to 
> get pushed to the public tree. Hopefully should fix some of these 
> failures.



They didn't. I did a pull this morning and rebuilt everything.... same 
behavior, same problem.

Rob

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

I have continue to have the same problem as well.  (cs 7369:92c6021f23e4)

nic@wuwei:~$ sudo xm create breezy -c
Using config file "/etc/xen/breezy".
Started domain breezy
Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian
1:3.3.5-13)) #1 SMP Fri Oct 14 10:38:59 NZDT 2005
Built 1 zonelists
Kernel command line:  root=/dev/sda1 ro 4
...
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

I just noted these additional error messages in xm dmesg that might help:

(XEN) (file=irq.c, line=224) Cannot bind IRQ 2 to guest. In use by 'cascade'.
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000080,00010000,00010000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000100,00000000,00000000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000102,00000000,00000000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000080,00000000,00000000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000100,00000000,00000000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000102,00000000,00000000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000080,00000000,00000000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000100,00000045,ffffffffff5fd000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000101,ab124740,00002aaa).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000102,8038c980,ffffffff).


--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Rob Gardner]

Nicholas Lee wrote:

>I have continue to have the same problem as well.  (cs 7369:92c6021f23e4)
>  
>

I just succeeded in working around the problem by the simple expedient 
of reinstalling linux. ;)

I created a new disk partition, installed a fresh linux into it to host 
xen and dom0, then copied over the latest build, and now I can boot domU 
with no problems.

The conclusion: something was messed up on my system, and doing a xen 
install did not clean it up. I had tried manually removing all the xen 
files I could find or think of, but nothing seemed to help. Whatever was 
messed up, or stale, was hiding very very well.

Rob

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/14/05, Rob Gardner <rob.gardner@hp.com> wrote:
> I just succeeded in working around the problem by the simple expedient
> of reinstalling linux. ;)

I can to this conclusion just last night as well. When I reverted to a
changeset that worked previously.   I was thinking I'd boot into the
non-xen kernel some time today and nuke all the Xen files.

You are right though, completely reinstall might be the best option. 
Sounds like a windows box. :P

I guess at least with Xen we can be safe in the knowledge that might
domU data will remain completely unaffected.


--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/14/05, Nicholas Lee <emptysands@gmail.com> wrote:
> I just noted these additional error messages in xm dmesg that might help:

Installing a CONFIG_XEN_PRIVILEGED_GUEST=y guest doesn't seem to change this.

Exactly same error messages.

(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000101,ab124740,00002aaa).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000102,8038c980,ffffffff).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000080,00010000,00010000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000100,00000000,00000000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000102,00000000,00000000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000080,00000000,00000000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000100,00000000,00000000).
(XEN) (file=traps.c, line=960) Non-priv domain attempted
WRMSR(00000000c0000102,00000000,00000000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000080,00000000,00000000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000100,00000045,ffffffffff577000).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000101,ab124740,00002aaa).
(XEN) (file=traps.c, line=968) Non-priv domain attempted
RDMSR(00000000c0000102,803f5c00,ffffffff).

nic@wuwei:~$ sudo xm block-list 3
(2049 ((virtual-device 2049) (backend-id 0) (backend
/local/domain/0/backend/vbd/3/2049) (ring-ref 8) (event-channel 9)
(error '2 reading backend fields at
/local/domain/0/backend/vbd/3/2049')))




--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

RE: Re: Unable to find root device. domU??

[Ian Pratt]

> On 10/14/05, Nicholas Lee <emptysands@gmail.com> wrote:
> > I just noted these additional error messages in xm dmesg 
> that might help:
> 
> Installing a CONFIG_XEN_PRIVILEGED_GUEST=y guest doesn't seem 
> to change this.

These grumbles from Xen are nothing to worry about -- you only see them
because we're using a verbose build by default.

Ian
 
> Exactly same error messages.
> 
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000101,ab124740,00002aaa).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000102,8038c980,ffffffff).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000080,00010000,00010000).
> (XEN) (file=traps.c, line=960) Non-priv domain attempted 
> WRMSR(00000000c0000100,00000000,00000000).
> (XEN) (file=traps.c, line=960) Non-priv domain attempted 
> WRMSR(00000000c0000102,00000000,00000000).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000080,00000000,00000000).
> (XEN) (file=traps.c, line=960) Non-priv domain attempted 
> WRMSR(00000000c0000100,00000000,00000000).
> (XEN) (file=traps.c, line=960) Non-priv domain attempted 
> WRMSR(00000000c0000102,00000000,00000000).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000080,00000000,00000000).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000100,00000045,ffffffffff577000).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000101,ab124740,00002aaa).
> (XEN) (file=traps.c, line=968) Non-priv domain attempted 
> RDMSR(00000000c0000102,803f5c00,ffffffff).
> 
> nic@wuwei:~$ sudo xm block-list 3
> (2049 ((virtual-device 2049) (backend-id 0) (backend
> /local/domain/0/backend/vbd/3/2049) (ring-ref 8) 
> (event-channel 9) (error '2 reading backend fields at
> /local/domain/0/backend/vbd/3/2049')))
> 
> 
> 
> 
> --
> Nicholas Lee
> http://stateless.geek.nz
> gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/15/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> These grumbles from Xen are nothing to worry about -- you only see them
> because we're using a verbose build by default.

I was wondering about that. Still I guess since we are in testing mode
its better for me to be as noisy as possible as well. :)

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/15/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> These grumbles from Xen are nothing to worry about -- you only see them
> because we're using a verbose build by default.

I was wondering about that. Still I guess since we are in testing mode
its better for me to be as noisy as possible as well. :)

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/15/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> These grumbles from Xen are nothing to worry about -- you only see them
> because we're using a verbose build by default.

I was wondering about that. Still I guess since we are in testing mode
its better for me to be as noisy as possible as well. :)

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/15/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> These grumbles from Xen are nothing to worry about -- you only see them
> because we're using a verbose build by default.

I was wondering about that. Still I guess since we are in testing mode
its better for me to be as noisy as possible as well. :)

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: Re: Unable to find root device. domU??

[David Becker]

" >There are some fixes for domU device probing waiting in the queue to 
" >get pushed to the public tree. Hopefully should fix some of these 
" >failures.

I tried today's pull and xenU will still not detect the vbd.
This is not consistent across hardware.   xenU detects the vbd OK on
a Dell PE1650 but not on an IBM HS20 Blade (type 8678).
The Dell has a scsi drive and the IBM has IDE.  Both hosts 
have LVM partitions for the xenUs.


xenU on the IBM says:
    Xen virtual console successfully installed as tty1                   
    Event-channel device installed.                   
    xen_blk: Initialising virtual block device driver
    xen_net: Initialising virtual ethernet driver.   

xenU on the Dell says:
    Xen virtual console successfully installed as tty1
    Event-channel device installed.
    xen_blk: Initialising virtual block device driver
    Registering block device major 3
    xen_net: Initialising virtual ethernet driver.

Re: Re: Unable to find root device. domU??

[Rob Gardner]

David Becker wrote:

>" >There are some fixes for domU device probing waiting in the queue to 
>" >get pushed to the public tree. Hopefully should fix some of these 
>" >failures.
>
>I tried today's pull and xenU will still not detect the vbd.
>This is not consistent across hardware.   xenU detects the vbd OK on
>a Dell PE1650 but not on an IBM HS20 Blade (type 8678).
>The Dell has a scsi drive and the IBM has IDE.  Both hosts 
>have LVM partitions for the xenUs.
>
>
>xenU on the IBM says:
>    Xen virtual console successfully installed as tty1                   
>    Event-channel device installed.                   
>    xen_blk: Initialising virtual block device driver
>    xen_net: Initialising virtual ethernet driver.   
>  
>

This is exactly the problem I was seeing all last week. I re-imaged my 
base system to clean up the filesystem, and that appears to have solved 
the problem on two different machines. So it seems that the bug is also 
exposed or affected by something in the filesystem, possibly an out of 
date library, or something. The only clue I can offer (which may just be 
coincidence) is that all the affected systems had previously run xen 2.0 
in the past, while the new (working) system was a clone of a system that 
had only ever had xen 3.0 on it.

Rob Gardner

Re: Re: Unable to find root device. domU??

[David Becker]

bah,  the problem host was missing the hotplug package.   This hotplug
dependency bit me once before.  Can xm create just fail when hotplug is
missing?

Re: Re: Unable to find root device. domU??

[Nicholas Lee]

On 10/19/05, David Becker <becker@cs.duke.edu> wrote:
> dependency bit me once before.  Can xm create just fail when
> hotplug is missing?

I thought about suggesting this as well.

I'm guessing it would be easier enough to put an existence test in the
"xm create" python script.

I'm not sure sure exactly why Xen 3.0 depends on hotplug though.

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C