I believe I have a solution to my own problem: the VM in question was
configured by Vagrant, without "Data Exchange" selected in Hyper-V under
"Settings" -> "Integration Services".
Once "Data Exchange" is enabled, "/dev/vmbus/hv_kvp" shows up and the
"open /dev/vmbus/hv_kvp failed; error: 2 No suc
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870837/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870834/+files/Lspci.txt
--
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/1687631
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870835/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870839/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870836/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870833/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Attachment added: "These are the cloud tools installed."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870840/+files/cloud-tools.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1687631/+attachment/4870838/+files/UdevDb.txt
--
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/1687631
apport information
** Tags added: apport-collected xenial
** Description changed:
When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable to
start because the /dev/vmbus/hv_kvp device is missing.
Cons
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870817/+files/version.log
--
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/168
Public bug reported:
When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable to
start because the /dev/vmbus/hv_kvp device is missing.
Consequently, Hyper-V is unable to obtain networking information about
the VM
I just ran into this issue with Bento Box's 64-bit image for 16.04. We
were trying to boot into recovery mode in order to run `zerofree` prior
to packaging up a custom box for internal use (per steps from
https://snippets.khromov.se/shrinking-a-virtualbox-linux-image-with-
zerofree/).
I can confir
13 matches
Mail list logo
