stubdomain conf error

stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 1849 bytes --]

Hi there,

i've isntalled xen 3.4 from source on debian lenny and got the following
error when running hvm + stubdomain (hvm only works fine):

+ /bin/sh -c 'xm create -c /etc/xen/stubdoms/xmexample.hvm-dm target=15
memory=32 extra=" -d 15"'
Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
Started domain xmexample.hvm-dm (id=16)
Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
Unexpected error: <type 'exceptions.OSError'>

Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
  File "/usr/sbin/xm", line 7, in <module>
    main.main(sys.argv)
  File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 2979, in main
    _, rc = _run_cmd(cmd, cmd_name, args)
  File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 3003, in
_run_cmd
    return True, cmd(args)
  File "<string>", line 1, in <lambda>
  File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 1360, in
xm_importcommand
    cmd.main([command] + args)
  File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1371, in
main
    do_console(sxp.child_value(config, 'name', -1))
  File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1398, in
do_console
    (p, rv) = os.waitpid(cpid, os.WNOHANG)
OSError: [Errno 10] No child processes


This is the content of /etc/xen/stubdoms/xmexample.hvm-dm:
#This file is autogenerated, edit xmexample.hvm instead!
kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1, vncdisplay=0,
vnclisten=0.0.0.0, vncunused=1']
disk = [
'tap:aio:/home/ggelatti/disk.img,hda:disk,w','tap:aio:/home/ggelatti/debian-501-i386-CD-1.iso,hdc:cdrom,r'
]
vif = [ 'mac=00:16:3e:50:a5:ad' ]


It looks like something is wrong with the generated stub domain file.

Any help?
Thank you.

PS: I've posted on xen-devel cse the log file told me so :P

[-- Attachment #1.2: Type: text/html, Size: 2273 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]

On Wed, 8 Jul 2009, Giorgenes Gelatti wrote:
> Hi there,
> 
> i've isntalled xen 3.4 from source on debian lenny and got the following error when running hvm + stubdomain (hvm only
> works fine):
> 
> + /bin/sh -c 'xm create -c /etc/xen/stubdoms/xmexample.hvm-dm target=15 memory=32 extra=" -d 15"'
> Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
> Started domain xmexample.hvm-dm (id=16)
> Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
> Unexpected error: <type 'exceptions.OSError'>
> 
> Please report to xen-devel@lists.xensource.com
> Traceback (most recent call last):
>   File "/usr/sbin/xm", line 7, in <module>
>     main.main(sys.argv)
>   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 2979, in main
>     _, rc = _run_cmd(cmd, cmd_name, args)
>   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 3003, in _run_cmd
>     return True, cmd(args)
>   File "<string>", line 1, in <lambda>
>   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 1360, in xm_importcommand
>     cmd.main([command] + args)
>   File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1371, in main
>     do_console(sxp.child_value(config, 'name', -1))
>   File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1398, in do_console
>     (p, rv) = os.waitpid(cpid, os.WNOHANG)
> OSError: [Errno 10] No child processes
> 
> 
> This is the content of /etc/xen/stubdoms/xmexample.hvm-dm:
> #This file is autogenerated, edit xmexample.hvm instead!
> kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
> vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1, vncdisplay=0, vnclisten=0.0.0.0, vncunused=1']
> disk = [ 'tap:aio:/home/ggelatti/disk.img,hda:disk,w','tap:aio:/home/ggelatti/debian-501-i386-CD-1.iso,hdc:cdrom,r' ]
> vif = [ 'mac=00:16:3e:50:a5:ad' ]
> 
> 
> It looks like something is wrong with the generated stub domain file.
> 
> Any help?
> Thank you.
> 
> PS: I've posted on xen-devel cse the log file told me so :P
> 

Unfortunately the error message is just the generic error message you
get when the stubdom fails to start; also the generated config file
looks fine.
It is difficult to understand what the problem is with these
informations.

If you want to track down this bug you need to recompile xen and
stubdoms with "debug = y" in Config.mk, then try to start a stubdom
again and send me the output of "xm dmesg".



[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 2732 bytes --]

I've recompiled and rerunned it with debug, the results are attached.
For the sake of reference, the domain id in question was 5.

Thanks in advance.

[]'s

