On Thursday 01 November 2007 23:55:18 shuki k wrote:
> Hello,
>
> I am running:
>
> haifa-suse:~ # uname -a
> Linux haifa-suse 2.6.16.37-0.23-xen #1 SMP Mon Feb 19 14:25:39 UTC 2007
> i686 i686 i386 GNU/Linux
> haifa-suse:~ #
>
> & I try to boot the following VM configuration:
>
> cat /tmp/x1
> name="x1"
> memory=128
> ipaddr = "192.1.1.1"
> vcpus=1
> #uuid="14007590-96bc-e7c1-aa4a-02b4218984a6"
> on_crash="destroy"
> on_poweroff="destroy"
> on_reboot="restart"
> localtime=0
> builder="linux"
> kernel = "/boot/vmlinuz-xen"
> ramdisk = "/boot/initrd-2.6.16.37-0.23-xen"
> #bootloader="/usr/lib/xen/boot/domUloader.py"
> #bootargs="--entry=xvda1:/boot/vmlinuz-xen"
> #extra="TERM=xterm "
> disk=[ 'file:/vm1disk,xvda1,w' ]
> vif=[ 'mac=00:09:b7:da:5f:e1,bridge=xenbr0' ]
> #vfb=["type=vnc,vncunused=1"]
> root="/dev/xvda1 ro"
> extra="1"
> extra = "ignorebiostables max_loop=32 noirqbalance fastboot nousb selinux=0
> ide=nodma apm=off acpi=off xencons=tty128 console=tty128"
> #usb="yes"
From the above config file you've editted it beyond that created by default
using the Xen tools in SLES 10. I'm assuming there is a reason for this. Can
you clarify what it is exactly you're trying to achieve with this VM? (Beyond
getting it to boot I mean) Judging from the extra settings it looks like
you're trying to boot to single user mode in the equivalent of the 'Safe
Settings' from the SUSE grub menu?
> As you can see below it just hang:
>
> haifa-suse:/ # xm create -c /tmp/x1
> Using config file "/tmp/x1".
> Started domain x1
> Linux version 2.6.16.37-0.23-xen (geeko@buildhost) (gcc version
> 4.1.220070115 (prerelease) (SUSE Linux)) #1 SMP Mon Feb 19 14:25:39
> UTC 2007
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000008800000 (usable)
> 0MB HIGHMEM available.
> 136MB LOWMEM available.
> ACPI in unprivileged domain disabled
> Allocating PCI resources starting at 10000000 (gap: 08800000:f7800000)
> Built 1 zonelists
> Kernel command line: root=/dev/xvda1 ro ignorebiostables max_loop=32
> noirqbalance fastboot nousb selinux=0 ide=nodma apm=off acpi=off
The line above confirms what Amos had mentioned. The first extra (1) parameter
for the kernel boot options have been overwritten by the subsequent
parameters.
> xencons=tty128 console=tty128
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Xen reported: 1396.434 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Software IO TLB disabled
> vmalloc area: c9000000-fb7fe000, maxmem 33ffe000
> Memory: 118652k/139264k available (1977k kernel code, 12280k reserved, 674k
> data, 188k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok. Calibrating delay using timer specific routine.. 3493.16 BogoMIPS
> (lpj=6986321)
> Security Framework v1.0.0 initialized
> Mount-cache hash table entries: 512
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 512K
> Checking 'hlt' instruction... OK.
> checking if image is initramfs... it is
> Freeing initrd memory: 6376k freed
> Brought up 1 CPUs
> migration_cost=0
> Grant table initialized
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Subsystem revision 20060127
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> xen_mem: Initialising balloon driver.
> Setting mem allocation to 131072 kiB
> PCI: System does not support PCI
> PCI: System does not support PCI
> audit: initializing netlink socket (disabled)
> audit(1193933070.252:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> rtc: IRQ 8 is not free.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
> (usb?)
> Failed to obtain physical IRQ 6
> floppy0: no floppy controllers found
> RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
> Xen virtual console successfully installed as tty128
> Event-channel device installed.
> mice: PS/2 mouse device common for all mice
> input: PC Speaker as /class/input/input0
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> NET: Registered protocol family 1
> Using IPI No-Shortcut mode
> XENBUS: Device with no driver: device/vbd/51713
> XENBUS: Device with no driver: device/vif/0
> XENBUS: Device with no driver: device/console/0
> Freeing unused kernel memory: 188k freed
> netfront: Initialising virtual ethernet driver.
> netfront: device eth0 has copying receive path.
> Registering block device major 202
> blkfront: xvda1: barriers enabled
> ReiserFS: xvda1: found reiserfs format "3.6" with standard journal
> ReiserFS: xvda1: using ordered data mode
> reiserfs: using flush barriers
> ReiserFS: xvda1: journal params: device xvda1, size 8192, journal first
> block 18, max trans len 1024, max batch 900, max commit age 30, max trans
> age 30
> ReiserFS: xvda1: checking transaction log (xvda1)
> ReiserFS: xvda1: Using r5 hash to sort names
> reiserfs: enabling write barrier flush mode
> eth0 renamed to eth8
> device-mapper: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> loop: loaded (max 64 devices)
>
> haifa-suse:~ # xm list
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 874 2 r-----
> 170.3 sles10 256 1
> 0.0 sles10-1 256 1
> 0.3 x1 5 128 1 -b----
> 6.7 haifa-suse:~ #
>
> I am strugling with it long time..
>
> Any idea how to make it works?
128MB of RAM is really very little for SLES 10 (I know the installer will
likely fall over with this amount of RAM). Can you try increasing this amount
at all? If you're booting to single user mode, are you trying to perform some
disk checks or such on this instance? You could always lomount the disk image
if it's access to the disk that you require.
Jon
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home