Re: [Xen-devel] pvh+vcpus startup issue
On 28/02/18 9:35 PM, Juergen Gross wrote: On 28/02/18 09:27, Roger Pau Monné wrote: On Wed, Feb 28, 2018 at 01:34:31PM +1300, x...@randomwebstuff.com wrote: Regards, Peter http://ri.mu Startups start here. Hosting. DNS. Offsite backups. Monitoring. Email. On 27/02/18 12:42 AM, Juergen Gross wrote: On 22/02/18 21:38, x...@randomwebstuff.com wrote: On 22/02/18 6:35 PM, Juergen Gross wrote: On 22/02/18 05:37, x...@randomwebstuff.com wrote: Hi. I have a domU. Its params file has: vcpus = 8. It will start with pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6 or 5. It does start with vcpus = 4. I diffed the xl -v create logs, no difference there on either startup. I grabbed the domU console output for a vcpus = 5 start (attached). It dies right after: Dies as in crashes? Or simply gets stuck and there's no further output? domU console: [0.001000] cpu 0 spinlock event irq 5 [0.001000] Performance Events: unsupported p6 CPU model 23 no PMU driver, software events only. [0.001000] Hierarchical SRCU implementation. [0.001249] smp: Bringing up secondary CPUs ... [0.001582] installing Xen timer for CPU 1 [0.001642] x86: Booting SMP configuration: [0.001653] node #0, CPUs: #1 [0.003157] cpu 1 spinlock event irq 11 [0.003305] installing Xen timer for CPU 2 [0.003385] #2 [0.005152] cpu 2 spinlock event irq 17 [0.005311] installing Xen timer for CPU 3 [0.005375] #3 [0.007107] cpu 3 spinlock event irq 23 [0.007341] installing Xen timer for CPU 4 Which exact kernel version is this, and can you also send the .config Linux kernel file? Xen domU params file: cat /home/users/ot.glenn/params kernel = "/home/users/ot.glenn/linux" memory = 2000 swap = 128 This is not a xl option. name = "ot.glenn" ipaddr = "72.x.x.x" Same here. disk = [ 'phy:/dev/users/ot.glenn+centos6-x86_64-4.ext3,xvda1,w', 'phy:/dev/users/ot.glenn+swapfs.swp,xvda9,w' ] root = "/dev/xvda1 ro" restart = 'onreboot' console = 50089 And here. type = "pvh" vcpus = 5 vif = [ 'mac=aa:00:0b:67:50:64,bridge=br0' ] Please add: on_crash="preserve" to your domain config file and after the domain crashed call: /usr/lib/xen/bin/xenctx -C -s -a Juergen I commented out the non-standard options from the params file. (That did not appear to change any behavior). After the vm is started it just quits/exits. When I look at the domU console the last thing I see is: [ 0.007151] cpu 3 spinlock event irq 23 [ 0.007341] installing Xen timer for CPU 4 The domU stays in the xl list output after the on_crash preserve option is added and I see this: [root@host713 ~]# /usr/lib/xen/bin/xenctx -C -s /opt/xen/kernels/4.14.22-rh30-20180225201441.xenU.x86_64 -a 8 vcpu0 offline vcpu1 offline vcpu2 offline vcpu3 offline vcpu4: rip: 810013a8 flags: 0012 nz a rsp: 82603e18 rax: rcx: rdx: 0040 rbx: 0040 rsi: 82603e24 rdi: 0002 rbp: r8: r9: r10: 88007a418248 r11: 001800ff r12: r13: r14: 82d03680 r15: c938fe78 cs: 0010 ss: ds: es: fs: @ gs: @ 88007a40/ +0x7a40/ cr0: 80050033 cr2: cr3: 02624000 cr4: 000406a0 dr0: dr1: dr2: dr3: dr6: 0ff0 dr7: 0400 Code (instr addr 810013a8) cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 0f 01 c1 cc cc cc cc cc cc cc cc cc cc Config to the domU kernel is attached. Since this is pvh I am not able to try too many different kernels (e.g. an old 2.6 or 3.0 kernel or even a 4.4 kernel) since those are not supported by pvh. # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.14.22 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_MMU=y CONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
Re: [Xen-devel] pvh+vcpus startup issue
On 28/02/18 09:27, Roger Pau Monné wrote: > On Wed, Feb 28, 2018 at 01:34:31PM +1300, x...@randomwebstuff.com wrote: >> >> Regards, Peter >> http://ri.mu Startups start here. Hosting. DNS. Offsite backups. >> Monitoring. Email. >> >> On 27/02/18 12:42 AM, Juergen Gross wrote: >>> On 22/02/18 21:38, x...@randomwebstuff.com wrote: On 22/02/18 6:35 PM, Juergen Gross wrote: > On 22/02/18 05:37, x...@randomwebstuff.com wrote: >> Hi. I have a domU. Its params file has: vcpus = 8. It will start with >> pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6 >> or 5. It does start with vcpus = 4. >> >> I diffed the xl -v create logs, no difference there on either startup. >> >> I grabbed the domU console output for a vcpus = 5 start (attached). It >> dies right after: > > Dies as in crashes? Or simply gets stuck and there's no further output? > >> domU console: >> >> [0.001000] cpu 0 spinlock event irq 5 >> [0.001000] Performance Events: unsupported p6 CPU model 23 no PMU >> driver, software events only. >> [0.001000] Hierarchical SRCU implementation. >> [0.001249] smp: Bringing up secondary CPUs ... >> [0.001582] installing Xen timer for CPU 1 >> [0.001642] x86: Booting SMP configuration: >> [0.001653] node #0, CPUs: #1 >> [0.003157] cpu 1 spinlock event irq 11 >> [0.003305] installing Xen timer for CPU 2 >> [0.003385] #2 >> [0.005152] cpu 2 spinlock event irq 17 >> [0.005311] installing Xen timer for CPU 3 >> [0.005375] #3 >> [0.007107] cpu 3 spinlock event irq 23 >> [0.007341] installing Xen timer for CPU 4 > > Which exact kernel version is this, and can you also send the .config > Linux kernel file? > >> Xen domU params file: >> >> cat /home/users/ot.glenn/params >> kernel = "/home/users/ot.glenn/linux" >> memory = 2000 >> swap = 128 > > This is not a xl option. > >> name = "ot.glenn" >> ipaddr = "72.x.x.x" > > Same here. > >> disk = [ 'phy:/dev/users/ot.glenn+centos6-x86_64-4.ext3,xvda1,w', >> 'phy:/dev/users/ot.glenn+swapfs.swp,xvda9,w' ] >> root = "/dev/xvda1 ro" >> restart = 'onreboot' >> console = 50089 > > And here. > >> type = "pvh" >> vcpus = 5 >> vif = [ 'mac=aa:00:0b:67:50:64,bridge=br0' ] Please add: on_crash="preserve" to your domain config file and after the domain crashed call: /usr/lib/xen/bin/xenctx -C -s -a Juergen ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] pvh+vcpus startup issue
On Wed, Feb 28, 2018 at 01:34:31PM +1300, x...@randomwebstuff.com wrote: > > Regards, Peter > http://ri.mu Startups start here. Hosting. DNS. Offsite backups. > Monitoring. Email. > > On 27/02/18 12:42 AM, Juergen Gross wrote: > > On 22/02/18 21:38, x...@randomwebstuff.com wrote: > > > On 22/02/18 6:35 PM, Juergen Gross wrote: > > > > On 22/02/18 05:37, x...@randomwebstuff.com wrote: > > > > > Hi. I have a domU. Its params file has: vcpus = 8. It will start > > > > > with > > > > > pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or > > > > > 6 > > > > > or 5. It does start with vcpus = 4. > > > > > > > > > > I diffed the xl -v create logs, no difference there on either startup. > > > > > > > > > > I grabbed the domU console output for a vcpus = 5 start (attached). > > > > > It > > > > > dies right after: Dies as in crashes? Or simply gets stuck and there's no further output? > domU console: > > [0.001000] cpu 0 spinlock event irq 5 > [0.001000] Performance Events: unsupported p6 CPU model 23 no PMU driver, > software events only. > [0.001000] Hierarchical SRCU implementation. > [0.001249] smp: Bringing up secondary CPUs ... > [0.001582] installing Xen timer for CPU 1 > [0.001642] x86: Booting SMP configuration: > [0.001653] node #0, CPUs: #1 > [0.003157] cpu 1 spinlock event irq 11 > [0.003305] installing Xen timer for CPU 2 > [0.003385] #2 > [0.005152] cpu 2 spinlock event irq 17 > [0.005311] installing Xen timer for CPU 3 > [0.005375] #3 > [0.007107] cpu 3 spinlock event irq 23 > [0.007341] installing Xen timer for CPU 4 Which exact kernel version is this, and can you also send the .config Linux kernel file? > Xen domU params file: > > cat /home/users/ot.glenn/params > kernel = "/home/users/ot.glenn/linux" > memory = 2000 > swap = 128 This is not a xl option. > name = "ot.glenn" > ipaddr = "72.x.x.x" Same here. > disk = [ 'phy:/dev/users/ot.glenn+centos6-x86_64-4.ext3,xvda1,w', > 'phy:/dev/users/ot.glenn+swapfs.swp,xvda9,w' ] > root = "/dev/xvda1 ro" > restart = 'onreboot' > console = 50089 And here. > type = "pvh" > vcpus = 5 > vif = [ 'mac=aa:00:0b:67:50:64,bridge=br0' ] Thanks, Roger. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] pvh+vcpus startup issue
Regards, Peter
http://ri.mu Startups start here. Hosting. DNS. Offsite backups.
Monitoring. Email.
On 27/02/18 12:42 AM, Juergen Gross wrote:
On 22/02/18 21:38, x...@randomwebstuff.com wrote:
On 22/02/18 6:35 PM, Juergen Gross wrote:
On 22/02/18 05:37, x...@randomwebstuff.com wrote:
Hi. I have a domU. Its params file has: vcpus = 8. It will start with
pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6
or 5. It does start with vcpus = 4.
I diffed the xl -v create logs, no difference there on either startup.
I grabbed the domU console output for a vcpus = 5 start (attached). It
dies right after:
[ 0.007110] cpu 3 spinlock event irq 23
[ 0.007336] installing Xen timer for CPU 4
Can you please post the hypervisor log ("xl dmesg")?
Juergen
Attached.
Can you please try again with "loglvl=all guest_loglvl=all" in the
hypervisor's boot parameters and after the pvh guest failing?
Juergen
I added those options. I am attaching a log of 1) xl create -v 2) domU
console 3) xl dmesg 4) params file.
Reminder this issue seems to be only on certain CPUs. e.g. this one is
on a 2xE5420 host.
xl create -v log:
Parsing config from /home/users/ot.glenn/params
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 ro",
features=""
domainbuilder: detail: xc_dom_kernel_file: filename="/home/users/ot.glenn/linux"
domainbuilder: detail: xc_dom_malloc_filemap: 9325 kB
domainbuilder: detail: xc_dom_malloc: 32 MB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x91b5aa -> 0x20ed940
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.10, caps xen-3.0-x86_64
xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ...
domainbuilder: detail: loader probe OK
xc: detail: ELF: phdr: paddr=0x100 memsz=0x1522000
xc: detail: ELF: phdr: paddr=0x260 memsz=0x5c5000
xc: detail: ELF: phdr: paddr=0x2bc5000 memsz=0x21d18
xc: detail: ELF: phdr: paddr=0x2be7000 memsz=0x1cf000
xc: detail: ELF: memory: 0x100 -> 0x2db6000
xc: detail: ELF: note: GUEST_OS = "linux"
xc: detail: ELF: note: GUEST_VERSION = "2.6"
xc: detail: ELF: note: XEN_VERSION = "xen-3.0"
xc: detail: ELF: note: VIRT_BASE = 0x8000
xc: detail: ELF: note: INIT_P2M = 0x80
xc: detail: ELF: note: ENTRY = 0x82be7180
xc: detail: ELF: note: HYPERCALL_PAGE = 0x81001000
xc: detail: ELF: note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
xc: detail: ELF: note: SUPPORTED_FEATURES = 0x801
xc: detail: ELF: note: PAE_MODE = "yes"
xc: detail: ELF: note: LOADER = "generic"
xc: detail: ELF: note: unknown (0xd)
xc: detail: ELF: note: SUSPEND_CANCEL = 0x1
xc: detail: ELF: note: MOD_START_PFN = 0x1
xc: detail: ELF: note: HV_START_LOW = 0x8000
xc: detail: ELF: note: PADDR_OFFSET = 0
xc: detail: ELF: note: PHYS32_ENTRY = 0x1000360
xc: detail: ELF: addresses:
xc: detail: virt_base= 0x8000
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0x8000
xc: detail: virt_kstart = 0x8100
xc: detail: virt_kend= 0x82db6000
xc: detail: virt_entry = 0x82be7180
xc: detail: p2m_base = 0x80
domainbuilder: detail: xc_dom_parse_elf_kernel: hvm-3.0-x86_32:
0x8100 -> 0x82db6000
domainbuilder: detail: xc_dom_mem_init: mem 2000 MB, pages 0x7d000 pages, 4k
each
domainbuilder: detail: xc_dom_mem_init: 0x7d000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: xc_dom_malloc: 4000 kB
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail: 4KB PAGES: 0x
xc: detail: 2MB PAGES: 0x01e8
xc: detail: 1GB PAGES: 0x0001
S3 disabled
S4 disabled
CONV disabled
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_malloc: 178 kB
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x1000+0x1db6 at 0x7fd8d1521000
domainbuilder: detail: xc_dom_alloc_segment: kernel :
0x8100 -> 0x82db6000 (pfn 0x1000 + 0x1db6 pages)
xc: detail: ELF: phdr 0 at 0x7fd8d1521000 -> 0x7fd8d2a43000
xc: detail: ELF: phdr 1 at 0x7fd8d2b21000 -> 0x7fd8d30e6000
xc: detail: ELF: phdr 2 at 0x7fd8d30e6000 -> 0x7fd8d3107d18
xc: detail: ELF: phdr 3 at 0x7fd8d3108000 -> 0x7fd8d320e000
domainbuilder: detail: xc_dom_load_acpi: 64 bytes at address fffc0
domainbuilder: detail: xc_dom_load_acpi: 4096 bytes at address fc00
domainbuilder: detail: xc_dom_load_acpi: 28672 bytes at address fc001000
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x2db6+0x1
at 0x7fd8d7c4f000
domainbuilder: detail: xc_dom_alloc_segment: HVM start info :
0x82db6000 -> 0x82db7000 (pfn 0x2db6 + 0x1 pages)
domainbuilder: detail: alloc_pgtables_hvm: doing nothing
Re: [Xen-devel] pvh+vcpus startup issue
On 22/02/18 21:38, x...@randomwebstuff.com wrote:
>
> On 22/02/18 6:35 PM, Juergen Gross wrote:
>> On 22/02/18 05:37, x...@randomwebstuff.com wrote:
>>> Hi. I have a domU. Its params file has: vcpus = 8. It will start with
>>> pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6
>>> or 5. It does start with vcpus = 4.
>>>
>>> I diffed the xl -v create logs, no difference there on either startup.
>>>
>>> I grabbed the domU console output for a vcpus = 5 start (attached). It
>>> dies right after:
>>>
>>> [ 0.007110] cpu 3 spinlock event irq 23
>>> [ 0.007336] installing Xen timer for CPU 4
>> Can you please post the hypervisor log ("xl dmesg")?
>>
>>
>> Juergen
>
> Attached.
Can you please try again with "loglvl=all guest_loglvl=all" in the
hypervisor's boot parameters and after the pvh guest failing?
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] pvh+vcpus startup issue
On 22/02/18 6:35 PM, Juergen Gross wrote:
On 22/02/18 05:37, x...@randomwebstuff.com wrote:
Hi. I have a domU. Its params file has: vcpus = 8. It will start with
pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6
or 5. It does start with vcpus = 4.
I diffed the xl -v create logs, no difference there on either startup.
I grabbed the domU console output for a vcpus = 5 start (attached). It
dies right after:
[ 0.007110] cpu 3 spinlock event irq 23
[ 0.007336] installing Xen timer for CPU 4
Can you please post the hypervisor log ("xl dmesg")?
Juergen
Attached.
Regards, Peter
# xl dmesg
(XEN) parameter "cpufreq" has invalid value "xen", rc=-22!
Xen 4.10.0
(XEN) Xen version 4.10.0 (bu...@r.com) (gcc (GCC) 4.4.7 20120313 (Red Hat
4.4.7-18)) debug=n Sun Jan 7 23:45:02 UTC 2018
(XEN) Latest ChangeSet:
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: dom0_mem=2048M cpufreq=xen dom0_max_vcpus=2 dom0_vcpus_pin
loglvl=info vcpu_migration_delay=1000
(XEN) Xen image load base address: 0
(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 6 MBR signatures
(XEN) Found 6 EDD information structures
(XEN) Disabling Vixen because we are not running under Xen
(XEN) Xen-e820 RAM map:
(XEN) - 0009c000 (usable)
(XEN) 0009c000 - 000a (reserved)
(XEN) 000cc000 - 000d (reserved)
(XEN) 000e4000 - 0010 (reserved)
(XEN) 0010 - cff5 (usable)
(XEN) cff5 - cff65000 (ACPI data)
(XEN) cff65000 - cff8 (ACPI NVS)
(XEN) cff8 - d000 (reserved)
(XEN) e000 - f000 (reserved)
(XEN) fec0 - fec1 (reserved)
(XEN) fee0 - fee01000 (reserved)
(XEN) ff00 - 0001 (reserved)
(XEN) 0001 - 0010 (usable)
(XEN) New Xen image base address: 0xcf80
(XEN) ACPI: RSDP 000F6110, 0014 (r0 PTLTD )
(XEN) ACPI: RSDT CFF5D06E, 0060 (r1 SMCI SMCISLP2 604 LTP0)
(XEN) ACPI: FACP CFF644C2, 0074 (r1 INTEL TUMWATER 604 PTL 3)
(XEN) ACPI: DSDT CFF6003A, 4488 (r1 Intel BLAKFORD 604 MSFT 10E)
(XEN) ACPI: FACS CFF65FC0, 0040
(XEN) ACPI: APIC CFF64536, 00C8 (r1 PTLTDAPIC604 LTP0)
(XEN) ACPI: MCFG CFF645FE, 003C (r1 PTLTDMCFG604 LTP0)
(XEN) ACPI: BOOT CFF6463A, 0028 (r1 PTLTD $SBFTBL$ 604 LTP1)
(XEN) ACPI: SPCR CFF64662, 0050 (r1 PTLTD $UCRTBL$ 604 PTL 1)
(XEN) ACPI: SLIC CFF646B2, 0176 (r1 SMCI SMCISLP2 604 LTP0)
(XEN) ACPI: SSDT CFF5E941, 025F (r1 PmRef Cpu0Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E89B, 00A6 (r1 PmRef Cpu7Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E7F5, 00A6 (r1 PmRef Cpu6Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E74F, 00A6 (r1 PmRef Cpu5Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E6A9, 00A6 (r1 PmRef Cpu4Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E603, 00A6 (r1 PmRef Cpu3Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E55D, 00A6 (r1 PmRef Cpu2Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5E4B7, 00A6 (r1 PmRef Cpu1Tst 3000 INTL 20050228)
(XEN) ACPI: SSDT CFF5D0CE, 13E9 (r1 PmRefCpuPm 3000 INTL 20050228)
(XEN) System RAM: 64766MB (66321328kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at -0010
(XEN) Domain heap initialised
(XEN) CPU Vendor: Intel, Family 6 (0x6), Model 23 (0x17), Stepping 10 (raw
0001067a)
(XEN) found SMP MP-table at 000f6140
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x1008 (24 bits)
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1004,1:0], pm1x_evt[1:1000,1:0]
(XEN) ACPI: wakeup_vec[cff65fcc], vec_size[20]
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec0] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address
Re: [Xen-devel] pvh+vcpus startup issue
On 22/02/18 05:37, x...@randomwebstuff.com wrote:
> Hi. I have a domU. Its params file has: vcpus = 8. It will start with
> pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6
> or 5. It does start with vcpus = 4.
>
> I diffed the xl -v create logs, no difference there on either startup.
>
> I grabbed the domU console output for a vcpus = 5 start (attached). It
> dies right after:
>
> [ 0.007110] cpu 3 spinlock event irq 23
> [ 0.007336] installing Xen timer for CPU 4
Can you please post the hypervisor log ("xl dmesg")?
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
[Xen-devel] pvh+vcpus startup issue
Hi. I have a domU. Its params file has: vcpus = 8. It will start with pv, but not type="pvh". It will not start (on pvh) with vcpus = 7 or 6 or 5. It does start with vcpus = 4. I diffed the xl -v create logs, no difference there on either startup. I grabbed the domU console output for a vcpus = 5 start (attached). It dies right after: [ 0.007110] cpu 3 spinlock event irq 23 [ 0.007336] installing Xen timer for CPU 4 I think this issue is only affecting some CPUs. So it might be related to some CPU calculation/allocation code? I see xl info reports nr_nodes to be 1. This is a server with two E5420 CPUs. I see other dual socket, dual CPU servers (e.g. E5410, E5310) that report at nr_nodes 1 . I also see one newer CPU that I'd expect to have nr_nodes 2. nr_cpus : 20nr_nodes : 1cores_per_socket : 10threads_per_core : 2 model name : Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz I note that a v3 version of that CPU reports nr_nodes 2 as I would expect. nr_cpus : 32nr_nodes : 2cores_per_socket : 8threads_per_core : 2 model name : Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz # xl info release : 4.14.12-2.el6xen.x86_64 version : #2 SMP Sat Jan 6 03:49:33 UTC 2018 machine : x86_64 nr_cpus : 8 max_cpu_id : 7 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2500 hw_caps : bfebfbff:040ce3bd:20100800:0001:::: virt_caps : hvm total_memory : 64766 free_memory : 15433 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 10 xen_extra : .0 xen_version : 4.10.0 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0x8000 xen_changeset : xen_commandline : dom0_mem=2048M cpufreq=xen dom0_max_vcpus=2 dom0_vcpus_pin loglvl=info vcpu_migration_delay=1000 cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-18) cc_compile_by : build cc_compile_date : Sun Jan 7 23:45:02 UTC 2018 build_id : f61b02cac217640909b4c2d0f07ba50e0fe0f3d1 xend_config_format : 4 cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5420 @ 2.50GHz ... processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5420 @ 2.50GHz Possibly related to https://lists.xenproject.org/archives/html/xen-devel/2018-01/msg01471.html https://lists.xen.org/archives/html/xen-users/2018-01/msg00031.html https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=7209b8bf08700b1ed3b7dd15c6ca0b76f537ddb3 " x86: Don't use potentially incorrect CPUID values for topology information" Regards, Peter [0.00] Command line: root=/dev/xvda1 ro console=hvc0 elevator=noop xen-blkfront.max=64 init=/bin/bash [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009] usable [0.00] BIOS-e820: [mem 0x000a-0x000fefff] reserved [0.00] BIOS-e820: [mem 0x000ff000-0x000f] ACPI data [0.00] BIOS-e820: [mem 0x0010-0x83ff] usable [0.00] BIOS-e820: [mem 0xfc00-0xfc007fff] ACPI data [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] Hypervisor detected: Xen HVM [0.00] Xen version 4.10. [0.00] Xen Platform PCI: unrecognised magic value [0.00] tsc: Fast TSC calibration failed [0.00] tsc: Unable to calibrate against PIT [0.00] tsc: No reference (HPET/PMTIMER) available [0.00] e820: last_pfn = 0x8 max_arch_pfn = 0x4 [0.00] MTRR: Disabled [0.00] x86/PAT: MTRRs disabled, skipping PAT initialization too. [0.00] CPU MTRRs all blank - virtualized system. [0.00] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000FFFC0 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC007F80 34 (v01 XenHVM HVML ) [0.00] ACPI: FACP