2009/7/9 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Wed, 8 Jul 2009, Giorgenes Gelatti wrote:
> > Hi there,
> >
> > i've isntalled xen 3.4 from source on debian lenny and got the following
> error when running hvm + stubdomain (hvm only
> > works fine):
> >
> > + /bin/sh -c 'xm create -c /etc/xen/stubdoms/xmexample.hvm-dm target=15
> memory=32 extra=" -d 15"'
> > Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
> > Started domain xmexample.hvm-dm (id=16)
> > Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
> > Unexpected error: <type 'exceptions.OSError'>
> >
> > Please report to xen-devel@lists.xensource.com
> > Traceback (most recent call last):
> >   File "/usr/sbin/xm", line 7, in <module>
> >     main.main(sys.argv)
> >   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 2979, in
> main
> >     _, rc = _run_cmd(cmd, cmd_name, args)
> >   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 3003, in
> _run_cmd
> >     return True, cmd(args)
> >   File "<string>", line 1, in <lambda>
> >   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 1360, in
> xm_importcommand
> >     cmd.main([command] + args)
> >   File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1371, in
> main
> >     do_console(sxp.child_value(config, 'name', -1))
> >   File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1398, in
> do_console
> >     (p, rv) = os.waitpid(cpid, os.WNOHANG)
> > OSError: [Errno 10] No child processes
> >
> >
> > This is the content of /etc/xen/stubdoms/xmexample.hvm-dm:
> > #This file is autogenerated, edit xmexample.hvm instead!
> > kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
> > vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
> vncdisplay=0, vnclisten=0.0.0.0, vncunused=1']
> > disk = [
> 'tap:aio:/home/ggelatti/disk.img,hda:disk,w','tap:aio:/home/ggelatti/debian-501-i386-CD-1.iso,hdc:cdrom,r'
> ]
> > vif = [ 'mac=00:16:3e:50:a5:ad' ]
> >
> >
> > It looks like something is wrong with the generated stub domain file.
> >
> > Any help?
> > Thank you.
> >
> > PS: I've posted on xen-devel cse the log file told me so :P
> >
>
> Unfortunately the error message is just the generic error message you
> get when the stubdom fails to start; also the generated config file
> looks fine.
> It is difficult to understand what the problem is with these
> informations.
>
> If you want to track down this bug you need to recompile xen and
> stubdoms with "debug = y" in Config.mk, then try to start a stubdom
> again and send me the output of "xm dmesg".
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 3648 bytes --]

[-- Attachment #2: log.tgz --]
[-- Type: application/x-gzip, Size: 24659 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 2903 bytes --]

Ops, forgot the xm dmesg. attached.


2009/7/9 Giorgenes Gelatti <giorgenes@gmail.com>

> I've recompiled and rerunned it with debug, the results are attached.
> For the sake of reference, the domain id in question was 5.
>
> Thanks in advance.
>
> []'s
>
> 2009/7/9 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> On Wed, 8 Jul 2009, Giorgenes Gelatti wrote:
>> > Hi there,
>> >
>> > i've isntalled xen 3.4 from source on debian lenny and got the following
>> error when running hvm + stubdomain (hvm only
>> > works fine):
>> >
>> > + /bin/sh -c 'xm create -c /etc/xen/stubdoms/xmexample.hvm-dm target=15
>> memory=32 extra=" -d 15"'
>> > Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
>> > Started domain xmexample.hvm-dm (id=16)
>> > Using config file "/etc/xen/stubdoms/xmexample.hvm-dm".
>> > Unexpected error: <type 'exceptions.OSError'>
>> >
>> > Please report to xen-devel@lists.xensource.com
>> > Traceback (most recent call last):
>> >   File "/usr/sbin/xm", line 7, in <module>
>> >     main.main(sys.argv)
>> >   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 2979, in
>> main
>> >     _, rc = _run_cmd(cmd, cmd_name, args)
>> >   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 3003, in
>> _run_cmd
>> >     return True, cmd(args)
>> >   File "<string>", line 1, in <lambda>
>> >   File "usr/lib/python2.5/site-packages/xen/xm/main.py", line 1360, in
>> xm_importcommand
>> >     cmd.main([command] + args)
>> >   File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1371, in
>> main
>> >     do_console(sxp.child_value(config, 'name', -1))
>> >   File "usr/lib/python2.5/site-packages/xen/xm/create.py", line 1398, in
>> do_console
>> >     (p, rv) = os.waitpid(cpid, os.WNOHANG)
>> > OSError: [Errno 10] No child processes
>> >
>> >
>> > This is the content of /etc/xen/stubdoms/xmexample.hvm-dm:
>> > #This file is autogenerated, edit xmexample.hvm instead!
>> > kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
>> > vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
>> vncdisplay=0, vnclisten=0.0.0.0, vncunused=1']
>> > disk = [
>> 'tap:aio:/home/ggelatti/disk.img,hda:disk,w','tap:aio:/home/ggelatti/debian-501-i386-CD-1.iso,hdc:cdrom,r'
>> ]
>> > vif = [ 'mac=00:16:3e:50:a5:ad' ]
>> >
>> >
>> > It looks like something is wrong with the generated stub domain file.
>> >
>> > Any help?
>> > Thank you.
>> >
>> > PS: I've posted on xen-devel cse the log file told me so :P
>> >
>>
>> Unfortunately the error message is just the generic error message you
>> get when the stubdom fails to start; also the generated config file
>> looks fine.
>> It is difficult to understand what the problem is with these
>> informations.
>>
>> If you want to track down this bug you need to recompile xen and
>> stubdoms with "debug = y" in Config.mk, then try to start a stubdom
>> again and send me the output of "xm dmesg".
>>
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 4065 bytes --]

