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

Re: [Xen-users] New user question...

Can any body comment on this Please :trying to run ttylinux as a domU with a 
vmlinuz-2.6.11-1.1369_FC4xenU kernel and vmlinuz-2.6.11-1.1369_FC4xen0 as the 
dom0

On Tuesday 09 August 2005 19:32, digz wrote:
> Thanks Mark ,but still couldnt get thro'
>
> this is what i did
> [root@localhost Desktop]# bzcat ttylinux-xen.bz2 >ttylinux
> [root@localhost Desktop]# rm -rf /tftpboot/
> [root@localhost Desktop]# cp ttylinux tftpboot/
>
>
> My stripped conf file looks like this:
>
> kernel = "/boot/vmlinuz-2.6.11-1.1369_FC4xenU"
> memory = 64
> name = "ttylinux1"
> nics = 1
> ip = "1.2.3.4"
> disk = ['file:/tftpboot/ttylinux,sda1,w']
> root = "/dev/sda1 ro"
>
> I dont have a /dev/sda1 partition in my harddisk (the only partition which
> is is a root partition is /dev/hda6 which holds the FC4 install I am using
> as dom0 , am i being dumb in not understanding that the root fs has to be a
> real partition having all the files or /dev/sda1 will do ???..please
> explain the difference between disk and root..
>
>
> when i say:
> [root@localhost ~]# xm create ttyconf1 -c
> Using config file "/etc/xen/ttyconf1".
> Started domain ttylinux1, console on port 9616
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> Linux version 2.6.11-1.1369_FC4xenU (bhcompile@xxxxxxxxxxxxxxxxxxxxxxxxxx)
> (gcc version 4.0.0 20050525 (Red Hat 4.0.0-9)) #1 SMP Thu Jun 2 23:33:51
> EDT 2005
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000004000000 (usable)
> 64MB LOWMEM available.
> Using x86 segment limits to approximate NX protection
> DMI not present.
> IRQ lockup detection disabled
> Allocating PCI resources starting at 04000000 (gap: 04000000:fc000000)
> Built 1 zonelists
> Kernel command line:  ip=1.2.3.4:1.2.3.4::::eth0:off root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Xen reported: 2258.351 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: 60800k/65536k available (1785k kernel code, 4648k reserved, 506k
> data, 156k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok. Security Framework v1.0.0 initialized
> SELinux:  Initializing.
> SELinux:  Starting in permissive mode
> selinux_register_security:  Registering secondary module capability
> Capability LSM initialized as secondary
> Mount-cache hash table entries: 512
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 512K
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> CPU0: Intel(R) Pentium(R) 4 CPU 2.26GHz stepping 07
> per-CPU timeslice cutoff: 1462.80 usecs.
> task migration cache decay timeout: 2 msecs.
> SMP motherboard not detected.
> smpboot_clear_io_apic_irqs
> Brought up 1 CPUs
> softlockup thread 0 started up.
> NET: Registered protocol family 16
> xen_mem: Initialising balloon driver.
> Grant table initialized
> audit: initializing netlink socket (disabled)
> audit(1123595064.572:1): initialized
> Total HugeTLB memory allocated, 0
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> SELinux:  Registering netfilter hooks
> Initializing Cryptographic API
> ksign: Installing public key data
> Loading keyring
> - Added public key 42BD35A990375F72
> - User ID: Red Hat, Inc. (Kernel Module GPG key)
> 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
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> Blkif frontend is using grant tables.
> xen_blk: Initialising virtual block device driver
> xen_net: Initialising virtual ethernet driver.
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> NET: Registered protocol family 2
> IP: routing cache hash table of 256 buckets, 4Kbytes
> TCP established hash table entries: 4096 (order: 4, 65536 bytes)
> TCP bind hash table entries: 4096 (order: 3, 49152 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 156k freed
> Inconsistency detected by ld.so: rtld.c: 1180: dl_main: Assertion `(void *)
> ph->p_vaddr == _rtld_local._dl_sysinfo_dso
>
> PERHAPS I AM AGAIN MAKING A MISTAKE
> thanks and regards
> Digz
> ===========================================================================
>===========
>
> > >         I am trying to run a simple ttylinux as a domU
> > >         ( from sf.net/xen )
> >
> > OK.
> >
> > >         /etc/xen/ttyconf looks like what the Xen 2.0 documentation
> > >         suggests
> > >
> > >         kernel = "/boot/vmlinuz-2.6.11-1.1369_FC4xenU"
> > >         memory = 64
> > >         name = "ttylinux"
> > >         nics=1ip="1.2.3.4"
> > >         disk=['file:/tftpboot,sda1,w'] .................#the Xen doc
> > >         says /path/to/ttylinux/rootfs
> > >         root="/dev/sda1 ro"
> > >
> > >         [root@localhost tftpboot]# xm create ttyconf1 -c vmid=2
> > >         Using config file "/etc/xen/ttyconf1".
> > >         Error: Error creating domain: vbd: Segment not found:
> > >         uname=file:/tftpboot
> > >
> > >         i untarred the ttylinux.bz2 in the empty tftpboot directory
> > > (not for any particular reason)
> > >         [root@localhost ~]# ls /tftpboot
> > >         bin  dev  etc  init  lib  linux-install  loopfs  proc  sbin 
> > > sys sysroot  ttylinux
> >
> > Are you sure the tftpboot directory was empty?  ttylinux.bz2 is not a tar
> > file, just a compressed file - all it should have left behind it the file
> > "ttylinux".  I don't know where the other directories came from :-)
> >
> > The file: directive needs to point to the disk file itself, not to a
> > directory.  Could you please try:
> > disk=['file:/tftpboot/ttylinux,sda1,w']
> >
> > Let us know how you get on!
> >
> > Cheers,
> > Mark
> >
> > >         what is that i need to change ..the domU is from an FC4 Rpm and
> > >         i have not been able to run from a physical device as root fs
> > >         either ,the kernel starts booting and stops at freeing unused
> > >         memory..156K..which from the FAQ i saw was related to initrd
> > >         could not fix it that way.....so just waiting for help
> > >
> > >         Digz
> > >
> > >
> > >
> > > **************** CAUTION - Disclaimer *****************
> > > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> > > solely for the use of the addressee(s). If you are not the intended
> > > recipient, please notify the sender by e-mail and delete the original
> > > message. Further, you are not to copy, disclose, or distribute this
> > > e-mail or its contents to any other person and any such actions are
> > > unlawful. This e-mail may contain viruses. Infosys has taken every
> > > reasonable precaution to minimize this risk, but is not liable for any
> > > damage you may sustain as a result of any virus in this e-mail. You
> > > should carry out your own virus checks before opening the e-mail or
> > > attachment. Infosys reserves the right to monitor and review the
> > > content of all messages sent to or from this e-mail address. Messages
> > > sent to or from this e-mail address may be stored on the Infosys e-mail
> > > system. ***INFOSYS******** End of Disclaimer ********INFOSYS***

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