Marking as Fix Released per comment #14. If this bug still exists,
please change the status back to Confirmed.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I can confirm that this bug is fixed in Ubuntu 14.04 with the follwing kernel
package:
kernel linux-image-3.13.0-43-generic 3.13.0-43.72
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The patch from Dexuan was included in upstream v3.13.11.11. The latest
Ubuntu kernel: 3.13.0-41.70 now has the upstream 3.13.11.11 updates, so
this bug should be fixed in Trusty.
Can you test the latest Trusty kernel and confirm that this bug is
fixed?
Thanks in advance!
** Changed in: linux
This is caused by a bug kernel API used by recent hyper-v synthetic
network driver in Ubuntu 14.04 (Ubuntu 13.10 is not affected).
This only affects 32-PAE Linux VM when the VM has more-than-about-4GB
memory.
I have fixed the issue:
I also have issues on a x86_64 system. I can't run the command apport
collect, because it's not installed at this time.
The only way to connect to this system is via a tap-interface. This host is a
VPN-Server.
If you need more information, just let me know! :)
--
You received this bug
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1338185
Title:
networking fails in 32-bit 14.04 using HyperV on Win2012R2
Status in “linux”
Following up on latest kernel, I upgraded kernel on Ubuntu 14.04LTS
32-bit Hyper-V VM with 2GB memory to v3.16-rc6 then increased to memory
to 4GB after confirming kernel upgrade. It still experiences network
issue/bug. I also tried more recent kernel v3.16-rc7 with the same
results. Once the
Can you see if this bug also affects the latest mainline kernel, which is
available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc6-utopic/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Good afternoon,
Wanted to share an observation. When I shut down my 32-bit Hyper-V VM
running Ubuntu 14.04 and reduce the memory from 4GB to 2GB, the
networking became functional again on the next boot. This confirms MG's
observation.
--
You received this bug notification because you are a
I encountered the exact same issue with loss of network upgrading Ubuntu
12.04LTS 32-bit to 14.04LTS 32-bit on a Hyper-V VM (Windows 2008R2). I
went through the same steps to do a fresh install of 14.04LTS 32-bit and
had the same result. Also found Ubuntu 14.04LTS 64-bit worked well and
did not
Good afternoon MG (heyrastamon),
Thanks for the feedback here. I can confirm that I performed my upgrade
to 14.04 in a Hyper-V VM with 4 GB of RAM assigned. When I tried the
new installation, I also chose 4 GB for the new VM so got the same
networking failure.
I saw the note that the 32-bit
Hello Joseph,
I can confirm the bug is present in the 32-bit daily image from your
link. I tried the installation using the utopic-desktop-i386.iso image
dated 22-May-2014.
The Hyper-V VM where I tried the installation was configured for 4 GB of
RAM. MG observed the same issue and was able to
Can you see if this bug also affects the latest 32 bit daily image, which is
available from:
http://cdimage.ubuntu.com/daily-live/current/
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-hyper-v
** Tags added: kernel-da-key
--
You received this bug
** Package changed: ubuntu = linux (Ubuntu)
** Description changed:
I was running Ubuntu 13.10 32-bit as a VM on a Windows Server 2012 R2
- machine with Hyper-V. I am using 32-bit for legacy cross-compiling that
- is not compatible with 64-bit.
+ machine with Hyper-V. In 32-bit 13.10,
I was requested to run the command apport-collect 1338185.
The reason for the bug is that all my 32-bit Ubuntu 14.10 installations
in Hyper-V do not have a network device. Therefore, I followed the next
instructions:
If, due to the nature of the issue you have encountered, you are unable
to run
15 matches
Mail list logo