[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 12166 bytes --]

 __  __            _____ _  _    ___  
 \ \/ /___ _ __   |___ /| || |  / _ \ 
  \  // _ \ \047_ \    |_ \| || |_| | | |
  /  \  __/ | | |  ___) |__   _| |_| |
 /_/\_\___|_| |_| |____(_) |_|(_)___/ 
                                      
(XEN) Xen version 3.4.0 (ggelatti@tteng.com.br) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Thu Jul  9 11:59:44 EDT 2009
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: noreboot com1=9600,8n1 console=com1,vga
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e8000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000077eb7f00 (usable)
(XEN)  0000000077eb7f00 - 0000000080000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fed40000 (reserved)
(XEN)  00000000fed45000 - 0000000100000000 (reserved)
(XEN) System RAM: 1918MB (1964376kB)
(XEN) ACPI: RSDP 000E7610, 0014 (r0 COMPAQ)
(XEN) ACPI: RSDT 77EC7F40, 0040 (r1 HPQOEM SLIC-BPC 20070125             0)
(XEN) ACPI: FACP 77EC7FE8, 0074 (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: DSDT 77EC8343, 934E (r1 COMPAQ DSDT_PRJ        1 MSFT  100000E)
(XEN) ACPI: FACS 77EC7F00, 0040
(XEN) ACPI: APIC 77EC805C, 0068 (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: ASF! 77EC80C4, 0063 (r32 COMPAQ HP_RS485        1             0)
(XEN) ACPI: MCFG 77EC8127, 003C (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: TCPA 77EC8163, 0032 (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: SLIC 77EC8195, 0176 (r1 HPQOEM SLIC-BPC        1             0)
(XEN) ACPI: HPET 77EC830B, 0038 (r1 COMPAQ HP_RS485        1             0)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-0000000077eb7000
(XEN) Xen heap: 9MB (9644kB)
(XEN) Domain heap initialised
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0xf808
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[f804,860], pm1x_evt[f800,0]
(XEN) ACPI:                  wakeup_vec[77ec7f0c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:11 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:11 APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 33, 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 low 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) ACPI: HPET id: 0x10028300 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2094.830 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU 0(2) -> Core 0
(XEN) AMD SVM: ASIDs enabled. 
(XEN) HVM: SVM enabled
(XEN) CPU0: AMD K8 machine check reporting enabled.
(XEN) CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping 01
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU1: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU 1(2) -> Core 1
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD SVM: ASIDs enabled. 
(XEN) CPU1: AMD K8 machine check reporting enabled.
(XEN) CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping 01
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: 
(XEN) CPU#0 had -2043992 usecs TSC skew, fixed it up.
(XEN) CPU#1 had 0 usecs TSC skew, fixed it up.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) I/O virtualisation disabled
(XEN) HP Compaq Laptop series board detected. Selecting BIOS-method for reboots.
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) MCA: Use hw thresholding to adjust polling frequency
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xc0100000 memsz=0x279424
(XEN) elf_parse_binary: phdr: paddr=0xc037a000 memsz=0x12735c
(XEN) elf_parse_binary: memory: 0xc0100000 -> 0xc04a135c
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc0100000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc0101000
(XEN) elf_xen_parse_note: HV_START_LOW = 0xf5800000
(XEN) elf_xen_parse_note: FEATURES = "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xc0000000
(XEN)     elf_paddr_offset = 0xc0000000
(XEN)     virt_offset      = 0x0
(XEN)     virt_kstart      = 0xc0100000
(XEN)     virt_kend        = 0xc04a135c
(XEN)     virt_entry       = 0xc0100000
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc04a135c
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (446241 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c04a135c
(XEN)  Init. ramdisk: c04a2000->c13efc00
(XEN)  Phys-Mach map: c13f0000->c15abc84
(XEN)  Start info:    c15ac000->c15ac47c
(XEN)  Page tables:   c15ad000->c15be000
(XEN)  Boot stack:    c15be000->c15bf000
(XEN)  TOTAL:         c0000000->c1800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xc0100000 -> 0xc0379424
(XEN) elf_load_binary: phdr 1 at 0xc037a000 -> 0xc04339e4
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen)
(XEN) Freed 116kB init memory.
(XEN) io_apic.c:2139: 
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) PCI add device 00:14.1
(XEN) platform_hypercall.c:183: Domain 0 says that IO-APIC REGSEL is good
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN) 	_PSS: state_count=4
(XEN) 	State0: 2100MHz 100000mW 100us 9us 0xe8202b0d 0x30d
(XEN) 	State1: 2000MHz 91466mW 100us 9us 0xe8202b4c 0x34c
(XEN) 	State2: 1800MHz 75737mW 100us 9us 0xe8202bca 0x3ca
(XEN) 	State3: 1000MHz 36876mW 100us 9us 0xe8202c82 0x482
(XEN) 	_PSD: num_entries=5 rev=0 domain=0 coord_type=253 num_processors=2
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN) 	_PPC: 0
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN) 	_PCT: descriptor=130, length=12, space_id=127, bit_width=0, bit_offset=0, reserved=0, address=0
(XEN) 	_PSS: state_count=4
(XEN) 	State0: 2100MHz 100000mW 100us 9us 0xe8202b0d 0x30d
(XEN) 	State1: 2000MHz 91466mW 100us 9us 0xe8202b4c 0x34c
(XEN) 	State2: 1800MHz 75737mW 100us 9us 0xe8202bca 0x3ca
(XEN) 	State3: 1000MHz 36876mW 100us 9us 0xe8202c82 0x482
(XEN) 	_PSD: num_entries=5 rev=0 domain=0 coord_type=253 num_processors=2
(XEN) 	_PPC: 0
(XEN) no cpu_id for acpi_id 3
(XEN) no cpu_id for acpi_id 4
(XEN) PCI add device 00:12.0
(XEN) PCI add device 00:13.0
(XEN) PCI add device 00:13.1
(XEN) PCI add device 00:13.2
(XEN) PCI add device 00:13.3
(XEN) PCI add device 00:13.4
(XEN) PCI add device 00:13.5
(XEN) PCI add device 00:14.1
(XEN) PCI add device 3f:00.0
(XEN) PCI add device 07:04.0
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:01.0
(XEN) PCI add device 00:07.0
(XEN) PCI add device 00:14.2
(XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2 of 3)
(XEN) HVM3: HVM Loader
(XEN) HVM3: Detected Xen v3.4.0
(XEN) HVM3: CPU speed is 2095 MHz
(XEN) irq.c:243: Dom3 PCI link 0 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:243: Dom3 PCI link 1 changed 0 -> 10
(XEN) HVM3: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:243: Dom3 PCI link 2 changed 0 -> 11
(XEN) HVM3: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:243: Dom3 PCI link 3 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 3 routed to IRQ5
(XEN) HVM3: pci dev 01:3 INTA->IRQ10
(XEN) HVM3: pci dev 03:0 INTA->IRQ5
(XEN) HVM3: pci dev 04:0 INTA->IRQ5
(XEN) HVM3: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM3: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM3: pci dev 02:0 bar 14 size 00001000: f3000000
(XEN) HVM3: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM3: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM3: pci dev 04:0 bar 14 size 00000100: f3001000
(XEN) HVM3: pci dev 01:1 bar 20 size 00000010: 0000c201
(XEN) HVM3: Multiprocessor initialisation:
(XEN) HVM3:  - CPU0 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3: Testing HVM environment:
(XEN) HVM3:  - REP INSB across page boundaries ... passed
(XEN) HVM3: Passed 1/1 tests
(XEN) HVM3: Writing SMBIOS tables ...
(XEN) HVM3: Loading ROMBIOS ...
(XEN) HVM3: 9788 bytes of ROMBIOS high-memory extensions:
(XEN) HVM3:   Relocating to 0xfc000000-0xfc00263c ... done
(XEN) HVM3: Creating MP tables ...
(XEN) HVM3: Loading Cirrus VGABIOS ...
(XEN) HVM3: Loading PCI Option ROM ...
(XEN) HVM3:  - Manufacturer: http://etherboot.org
(XEN) HVM3:  - Product name: gPXE
(XEN) HVM3: Loading ACPI ...
(XEN) HVM3:  - Lo data: 000ea020-000ea04f
(XEN) HVM3:  - Hi data: fc002800-fc005c9f
(XEN) HVM3: vm86 TSS at fc006000
(XEN) HVM3: BIOS map:
(XEN) HVM3:  c0000-c8fff: VGA BIOS
(XEN) HVM3:  c9000-d57ff: Etherboot ROM
(XEN) HVM3:  eb000-eb13e: SMBIOS tables
(XEN) HVM3:  f0000-fffff: Main BIOS
(XEN) HVM3: Invoking ROMBIOS ...
(XEN) HVM3: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(XEN) HVM3: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $
(XEN) HVM3: Bochs BIOS - build: 06/23/99
(XEN) HVM3: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
(XEN) HVM3: Options: apmbios pcibios eltorito PMM 
(XEN) HVM3: 
(XEN) HVM3: ata0-0: PCHS=8322/16/63 translation=lba LCHS=522/255/63
(XEN) HVM3: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (4096 MBytes)
(XEN) HVM3: IDE time out
(XEN) HVM3: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) HVM3: IDE time out
(XEN) HVM3: 
(XEN) HVM3: 
(XEN) HVM3: 
(XEN) HVM3: Press F12 for boot menu.
(XEN) HVM3: 
(XEN) HVM3: Booting from CD-Rom...
(XEN) HVM3: 646MB medium detected
(XEN) HVM3: Booting from 0000:7c00
(XEN) stdvga.c:151:d3 leaving stdvga
(XEN) HVM4: HVM Loader
(XEN) HVM4: Detected Xen v3.4.0
(XEN) HVM4: CPU speed is 2095 MHz

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

