Christian Hertel
2006-Feb-13 10:34 UTC
AW: AW: [Xen-users] Exporting Dom0 disks to DomU as SCSI disksdoesnot work
Hello,> I am not able to understand this problem right away ,but SCSI > major number is 8 and i can see your kernel cribbing about > registering block device with major number 8 when its > booting up,..just before it panics ....below , i have > separated it with equal to marksHm perhaps I should mention I don''t included any SCSI low-level driver in my DomU, but for my understanding, this should also be no problem. The DomU kernel doesn''t know anything about the underlying hardware and I didn''t compile in physical hardware access, so I''m curios about why SCSI low-level is shown in menuconfig at all. Might this be a bug?> can you paste the output for the successfull hda bootup ??Yes, here it comes: --- snip --- Using config file "/etc/xen/test1". Started domain test1 Linux version 2.6.12.6-xenU (root@sarge64) (gcc-Version 3.3.5 (Debian 1:3.3.5-13)) #2 SMP Fri Feb 10 17:02:40 CET 2006 kernel direct mapping tables upto 20800000 @ 4ac000-5b2000 Built 1 zonelists Kernel command line: root=/dev/hdb1 ro Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) Xen reported: 2992.692 MHz processor. Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 509184k/532480k available (1564k kernel code, 22552k reserved, 587k data, 136k init) Mount-cache hash table entries: 256 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 Brought up 1 CPUs Grant table initialized 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 IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. netfront: Initialising virtual ethernet driver. NET: Registered protocol family 2 Registering block device major 3 IP: routing cache hash table of 2048 buckets, 32Kbytes TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. INIT: version 2.86 booting NET: Registered protocol family 1 Activating swap. Adding 1048568k swap on /dev/hda1. Priority:-1 extents:1 EXT3 FS on hdb1, internal journal Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. System time was Fri Feb 10 16:38:47 UTC 2006. Setting the System Clock using the Hardware Clock as reference... Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. System Clock set. System local time is now Fri Feb 10 16:38:47 UTC 2006. Cleaning up ifupdown...done. Calculating module dependencies... done. Loading modules... All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) Setting kernel variables ... ... done. Mounting local filesystems... Cleaning /tmp /var/run /var/lock. Running 0dns-down to make sure resolv.conf is ok...done. Setting up networking...done. Setting up IP spoofing protection: rp_filter. Configuring network interfaces...done. Setting the System Clock using the Hardware Clock as reference... Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. System Clock set. Local time: Fri Feb 10 16:38:48 UTC 2006 Initializing random number generator...done. Recovering nvi editor sessions... done. INIT: Entering runlevel: 2 Starting system log daemon: syslogd. Starting kernel log daemon: klogd. Starting MTA: exim4. Starting internet superserver: inetd. Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. Debian GNU/Linux 3.1 test1 tty1 --- snap --- Christian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Hertel
2006-Feb-13 13:00 UTC
AW: AW: [Xen-users] Exporting Dom0 disks to DomU as SCSI disksdoesnot work
Hello again,> This is my 2.6.11-1.1360FC$4xenU as different from yours and it boots > when physical devices are exported as SCSI, I am not a SCSI expert so > wont be able to tell you why , try this and mail the result...I have > also attached the fileMeanwhile, I added SATA support to my DomU, but it still doesn''t work :( Someone else got an idea? Help is greatly appreciated. Christian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users