similar to: Bug#684334: xen-hypervisor-4.0-amd64: Does not complete boot of dom0 kernel, extremely slow boot from BIOS RAM map onwards

Hi, I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 (3.2.1-2) / linux-image-2.6.26-2-xen-amd64 (2.6.26-29) without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 (4.0.1-4) / linux-image-2.6.32-5-xen-amd64 (2.6.32-45) and now it does not complete a boot of the dom0

Hey, I''m experiencing strange problem: non-deterministic PV domain hang, only on some machines (with fast SSD drive). I''ve tried xen-4.1.0 and xen-4.1.1 with many kernels different kernels: VM: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.0.3 - vanilla 3.1 rc2 dom0: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.1 rc2 Result always the same: sometimes VM

Hi Michael: Sorry to brother. But I''ve been suffered this issue quite a long time. My test environment is 2.6.32.36 + xen 4.0.1 + bnx2, 2.3. Also cpu idle is disabled in grub. Grub info: title Red Hat Enterprise Linux Server (2.6.32.36xen) kernel /xen-4.0.1.gz iommu=off x2apic=off console=com1,vga com1=115200,8n1 noreboot cpuidle=0 cpufreq=none

On Sun, Jul 22, 2012 at 03:34:42PM +0200, Ingo Molnar wrote: > Linus, > > Please pull the latest timers-core-for-linus git tree from: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-for-linus > > HEAD: eec19d1a0d04c80e66eef634f7b8f460f2ca5643 Merge branch ''linus'' into timers/core > > Continued cleanups of the core

Hi, this is ontop of Linus' tree from the 4th (lemme know if I should try the latest) on one of my test boxes: nouveau 0000:01:00.0: vgaarb: deactivate vga console Console: switching to colour dummy device 80x25 nouveau 0000:01:00.0: NVIDIA GT218 (0a8280b1) CE: hpet increased min_delta_ns to 20115 nsec nouveau 0000:01:00.0: bios: version 70.18.49.00.00 nouveau 0000:01:00.0: fb: 1024 MiB DDR3

Hey, I have a nighly build/test system that boots various machines with upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable. After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'') has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'') the PVHVM

Hello, I have been using Xen on a Debian Lenny server for quite some time. I decided to build a new Dom0 using identical hardware, but newest version of Xen from repositories with Debian Squeeze. I attempting to create a new DomU on the new host which is similar to an existing DomU running on the older Lenny host. The DomU is a three NIC firewall. Two of the NICs are virtualized. One NIC is a

Dear list, I am seeing an error across multiple machines during heavy I/O, either disk or network. The VMs are on different Intel CPUs (Core 2 Quad, Core i5, Xeon) with varying boards (Abit, Asus, Supermicro). Machines that get this error are running either BackupPC, Zabbix (MySQL) or SABNZBd. I can also reproduce the error on the Supermicros with a looped wget of an ubuntu ISO as they are

hi xen 4.0.1 w/2.6.32.41 Last week dom0 experienced an hard crash and box need to be restarted manually (despite kernel.panic=20). Serial console was not setup, only netconsole. No relevant entries through netconsole, but analyzing logs I see some crashes twenty minutes before fatal hang. Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.011963] Call Trace: Dec 2 01:29:39 xenhost-rack1 kernel:

No problemos with x86_64, however on i686 kworker/u16:57: page allocation failure: order:0, mode:0x284000 CPU: 0 PID: 1425 Comm: kworker/u16:57 Not tainted 3.18.0-0.rc5.git0.1.fc22.i686+debug #1 Workqueue: events_unbound async_run_entry_fn Call Trace: [<c0b2b55a>] dump_stack+0x48/0x60 [<c056f3d4>] warn_alloc_failed+0xd4/0x110 [<c0571ade>] __alloc_pages_nodemask+0x81e/0xc30

Yesterday morning I awoke to alerts from my SAN that one of my OS disks was faulty, FMA said it was in hardware failure. By the time I got to work (1.5 hours after the email) ALL of my pools were in a degraded state, and "tank" my primary pool had kicked in two hot spares because it was so discombobulated. ------------------- EMAIL ------------------- List of faulty resources:

HPET intr-near-missing means if the current counter value is too close to the comparator value to be reprogrammed the expected HPET intr may be missing. Linux kernel uses a mininal 48-hpet-ticks(~3.5us) distance to workaround this, but personal observation showed there is still failure case while delta=0xba (~13.5us). So choosing 20us as the MIN_DELTA_NS should be helpful to prevent near-missing

Processing commands for control at bugs.debian.org: > close 684334 4.1.0~rc6-1 Bug #684334 [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: Does not complete boot of dom0 kernel, extremely slow boot from BIOS RAM map onwards There is no source info for the package 'xen-hypervisor-4.0-amd64' at version '4.1.0~rc6-1' with architecture '' Unable to make a source

Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 1 seconds (XEN) EDID info not

Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16

On Fri, Aug 03, 2018 at 12:06:51PM -0700, Andrei Vagin wrote: > On Fri, Aug 03, 2018 at 12:08:05AM +0300, Michael S. Tsirkin wrote: > > On Thu, Aug 02, 2018 at 02:04:12PM -0700, Nambiar, Amritha wrote: > > > On 8/1/2018 5:11 PM, Andrei Vagin wrote: > > > > On Tue, Jul 10, 2018 at 07:28:49PM -0700, Nambiar, Amritha wrote: > > > >> With this patch series,

Convert VMI timer to use clock events, making it properly able to use the NO_HZ infrastructure. On UP systems, with no local APIC, we just continue to route these events through the PIT. On systems with a local APIC, or SMP, we provide a single source interrupt chip which creates the local timer IRQ. It actually gets delivered by the APIC hardware, but we don't want to use the same local

Convert VMI timer to use clock events, making it properly able to use the NO_HZ infrastructure. On UP systems, with no local APIC, we just continue to route these events through the PIT. On systems with a local APIC, or SMP, we provide a single source interrupt chip which creates the local timer IRQ. It actually gets delivered by the APIC hardware, but we don't want to use the same local

Hello, I was reading about secure Dialect negotiation to prevent man-in-middle to downgrade dialects & capabilities. _https://blogs.msdn.microsoft.com/openspecification/2012/06/28/smb3-secure-dialect-negotiation/_ I wanted to ask, is there any option to disable SMB2 to do dialect renegotiation as present in Windows8 clients, as they can control using RequireSecureNegotiate. -- Thanks Amit

Hi, I've noticed a discrepancy between Samba Version 3.0.28a and Version 3.0.24 in relation to Winbind rid idmap and trusted domains behaviour. I have an environment with 2 domains linked via a trust, an Active Directory domain and an NT4 domain. On 3.0.24 the rid backend seems to work fine, but on 3.0.28a it shows OTHERDOMAIN\domain admins instead of the primary domain's domain