Hello, I trying to run XEN 2.0 (2.4.27, 2.4.28, 2.6.9) on gentoo 2004.3. When i boot guest domain i get this: anubis xen # xm create -f ttylinux -c Using config file "ttylinux". Started domain ttylinux, console on port 9601 ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** Linux version 2.4.28-xenU (root@anubis) (gcc version 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7)) #3 Thu Nov 25 22:05:31 CET 2004 On node 0 totalpages: 16384 zone(0): 4096 pages. zone(1): 12288 pages. zone(2): 0 pages. Kernel command line: ip=192.168.244.15:1.2.3.4::::eth0:off root=/dev/sda1 ro Initializing CPU#0 Xen reported: 1064.625 MHz processor. Calibrating delay loop... 2116.81 BogoMIPS Memory: 61792k/65536k available (2231k kernel code, 3744k reserved, 342k data, 64k init, 0k highmem) Dentry cache hash table entries: 8192 (order: 4, 65536 bytes) Inode cache hash table entries: 4096 (order: 3, 32768 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: Intel Pentium III (Coppermine) stepping 0a POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd VFS: Disk quotas vdquot_6.5.1 Journalled Block Device driver loaded devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x0 Installing knfsd (copyright (C) 1996 okir@monad.swb.de). SGI XFS with realtime, tracing, debug enabled SGI XFS Quota Management subsystem Event-channel device installed. Xen virtual console successfully installed as tty Starting Xen Balloon driver pty: 256 Unix98 ptys configured [XEN] Initialising virtual block device driver [XEN] Timeout connecting block device driver! RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) SCSI subsystem driver Revision: 1.00 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 [XEN] Initialising virtual ethernet driver. It stop here, and dont go :/ Regards, Lukasz Grzelak ------------------------------------------------------ iTk - info@itk.pl - http://www.itk.pl - +48 91 8137012 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, 26 Nov 2004, Jacob Gorm Hansen wrote:> Lukasz Grzelak wrote: >> Hello, >> >> It stop here, and dont go :/ >> > > It could look like your xend is not running correctly? > > JacobNo, xend running and work fine. Pozdrawiam. Lukasz Grzelak Sys-Net Admin ------------------------------------------------------ iTk - info@itk.pl - http://www.itk.pl - +48 91 8137012 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> On Fri, 26 Nov 2004, Jacob Gorm Hansen wrote: > > > Lukasz Grzelak wrote: > >> Hello, > >> > >> It stop here, and dont go :/ > >> > > > > It could look like your xend is not running correctly? > > > > Jacob > > No, xend running and work fine.Perhaps start xend with ''xend trace_start'' and then see if xend.log can shed any light. While the hang is going on, do you see the new vif if you do an ''ifconfig'' in domain 0? Has it been added to the bridge? Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Lukasz Grzelak wrote:> Hello, > > It stop here, and dont go :/ >It could look like your xend is not running correctly? Jacob ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, 26 Nov 2004, Ian Pratt wrote:> Perhaps start xend with ''xend trace_start'' and then see if > xend.log can shed any light.Xend work fine i thing i have broken kernel or system.> While the hang is going on, do you see the new vif if you do an > ''ifconfig'' in domain 0? Has it been added to the bridge?5: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether 00:50:da:1c:b1:74 brd ff:ff:ff:ff:ff:ff inet 192.168.244.13/32 scope global xen-br0 inet6 fe80::200:ff:fe00:0/64 scope link 6: vif1.0: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc noop link/ether aa:00:01:7d:49:8a brd ff:ff:ff:ff:ff:ff anubis ~ # brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.0050da1cb174 no eth0 vif1.0 vif1.0 added to system and to bridge, but it dont up. Pozdrawiam. Lukasz Grzelak Sys-Net Admin ------------------------------------------------------ iTk - info@itk.pl - http://www.itk.pl - +48 91 8137012 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
>> Perhaps start xend with ''xend trace_start'' and then see if >> xend.log can shed any light. > > Xend work fine i thing i have broken kernel or system.Whatever the problem is, if you run Xend with tracing, the log files might reveal more information about where things went wrong. Xend is intimately involved in setting up virtual devices, so it''s quite possible we''d be able to figure out where /why it''s hanging using the logs. Cheers, Mark>> While the hang is going on, do you see the new vif if you do an >> ''ifconfig'' in domain 0? Has it been added to the bridge? > > > 5: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > link/ether 00:50:da:1c:b1:74 brd ff:ff:ff:ff:ff:ff > inet 192.168.244.13/32 scope global xen-br0 > inet6 fe80::200:ff:fe00:0/64 scope link > 6: vif1.0: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc noop > link/ether aa:00:01:7d:49:8a brd ff:ff:ff:ff:ff:ff > > anubis ~ # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.0050da1cb174 no eth0 > vif1.0 > > > vif1.0 added to system and to bridge, but it dont up. > > > Pozdrawiam. > > Lukasz Grzelak > Sys-Net Admin > ------------------------------------------------------ > iTk - info@itk.pl - http://www.itk.pl - +48 91 8137012 > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > On Fri, 26 Nov 2004, Ian Pratt wrote: > > > Perhaps start xend with ''xend trace_start'' and then see if > > xend.log can shed any light. > > Xend work fine i thing i have broken kernel or system.Have you used your own kernel config? You haven''t disabled CONFIG_XEN_NETDEV_FRONTEND have you? What happens if you use our binary install? Ian> > While the hang is going on, do you see the new vif if you do an > > ''ifconfig'' in domain 0? Has it been added to the bridge? > > > 5: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > link/ether 00:50:da:1c:b1:74 brd ff:ff:ff:ff:ff:ff > inet 192.168.244.13/32 scope global xen-br0 > inet6 fe80::200:ff:fe00:0/64 scope link > 6: vif1.0: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc noop > link/ether aa:00:01:7d:49:8a brd ff:ff:ff:ff:ff:ff > > anubis ~ # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.0050da1cb174 no eth0 > vif1.0 > > > vif1.0 added to system and to bridge, but it dont up. > > > Pozdrawiam. > > Lukasz Grzelak > Sys-Net Admin > ------------------------------------------------------ > iTk - info@itk.pl - http://www.itk.pl - +48 91 8137012 > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, 26 Nov 2004, Ian Pratt wrote:>> >> On Fri, 26 Nov 2004, Ian Pratt wrote: >> >>> Perhaps start xend with ''xend trace_start'' and then see if >>> xend.log can shed any light. >> >> Xend work fine i thing i have broken kernel or system. > > Have you used your own kernel config? You haven''t disabled > CONFIG_XEN_NETDEV_FRONTEND have you? > > What happens if you use our binary install?The same, I tryed xen-2.0-install (2.4.27 and 2.4.9). Meaby gentoo 2004.3 dont work correctly ? Pozdrawiam. Lukasz Grzelak Sys-Net Admin ------------------------------------------------------ iTk - info@itk.pl - http://www.itk.pl - +48 91 8137012 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
>>>>Perhaps start xend with ''xend trace_start'' and then see if >>>>xend.log can shed any light. >>> >>>Xend work fine i thing i have broken kernel or system. >> >>Have you used your own kernel config? You haven''t disabled >>CONFIG_XEN_NETDEV_FRONTEND have you? >> >>What happens if you use our binary install? > > > The same, I tryed xen-2.0-install (2.4.27 and 2.4.9). Meaby gentoo 2004.3 > dont work correctly ?i start believe the same... with same kernel ttylinux now boots, network is ok, rtc-errors (...) of course. with my cloned gentoo xen0 system this happens (xen 2.0.1 source, but similar with bin-version): Linux version 2.6.9-xenU (root@vm0) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #2 Sat Nov 27 17:36:31 GMT 2004 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000004000000 (usable) 64MB LOWMEM available. DMI not present. Built 1 zonelists Kernel command line: ip=192.168.1.101:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off root=/dev/hda1 ro 3 Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Xen reported: 1357.516 MHz processor. Using tsc for high-res timesource Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 62004k/65536k available (1768k kernel code, 3492k reserved, 478k data, 112k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: AMD Athlon(tm) stepping 00 Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... disabled NET: Registered protocol family 16 Initializing Cryptographic API RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Xen virtual console successfully installed as tty Event-channel device installed. Starting Xen Balloon driver xen_blk: Initialising virtual block device driver Using anticipatory io scheduler Unable to handle kernel NULL pointer dereference at virtual address 00000008 printing eip: c0185116 *pde = ma 00000000 pa 55555000 [<c0185203>] sysfs_create_dir+0x40/0x73 [<c0185203>] sysfs_create_dir+0x40/0x73 [<c0200779>] create_dir+0x1f/0x4b [<c0200c6d>] kobject_add+0x93/0xdd [<c0200cdf>] kobject_register+0x28/0x59 [<c021da17>] blk_register_queue+0x96/0xc0 [<c02283dc>] xlvbd_get_gendisk+0x19d/0x1bb [<c0228462>] xlvbd_init_device+0x68/0xdc [<c022853b>] xlvbd_init+0x65/0x98 [<c0227d1e>] blkif_connect+0xae/0xc2 [<c0227459>] blkif_int+0x0/0x19a [<c0227eaa>] blkif_ctrlif_rx+0x36/0x38 [<c0108a56>] __ctrl_if_rxmsg_deferred+0x4a/0x59 [<c012b8ae>] worker_thread+0x1ea/0x2e0 [<c0108a0c>] __ctrl_if_rxmsg_deferred+0x0/0x59 [<c0118cae>] default_wake_function+0x0/0x12 [<c0118cae>] default_wake_function+0x0/0x12 [<c012b6c4>] worker_thread+0x0/0x2e0 [<c012f8e9>] kthread+0xa5/0xab [<c012f844>] kthread+0x0/0xab [<c010ed7d>] kernel_thread_helper+0x5/0xb Oops: 0000 [#1] PREEMPT Modules linked in: CPU: 0 EIP: 0061:[<c0185116>] Not tainted VLI EFLAGS: 00010292 (2.6.9-xenU) EIP is at create_dir+0x17/0x9a eax: c10ebe48 ebx: c118ce3c ecx: 00000000 edx: c118ce40 esi: 00000000 edi: c10ebe48 ebp: c10dec00 esp: c10ebe1c ds: 007b es: 007b ss: 0069 Process events/0 (pid: 3, threadinfo=c10ea000 task=c10d9020) Stack: c10afe2c c02fbaf0 c0185203 c118ce3c c118ce3c c10afe2c c0185203 c118ce3c 00000000 c118ce40 c10ebe48 00000000 00000000 c0200779 c118ce3c c118ce3c ffffffea c0200c6d c118ce3c fffffffd c118ce3c ffffffea c118ce3c c0200cdf Call Trace: [<c0185203>] sysfs_create_dir+0x40/0x73 [<c0185203>] sysfs_create_dir+0x40/0x73 [<c0200779>] create_dir+0x1f/0x4b [<c0200c6d>] kobject_add+0x93/0xdd [<c0200cdf>] kobject_register+0x28/0x59 [<c021da17>] blk_register_queue+0x96/0xc0 [<c02283dc>] xlvbd_get_gendisk+0x19d/0x1bb [<c0228462>] xlvbd_init_device+0x68/0xdc [<c022853b>] xlvbd_init+0x65/0x98 [<c0227d1e>] blkif_connect+0xae/0xc2 [<c0227459>] blkif_int+0x0/0x19a [<c0227eaa>] blkif_ctrlif_rx+0x36/0x38 [<c0108a56>] __ctrl_if_rxmsg_deferred+0x4a/0x59 [<c012b8ae>] worker_thread+0x1ea/0x2e0 [<c0108a0c>] __ctrl_if_rxmsg_deferred+0x0/0x59 [<c0118cae>] default_wake_function+0x0/0x12 [<c0118cae>] default_wake_function+0x0/0x12 [<c012b6c4>] worker_thread+0x0/0x2e0 [<c012f8e9>] kthread+0xa5/0xab [<c012f844>] kthread+0x0/0xab [<c010ed7d>] kernel_thread_helper+0x5/0xb Code: 2f 2f c0 c7 80 88 00 00 00 e0 2e 2f c0 83 40 24 01 31 c0 c3 83 ec 18 89 74 24 10 89 7c 24 14 89 5c 24 0c 8b 74 24 20 8b 7c 24 28 <8b> 46 08 8d 48 68 ff 48 68 0f 88 c3 03 00 00 89 34 24 8b 44 24 <6>xen_net: Initialising virtual ethernet driver. xen_net: Failed to connect all virtual interfaces: err=-100 NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) IPv4 over IPv4 tunneling driver GRE over IPv4 tunneling driver ip_conntrack version 2.1 (512 buckets, 4096 max) - 332 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/ arp_tables: (C) 2002 David S. Miller NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 IP-Config: Device `eth0'' not found. --- hangs --- my xend.log (xend trace_start) says the following: [2004-11-27 22:03:23 xend] INFO (SrvDaemon:607) Xend Daemon started [2004-11-27 22:03:23 xend] INFO (XendRoot:91) EVENT> xend.start 0 [2004-11-27 22:03:36 xend] DEBUG (XendDomainInfo:720) init_domain> Created domain=5 name=vm101 memory=64 [2004-11-27 22:03:36 xend] INFO (console:92) Created console id=13 domain=5 port=9605 [2004-11-27 22:03:36 xend] DEBUG (XendDomainInfo:1102) Creating vbd dom=5 uname=phy:vg1/vm101 [2004-11-27 22:03:36 xend] DEBUG (blkif:146) Connecting blkif <BlkifBackendInterface 5 0> [2004-11-27 22:03:36 xend] DEBUG (XendDomainInfo:1102) Creating vbd dom=5 uname=phy:vg1/vm101-swap [2004-11-27 22:03:36 xend] DEBUG (blkif:146) Connecting blkif <BlkifBackendInterface 5 0> [2004-11-27 22:03:36 xend] DEBUG (XendDomainInfo:1102) Creating vbd dom=5 uname=phy:sdb7 [2004-11-27 22:03:36 xend] DEBUG (blkif:146) Connecting blkif <BlkifBackendInterface 5 0> [2004-11-27 22:03:36 xend] DEBUG (XendDomainInfo:1102) Creating vbd dom=5 uname=phy:sdc5 [2004-11-27 22:03:36 xend] DEBUG (blkif:146) Connecting blkif <BlkifBackendInterface 5 0> [2004-11-27 22:03:36 xend] DEBUG (XendDomainInfo:1079) Creating vif dom=5 vif=0 mac=aa:00:00:57:6a:d7 [2004-11-27 22:03:36 xend] INFO (XendRoot:91) EVENT> xend.console.create [13, 5, 9605] [2004-11-27 22:03:37 xend] INFO (XendRoot:91) EVENT> xend.domain.create [''vm101'', ''5''] [2004-11-27 22:03:37 xend] INFO (XendRoot:91) EVENT> xend.domain.unpause [''vm101'', ''5''] [2004-11-27 22:03:37 xend] DEBUG (blkif:192) Connecting blkif to event channel <BlkifBackendInterface 5 0> ports=19:3 [2004-11-27 22:03:55 xend] INFO (console:42) Console connected 13 127.0.0.1 32794 [2004-11-27 22:03:55 xend] INFO (XendRoot:91) EVENT> xend.console.connect [13, ''127.0.0.1'', 32794] any hints? what''s going wrong here? what''s other than in older gentoo? it wasn''t a problem like that to get xeno-unstable or 1.2 to work on older versions. devfs replaced with udev now. Thanks, Björn ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel