Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upR4.0-rc4: 47% performance regression vs R3.2 #3639
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 28, 2018
Member
Are you comparing fully updated 3.2 with fully updated 4.0? One thing that happened in the meantime is Mealtdown, where patches do have performance impact.
Regarding memory assignment - this may have also impact on compile time, especially when swap is involved. This may also cause apps freezing (linking often require more memory) - this is how Linux behave when low on memory. Try disabling dynamic memory management for such VM (and make initial memory = max memory).
What error do you get when booting VM with maxmem 48GB on 4.0?
|
Are you comparing fully updated 3.2 with fully updated 4.0? One thing that happened in the meantime is Mealtdown, where patches do have performance impact. Regarding memory assignment - this may have also impact on compile time, especially when swap is involved. This may also cause apps freezing (linking often require more memory) - this is how Linux behave when low on memory. Try disabling dynamic memory management for such VM (and make initial memory = max memory). What error do you get when booting VM with maxmem 48GB on 4.0? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
Feb 28, 2018
Unless there were new dom0 updates for 3.2 in the last couple days then then 3.2 install is fully updated. I'm pretty sure the 3.2 times already include the Meltdown patches because it the compile job used to take just under 4 minutes.
[user@dom0 ~]$ qvm-start development
Cannot execute qrexec-daemon!
I get that message after several seconds of delay if I've set the max memory too high.
justusranvier
commented
Feb 28, 2018
•
|
Unless there were new dom0 updates for 3.2 in the last couple days then then 3.2 install is fully updated. I'm pretty sure the 3.2 times already include the Meltdown patches because it the compile job used to take just under 4 minutes.
I get that message after several seconds of delay if I've set the max memory too high. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
See /var/log/xen/console/guest-development.log |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
Feb 28, 2018
[ 0.000000] Linux version 4.14.13-3.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Tue Jan 30 19:18:44 UTC 2018
[ 0.000000] Command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 nopat
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000efffefff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000effff000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fc000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000c0effffff] usable
[ 0.000000] x86/PAT: PAT support disabled.
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] random: fast init done
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: Xen HVM domU, BIOS 4.8.3 01/30/2018
[ 0.000000] Hypervisor detected: Xen HVM
[ 0.000000] Xen version 4.8.
[ 0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
[ 0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks.
[ 0.000000] You might have to change the root device
[ 0.000000] from /dev/hd[a-d] to /dev/xvd[a-d]
[ 0.000000] in your root= kernel command line option
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] e820: last_pfn = 0xc0f000 max_arch_pfn = 0x400000000
[ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC
[ 0.000000] e820: last_pfn = 0xeffff max_arch_pfn = 0x400000000
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] RAMDISK: [mem 0x7fa7d000-0x7fffffff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000F6B30 000024 (v02 Xen )
[ 0.000000] ACPI: XSDT 0x00000000FC00B040 000054 (v01 Xen HVM 00000000 HVML 00000000)
[ 0.000000] ACPI: FACP 0x00000000FC00AC30 0000F4 (v04 Xen HVM 00000000 HVML 00000000)
[ 0.000000] ACPI: DSDT 0x00000000FC001C00 008FAC (v02 Xen HVM 00000000 INTL 20160831)
[ 0.000000] ACPI: FACS 0x00000000FC001BC0 000040
[ 0.000000] ACPI: FACS 0x00000000FC001BC0 000040
[ 0.000000] ACPI: APIC 0x00000000FC00AD30 0001A0 (v02 Xen HVM 00000000 HVML 00000000)
[ 0.000000] ACPI: HPET 0x00000000FC00AF50 000038 (v01 Xen HVM 00000000 HVML 00000000)
[ 0.000000] ACPI: WAET 0x00000000FC00AF90 000028 (v01 Xen HVM 00000000 HVML 00000000)
[ 0.000000] ACPI: SSDT 0x00000000FC00AFC0 000031 (v02 Xen HVM 00000000 INTL 20160831)
[ 0.000000] ACPI: SSDT 0x00000000FC00B000 000031 (v02 Xen HVM 00000000 INTL 20160831)
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x0000000c0effffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0xc0efd5000-0xc0effffff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x0000000c0effffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009efff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x00000000efffefff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x0000000c0effffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x0000000c0effffff]
[ 0.000000] ACPI: PM-Timer IO Port: 0xb008
[ 0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 40 CPUs, 0 hotplug CPUs
[ 0.000000] e820: [mem 0xf0000000-0xfbffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on Xen HVM
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:40 nr_node_ids:1
[ 0.000000] percpu: Embedded 44 pages/cpu @ffff8b6eddc00000 s139736 r8192 d32296 u262144
[ 0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 12382152
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 nopat
[ 0.000000] log_buf_len individual max cpu contribution: 4096 bytes
[ 0.000000] log_buf_len total cpu_extra contributions: 159744 bytes
[ 0.000000] log_buf_len min size: 262144 bytes
[ 0.000000] log_buf_len: 524288 bytes
[ 0.000000] early log buf free: 253940(96%)
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Memory: 49421832K/50314868K available (12300K kernel code, 1383K rwdata, 3732K rodata, 2520K init, 1280K bss, 893036K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=40, Nodes=1
[ 0.000000] Kernel/User page tables isolation: enabled
[ 0.000000] ftrace: allocating 34840 entries in 137 pages
[ 0.001000] Hierarchical RCU implementation.
[ 0.001000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=40.
[ 0.001000] Tasks RCU enabled.
[ 0.001000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=40
[ 0.001000] NR_IRQS: 4352, nr_irqs: 1152, preallocated irqs: 16
[ 0.001000] xen:events: Using FIFO-based ABI
[ 0.001000] xen:events: Xen HVM callback vector for event delivery is enabled
[ 0.001000] Offload RCU callbacks from CPUs: .
[ 0.001000] Console: colour VGA+ 80x25
[ 0.001000] console [hvc0] enabled
[ 0.001000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 30580167144 ns
[ 0.002000] tsc: Fast TSC calibration using PIT
[ 0.026003] tsc: Detected 2199.942 MHz processor
[ 0.026011] Calibrating delay loop (skipped), value calculated using timer frequency.. 4400.00 BogoMIPS (lpj=2200002)
[ 0.026023] pid_max: default: 40960 minimum: 320
[ 0.026054] ACPI: Core revision 20170728
[ 0.030751] ACPI: 3 ACPI AML tables successfully acquired and loaded
[ 0.030851] Security Framework initialized
[ 0.030857] Yama: becoming mindful.
[ 0.055424] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
[ 0.068104] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
[ 0.068389] Mount-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.068615] Mountpoint-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.080556] CPU: Physical Processor ID: 0
[ 0.080564] CPU: Processor Core ID: 0
[ 0.080571] mce: CPU supports 2 MCE banks
[ 0.080593] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[ 0.080605] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[ 0.081740] Freeing SMP alternatives memory: 28K
[ 0.085073] smpboot: Max logical packages: 2
[ 0.085429] x2apic: IRQ remapping doesn't support X2APIC mode
[ 0.086004] Switched APIC routing to physical flat.
[ 0.087000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
[ 0.097525] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[ 0.097553] installing Xen timer for CPU 0
[ 0.097642] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (family: 0x6, model: 0x4f, stepping: 0x1)
[ 0.097699] cpu 0 spinlock event irq 53
[ 0.097846] Performance Events: unsupported p6 CPU model 79 no PMU driver, software events only.
[ 0.098014] Hierarchical SRCU implementation.
[ 0.100438] NMI watchdog: Perf event create on CPU 0 failed with -2
[ 0.100448] NMI watchdog: Perf NMI watchdog permanently disabled
[ 0.101575] smp: Bringing up secondary CPUs ...
[ 0.101774] installing Xen timer for CPU 1
[ 0.101862] x86: Booting SMP configuration:
[ 0.101868] .... node #0, CPUs: #1
[ 0.102606] cpu 1 spinlock event irq 59
[ 0.103146] installing Xen timer for CPU 2
[ 0.103245] #2
[ 0.104145] cpu 2 spinlock event irq 65
[ 0.104177] installing Xen timer for CPU 3
[ 0.104177] #3
[ 0.105097] cpu 3 spinlock event irq 71
[ 0.105137] installing Xen timer for CPU 4
[ 0.105146] #4
[ 0.106096] cpu 4 spinlock event irq 77
[ 0.106126] installing Xen timer for CPU 5
[ 0.106152] #5
[ 0.107112] cpu 5 spinlock event irq 83
[ 0.107145] installing Xen timer for CPU 6
[ 0.107183] #6
[ 0.108104] cpu 6 spinlock event irq 89
[ 0.108137] installing Xen timer for CPU 7
[ 0.108202] #7
[ 0.109112] cpu 7 spinlock event irq 95
[ 0.193210] installing Xen timer for CPU 8
[ 0.194081] #8
[ 0.194904] cpu 8 spinlock event irq 101
[ 0.195160] installing Xen timer for CPU 9
[ 0.195281] #9
[ 0.197343] cpu 9 spinlock event irq 107
[ 0.197343] installing Xen timer for CPU 10
[ 0.197343] #10
[ 0.198441] cpu 10 spinlock event irq 113
[ 0.198441] installing Xen timer for CPU 11
[ 0.198441] #11
[ 0.199571] cpu 11 spinlock event irq 119
[ 0.199571] installing Xen timer for CPU 12
[ 0.200035] #12
[ 0.200743] cpu 12 spinlock event irq 125
[ 0.201094] installing Xen timer for CPU 13
[ 0.201229] #13
[ 0.202050] cpu 13 spinlock event irq 131
[ 0.202375] installing Xen timer for CPU 14
[ 0.202527] #14
[ 0.203250] cpu 14 spinlock event irq 137
[ 0.203250] installing Xen timer for CPU 15
[ 0.203293] #15
[ 0.204200] cpu 15 spinlock event irq 143
[ 0.204200] installing Xen timer for CPU 16
[ 0.204259] #16
[ 0.206201] cpu 16 spinlock event irq 149
[ 0.206632] installing Xen timer for CPU 17
[ 0.207331] #17
[ 0.208213] cpu 17 spinlock event irq 155
[ 0.208536] installing Xen timer for CPU 18
[ 0.209013] #18
[ 0.209784] cpu 18 spinlock event irq 161
[ 0.210577] installing Xen timer for CPU 19
[ 0.210848] #19
[ 0.211660] cpu 19 spinlock event irq 167
[ 0.212306] installing Xen timer for CPU 20
[ 0.212428] #20
[ 0.214057] cpu 20 spinlock event irq 173
[ 0.214483] installing Xen timer for CPU 21
[ 0.214725] #21
[ 0.215724] cpu 21 spinlock event irq 179
[ 0.216697] installing Xen timer for CPU 22
[ 0.216945] #22
[ 0.217590] cpu 22 spinlock event irq 185
[ 0.218522] installing Xen timer for CPU 23
[ 0.218812] #23
[ 0.219557] cpu 23 spinlock event irq 191
[ 0.220422] installing Xen timer for CPU 24
[ 0.220709] #24
[ 0.221560] cpu 24 spinlock event irq 197
[ 0.223401] installing Xen timer for CPU 25
[ 0.232279] #25
[ 0.234000] cpu 25 spinlock event irq 203
[ 0.237220] installing Xen timer for CPU 26
[ 0.248841] #26
[ 0.251243] cpu 26 spinlock event irq 209
[ 0.253940] installing Xen timer for CPU 27
[ 0.265770] #27
[ 0.268301] cpu 27 spinlock event irq 215
[ 0.270210] installing Xen timer for CPU 28
[ 0.279885] #28
[ 0.282675] cpu 28 spinlock event irq 221
[ 0.284740] installing Xen timer for CPU 29
[ 0.294794] #29
[ 0.297801] cpu 29 spinlock event irq 227
[ 0.300068] installing Xen timer for CPU 30
[ 0.310113] #30
[ 0.313000] cpu 30 spinlock event irq 233
[ 0.315280] installing Xen timer for CPU 31
[ 0.325963] #31
[ 0.328985] cpu 31 spinlock event irq 239
[ 0.331947] installing Xen timer for CPU 32
[ 0.343900] #32
[ 0.348031] random: crng init done
[ 0.405810] cpu 32 spinlock event irq 245
[ 0.407339] installing Xen timer for CPU 33
[ 0.410696] #33
[ 0.413456] cpu 33 spinlock event irq 251
[ 0.415270] installing Xen timer for CPU 34
[ 0.426132] #34
[ 0.429343] cpu 34 spinlock event irq 257
[ 0.432324] installing Xen timer for CPU 35
[ 0.444788] #35
[ 0.448196] cpu 35 spinlock event irq 263
[ 0.450590] installing Xen timer for CPU 36
[ 0.463050] #36
[ 0.466501] cpu 36 spinlock event irq 269
[ 0.469958] installing Xen timer for CPU 37
[ 0.485363] #37
[ 0.489137] cpu 37 spinlock event irq 275
[ 0.492079] installing Xen timer for CPU 38
[ 0.509081] #38
[ 0.513556] cpu 38 spinlock event irq 281
[ 0.516944] installing Xen timer for CPU 39
[ 0.534825] #39
[ 0.537942] cpu 39 spinlock event irq 287
[ 0.538129] smp: Brought up 1 node, 40 CPUs
[ 0.538129] smpboot: Total of 40 processors activated (176367.16 BogoMIPS)
[ 0.548620] devtmpfs: initialized
[ 0.549152] x86/mm: Memory block size: 128MB
[ 0.573489] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[ 0.573983] futex hash table entries: 16384 (order: 8, 1048576 bytes)
[ 0.584158] pinctrl core: initialized pinctrl subsystem
[ 0.584518] RTC time: 14:45:10, date: 02/28/18
[ 0.589968] NET: Registered protocol family 16
[ 0.593617] cpuidle: using governor menu
[ 0.595153] ACPI: bus type PCI registered
[ 0.597187] PCI: Using configuration type 1 for base access
[ 0.604089] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.604224] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.610596] ACPI: Added _OSI(Module Device)
[ 0.610606] ACPI: Added _OSI(Processor Device)
[ 0.610614] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.610622] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.617322] ACPI: Interpreter enabled
[ 0.617361] ACPI: (supports S0 S3 S5)
[ 0.617469] ACPI: Using IOAPIC for interrupt routing
[ 0.617534] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.618000] ACPI: Enabled 2 GPEs in block 00 to 0F
[ 0.639767] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.639816] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
[ 0.639884] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.639949] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
[ 0.640888] PCI host bridge to bus 0000:00
[ 0.640913] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 0.640994] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 0.641068] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 0.641175] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfbffffff window]
[ 0.641218] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.672217] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
[ 0.672238] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
[ 0.672250] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
[ 0.672262] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
[ 0.695840] pci 0000:00:01.3: quirk: [io 0xb000-0xb03f] claimed by PIIX4 ACPI
[ 0.695973] pci 0000:00:01.3: quirk: [io 0xb100-0xb10f] claimed by PIIX4 SMB
[ 0.729913] ACPI: PCI Interrupt Link [LNKA] (IRQs *5 10 11)
[ 0.730749] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.731291] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.732015] ACPI: PCI Interrupt Link [LNKD] (IRQs *5 10 11)
[ 0.739013] xen:balloon: Initialising balloon driver
[ 0.775000] pci 0000:00:03.0: vgaarb: setting as boot VGA device
[ 0.775000] pci 0000:00:03.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 0.775017] pci 0000:00:03.0: vgaarb: bridge control possible
[ 0.775063] vgaarb: loaded
[ 0.775764] SCSI subsystem initialized
[ 0.780207] ACPI: bus type USB registered
[ 0.780314] usbcore: registered new interface driver usbfs
[ 0.780388] usbcore: registered new interface driver hub
[ 0.789518] usbcore: registered new device driver usb
[ 0.803731] EDAC MC: Ver: 3.0.0
[ 0.808356] PCI: Using ACPI for IRQ routing
[ 0.815135] NetLabel: Initializing
[ 0.815187] NetLabel: domain hash size = 128
[ 0.815253] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.815364] NetLabel: unlabeled traffic allowed by default
[ 0.817449] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.818097] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.819023] hpet0: 3 comparators, 64-bit 62.500000 MHz counter
justusranvier
commented
Feb 28, 2018
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 28, 2018
Member
That's all? Maybe it was killed by Xen, check xl dmesg. If there is something about running out of PoD pages, increase initial memory size.
|
That's all? Maybe it was killed by Xen, check |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
Feb 28, 2018
Xen 4.8.3-2.fc25
(XEN) Xen version 4.8.3 (user@) (gcc (GCC) 6.4.1 20170727 (Red Hat 6.4.1-1)) debug=n Tue Jan 30 01:16:56 UTC 2018
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.02~beta3
(XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 4 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009ac00 (usable)
(XEN) 000000000009ac00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000078dc7000 (usable)
(XEN) 0000000078dc7000 - 00000000796d6000 (reserved)
(XEN) 00000000796d6000 - 0000000079c1f000 (ACPI NVS)
(XEN) 0000000079c1f000 - 0000000090000000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed45000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000001080000000 (usable)
(XEN) ACPI: RSDP 000F0580, 0024 (r2 SUPERM)
(XEN) ACPI: XSDT 7973E0A8, 00CC (r1 1072009 AMI 10013)
(XEN) ACPI: FACP 7976EE18, 010C (r5 SUPERM SMCI--MB 1072009 AMI 10013)
(XEN) ACPI: DSDT 7973E208, 30C0F (r2 SUPERM SMCI--MB 1072009 INTL 20091013)
(XEN) ACPI: FACS 79C1DF80, 0040
(XEN) ACPI: APIC 7976EF28, 0294 (r3 SUPERM SMCI--MB 1072009 AMI 10013)
(XEN) ACPI: FPDT 7976F1C0, 0044 (r1 SUPERM SMCI--MB 1072009 AMI 10013)
(XEN) ACPI: FIDT 7976F208, 009C (r1 SUPERM SMCI--MB 1072009 AMI 10013)
(XEN) ACPI: SPMI 7976F2A8, 0040 (r5 SUPERM SMCI--MB 0 AMI. 0)
(XEN) ACPI: MCFG 7976F2E8, 003C (r1 SUPERM SMCI--MB 1072009 MSFT 97)
(XEN) ACPI: UEFI 7976F328, 0042 (r1 SUPERM SMCI--MB 1072009 0)
(XEN) ACPI: HPET 7976F370, 0038 (r1 SUPERM SMCI--MB 1 INTL 20091013)
(XEN) ACPI: MSCT 7976F3A8, 0090 (r1 SUPERM SMCI--MB 1 INTL 20091013)
(XEN) ACPI: SLIT 7976F438, 002D (r1 SUPERM SMCI--MB 1 INTL 20091013)
(XEN) ACPI: SRAT 7976F468, 1158 (r3 SUPERM SMCI--MB 1 INTL 20091013)
(XEN) ACPI: WDDT 797705C0, 0040 (r1 SUPERM SMCI--MB 0 INTL 20091013)
(XEN) ACPI: SSDT 79770600, 1700F (r2 SUPERM PmMgt 1 INTL 20120913)
(XEN) ACPI: SSDT 79787610, 264C (r2 SUPERM SpsNm 2 INTL 20120913)
(XEN) ACPI: SSDT 79789C60, 0064 (r2 SUPERM SpsNvs 2 INTL 20120913)
(XEN) ACPI: PRAD 79789CC8, 0102 (r2 SUPERM SMCI--MB 2 INTL 20120913)
(XEN) ACPI: DMAR 79789DD0, 0158 (r1 SUPERM SMCI--MB 1 INTL 20091013)
(XEN) ACPI: HEST 79789F28, 027C (r1 SUPERM SMCI--MB 1 INTL 1)
(XEN) ACPI: BERT 7978A1A8, 0030 (r1 SUPERM SMCI--MB 1 INTL 1)
(XEN) ACPI: ERST 7978A1D8, 0230 (r1 SUPERM SMCI--MB 1 INTL 1)
(XEN) ACPI: EINJ 7978A408, 0130 (r1 SUPERM SMCI--MB 1 INTL 1)
(XEN) System RAM: 65421MB (66991492kB)
(XEN) SRAT: Node 1 has no memory. BIOS Bug or mis-configured hardware?
(XEN) Domain heap initialised DMA width 32 bits
(XEN) x2APIC mode is already enabled by BIOS.
(XEN) ACPI: 32/64X FACS address mismatch in FADT - 79c1df80/0000000000000000, using 32
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec01000, GSI 24-47
(XEN) IOAPIC[2]: apic_id 3, version 32, address 0xfec40000, GSI 48-71
(XEN) Switched to APIC driver x2apic_cluster.
(XEN) xstate: size: 0x340 and states: 0x7
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 17, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 18, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 19, using 0x1
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 2200.003 MHz processor.
(XEN) Initing memory sharing.
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Posted Interrupt not enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) Allocated console ring of 128 KiB.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) - APIC Register Virtualization
(XEN) - Virtual Interrupt Delivery
(XEN) - Posted Interrupt Processing
(XEN) - VMCS shadowing
(XEN) - VM Functions
(XEN) - Virtualisation Exceptions
(XEN) - Page Modification Logging
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) CMCI: threshold 0x2 too large for CPU20 bank 17, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU20 bank 18, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU20 bank 19, using 0x1
(XEN) Brought up 40 CPUs
(XEN) Dom0 has maximum 1224 PIRQs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2a92000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000001048000000->000000104c000000 (1024717 pages to be allocated)
(XEN) Init. ramdisk: 000000107e2cd000->000000107ffff1b8
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff82a92000
(XEN) Init. ramdisk: 0000000000000000->0000000000000000
(XEN) Phys-Mach map: 0000008000000000->0000008000800000
(XEN) Start info: ffffffff82a92000->ffffffff82a924b4
(XEN) Page tables: ffffffff82a93000->ffffffff82aac000
(XEN) Boot stack: ffffffff82aac000->ffffffff82aad000
(XEN) TOTAL: ffffffff80000000->ffffffff82c00000
(XEN) ENTRY ADDRESS: ffffffff826cc180
(XEN) Dom0 has maximum 40 VCPUs
(XEN) Scrubbing Free RAM on 2 nodes using 10 CPUs
(XEN) .....................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 312kB init memory
(XEN) [VT-D] It's risky to assign 0000:81:00.0 with shared RMRR at 7ba77000 for Dom17.
(XEN) Cannot setup identity map d17:7ba77, gfn already mapped to 5bba77.
(XEN) Cannot setup identity map d17:7ba78, gfn already mapped to 5bba78.
(XEN) Cannot setup identity map d17:7ba79, gfn already mapped to 5bba79.
(XEN) Cannot setup identity map d17:7ba7a, gfn already mapped to 5bba7a.
(XEN) Cannot setup identity map d17:7ba7b, gfn already mapped to 5bba7b.
(XEN) Cannot setup identity map d17:7ba7c, gfn already mapped to 5bba7c.
(XEN) Cannot setup identity map d17:7ba7d, gfn already mapped to 5bba7d.
(XEN) Cannot setup identity map d17:7ba7e, gfn already mapped to 5bba7e.
(XEN) Cannot setup identity map d17:7ba7f, gfn already mapped to 5bba7f.
justusranvier
commented
Feb 28, 2018
•
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 28, 2018
Member
I assume those messages about domain 17 are unrelated, right? Anyway try increasing initial memory, for example 8GB.
|
I assume those messages about domain 17 are unrelated, right? Anyway try increasing initial memory, for example 8GB. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
commented
Feb 28, 2018
|
It must be unrelated. According to qubes.xml development is domain 8. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
Feb 28, 2018
Increasing initial memory to 8 GB, then 16 GB both resulted in the same failure to start.
justusranvier
commented
Feb 28, 2018
|
Increasing initial memory to 8 GB, then 16 GB both resulted in the same failure to start. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@HW42 any idea? |
andrewdavidwong
added
the
bug
label
Mar 1, 2018
andrewdavidwong
added this to the Release 4.0 milestone
Mar 1, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
Mar 7, 2018
I installed dom0 and fedora-26 template updates today and did some more experiments. For the experiments I did a fresh reboot with no vms configured to start automatically, and I temporarily disabled networking in the vm I was testing.
- Start development with 48 GiB -> failed
- Start development with 30 GiB -> success
- Shutdown development
- Start development with 39 GiB -> failed
- Start development with 34 GiB -> failed
- Start development with 32 GiB -> failed
- Start development with 31 GiB -> failed
- Start development with 30 GiB -> failed
reboot
- Start development with 30 GiB -> success
- Shutdown development
- Start development with 30 GiB -> success
- Shutdown development
- Start development with 30 GiB -> success
- Shutdown development
- Start development with 32 GiB -> failed
- Start development with 30 GiB -> failed
- Start development with 16 GiB -> success
- Start development with 29 GiB -> success
- Shutdown development
- Start development with 29 GiB -> success
- Shutdown development
- Start development with 30 GiB -> success
- Shutdown development
- Start development with 30 GiB -> success
reboot
- Start development with 31 GiB -> failed
- Start development with 30 GiB -> success
- Shutdown development
- Start development with 30 GiB -> failed
- Start development with 30 GiB -> success
- Enable networking
- Start development (causes sys-net and sys-firewall to start) with 30 GiB -> success
justusranvier
commented
Mar 7, 2018
|
I installed dom0 and fedora-26 template updates today and did some more experiments. For the experiments I did a fresh reboot with no vms configured to start automatically, and I temporarily disabled networking in the vm I was testing.
reboot
reboot
|
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 31, 2018
andrewdavidwong
referenced this issue
Apr 8, 2018
Closed
Significant performance reduction after R3.2 -> R4.0 upgrade #3803
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kravietz
Apr 8, 2018
In my case #3803 it's not a problem with memory, the VM is using 2.8 GB out of 4 GB allocated, and there's plenty of free memory.
kravietz
commented
Apr 8, 2018
|
In my case #3803 it's not a problem with memory, the VM is using 2.8 GB out of 4 GB allocated, and there's plenty of free memory. |
andrewdavidwong
referenced this issue
Apr 29, 2018
Closed
Performance regression in Qubes R4.0 #3867
andrewdavidwong
added
the
P: major
label
Apr 29, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
justusranvier
Jun 7, 2018
The vm startup reliability problem stopped happening several weeks ago when I enabled the updates-testing repo in dom0 and got some updates that were not default repo at the time. I'm also able to allocate the same amount of ram as I could in 3.2.
The performance issue, however, remains.
The freezing seems to be triggered by IO more than by memory or CPU usage. I can reliably trigger pathological behavior by changing one .cpp file in a project I'm working on and then running "make -j1".
The entire VM will reliably freeze during an IO-intensive portion of the linking phase. The freezing lasts for over a minute before the compile continues and finishes. A console running top during this process won't show any obvious CPU or memory bottlenecks.
Within about a minute of the compile finishing there will be a second freeze during which no application running on the VM will respond at all.
From beginning the compile process until the VM is restored to normal usability takes upwards of 5 minutes, which is about a two order of magnitude regression in an edit-compile-test cycle that used to take seconds.
justusranvier
commented
Jun 7, 2018
|
The vm startup reliability problem stopped happening several weeks ago when I enabled the updates-testing repo in dom0 and got some updates that were not default repo at the time. I'm also able to allocate the same amount of ram as I could in 3.2. The performance issue, however, remains. The freezing seems to be triggered by IO more than by memory or CPU usage. I can reliably trigger pathological behavior by changing one .cpp file in a project I'm working on and then running "make -j1". The entire VM will reliably freeze during an IO-intensive portion of the linking phase. The freezing lasts for over a minute before the compile continues and finishes. A console running top during this process won't show any obvious CPU or memory bottlenecks. Within about a minute of the compile finishing there will be a second freeze during which no application running on the VM will respond at all. From beginning the compile process until the VM is restored to normal usability takes upwards of 5 minutes, which is about a two order of magnitude regression in an edit-compile-test cycle that used to take seconds. |
justusranvier commentedFeb 28, 2018
•
edited
Edited 1 time
-
justusranvier
edited Feb 28, 2018 (most recent)
After migrating from 3.2 to 4.0 I've seen a severe loss of performance in the vm I use for compiling. Build time has increased by 47%.
In addition sometimes under heavy load all applications in the vm will completely stop responding for tens of seconds. Every time I've observed this it was during the linking phase of build process rather than the compile phase.
One possible clue is that in 4.0 I'm unable to allocate as much memory to this vm as I could in 3.2. 3.2 was happy to let me set the maximum memory to 48 GB, but the vm refuses to start in 4.0 if I give it more than 29 GB.
Qubes 3.2:
Initial memory: 5120
Max memory: 49152
VCPUs no.: 40
Qubes 4.0
Initial memory: 5120
Max memory: 29696
VCPUs no.: 40