On Thu, 9 Jul 2009, Giorgenes Gelatti wrote:
> Ops, forgot the xm dmesg. attached.
> 

It seems that the stubdom fails to start with a memory problem:

(XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2 of 3)

I have seen this message appearing on the console only recently and
since then stubdoms fail to start.
Do anyone know the reason for this?

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 629 bytes --]

I've read something out there about stubdomains failing with non-PAE xen,
could it have something to do with it?
Where could I enable it in the sources?

Thank you.

2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Thu, 9 Jul 2009, Giorgenes Gelatti wrote:
> > Ops, forgot the xm dmesg. attached.
> >
>
> It seems that the stubdom fails to start with a memory problem:
>
> (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2
> of 3)
>
> I have seen this message appearing on the console only recently and
> since then stubdoms fail to start.
> Do anyone know the reason for this?
>
>

[-- Attachment #1.2: Type: text/html, Size: 978 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:
> I've read something out there about stubdomains failing with non-PAE xen, could it have something to do with it?
> Where could I enable it in the sources?
> 
> Thank you.
> 
> 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>       On Thu, 9 Jul 2009, Giorgenes Gelatti wrote:
>       > Ops, forgot the xm dmesg. attached.
>       >
> 
> It seems that the stubdom fails to start with a memory problem:
> 
> (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0 (2 of 3)
> 
> I have seen this message appearing on the console only recently and
> since then stubdoms fail to start.
> Do anyone know the reason for this?
> 

The patch I just sent should fix the issue.

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]

To which version should I apply the patch?
My version (3.4) doesn't have the lines in the patch.
I tryed adding the lines to the stubdom-dm but it didn't work.
Should I get the "unstable" version?

Thank you.

[]'s

2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:
> > I've read something out there about stubdomains failing with non-PAE xen,
> could it have something to do with it?
> > Where could I enable it in the sources?
> >
> > Thank you.
> >
> > 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> >       On Thu, 9 Jul 2009, Giorgenes Gelatti wrote:
> >       > Ops, forgot the xm dmesg. attached.
> >       >
> >
> > It seems that the stubdom fails to start with a memory problem:
> >
> > (XEN) memory.c:128:d0 Could not allocate order=9 extent: id=1 memflags=0
> (2 of 3)
> >
> > I have seen this message appearing on the console only recently and
> > since then stubdoms fail to start.
> > Do anyone know the reason for this?
> >
>
> The patch I just sent should fix the issue.
>

[-- Attachment #1.2: Type: text/html, Size: 1623 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:
> To which version should I apply the patch?
> My version (3.4) doesn't have the lines in the patch.
> I tryed adding the lines to the stubdom-dm but it didn't work.

Uhm.. I couldn't reproduce the issue on 3.4 testing.
If you are using 3.4, which CS is the tip of you xen and qemu trees?

> Should I get the "unstable" version?

The "unstable" version works for me at the moment, you can give it a
try.

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 667 bytes --]

#xen-3.4.0> cat .hg_archival.txt
repo: ab039beb22dc9d53f224a5ef2ef88d534b561898
node: d2a5c477c647dc7b3f51a761ab481ed80d5a1771


2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:
> > To which version should I apply the patch?
> > My version (3.4) doesn't have the lines in the patch.
> > I tryed adding the lines to the stubdom-dm but it didn't work.
>
> Uhm.. I couldn't reproduce the issue on 3.4 testing.
> If you are using 3.4, which CS is the tip of you xen and qemu trees?
>
> > Should I get the "unstable" version?
>
> The "unstable" version works for me at the moment, you can give it a
> try.
>

[-- Attachment #1.2: Type: text/html, Size: 1099 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]

Well, I've just find out that I was missing a basic step: running
fs-backend.
I couldn't run the stubdomain running it either.
Now i'm trying with xen-unstable and I'm getting this error:

# xm create xmexample.hvm-stubdom
Using config file "./xmexample.hvm-stubdom".
Error: Device 768 (vbd) could not be connected.
File /home/ggelatti/disk.img is loopback-mounted through /dev/loop2,
which is mounted in a guest domain,
and so cannot be mounted now.

Any thoughts on that?
Tks again.

2009/7/13 Giorgenes Gelatti <giorgenes@gmail.com>

> #xen-3.4.0> cat .hg_archival.txt
> repo: ab039beb22dc9d53f224a5ef2ef88d534b561898
> node: d2a5c477c647dc7b3f51a761ab481ed80d5a1771
>
>
> 2009/7/10 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
>> On Fri, 10 Jul 2009, Giorgenes Gelatti wrote:
>> > To which version should I apply the patch?
>> > My version (3.4) doesn't have the lines in the patch.
>> > I tryed adding the lines to the stubdom-dm but it didn't work.
>>
>> Uhm.. I couldn't reproduce the issue on 3.4 testing.
>> If you are using 3.4, which CS is the tip of you xen and qemu trees?
>>
>> > Should I get the "unstable" version?
>>
>> The "unstable" version works for me at the moment, you can give it a
>> try.
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2012 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

On Tue, 14 Jul 2009, Giorgenes Gelatti wrote:
> Well, I've just find out that I was missing a basic step: running fs-backend.
> I couldn't run the stubdomain running it either.
> Now i'm trying with xen-unstable and I'm getting this error:
> 
> # xm create xmexample.hvm-stubdom
> Using config file "./xmexample.hvm-stubdom".
> Error: Device 768 (vbd) could not be connected.
> File /home/ggelatti/disk.img is loopback-mounted through /dev/loop2,
> which is mounted in a guest domain,
> and so cannot be mounted now.
> 
> Any thoughts on that?
> Tks again.
> 

Try unmouting /dev/loop2, it probably remained mounted from one of your
previous failed attempts.

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 1723 bytes --]

I think it isn't the case. mount and losetup don't show anything.
I looks like it just happens the first time I run xm create.
If I try it again it "works".
Well, the first time it "worked" it freezed the whole system actually.
After reboot, I issued xm create again, which caused the same error again.
I rerunned it and this time it created the VM pair: the hvm and the
stubdomain.
Connecting to the VNC interface works, but only shows a black screen.
Running xm list shows the stubdomain isn't running at all:

# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0   252     2     r-----
204.0
debstubhvm                                   3   128     1     r-----
9356.5
debstubhvm-dm                                4    32     1     -b----
0.0

the stubdomain status started with "p", then I unpaused it manually and it
went into "b" forever.

Any clue?
Thanks for your help.

2009/7/14 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Tue, 14 Jul 2009, Giorgenes Gelatti wrote:
> > Well, I've just find out that I was missing a basic step: running
> fs-backend.
> > I couldn't run the stubdomain running it either.
> > Now i'm trying with xen-unstable and I'm getting this error:
> >
> > # xm create xmexample.hvm-stubdom
> > Using config file "./xmexample.hvm-stubdom".
> > Error: Device 768 (vbd) could not be connected.
> > File /home/ggelatti/disk.img is loopback-mounted through /dev/loop2,
> > which is mounted in a guest domain,
> > and so cannot be mounted now.
> >
> > Any thoughts on that?
> > Tks again.
> >
>
> Try unmouting /dev/loop2, it probably remained mounted from one of your
> previous failed attempts.
>
>

[-- Attachment #1.2: Type: text/html, Size: 2456 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

On Tue, 14 Jul 2009, Giorgenes Gelatti wrote:
> I think it isn't the case. mount and losetup don't show anything.
> I looks like it just happens the first time I run xm create.
> If I try it again it "works".
> Well, the first time it "worked" it freezed the whole system actually.
> After reboot, I issued xm create again, which caused the same error again.
> I rerunned it and this time it created the VM pair: the hvm and the stubdomain.
> Connecting to the VNC interface works, but only shows a black screen.
> Running xm list shows the stubdomain isn't running at all:
> 
> # xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0   252     2     r-----    204.0
> debstubhvm                                   3   128     1     r-----   9356.5
> debstubhvm-dm                                4    32     1     -b----      0.0
> 
> the stubdomain status started with "p", then I unpaused it manually and it went into "b" forever.
> 
> Any clue?

It is hard to say with these informations.
What does the xm dmesg say?
Could you also send the qemu and stubdom logs?

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]

Attached.

tks again

[]'s

2009/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Tue, 14 Jul 2009, Giorgenes Gelatti wrote:
> > I think it isn't the case. mount and losetup don't show anything.
> > I looks like it just happens the first time I run xm create.
> > If I try it again it "works".
> > Well, the first time it "worked" it freezed the whole system actually.
> > After reboot, I issued xm create again, which caused the same error
> again.
> > I rerunned it and this time it created the VM pair: the hvm and the
> stubdomain.
> > Connecting to the VNC interface works, but only shows a black screen.
> > Running xm list shows the stubdomain isn't running at all:
> >
> > # xm list
> > Name                                        ID   Mem VCPUs      State
> Time(s)
> > Domain-0                                     0   252     2     r-----
> 204.0
> > debstubhvm                                   3   128     1     r-----
> 9356.5
> > debstubhvm-dm                                4    32     1
> -b----      0.0
> >
> > the stubdomain status started with "p", then I unpaused it manually and
> it went into "b" forever.
> >
> > Any clue?
>
> It is hard to say with these informations.
> What does the xm dmesg say?
> Could you also send the qemu and stubdom logs?

[-- Attachment #1.2: Type: text/html, Size: 1954 bytes --]

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 5622 bytes --]

 __  __            _____  ____                     _        _     _      
 \ \/ /___ _ __   |___ / | ___|    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \    |_ \ |___ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.5-unstable (ggelatti@tteng.com.br) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) Tue Jul 14 08:26:21 EDT 2009
