“ACPIQEMU0001” unknown ACPI device after Windows 2008 install with libvirtWebcam becomes “Unknown...
Has any human ever had the choice to leave Earth permanently?
What is a good reason for every spaceship to carry a weapon on board?
Can you tell from a blurry photo if focus was too close or too far?
If I delete my router's history can my ISP still provide it to my parents?
Graph with overlapping labels
How does Leonard in "Memento" remember reading and writing?
How do you funnel food off a cutting board?
What would the chemical name be for C13H8Cl3NO
False written accusations not made public - is there law to cover this?
Is it possible to grant users sftp access without shell access? If yes, how is it implemented?
How would an AI self awareness kill switch work?
What are "industrial chops"?
Should I reinstall Linux when changing the laptop's CPU?
Odd 74HCT1G125 behaviour
What is the use of 'de' preposition in 'Yo voy *de* compras todos los sábados'
Dilemma of explaining to interviewer that he is the reason for declining second interview
Mathematics and the art of linearizing the circle
How to play electric guitar and bass as a duet
What are the exceptions to Natural Selection?
Why is it that Bernie Sanders is always called a "socialist"?
How can I play a serial killer in a party of good PCs?
Is using an 'empty' metaphor considered bad style?
Is there any risk in sharing info about technologies and products we use with a supplier?
Can I make estimated tax payments instead of withholding from my paycheck?
“ACPIQEMU0001” unknown ACPI device after Windows 2008 install with libvirt
Webcam becomes “Unknown Device” after Windows Messenger 2011 is installedvagrant fails to create box with libvirtHow can I get hard drive to work for QEMU-virtualized Windows Home Server 2011?Use libvirt to configure KVM guest with user defined tap deviceVERR_VMX_IN_VMX_ROOT_MODE when running VirtualBox with libvirt installedUnknown USB Device (Device Descriptor Request Failed)Vagrant local box with libvirtlibvirt VM using video device with 2 heads not workingStarting libvirt while kickstart install RHEL7How to(Libvirt) attach floppy image device to guest VM?
After installing Windows 2008 in a libvirt virtual environment (command below for reference), I'm stuck with an "Unknown device" in Device Manager. The Hardware Ids
show ACPIQEMU0001
.
I tried using the drivers from the virtio-win-0.1-74.iso
(required for Network and Disk in my case), but no luck.
virt-install --name=win2008 --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/mapper/vgHP-win2008,bus=virtio --network bridge=br0,model=virtio --vnc --noautoconsole
ACPI shutdown (through '# virsh shutdown') does seem to work.
I do have the proper ACPI entries in my domain's XML, from installation time onwards:
<features>
<acpi/>
<apic/>
<pae/>
</features>
Windows cannot find drivers online either. Any idea on how to fix this?
Is it mandatory to fix, or can this be ignored?
I tried again without virtio drivers, i.e. a standard install with IDE, using following command:
# virt-install --name=winserver --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/vgHP/winserver --network bridge=br0 --vnc --noautoconsole
Same behavior though - still an 'Unknown device'.
drivers virtualization qemu libvirt
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
After installing Windows 2008 in a libvirt virtual environment (command below for reference), I'm stuck with an "Unknown device" in Device Manager. The Hardware Ids
show ACPIQEMU0001
.
I tried using the drivers from the virtio-win-0.1-74.iso
(required for Network and Disk in my case), but no luck.
virt-install --name=win2008 --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/mapper/vgHP-win2008,bus=virtio --network bridge=br0,model=virtio --vnc --noautoconsole
ACPI shutdown (through '# virsh shutdown') does seem to work.
I do have the proper ACPI entries in my domain's XML, from installation time onwards:
<features>
<acpi/>
<apic/>
<pae/>
</features>
Windows cannot find drivers online either. Any idea on how to fix this?
Is it mandatory to fix, or can this be ignored?
I tried again without virtio drivers, i.e. a standard install with IDE, using following command:
# virt-install --name=winserver --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/vgHP/winserver --network bridge=br0 --vnc --noautoconsole
Same behavior though - still an 'Unknown device'.
drivers virtualization qemu libvirt
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I think it might be an audio device. Did a quick search on the hardware vendor id and got some hits about audio drivers. Also, noticed that there is no audio device listed in device manger.
– Alex
Apr 9 '14 at 18:15
add a comment |
After installing Windows 2008 in a libvirt virtual environment (command below for reference), I'm stuck with an "Unknown device" in Device Manager. The Hardware Ids
show ACPIQEMU0001
.
I tried using the drivers from the virtio-win-0.1-74.iso
(required for Network and Disk in my case), but no luck.
virt-install --name=win2008 --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/mapper/vgHP-win2008,bus=virtio --network bridge=br0,model=virtio --vnc --noautoconsole
ACPI shutdown (through '# virsh shutdown') does seem to work.
I do have the proper ACPI entries in my domain's XML, from installation time onwards:
<features>
<acpi/>
<apic/>
<pae/>
</features>
Windows cannot find drivers online either. Any idea on how to fix this?
Is it mandatory to fix, or can this be ignored?
I tried again without virtio drivers, i.e. a standard install with IDE, using following command:
# virt-install --name=winserver --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/vgHP/winserver --network bridge=br0 --vnc --noautoconsole
Same behavior though - still an 'Unknown device'.
drivers virtualization qemu libvirt
After installing Windows 2008 in a libvirt virtual environment (command below for reference), I'm stuck with an "Unknown device" in Device Manager. The Hardware Ids
show ACPIQEMU0001
.
I tried using the drivers from the virtio-win-0.1-74.iso
(required for Network and Disk in my case), but no luck.
virt-install --name=win2008 --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/mapper/vgHP-win2008,bus=virtio --network bridge=br0,model=virtio --vnc --noautoconsole
ACPI shutdown (through '# virsh shutdown') does seem to work.
I do have the proper ACPI entries in my domain's XML, from installation time onwards:
<features>
<acpi/>
<apic/>
<pae/>
</features>
Windows cannot find drivers online either. Any idea on how to fix this?
Is it mandatory to fix, or can this be ignored?
I tried again without virtio drivers, i.e. a standard install with IDE, using following command:
# virt-install --name=winserver --ram=3072 --os-type=windows --vcpus=2 --os-variant=win2k8 --cdrom=/var/lib/libvirt/images/6001.18000.080118-1840_amd64fre_Server_en-us-KRMSXFRE_EN_DVD.iso --disk path=/dev/vgHP/winserver --network bridge=br0 --vnc --noautoconsole
Same behavior though - still an 'Unknown device'.
drivers virtualization qemu libvirt
drivers virtualization qemu libvirt
edited Jan 8 '14 at 9:27
SaeX
asked Dec 31 '13 at 11:02
SaeXSaeX
299414
299414
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I think it might be an audio device. Did a quick search on the hardware vendor id and got some hits about audio drivers. Also, noticed that there is no audio device listed in device manger.
– Alex
Apr 9 '14 at 18:15
add a comment |
I think it might be an audio device. Did a quick search on the hardware vendor id and got some hits about audio drivers. Also, noticed that there is no audio device listed in device manger.
– Alex
Apr 9 '14 at 18:15
I think it might be an audio device. Did a quick search on the hardware vendor id and got some hits about audio drivers. Also, noticed that there is no audio device listed in device manger.
– Alex
Apr 9 '14 at 18:15
I think it might be an audio device. Did a quick search on the hardware vendor id and got some hits about audio drivers. Also, noticed that there is no audio device listed in device manger.
– Alex
Apr 9 '14 at 18:15
add a comment |
1 Answer
1
active
oldest
votes
I have ubuntu 13.10 server + kvm. On XP guest i had unknovn device ACPIQEMU00014&2C5A7332&0
Turns out it was VirtIO-Serial communication device.
Extracted driver from virtio-win-0.1-74.iso virtio-winWXP
hope it helps someone.
;]
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f695283%2facpi-qemu0001-unknown-acpi-device-after-windows-2008-install-with-libvirt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have ubuntu 13.10 server + kvm. On XP guest i had unknovn device ACPIQEMU00014&2C5A7332&0
Turns out it was VirtIO-Serial communication device.
Extracted driver from virtio-win-0.1-74.iso virtio-winWXP
hope it helps someone.
;]
add a comment |
I have ubuntu 13.10 server + kvm. On XP guest i had unknovn device ACPIQEMU00014&2C5A7332&0
Turns out it was VirtIO-Serial communication device.
Extracted driver from virtio-win-0.1-74.iso virtio-winWXP
hope it helps someone.
;]
add a comment |
I have ubuntu 13.10 server + kvm. On XP guest i had unknovn device ACPIQEMU00014&2C5A7332&0
Turns out it was VirtIO-Serial communication device.
Extracted driver from virtio-win-0.1-74.iso virtio-winWXP
hope it helps someone.
;]
I have ubuntu 13.10 server + kvm. On XP guest i had unknovn device ACPIQEMU00014&2C5A7332&0
Turns out it was VirtIO-Serial communication device.
Extracted driver from virtio-win-0.1-74.iso virtio-winWXP
hope it helps someone.
;]
answered May 23 '14 at 17:03
user01user01
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f695283%2facpi-qemu0001-unknown-acpi-device-after-windows-2008-install-with-libvirt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think it might be an audio device. Did a quick search on the hardware vendor id and got some hits about audio drivers. Also, noticed that there is no audio device listed in device manger.
– Alex
Apr 9 '14 at 18:15