[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
Recent work on bug 101301 was done in email rather than in the bug. The
following patch was tested on Hyper-V and then accepted into the PCI
tree.
arch/x86/kernel/acpi/boot.c |1 +
drivers/acpi/pci_link.c | 16
include/linux/acpi.h|2 +-
3 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c index
e49ee24da85e..9393896717d0 100644
--- a/arch/x86/kernel/acpi/boot.c
+++ b/arch/x86/kernel/acpi/boot.c
@@ -445,6 +445,7 @@ static void __init acpi_sci_ioapic_setup(u8 bus_irq, u16
polarity, u16 trigger,
polarity = acpi_sci_flags & ACPI_MADT_POLARITY_MASK;
mp_override_legacy_irq(bus_irq, polarity, trigger, gsi);
+ acpi_penalize_sci_irq(bus_irq, trigger, polarity);
/*
* stash over-ride to indicate we've been here diff --git
a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c index
cfd7581cc19f..b09ad554430a 100644
--- a/drivers/acpi/pci_link.c
+++ b/drivers/acpi/pci_link.c
@@ -826,6 +826,22 @@ void acpi_penalize_isa_irq(int irq, int active) }
/*
+ * Penalize IRQ used by ACPI SCI. If ACPI SCI pin attributes conflict
+with
+ * PCI IRQ attributes, mark ACPI SCI as ISA_ALWAYS so it won't be use
+for
+ * PCI IRQs.
+ */
+void acpi_penalize_sci_irq(int irq, int trigger, int polarity) {
+ if (irq >= 0 && irq < ARRAY_SIZE(acpi_irq_penalty)) {
+ if (trigger != ACPI_MADT_TRIGGER_LEVEL ||
+ polarity != ACPI_MADT_POLARITY_ACTIVE_LOW)
+ acpi_irq_penalty[irq] += PIRQ_PENALTY_ISA_ALWAYS;
+ else
+ acpi_irq_penalty[irq] += PIRQ_PENALTY_PCI_USING;
+ }
+}
+
+/*
* Over-ride default table to reserve additional IRQs for use by ISA
* e.g. acpi_irq_isa=5
* Useful for telling ACPI how not to interfere with your ISA sound card.
diff --git a/include/linux/acpi.h b/include/linux/acpi.h index
d2445faf..0b2394f61af4 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -221,7 +221,7 @@ struct pci_dev;
int acpi_pci_irq_enable (struct pci_dev *dev); void acpi_penalize_isa_irq(int
irq, int active);
-
+void acpi_penalize_sci_irq(int irq, int trigger, int polarity);
void acpi_pci_irq_disable (struct pci_dev *dev);
extern int ec_read(u8 addr, u8 *val);
--
1.7.10.4
--
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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in Linux:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Vivid:
In Progress
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS> Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation
[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
Typo - the above patch was accepted into the ACPI tree.
--
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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in Linux:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Vivid:
In Progress
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS> Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 6473-7986-1993-5777-7899-0719-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440072/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
Hi Joseph, In Linux-next, we have seen an issue caused by memory not being onlined after hot adding. This bug caused our guest to falsely report memory to host as being assigned; even though it was actually inaccessible. We wonder if this is what you’re seeing as well. There were two relevant patches to fix hot-add: - https://lkml.org/lkml/diff/2015/7/17/374/1 = this patch fixes BUG_ON crash when hot-adding memory - https://lkml.org/lkml/diff/2015/8/3/104/1 = this patch fixes the onlining issue described above -- 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/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
Hot Add issues remain.
Memory is Hot Added as demand increases.
Memory is not ballooned down after demand is reduced.
syslog has numerous call traces for hung task.
Call stack shows calls to mem_hotplug_begin()
Tail end of syslog attached as syslog.log.
Test procedure:
- Create 15.04 VM.
- Install test kernel.
- Configure dynamic memory
- Startup memory : 1536 MB
- Minimum memory : 1024 MB
- Maximum memory : 8192 MB
- Reboot
- Start 7 separate instances of stressapptest.
- Each instance consumes 128 MB and runs for 90 seconds.
- Allow 5 seconds before starting a new instance.
- Wait for Hyper-V host to balloon down assigned memory.
- Repeat test.
Test results:
VM State Assigned Mem Memory Demand
=
Idle 1024 MB399 MB
stress x7 1778 MB 1778 MB
no stress 1778 MB462 MB
10 min later 1778 MB462 MB
20 min later 1778 MB462
** Attachment added: Tail end of syslog - during hot add test.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1294283/+attachment/4440536/+files/syslog.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/1294283
Title:
Memory balloning in Hyper-V generation 2 does not work
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Utopic:
In Progress
Status in linux source package in Vivid:
In Progress
Status in linux source package in Wily:
In Progress
Bug description:
The generation 2 VM has been assinged a memory range of 512 MiB-
4096MiB with a starting memory of 512 MiB. It should get additional
memory when needed, but the total available memory in the VM stays at
the intial 512 MiB and the kernel starts swapping instead of
allocating more memory from the host.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-18-generic 3.13.0-18.38
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Tue Mar 18 19:28:54 2014
HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b
InstallationDate: Installed on 2014-03-12 (6 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed
root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080
quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-18-generic N/A
linux-backports-modules-3.13.0-18-generic N/A
linux-firmware 1.126
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v1.0
dmi.modalias:
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
dmi.product.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation
---
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700
InstallationDate: Installed on 2014-03-29 (9 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
ProcFB: 0 hyperv_fb
ProcKernelCmdLine:
[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
Installed the test kernel from comment #8 on a 14.10 server VM. Everything looks good. IPerf3 ran with no issues. The two Hyper-V hosts used for the test only had 1GB NICs, so iperf reported 920MB throughput. -- 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/1454892 Title: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Released Bug description: hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Based on the information given to this driver (via the xmit_more skb flag), we can defer signaling the host if more packets are on the way. This will help make the host more efficient since it can potentially process a larger batch of packets. Implement this optimization. Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a This commit may imply other commits previously requested, for example https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074 Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04, 14.04 HWE, 12.02, and 12.02 HWE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
Following information was provided to the kernel.org bug:
1. Researching if Tulip GSI is shared with ACPI SCI.
2. acpi_sci=low works! Tulip driver successfully loaded.
Attached is the output from acpidump when VM was booted without an acpi_sci
option.
** Attachment added: Output from acpidump utility
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440072/+attachment/4428918/+files/acpidump.out
--
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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in Linux:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Vivid:
In Progress
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 6473-7986-1993-5777-7899-0719-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440072/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
It works!
This build successfully allowed the tulip driver to load. I was able to bring
the interface up and acquire an IP address.
--
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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Confirmed
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 6473-7986-1993-5777-7899-0719-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440072/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
Tested the v4.2-rc2 unstable kernel. Problem still exists.
Added tag: kernel-bug-exists-upstream.
** 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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in linux package in Ubuntu:
Confirmed
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 6473-7986-1993-5777-7899-0719-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440072/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
I opened bug 101301 in the kernel.org bugzilla on the same day I post
comment 14 above. It looks like I left this bug number out of comment
14.
--
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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Vivid:
In Progress
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 6473-7986-1993-5777-7899-0719-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440072/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440072] Re: [Hyper-V] Legacy network adapter is not detected
The tulip driver fails to initialize in a Linux VM running on Hyper-V.
The following messages are logged in syslog when trying to load the tulip
driver:
tulip: Linux Tulip drivers version 1.1.15 (Feb 27, 2007)
tulip: :00:0a.0: PCI INT A: failed to register GSI
tulip: Cannot enable tulip board #0, aborting
tulip: probe of :00:0a.0 failed with error -16
The tulip drivers initialization function tulip_init_one() calls
pci_enable_device(). The call to pci_enable_device() eventually
results in a call to alloc_isa_irq_from_domain(), which returns -EBUSY (-16)
The message tulip: :00:0a.0: PCI INT A: failed to register GSI is
logged by acpi_pci_irq_enable().
The flow of calls to the error is returned is:
acpi_pci_irq_enable() - Logs the message PCI INT A: failed to register GSI
acpi_register_gsi()
__acpi_register_gsi() is afunction pointer - acpi_register_gsi_ioapic()
acpi_register_gsi_ioapic()
mp_map_gsi_to_irq()
mp_map_ppin_to_irq()
alloc_isa_irq_from_domain()
Returning -EBUSY when mp_check_pin_attr() returns false.
mp_check_pin_attr()
data-trigger = 1
data-polarity = 0
info-ioapic_trigger = 1
info-ioapic_polarity = 1
mp_check_pin_attr() returns false because the two polarity values do
not match.
acpi_register_gsi_ioapic() is setting trigger and polarity to:
trigger = 1
polarity = 1
mp_check_pin_attr() is calling irq_get_chip_data(irq) which is returning a
mp_chip_data structure with
trigger = 1
polarity = 0
Since the two polarity values do not match, mp_check_pin_attr() returns false.
Broken in 3.19.0 kernel
Works in 3.17 kernel.
Using commits to arch/x86/kernel/acpi/boot.c as reference, the commit where the
issue appears is
cd68f6bd53cf89d1d5ed889b8aaf65e9c3574a079
x86, irq, acpi: Git rid of special handling of GSI for ACPI SCI
--
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/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in linux package in Ubuntu:
Confirmed
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
-- -- -- -- --
---
Network AdapterFalse vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 6 08:17 seq
crw-rw 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
Ballooning works. Hot Add has issues. The original issue as reported has been resolved. Initially, memory is successfully hot added to the VM. As demand continues to increase, no additional memory is hot added. Eventually a hung task message is logged in syslog. The call trace shows hot_add_req() on the call stack. At this point, attempting to shutdown the system with init 0 results in the system hung during the shutdown. The console is showing messages of: INFO: task kworker/0:1:1250 blocked for more than 120 seconds. Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu INFO: task systemd-udev:1317 blocked for more than 120 seconds. Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu See attached file for call traces in syslog. Test environment Host: Windows Server 2012 R2 VM:Ubuntu 14.04, upgraded to current packages (apt-get upgrade) VM Dynammic memory configuration Minimum Memory : 512MB Startup Memory : 512MB Maximum Memory : 4096 Test is to run 8 instances of stressapptest where each instance consumes 128MB for 90 seconds. There is a 5 second delay between starting each instance of stressapptest. ** Attachment added: syslog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1294283/+attachment/4422989/+files/syslog.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/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: Confirmed Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed
[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid
It was requested that I test Ballooning on 14.04.02. Ballooning fails on 14.04.02. Ballooning test on 14.04.02 after running apt-get upgrade Startup Memory : 2048 Minimum Memory : 1024 Maximum Memory : 8192 The utility stressapptest was used to generate memory demand. Let memory settle to 2048MB assigned, 644MB demand. Addd memory demand of 1664MB Assigned memory grew to 2624MB assigned, 2125MB demand. Let system settle to 1044MB assigned, 428MB demand Added memory demand of 1664MB Assigned memory grew to 2732MB assigned, 2376MB demand. After all instances of stressapptest terminated demand dropped to 464MB Assigned memory did not balloon down after 15 minutes. Configured second VM to have a startup memory value to consume all of the hosts free memory. Test VM assigned memory did not balloon down. The dmesg log has stack traces for hung_task_timeout_secs. The call traces are trying to add pages. See attached file. ** Attachment added: dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4412805/+files/dmesg.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/1440103 Title: [Hyper-V] Kernel panic not functional on Vivid Status in linux package in Ubuntu: Confirmed Bug description: Issue description: Triggering a kernel panic will not produce a crash dump file. Steps to Reproduce: 1. install kdump related packages. 2. verify crashmem value - defaults to 384M-:129M 3. verify that the system is ready for crash: # cat /sys/kernel/kexec_crash_loaded 1 4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger 5. The system will freeze and no kernel dump will be generated, system is not rebooted automatically as configured in kdump-tools config. Versions details: Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter build 9600 Distribution name and release: Ubuntu Vivid Vervet Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 SMP Repro output with VM settings as follows: 2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M [ 149.328829] SysRq : Trigger a crash [ 149.342418] BUG: unable to handle kernel NULL pointer dereference at (null) [ 149.346369] IP: [814ae776] sysrq_handle_crash+0x16/0x20 [ 149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0 [ 149.346369] Oops: 0002 [#1] SMP [ 149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 8250_fintek hyperv_keyboard hv_balloon hyp erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy pata_acpi hv_vmbus [ 149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic #11lp14233432v201504021617 [ 149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 [ 149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 88007be7c000 [ 149.346369] RIP: 0010:[814ae776] [814ae776] sysrq_handle_crash+0x16/0x20 [ 149.346369] RSP: 0018:88007be7fe68 EFLAGS: 00010292 [ 149.346369] RAX: 000f RBX: 0063 RCX: 000f [ 149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 0063 [ 149.346369] RBP: 88007be7fe68 R08: 0002 R09: 0275 [ 149.346369] R10: 0092 R11: 0275 R12: 0004 [ 149.346369] R13: R14: 81cb38e0 R15: 0008 [ 149.346369] FS: 7f0a2e22a700() GS:88007ce0() knlGS: [ 149.346369] CS: 0010 DS: ES: CR0: 8005003b [ 149.346369] CR2: CR3: 36047000 CR4: 06f0 [ 149.346369] Stack: [ 149.346369] 88007be7fe98 814aef96 0002 fffb [ 149.346369] 7ffc64e934b0 0002 88007be7feb8 814af443 [ 149.346369] 7ffc64e934b0 8800364f15c0 88007be7fed8 8125ad98 [ 149.346369] Call Trace: [ 149.346369] [814aef96] __handle_sysrq+0x106/0x170 [ 149.346369] [814af443] write_sysrq_trigger+0x33/0x40 [ 149.346369] [8125ad98] proc_reg_write+0x48/0x70 [ 149.346369] [811f33d7] vfs_write+0xb7/0x1f0 [ 149.346369] [811f3ece] ? vfs_read+0x11e/0x140 [ 149.346369] [811f3fe6] SyS_write+0x46/0xb0 [ 149.346369] [817c924d] system_call_fastpath+0x16/0x1b [ 149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00 01 00 00 00 48 89 e5 0f ae f8 c6 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 55 31 c0 48 89 e5 [ 149.346369] RIP [814ae776] sysrq_handle_crash+0x16/0x20 [ 149.346369] RSP 88007be7fe68 [ 149.346369] CR2: [0.00]
[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler
The test kernel worked. The above test kernel successfully logged the 18590 event when the VMs guest OS had a kernel panic. -- 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/1463584 Title: [Hyper-V] Add support for VMBus panic notifier handler Status in linux package in Ubuntu: Confirmed Bug description: Please take these patches to our Hyper-V VMBus driver to enable kernel crash notification: Drivers: hv: vmbus: Add support for VMBus panic notifier handler https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81 Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13 In the event of a kernel panic, VMBus driver supports sending five 64-bit values to be recorded in the log. On Hyper-V this is recorded in the event log, and on Azure we can use this data to better detect failures like this in the guest VM and surface that as part of our diagnostics information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
As a way to validate if equivalent patches have been submitted, the Linux-Next kernel from April 15, 2015 was built and installed on a 14.10 Gen 2 VM. After rebooting into the Linux-Next kernel (version 4.0.0-next-20150415), ballooning worked. Tested dynamic memory configuration: Minimum Memory: 1024MB Startup Memory : 2048MB Maximum Memory: 4096MB Memory buffer: 20% Memory Weight: 50 Two minutes after booting, memory was ballooned down from 2048MB to 1024MB Ran stressapptest to generate 600MB of memory demand Memory was ballooned up to 1762MB After memory demand was removed, memory was ballooned down to 1024MB Ballooning does work with the upstream kernel on a Ubuntu 14.10 Gen 2 VM. -- 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/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: Confirmed Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation
[Kernel-packages] [Bug 1294283] Re: Memory balloning in Hyper-V generation 2 does not work
Bug 1292400 references an email from KY which describes a patch to mm/memory_hotplug.c. KY confirmed the patch in the referenced email was not submitted, but equivalent patches have been submitted. -- 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/1294283 Title: Memory balloning in Hyper-V generation 2 does not work Status in linux package in Ubuntu: Confirmed Bug description: The generation 2 VM has been assinged a memory range of 512 MiB- 4096MiB with a starting memory of 512 MiB. It should get additional memory when needed, but the total available memory in the VM stays at the intial 512 MiB and the kernel starts swapping instead of allocating more memory from the host. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-18-generic 3.13.0-18.38 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Mar 18 19:28:54 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-18-generic N/A linux-backports-modules-3.13.0-18-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=2673d21f-4b48-43f1-9b06-8c141a492700 InstallationDate: Installed on 2014-03-29 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=cccf5e59-012e-4ab5-a6ba-08850e60aba1 ro video=hyperv_fb:1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 RfKill: Tags: trusty Uname: Linux 3.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias:
