Can you also share the kernel logs, and all the files in
/var/lib/waagent?
In the waagent.log, the new host name seems uncommon:
2013/06/28 15:08:12 EnvMonitor: Detected host name change: ubuntu -
gwaclhostblkhljy4re3yp9swkdwp63kswkss9bqhn0zm3f3gunipzu5vwdr8qzw
2013/06/28 15:08:12 Setting host
Can you also share the kernel logs, and all the files in
/var/lib/waagent?
In the waagent.log, the new host name seems uncommon:
2013/06/28 15:08:12 EnvMonitor: Detected host name change: ubuntu -
gwaclhostblkhljy4re3yp9swkdwp63kswkss9bqhn0zm3f3gunipzu5vwdr8qzw
2013/06/28 15:08:12 Setting host
Update: We only see this issue when using 1 CPU for a Hyper-V guest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994870
Title:
kernel panic on boot with hyper-v
To manage notifications about
After removing ata_piix from the kernel, the panic problem goes away.
It seems the regression comes from this commit:
commit a207c1ea485cc9cd7d546eadeb0877515c952f2a
Author: Andy Whitcroft a...@canonical.com
Date: Thu Mar 8 11:32:35 2012 +
UBUNTU: SAUCE: ata_piix: defer disks to the
This is a 64bit instance. This VM is running on 8 VCPU and 14GB RAM.
This issue repros on other VCPU and RAM settings too but with much less
chance.
However, the kernel panic traces are not consistent for each repro. The
trace in the bug report happens at a early stage of boot, at which point
we
Tested. Everything worked as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581243
Title:
[Hyper-V] PCI Passthrough kernel hang and explicit barriers
To manage notifications about this
We have tested the proposed kernel. It is looking good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570124
Title:
[Hyper-V] In-flight PCI Passthrough Patches
To manage notifications about this
Public bug reported:
On Azure, the RDMA device is exposed as a iWARP device. There is only
one such device in each VM, they are set at port 1.
A recent patch 5ecce4c9b17b("Check port number supplied by user verbs
cmds") starts checking on port_num in qp attributes passed from user
mode
Please build the driver as a kernel module package. The package name
should have something that match the hosting cluster ND version.
Currently we have 142 and 144.
For this driver, please build two kernel module packages:
.142.deb and .144.deb (those two packages are
binary identical because
** Patch added: "Infiniband driver for kernel 4.11"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701744/+attachment/4906980/+files/0001-Add-infiniband-driver-for-Azure-HPC.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: "Infiniband driver build configuration for kernel 4.11"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701744/+attachment/4906981/+files/0002-Add-driver-build-configuration-to-infiniband.patch
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
This is the infiniband driver for Azure HPC.
Windows Azure agent will provision an image for running infiniband RDMA
via DAPL when "OS.EnableRDMA=y" is defined in waagent.conf.
Note: Ubuntu image needs to load rdma_ucm on boot to expose the RDMA CM
interface to user-mode
Public bug reported:
The Linux agent checks for module version, then decide how to pass the
Infiniband IP address to the RDMA driver.
The new RDMA driver supports discovery of IP by trying to bind to all
possible IP address. The driver needs to export the module version to
have linux agent use
** Patch added: "Patch for RDMA driver"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1686208/+attachment/4867953/+files/0001-vmbus-rdma-add-version-number.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Patch for RDMA driver"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1689627/+attachment/4874277/+files/0001-vmbus-rdma-add-version-number.patch
** Package changed: walinuxagent (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1689627 ***
https://bugs.launchpad.net/bugs/1689627
** This bug has been marked a duplicate of bug 1689627
add version to rdma driver to support new method to bind to ND IP interface
--
You received this bug notification because you are a member of
Public bug reported:
The Linux agent (WALA) checks for module version, then decides how to
pass the InfiniBand IP address to the RDMA driver. The new RDMA driver
supports discovery of IP by trying to bind to all possible IP address.
The driver needs to export the module version to have WALA use
I suggest we can just keep 142 as is. The extra module size on disk is
not that bad at 140k.
The original design was to deal with future ND version updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't think we have ND 142 cluster in use, they have all been upgraded
to 144. So we only need the patch for ND 144.
This is not needed for 4.15. Ubuntu 16.04 is running older user-mode
drivers that don't cause problems.
--
You received this bug notification because you are a member of Ubuntu
When kernel device is probed, its vendor ID and device ID are used to
ask user-mode library to find the correct device driver in user-mode.
The patch will enable the correct user-mode driver is selected. There is
no additional configuration or time spent on the device initialization,
because at
20 matches
Mail list logo
