Hi, I''ve been playing around with xen 3.0.2 with an intel 6400 on an gigabyte GA-965P-ds4 motherboard with 2Gb of ram, but i had no success in putting it to work. If i install it from source, using an debian sarge, it would compile okey and it would boot ok, but after dom0 i have some problems. If i try to open 2 or 3 ssh sessions to the dom0, it just reboot''s and if login locally in the machine then it just boot now and then in some commands. Upgraded the machine to debian etch and tried the debian packages but it just gives an kernel panic on boot and reboot''s again. The testing repository from debian currently hosts xen with kernel 2.6.17-2. I''ve unable to compile the kernel from testing as it just gives error on udf filesystem and infiniband support Current i''m using kernel 2.6.18 and the machine just run''s smoothly and no problems at all. I would like to put xen to work in here. If anyone has any idea i would glad thanks. regard''s hugo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/6/06, Hugo Brites <hugo@brites.com> wrote:> If i try to open 2 or 3 ssh sessions to the dom0, it just reboot''s and if > login locally in the machine then it just boot now and then in some commands.The things happening in your dom0 seem really strange. Either you have really bad hardware for running xen, or your software install is totally broken. It doesn''t get better when you start mixing debian stable and testing. Xen should work fine with Debian sarge, so no need to upgrade. What do your xen logs and dmesg say? Is your mainboard and CPU listed in any Xen hardware compatibility list?> Upgraded the machine to debian etch and tried the debian packages but it just > gives an kernel panic on boot and reboot''s again. The testing repository from > debian currently hosts xen with kernel 2.6.17-2.You should not mix your self-compiled Xen install with the Debian packages. Go the one way or the other. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris Fanning wrote:> Hi, > >> You should not mix your self-compiled Xen install with the Debian >> packages. Go the one way or the other. > > I compile xen source on debian testing and use the debian package > libc6-xen. > So far no problems mixing that. Or are you refering to something else?It _can_ work to mix some testing packages into stable. But it _can_ also break a lot. In Hugo''s case, on the one hand it isn''t exactly ckear to me what exactly he''s about to do, but it looked like he wanted to use one of the xen-kernels provided by debian together with the self-built Xen from xensources. And that might be not a good idea. I would use the xen hypervisor from debian with the Debian kernels, and the xensource hypervisor with the xensource kernels. Henning (please keep discussion on list, as I didn''t see your response cpoming in there, just to me personally) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On Sunday 08 October 2006 20:39, Henning Sprang wrote:> Chris Fanning wrote: > > Hi, > > > >> You should not mix your self-compiled Xen install with the Debian > >> packages. Go the one way or the other. > > > > I compile xen source on debian testing and use the debian package > > libc6-xen. > > So far no problems mixing that. Or are you refering to something else? > > It _can_ work to mix some testing packages into stable. But it _can_ > also break a lot. > > In Hugo''s case, on the one hand it isn''t exactly ckear to me what > exactly he''s about to do, but it looked like he wanted to use one of the > xen-kernels provided by debian together with the self-built Xen from > xensources. And that might be not a good idea. I would use the xen > hypervisor from debian with the Debian kernels, and the xensource > hypervisor with the xensource kernels. >That was not my idea. The meaning of install the testing the kernel from debian was to see if it would work, just to try to see if the server would became stable with it. I''ve also installed the debian binaries. In response to the other email, the processor does not appear in the compatible processor listing, but in the malling list there is already at least a post that claims to been able to install xen. The motherboard, it it based on chipset intel 965p, ich8r, and i think it''s here that resides the problem. It is used an jmicro controller, which while being ahci compatible it''s not well supported on kernel''s bellow 2.6.18. I''ve tried using an promise sata controller but the gigabyte motherboard doesn''t allow to turn off the onboard sata controller. Right now i''m not at the office, but as soon i get there i will post xen dmesg.> Henning > > (please keep discussion on list, as I didn''t see your response cpoming > in there, just to me personally) > >Regards Hugo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,
I''ve fainally get the server to work. I started an clean install i
after some
bios testing i''ve got the right setting''s. I had to turn off
the ahci from
the sata controller''s.
One thing i noticed. With the ahci enabled the xen-enabled kernel does
booted, and does allowed me to ssh to the system many times, as much as 12
ssh sessions. As soon as I started the xend daemon as soon as I ssh to the
system just rebooted.
I was compiling xen with 4gb memory support as the system currently as 2gb
but will soon be upgraded to 4gb.
I also try to compile with pae support as the system can support an maximum
memory of 8gb. the result''s were the same.
Currently the system is running, with xen-enabled kernel, 4gb memory support.
I''ve ssh into the system 28 time''s in the run, and it does
not rebooted.
Here is xm dmesg, but the system''s will be leaving tomorrow.
the two of them are up and running now.
regard''s
hugo
__ __ _____ ___ ____ ____
\ \/ /___ _ __ |___ / / _ \ |___ \ |___ \
\ // _ \ ''_ \ |_ \| | | | __) |__ __) |
/ \ __/ | | | ___) | |_| | / __/|__/ __/
/_/\_\___|_| |_| |____(_)___(_)_____| |_____|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.2-2 (root@localdomain) (gcc version 3.3.5 (Debian
1:3.3.5-13)) Tue Oct 10 09:32:55 WEST 2006
Latest ChangeSet: Thu Apr 13 15:18:37 2006 +0100 9617:5802713c159b
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009f800 (usable)
(XEN) 000000000009f800 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bfff0000 (usable)
(XEN) 00000000bfff0000 - 00000000bfff3000 (ACPI NVS)
(XEN) 00000000bfff3000 - 00000000c0000000 (ACPI data)
(XEN) 00000000f0000000 - 00000000f4000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3071MB (3145276kB)
(XEN) Xen heap: 10MB (10528kB)
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) PAE disabled.
(XEN) found SMP MP-table at 000f5480
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 GBT ) @ 0x000f6e00
(XEN) ACPI: RSDT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbfff3040
(XEN) ACPI: FADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbfff30c0
(XEN) ACPI: MCFG (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbfff7b80
(XEN) ACPI: MADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @
0xbfff7a80
(XEN) ACPI: SSDT (v001 PmRef Cpu0Ist 0x00003000 INTL 0x20040311) @
0xbfff7c00
(XEN) ACPI: SSDT (v001 PmRef CpuPm 0x00003000 INTL 0x20040311) @
0xbfff8090
(XEN) ACPI: DSDT (v001 GBT AWRDACPI 0x00001000 MSFT 0x0100000c) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2133.368 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMXON is done
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz stepping 06
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) VMXON is done
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz stepping 06
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) Using IPI Shortcut mode
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 03000000->04000000 (740848 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c0476874
(XEN) Init. ramdisk: c0477000->c0618000
(XEN) Phys-Mach map: c0618000->c08ef7c0
(XEN) Start info: c08f0000->c08f1000
(XEN) Page tables: c08f1000->c08f5000
(XEN) Boot stack: c08f5000->c08f6000
(XEN) TOTAL: c0000000->c0c00000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x1a1000, start at 0xc0477000
(XEN) Scrubbing Free RAM: ...............................done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to
Xen).
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi, Well, it seem''s not everything it''s okey. I''ve noticed that if the memory from the motherboard it''s in dual-channel that the system just reboot anyway. I''ve been testing the system with 3Gb memory, so the memory was not on dual-channel. If using 1Gb memory, than the system just run''s fine. Strange. Regards hugo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users