similar to: Bug#748052: xen-hypervisor-4.3-amd64: No USB keyboard after booting into Dom0

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum

Ian Campbell <ijc at hellion.org.uk> writes: #I think at a minimum to make any progress we would need to see some #logs. Probably the dom0 dmesg (perhaps compared to the native boot #dmesg) and the set of modules which are loaded would be a good start. #Probably xen's dmesg would be useful too. Lastly, it would be good to #mention what sort of keyboard this is (USB, PS2?) # #Also the

On Wed, 2014-05-14 at 13:11 -0700, Mike Egglestone wrote: > Here is part of the dmesg from NON-XEN that might be relevant. > (I can provide the whole log if needed) Thanks. Please do provide the whole thing (for both cases), the log here shows that it is not finding the device but doesn't include the bit where the USB driver itself is initialising and whether something is wrong at that

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

Here's some more info: I went into the BIOS, Advanced Tab-->USB Configuration and set the following: USB Controller [Enabled] Legacy USB Support [Disabled] Port 60/64 Emulation [Disabled] Make USB Devices Non-Bootable [Disasbled] Device Reset timeout [20 sec] I then rebooted into xen4.3 kernel 3.13. The keyboard does NOT work at the grub menu. But 5 seconds pass and the

On Fri, 2014-05-16 at 11:08 +0100, Jan Beulich wrote: Thanks for taking a look. FYI Mike has since mentioned on the bug report that 4.1 worked. I've asked for logs of Xen 4.1 + Linux 3.13 and Xen 4.3 + Linux 3.13 for comparison. > >>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: > > So it seems like dom0 is unable to (correctly) bind to some hardware >

Ian Campbell <ijc at hellion.org.uk> writes: #Sadly I don't think the Debian packages currently retain these. # #Mike, the easiest way to gather these might be # apt-get source xen=<pkg-version> # cd xen-XXX # make -C xen # #Then boot with the resulting xen/xen.gz. Then xen/xen-syms is the symbol #file which Jan refers to. Forgive me as I'm not that familiar with source code.

On Fri, 2014-05-23 at 08:52 +0100, Jan Beulich wrote: > > I am a noob when working with source code. How do I bump my xen up to 4.3.3? > > I guess this > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source > should help you. Since this only needs a new hypervisor binary and not a full set of tools etc to reproduce I think it can be simplified to replacing the previous

Attached are the most recent boot logs. All tests have been on the same system, an Intel S1200BTL motherboard. I did 2 boots, both with kernel 3.13. First one into xen 4.3 and the 2nd into xen 4.1. The keyboard works on xen 4.1, not on 4.3. Cheers, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL:

>>> On 22.05.14 at 19:19, <mike at estone.ca> wrote: > "Jan Beulich" <JBeulich at suse.com> writes: > #Okay, this at least clarifies there is a (relatively big) RMRR. There is > #a change to the handling of these among the ones that'll become > #4.3.3 - mind giving > #http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2 >

On Fri, 2014-05-16 at 10:05 -0700, Mike Egglestone wrote: > Here's some more info: > > I went into the BIOS, Advanced Tab-->USB Configuration > and set the following: > > USB Controller [Enabled] > Legacy USB Support [Disabled] > Port 60/64 Emulation [Disabled] > > Make USB Devices Non-Bootable

"Jan Beulich" <JBeulich at suse.com> writes: #Okay, this at least clarifies there is a (relatively big) RMRR. There is #a change to the handling of these among the ones that'll become #4.3.3 - mind giving #http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2887afabd606bc4bd5523f #a try on top of your 4.3.2 (or trying the tip of the stable-4.3 branch)? #

Package: xen-hypervisor-4.0-i386 Version: 4.0.1~rc6-1 Severity: important --- Please enter the report below this line. --- Booting up the Xen Dom0 fails with an error in "i387.c:159" --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686-bigmem Kernel: Linux 2.6.32-5-xen-686 Debian Release: squeeze/sid 500 testing security.debian.org 500

Ian Campbell <ijc at hellion.org.uk> writes: #Was that with the Jessie or Wheezy dom0 kernel? Actually tried both kernels. 3.13 on Jessie and 3.2 on Wheezy. The keyboard failed on any xen 4.3 boot. If it was nonxen, or xen 4.1 on any kernel the keyboard worked normal. Thanks for your help troubleshooting. Cheers, Mike -------------- next part -------------- An HTML attachment was

>>> On 20.05.14 at 18:25, <mike at estone.ca> wrote: > I've added iommu=debug to the XEN CMD Line under grub. > Attached is the xl dmesg log and system dmesg. Okay, this at least clarifies there is a (relatively big) RMRR. There is a change to the handling of these among the ones that'll become 4.3.3 - mind giving

Package: xen-hypervisor-3.2-1-i386 Version: 3.2-1 Severity: critical Tags: security Justification: DoS of entire system regardless of privilege When running the exploit listed in bug 464953 [1], Xen's memory state becomes corrupted and the hypervisor eventually crashes, taking all of the domU's with it. As such, this breaks operational behaviour, so I have marked this as critical. [1]

Package: xen-hypervisor-4.6-amd64 Version: 4.6.0-1 Severity: normal Dear maintaners, I was using XEN 4.4 on that machine ("unstable") and want to switch to 4.6. All xen stuff was uninstalled (XEN 4.4), the machine restarted before installing 4.6. When I uninstall XEN 4.4 (libxenlight4.4) it deinstall also part of QEMU and when I reinstall QEMU libxenlight-4.4 aws reinstalled. First

Ian Campbell <ijc at hellion.org.uk> writes: #What were the previous settings (the ones which worked for grub but not #Xen)? Do these new settings work with native Linux? # #Given the change in behaviour my gut feeling is that either the Legacy #USB Support option or the 60/64 emulation ones are the one which matters #out of that set. The default and previous settings were everything

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-2 Severity: important When I try to start a domU with more than 6 vdb it crash. The first time the vm does not launch and aparently wait for the loop device creation (some scripts/block add, udev --daemon and sleep 1 process running). And nothing happen until I Ctrl+C the xm create. My loop module is loaded with 64 loops. After this first

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer