> For example, the mini-os in the extras directory doesn''t compile because there > is some unknown fields in structure HYPERVISOR_shared_info (line 74 of time.c > and some others)Thanks we''ll fix this.> There is another problem in the tools directory with the file misc/xen_log.c. > It includes file <tcpd.h> that doesn''t exist. I think this file is just not > needed to compile...I have /usr/include/tcpd.h from tcp_wrappers-7.6-34.i386.rpm If it''s not required, we''ll remove it.> The problem occurs with the new build tools (xenctl & co) because I cannot start > a new domain with them. As soon as I run the command "xenctl script > -f/etc/xen-mynewdom" the computer reboot. It worked with old binaries (I mean > with xenctl recovered from the CD the same command works). I don''t know where is > the problem because I don''t see any error message during the compilation nor > during the crash. I will try to start a new domain with xi_* commands to see if > the system will have the same behavior.You need to make sure you''re using the xi_* tools that go with the appropriate Xen / Xenolinux version. There were significant changes between 1.0 and 1.1 that require the tools to be upgraded. I''m afraid there''s currently no version checking, so it''s quite possible that Xen will fault and die. Please can you retry with matching tools and let us know what happens.> I also have a question about future work. Do you plan to port > Xen on IA64 architecture? I will be really interesting by > that. If not, do you think it will be difficult to port?We''re interested in an IA-64 port (as are some people at HP), but it''s not high on our current todo list, though this may change, depending on resources. Doing a port would be pretty straight forward as the ia-64 is rather easier to virtualise.> Otherwise, I saw a draft in Xen 1.1 concerning the internals of > Xen. Is there some documents already ready like a presentation > (about internals). I know there is the source but I don''t know > where I should start to understand how it works (maybe device > part is easier) and help the Xen team to develop it (for > example by porting on IA64 ;)We''re currently desperately short of internal documentation, though this is slowly beginning to be fixed -- expect to see some docs checked into the unstable tree.> Is it possible to have a binary of xinxp image (I think not but > I can always ask ;).I''m afraid the XP binary is currently only available under special licensing terms, and I don''t expect this to change in the near term.> I know that the "xenonetbsd" is not in progress but is there a > running version?We abandoned the NetBSD port for the moment, but Kip Macy has been making good progress in his spare time getting FreeBSD 4.8 up and running. You can follow his progress on xen-devel. Best, Ian ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > > For example, the mini-os in the extras directory doesn''t compile because there > > is some unknown fields in structure HYPERVISOR_shared_info (line 74 of time.c > > and some others) > > Thanks we''ll fix this.Fixed in both the 1.1 and unstable trees. The unstable mmini-os is tested and working. The 1.1 mini-os builds but I haven''t tested it.> > There is another problem in the tools directory with the file misc/xen_log.c. > > It includes file <tcpd.h> that doesn''t exist. I think this file is just not > > needed to compile... > > I have /usr/include/tcpd.h from tcp_wrappers-7.6-34.i386.rpm > > If it''s not required, we''ll remove it.It''s not required -- I removed it in both the 1.1 and unstable trees.> > Otherwise, I saw a draft in Xen 1.1 concerning the internals of > > Xen. Is there some documents already ready like a presentation > > (about internals). I know there is the source but I don''t know > > where I should start to understand how it works (maybe device > > part is easier) and help the Xen team to develop it (for > > example by porting on IA64 ;) > > We''re currently desperately short of internal documentation, > though this is slowly beginning to be fixed -- expect to see some > docs checked into the unstable tree.I''m planning to document the interface at some point, which is why there''s some skeleton LaTeX in the docs directory. Hopefully I''ll fill in some details soon :-) We also have some user howtos in progress. -- Keir ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Selon Ian Pratt <Ian.Pratt@cl.cam.ac.uk>:> You need to make sure you''re using the xi_* tools that go with > the appropriate Xen / Xenolinux version. There were significant > changes between 1.0 and 1.1 that require the tools to be > upgraded. I''m afraid there''s currently no version checking, so > it''s quite possible that Xen will fault and die. > > Please can you retry with matching tools and let us know what > happens.So I compile new xen and xenolinux images with the matching tools and I have some troubles. When I boot the first time with new kernels, the boot frozen after enabling the Real Time Clock Driver. So I removed it from the kernel and everything went fine. I don''t know if this driver is a problem. I will make a new try with "Enhanced Real Time Clock Support" enable in the kernel... Another problem occures when I try to start a new domain. I receive a kernel panic during the boot. I use the following /etc/xenctl.xml file: -------------------------------------------------- xenohost2:~# cat /etc/xenctl.xml <?xml version="1.0"?> <domctl_defaults> <domain_name>XenoLinuxDeb</domain_name> <domain_size_kb>98304</domain_size_kb> <domain_image>/boot/xenolinux11.gz</domain_image> <domain_vifs>1</domain_vifs> <root_device>/dev/hda5</root_device> <root_args>rw</root_args> <args>4 DOMID=+</args> <nw_ip>169.254.1.0+</nw_ip> <nw_gw>169.254.1.0</nw_gw> <nw_mask>255.255.0.0</nw_mask> <nw_nfs_server>169.254.1.0</nw_nfs_server> <max_domain_number>1000</max_domain_number> <xi_tools_dir>/usr/local/bin/</xi_tools_dir> </domctl_defaults> -------------------------------------------------------- And when I use the command "xenctl script -f/etc/xen-mynewdom" I have the following output: -------------------------------------------------------- Domain defaults: name XenoLinuxDeb size 98304 vifs 1 domainImage /boot/xenolinux11.gz domainInitRD null rootDevice /dev/hda5 rootArgs rw usrDevice null NWIP 169.254.1.0+ NWGW 169.254.1.0 NWMask 255.255.0.0 MaxDomainNumber 1000 NWNFSServer 169.254.1.0 NWNFSRoot null XIToolsDir /usr/local/bin/ args 4 DOMID=+ Domain created with arguments: /usr/local/bin/xi_create 98304 XenoLinuxDeb Domain built with arguments: /usr/local/bin/xi_build 5 /tmp/xen-image-28237.tmp 1 ip=169.254.1.5:169.254.1.0:169.254.1.0:255.255.0.0::eth0:off 4 DOMID=5 root=/dev/hda5 rw VIF 0 initialized with arguments: /usr/local/bin/xi_vifinit 5 0 169.254.1.5 Granted physical access to domain 5 Started domain 5 -------------------------------------------------------- And in the console I can see : -------------------------------------------------------- [5] xen_console_init [5] Linux version 2.4.22-xeno (guill@xenohost1) (gcc version 3.3.2 (Debian)) #1 Wed Nov 5 14:55:42 CET 2003 [5] On node 0 totalpages: 24576 [5] zone(0): 4096 pages. [5] zone(1): 20480 pages. [5] zone(2): 0 pages. [5] Kernel command line: ip=169.254.1.5:169.254.1.0:169.254.1.0:255.255.0.0::eth0:off 4 DOMID=5 root=/dev/hda5 rw [5] Initializing CPU#0 [5] Xen reported: 666.692 MHz processor. [5] Calibrating delay loop... 2287.20 BogoMIPS [5] Memory: 95440k/98304k available (1136k kernel code, 2864k reserved, 210k data, 44k init, 0k highmem) [5] Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) [5] Inode cache hash table entries: 8192 (order: 4, 65536 bytes) [5] Mount cache hash table entries: 512 (order: 0, 4096 bytes) [5] Buffer cache hash table entries: 4096 (order: 2, 16384 bytes) [5] Page-cache hash table entries: 32768 (order: 5, 131072 bytes) [5] CPU: L1 I cache: 16K, L1 D cache: 16K [5] CPU: L2 cache: 256K [5] CPU: Intel Pentium III (Coppermine) stepping 06 [5] POSIX conformance testing by UNIFIX [5] Linux NET4.0 for Linux 2.4 [5] Based upon Swansea University Computer Society NET3.039 [5] Initializing RT netlink socket [5] Starting kswapd [5] Journalled Block Device driver loaded [5] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [5] Xeno console successfully installed [5] Starting Xeno Balloon driver [5] pty: 256 Unix98 ptys configured [5] Serial driver version 5.05c (2001-07-08) with no serial options enabled [5] ttyS00 at 0x03f8 (irq = 4) is a 16550A [5] ttyS01 at 0x02f8 (irq = 3) is a 16550A [5] Partition check: [5] hda:Bad return from blkdev data request: 1 [5] Bad return from blkdev data request: 1 [5] unable to read partition table [5] Skipping partition check on cdrom /dev/hdc [5] XenoLinux Virtual Segment Device Driver installed [device: 125] [5] NET4: Linux TCP/IP 1.0 for NET4.0 [5] IP Protocols: ICMP, UDP, TCP, IGMP [5] IP: routing cache hash table of 512 buckets, 4Kbytes [5] TCP: Hash tables configured (established 8192 bind 16384) [5] ip_conntrack version 2.1 (768 buckets, 6144 max) - 292 bytes per conntrack [5] ip_tables: (C) 2000-2002 Netfilter core team [5] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. [5] root_device_name = hda5 [5] Bad return from blkdev data request: 1 [5] EXT3-fs: unable to read superblock [5] Bad return from blkdev data request: 1 [5] EXT2-fs: unable to read superblock [5] Bad return from blkdev data request: 1 [5] isofs_read_super: bread failed, dev=03:05, iso_blknum=16, block=32 [5] Kernel panic: VFS: Unable to mount root fs on 03:05 -------------------------------------------------------- I don''t know when the partition is checked there is an error because it works fine during the boot of domain_0 as I can see with dmesg output: -------------------------------------------------------- xenohost2:~# dmesg Linux version 2.4.22-xeno (guill@xenohost1) (gcc version 3.3.2 (Debian)) #1 Wed Nov 5 14:55:42 CET 2003 On node 0 totalpages: 25000 zone(0): 4096 pages. zone(1): 20904 pages. zone(2): 0 pages. Kernel command line: /xenolinux11.gz root=/dev/hda6 console=tty0 Initializing CPU#0 Xen reported: 666.692 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 2660.76 BogoMIPS Memory: 97108k/100000k available (1136k kernel code, 2892k reserved, 210k data, 44k init, 0k highmem) Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode cache hash table entries: 8192 (order: 4, 65536 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: 32768 (order: 5, 131072 bytes) CPU: Before vendor init, caps: 0387fbff 00000000 00000000, vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: After vendor init, caps: 0387fbff 00000000 00000000 00000000 CPU: After generic, caps: 0387fbff 00000000 00000000 00000000 CPU: Common caps: 0387fbff 00000000 00000000 00000000 CPU: Intel Pentium III (Coppermine) stepping 06 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 Journalled Block Device driver loaded Installing knfsd (copyright (C) 1996 okir@monad.swb.de). Xeno console successfully installed Successfully installed virtual firewall/router interface Starting Xeno Balloon driver Detected PS/2 Mouse Port. pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with no serial options enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Partition check: hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 > Skipping partition check on cdrom /dev/hdc XenoLinux Virtual Segment Device Driver installed [device: 125] ... <after, boot sequence is ok> -------------------------------------------------------- So I will try to found what is going wrong. I don''t know if the new domain access to hardware via domain_0 or if it can access through the hypervisor because here it seems that my new domain is not allow to access /dev/hda... Guillaume ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> So I compile new xen and xenolinux images with the matching tools and I have > some troubles. When I boot the first time with new kernels, the boot frozen > after enabling the Real Time Clock Driver. So I removed it from the kernel and > everything went fine. I don''t know if this driver is a problem. I will make a > new try with "Enhanced Real Time Clock Support" enable in the kernel...Odd. I haven''t seen it hang with the RTC driver, but there''s known to be an issue here which is under investigation> Another problem occures when I try to start a new domain. I receive a kernel > panic during the boot. I use the following /etc/xenctl.xml file:Looks like you need to edit /etc/xen-mynewdom to grant read/write physical access to hda5. e.g. "physical grant -phda5 -w" Also, you probably want root_args to be "ro" in your /etc/xenctl.xml to avoid complaints by fsck. The interface to the tools isn''t very user friendly at present, and we''re hoping to fix this... Best, Ian ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> So I compile new xen and xenolinux images with the matching tools and I have > some troubles. When I boot the first time with new kernels, the boot frozen > after enabling the Real Time Clock Driver. So I removed it from the kernel and > everything went fine. I don''t know if this driver is a problem. I will make a > new try with "Enhanced Real Time Clock Support" enable in the kernel...What version of the BK repository are you using (i.e. the top changeset if you do ''bk sccslog | head'' in root directory of repository). The RTC drivers will definitely not work -- most of the drivers in drivers/char WILL NOT WORK. If they aren''t configured by default, they probably shouldn''t be configured. AFAIK drivers/char is the only area where you can configure stuff that will bite you.> Another problem occures when I try to start a new domain. I receive a kernel > panic during the boot. I use the following /etc/xenctl.xml file:The block-device code is in flux right now. We''ll take a look at the problem, but if you want to get up and running as quickly as possible you should be using the xeno-1.1.bk. -- Keir ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Selon Keir Fraser <Keir.Fraser@cl.cam.ac.uk>:> What version of the BK repository are you using (i.e. the top > changeset if you do ''bk sccslog | head'' in root directory of > repository).So I restart the compilation with freshly download xeno and everything works fine now. Is there an ftp site where I can download source? I ask that because my firewall blocks all ports (except http, ssh and ftp) and the access to http is controled (in term of quantities to be downloaded). ---------------------------- zepto:/home/guill/xeno/xeno-1.1.bk# bk sccslog | head ChangeSet 1.538 03/11/05 09:07:18 kaf24@scramble.cl.cam.ac.uk +2 -0 xen_log.c, time.c: Bug fixes. minios should work again now. ChangeSet 1.537 03/10/31 16:39:05 kaf24@scramble.cl.cam.ac.uk +2 -0 current.h, entry.S: Correct stack arithmetic when esp is not a multiple of 4 (eg. in the middle of skanky pcibios code). ----------------------------- I build the system starting by a make in xen directory, after that I build tools and finally I build xenolinux using : make xconfig ARCH=xeno && make dep && make bzImage ARCH=xeno && make modules ARCH=xeno && make modules_install Everything compiled, so I installed all stuff and now everything works. So the previous troubles maybe came from mistmach between xen versions and tools versions... Now I will test it and try to understand internals maybe for porting it on IA64. Thank you very much for your help and for your quick answers. Best, Guillaume ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel