Rainer Ternes
2006-Aug-18 20:14 UTC
[Xen-users] Xen3: Unable to start xenU with Intel Core Duo T2050
I have problems to get Xen 3.0 working on my notebook (FSC AMILO Pro V3205). I already used different operating systems for the xen0 domain, like FC5, SUSE 10.1 und Debian SID (2.6.16-2-xen-smp) but i always run into the same trouble. When I try to start a xenU domain it always hangs and I get this: ----------------------------------------------------------------------- debian37:~# xm create /etc/xen/vmsid1.cfg -c Using config file "/etc/xen/vmsid1.cfg". Started domain vmsid1 Linux version 2.6.16-2-xen-686 (Debian 2.6.16-17) (waldi@debian.org) (gcc versio n 4.0.4 20060630 (prerelease) (Debian 4.0.3-4)) #1 SMP Sun Jul 16 01:42:25 UTC 2 006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008000000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. ACPI in unprivileged domain disabled IRQ lockup detection disabled Built 1 zonelists Kernel command line: root=/dev/sda1 ro 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: 1596.544 MHz processor. 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: b9000000-fb7fe000, maxmem 43ffe000 Memory: 121696k/139264k available (1507k kernel code, 9232k reserved, 527k data, 144k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. ------------------------------------------------------------------------- Nothing else happens in the xenU domain. In "/var/log/messages" in the dom0 domain I get this: ------------------------------------------------------------------------ Aug 18 21:27:39 debian37 kernel: 0: 3529560000000 Aug 18 21:27:39 debian37 kernel: 1: 3529448000000 Aug 18 21:27:43 debian37 kernel: device vif6.0 entered promiscuous mode Aug 18 21:27:43 debian37 kernel: xenbr0: port 3(vif6.0) entering learning state Aug 18 21:27:43 debian37 kernel: xenbr0: topology change detected, propagating Aug 18 21:27:43 debian37 kernel: xenbr0: port 3(vif6.0) entering forwarding state Aug 18 21:27:44 debian37 kernel: printk: 161 messages suppressed. Aug 18 21:27:44 debian37 kernel: Timer ISR/1: Time went backwards: delta=-36922242 delta_cpu=51077758 shadow=918553 off=3534535644052 processed=3534572000000 cpu_processed=3534484000000 Aug 18 21:27:44 debian37 kernel: 0: 3534572000000 Aug 18 21:27:44 debian37 kernel: 1: 3534484000000 ----------------------------------------------------------------------- This is the output of "/proc/cpuinfo": ----------------------------------------------------------------------- processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2050 @ 1.60GHz stepping : 8 cpu MHz : 1596.527 cache size : 2048 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr bogomips : 3993.07 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2050 @ 1.60GHz stepping : 8 cpu MHz : 1596.527 cache size : 2048 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr bogomips : 3993.07 ------------------------------------------------------------------------ I would appreciate any suggestions. Rainer _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Possibly Parallel Threads
- RE: Hotplug scripts not working... xen/ia64 domU stoppedworking
- Bug#639942: Xen "non-bridged traffic is not supported anymore" with bridges
- peth1 not created on boot, now what?
- Can''t get NAT access to internet from Dom U in my small network
- No eth0 device found in domU