(XEN) Latest ChangeSet: Mon Jul 13 12:35:34 2009 +0100 19932:c0cb307d927f
(XEN) Command line: noreboot com1=9600,8n1 console=com1,vga dom0_mem=256M
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e8000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000077eb7f00 (usable)
(XEN)  0000000077eb7f00 - 0000000080000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fed40000 (reserved)
(XEN)  00000000fed45000 - 0000000100000000 (reserved)
(XEN) System RAM: 1918MB (1964376kB)
(XEN) ACPI: RSDP 000E7610, 0014 (r0 COMPAQ)
(XEN) ACPI: RSDT 77EC7F40, 0040 (r1 HPQOEM SLIC-BPC 20070125             0)
(XEN) ACPI: FACP 77EC7FE8, 0074 (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: DSDT 77EC8343, 934E (r1 COMPAQ DSDT_PRJ        1 MSFT  100000E)
(XEN) ACPI: FACS 77EC7F00, 0040
(XEN) ACPI: APIC 77EC805C, 0068 (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: ASF! 77EC80C4, 0063 (r32 COMPAQ HP_RS485        1             0)
(XEN) ACPI: MCFG 77EC8127, 003C (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: TCPA 77EC8163, 0032 (r1 COMPAQ HP_RS485        1             0)
(XEN) ACPI: SLIC 77EC8195, 0176 (r1 HPQOEM SLIC-BPC        1             0)
(XEN) ACPI: HPET 77EC830B, 0038 (r1 COMPAQ HP_RS485        1             0)
(XEN) Xen heap: 9MB (9796kB)
(XEN) Domain heap initialised
(XEN) Processor #0 15:11 APIC version 16
(XEN) Processor #1 15:11 APIC version 16
(XEN) IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2094.825 MHz processor.
(XEN) AMD SVM: ASIDs enabled. 
(XEN) HVM: SVM enabled
(XEN) CPU0: AMD K8 machine check reporting enabled.
(XEN) CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping 01
(XEN) Booting processor 1/1 eip 8c000
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD SVM: ASIDs enabled. 
(XEN) CPU1: AMD K8 machine check reporting enabled.
(XEN) CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping 01
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: 
(XEN) CPU#0 had -528663 usecs TSC skew, fixed it up.
(XEN) CPU#1 had 0 usecs TSC skew, fixed it up.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) HP Compaq Laptop series board detected. Selecting BIOS-method for reboots.
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1948000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000038000000->000000003c000000 (49152 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c1000000->c1948000
(XEN)  Init. ramdisk: c1948000->c2895c00
(XEN)  Phys-Mach map: c2896000->c28d6000
(XEN)  Start info:    c28d6000->c28d647c
(XEN)  Page tables:   c28d7000->c28f2000
(XEN)  Boot stack:    c28f2000->c28f3000
(XEN)  TOTAL:         c0000000->c2c00000
(XEN)  ENTRY ADDRESS: c170c000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: ................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 124kB init memory.
(XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0
(XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0
(XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=17, old_irq=17, new_irq=17
(XEN) ioapic_guest_write: old_entry=0000a9b0, new_entry=0001a9b0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
(XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16
(XEN) ioapic_guest_write: old_entry=0000a9a8, new_entry=0001a9a8
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) tmem: must specify tmem parameter on xen boot line

[-- Attachment #3: logs-stub.tar.gz --]
[-- Type: application/x-gzip, Size: 8478 bytes --]

[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Stefano Stabellini]

On Wed, 15 Jul 2009, Giorgenes Gelatti wrote:
> Attached.
> 
> tks again
> 

Unfortunately there is nothing on the logs: did you compile xen and
stubdom with debug = y?

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 344 bytes --]

Xen is crashing on boot with debug = y :(
It gives a "FATAL PAGE FAULT" and kernel panics.


2009/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>

> On Wed, 15 Jul 2009, Giorgenes Gelatti wrote:
> > Attached.
> >
> > tks again
> >
>
> Unfortunately there is nothing on the logs: did you compile xen and
> stubdom with debug = y?
>
>

[-- Attachment #1.2: Type: text/html, Size: 671 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: stubdomain conf error

[Giorgenes Gelatti]

[-- Attachment #1.1: Type: text/plain, Size: 919 bytes --]

Hi,

Tks for all the help.
It's seems like i've being failing miserably to use the kernels that comes
with the xen source.
I've tryed different versions: 3.4.0 stable, 3.5-unstable, and 3.4.1-rc7.
All kernels gave me different errors, some crashed with the debug options
on.
But the setup that ended up working for me was xen 3.5.1-rc7 with kernel
3.6.26-2 from the debian packages. The one released with the xen source
didn't work for me.

Now I've successfully ran an hvm with a stubdomain.

tks.

2009/7/16 Giorgenes Gelatti <giorgenes@gmail.com>

> Xen is crashing on boot with debug = y :(
> It gives a "FATAL PAGE FAULT" and kernel panics.
>
>
> 2009/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
>> On Wed, 15 Jul 2009, Giorgenes Gelatti wrote:
>>
>> > Attached.
>> >
>> > tks again
>> >
>>
>> Unfortunately there is nothing on the logs: did you compile xen and
>> stubdom with debug = y?
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 1616 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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