* [qemu bug] device assignment doesn't work: "error: requires KVM support"
@ 2011-10-27 2:56 Ren, Yongjie
2011-10-27 3:04 ` Alex Williamson
0 siblings, 1 reply; 10+ messages in thread
From: Ren, Yongjie @ 2011-10-27 2:56 UTC (permalink / raw)
To: KVM General; +Cc: Avi Kivity, Alex Williamson
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Hi,
When doing device assignment with qemu and kvm upstream, I met "error: requires KVM support".
Please also refer to the bug in qemu bugzilla.
https://bugs.launchpad.net/qemu/+bug/882358
qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890
I met the following error when doing device assignment with qemu in kvm host.
./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/rhel6u1.img
qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support
qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized
./x86_64-softmmu/qemu-system-x86_64 -device ? 2>&1 | grep -i pci-assign
name "pci-assign", bus PCI, desc "pass through host pci devices to the guest"
When configuring the qemu, it prints "KVM support yes". My qemu configuration log and compiling log are attached.
But commit edbb7c0d doesn't have this issue.
Best Regards,
Yongjie Ren (Jay)
[-- Attachment #2: configure.log --]
[-- Type: application/octet-stream, Size: 2328 bytes --]
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
library directory /usr/local/lib
include directory /usr/local/include
config directory /usr/local/etc
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /root/qemu-kvm
C compiler gcc
Host C compiler gcc
CFLAGS -O2 -g
QEMU_CFLAGS -Werror -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -I/usr/include/libpng12 -I$(SRC_PATH)/libcacard -I/usr/include/nss3 -I/usr/include/nspr4
LDFLAGS -Wl,--warn-common -m64 -g
make make
install install
python python
smbd /usr/sbin/smbd
host CPU x86_64
host big endian no
target list x86_64-softmmu
tcg debug enabled no
Mon debug enabled no
gprof enabled no
sparse enabled no
strip binaries yes
profiler no
static build no
-Werror enabled yes
SDL support no
curses support yes
curl support yes
check support no
mingw32 support no
Audio drivers oss
Extra audio cards ac97 es1370 sb16 hda
Block whitelist
Mixer emulation no
VNC support yes
VNC TLS support yes
VNC SASL support yes
VNC JPEG support no
VNC PNG support yes
VNC thread no
xen support no
CPU emulation yes
brlapi support no
bluez support no
Documentation no
NPTL support yes
GUEST_BASE yes
PIE user targets no
vde support no
Linux AIO support no
ATTR/XATTR support yes
Install blobs yes
KVM support yes
KVM PIT support yes
KVM device assig. yes
fdt support no
preadv support yes
fdatasync yes
madvise yes
posix_madvise yes
uuid support no
vhost-net support yes
Trace backend nop
Trace output file trace-<pid>
spice support no
rbd support no
xfsctl support no
nss used yes
usb net redir no
OpenGL support no
build guest agent yes
[-- Attachment #3: make.log --]
[-- Type: application/octet-stream, Size: 9474 bytes --]
GEN config-host.h
GEN trace.h
GEN qemu-options.def
GEN qapi-generated/qga-qapi-visit.h
GEN trace.c
GEN qemu-img-cmds.h
AS optionrom/multiboot.o
AS optionrom/linuxboot.o
AS optionrom/vapic.o
Building optionrom/multiboot.img
Building optionrom/linuxboot.img
Building optionrom/vapic.img
Building optionrom/multiboot.raw
Building optionrom/linuxboot.raw
Building optionrom/vapic.raw
Signing optionrom/multiboot.bin
Signing optionrom/linuxboot.bin
Signing optionrom/vapic.bin
GEN qapi-generated/qga-qapi-types.h
GEN qapi-generated/qga-qmp-marshal.c
CC qapi/qapi-visit-core.o
CC qapi/qmp-input-visitor.o
CC qapi/qmp-output-visitor.o
CC qapi/qapi-dealloc-visitor.o
CC qapi/qmp-registry.o
CC trace.o
CC qapi/qmp-dispatch.o
CC trace/default.o
CC trace/control.o
CC qint.o
CC qstring.o
CC qdict.o
CC qlist.o
CC qfloat.o
CC qbool.o
CC json-lexer.o
CC qjson.o
CC json-streamer.o
CC json-parser.o
CC qerror.o
CC error.o
CC qapi-generated/qga-qapi-visit.o
CC qapi-generated/qga-qmp-marshal.o
CC qemu-nbd.o
CC qemu-thread-posix.o
CC cache-utils.o
CC async.o
CC nbd.o
CC block.o
CC aio.o
CC aes.o
CC qemu-config.o
CC qemu-progress.o
CC qemu-coroutine.o
CC qemu-coroutine-lock.o
CC coroutine-ucontext.o
CC posix-aio-compat.o
CC block/cow.o
CC block/raw.o
CC block/qcow.o
CC block/vdi.o
CC block/vmdk.o
CC block/cloop.o
CC block/dmg.o
CC block/bochs.o
CC block/vpc.o
CC block/vvfat.o
CC block/qcow2.o
CC block/qcow2-refcount.o
CC block/qcow2-cluster.o
CC block/qcow2-snapshot.o
CC block/qcow2-cache.o
CC block/qed.o
CC block/qed-gencb.o
CC block/qed-l2-cache.o
CC block/qed-table.o
CC block/qed-cluster.o
CC block/qed-check.o
CC block/parallels.o
CC block/nbd.o
CC block/blkdebug.o
CC block/sheepdog.o
CC block/blkverify.o
CC block/raw-posix.o
CC block/curl.o
CC qemu-timer-common.o
CC qemu-img.o
CC qemu-io.o
CC cmd.o
CC libhw64/vl.o
CC blockdev.o
CC net.o
CC libhw64/loader.o
CC libhw64/virtio-console.o
CC libhw64/usb-libhw.o
CC libhw64/virtio-pci.o
CC libhw64/fw_cfg.o
CC libhw64/pci_bridge.o
CC libhw64/msix.o
CC net/queue.o
CC libhw64/msi.o
CC net/checksum.o
CC libhw64/pci_host.o
CC libhw64/pcie_host.o
CC libhw64/ioh3420.o
CC libhw64/xio3130_upstream.o
CC libhw64/xio3130_downstream.o
CC net/util.o
CC net/socket.o
CC net/dump.o
CC libhw64/watchdog.o
CC libhw64/serial.o
CC libhw64/parallel.o
CC net/tap.o
CC libhw64/pckbd.o
CC libhw64/usb-uhci.o
CC net/tap-linux.o
CC libhw64/usb-ohci.o
CC net/slirp.o
CC fsdev/qemu-fsdev.o
CC readline.o
CC libhw64/usb-ehci.o
CC libhw64/fdc.o
CC console.o
CC cursor.o
CC os-posix.o
CC tcg-runtime.o
CC host-utils.o
CC libhw64/pm_smbus.o
CC irq.o
CC libhw64/apm.o
CC input.o
CC i2c.o
CC smbus.o
CC libhw64/dma.o
CC smbus_eeprom.o
CC libhw64/hpet.o
CC libhw64/applesmc.o
CC eeprom93xx.o
CC libhw64/usb-ccid.o
CC libhw64/ccid-card-passthru.o
CC libhw64/ccid-card-emulated.o
CC libhw64/i8259.o
CC scsi-disk.o
CC libhw64/wdt_i6300esb.o
CC libhw64/pcie.o
CC libhw64/pcie_aer.o
CC cdrom.o
CC libhw64/pcie_port.o
CC scsi-generic.o
CC scsi-bus.o
CC libhw64/ne2000.o
CC hid.o
CC usb.o
CC libhw64/eepro100.o
CC usb-hub.o
CC usb-linux.o
CC usb-hid.o
CC usb-msd.o
CC usb-wacom.o
CC libhw64/pcnet-pci.o
CC libhw64/pcnet.o
CC usb-serial.o
CC libhw64/e1000.o
CC libhw64/rtl8139.o
CC usb-net.o
CC usb-bus.o
CC libhw64/ne2000-isa.o
CC usb-desc.o
CC libhw64/ide/core.o
CC bt.o
CC libhw64/ide/atapi.o
CC libhw64/ide/qdev.o
CC bt-host.o
CC bt-vhci.o
CC bt-l2cap.o
CC libhw64/ide/pci.o
CC bt-sdp.o
CC bt-hci.o
CC bt-hid.o
CC usb-bt.o
CC libhw64/ide/isa.o
CC libhw64/ide/piix.o
CC libhw64/ide/ahci.o
CC bt-hci-csr.o
CC libhw64/ide/ich.o
CC libhw64/lsi53c895a.o
CC libhw64/dma-helpers.o
CC libhw64/sysbus.o
CC libhw64/isa-bus.o
CC libhw64/qdev-addr.o
CC buffered_file.o
CC migration.o
CC libhw64/vga-pci.o
CC libhw64/vga-isa.o
CC migration-tcp.o
CC libhw64/vmware_vga.o
CC libhw64/vmmouse.o
CC qemu-char.o
CC savevm.o
CC msmouse.o
CC ps2.o
CC qdev.o
CC qdev-properties.o
CC libhw64/sb16.o
CC libhw64/es1370.o
CC block-migration.o
CC libhw64/ac97.o
CC libhw64/intel-hda.o
CC libhw64/hda-audio.o
CC iohandler.o
CC pflib.o
CC bitmap.o
CC bitops.o
CC migration-exec.o
CC migration-unix.o
CC migration-fd.o
CC audio/audio.o
CC libhw64/9pfs/virtio-9p.o
CC audio/noaudio.o
CC libhw64/9pfs/virtio-9p-debug.o
CC audio/wavaudio.o
CC libhw64/9pfs/virtio-9p-local.o
CC libhw64/9pfs/virtio-9p-xattr.o
CC audio/mixeng.o
CC libhw64/9pfs/virtio-9p-xattr-user.o
CC libhw64/9pfs/virtio-9p-posix-acl.o
CC libhw64/9pfs/virtio-9p-coth.o
CC libhw64/9pfs/cofs.o
CC libhw64/9pfs/codir.o
CC audio/ossaudio.o
CC audio/wavcapture.o
CC ui/keymaps.o
CC ui/curses.o
CC ui/vnc.o
CC ui/d3des.o
CC libhw64/9pfs/cofile.o
CC ui/vnc-enc-zlib.o
CC ui/vnc-enc-hextile.o
CC ui/vnc-enc-tight.o
CC ui/vnc-palette.o
CC ui/vnc-enc-zrle.o
CC libhw64/9pfs/coxattr.o
CC libhw64/9pfs/virtio-9p-handle.o
CC ui/vnc-tls.o
CC ui/vnc-auth-vencrypt.o
CC ui/vnc-auth-sasl.o
CC ui/vnc-jobs-sync.o
CC iov.o
CC acl.o
CC compatfd.o
CC notify.o
CC event_notifier.o
CC qemu-timer.o
CC slirp/cksum.o
CC slirp/ip_icmp.o
CC slirp/if.o
CC slirp/ip_input.o
CC slirp/ip_output.o
CC slirp/slirp.o
CC slirp/mbuf.o
CC slirp/misc.o
CC slirp/sbuf.o
CC slirp/socket.o
CC slirp/tcp_input.o
CC slirp/tcp_output.o
CC slirp/tcp_subr.o
CC slirp/udp.o
CC slirp/bootp.o
CC slirp/tftp.o
CC slirp/arp_table.o
CC qmp-marshal.o
CC qapi-visit.o
CC qapi-types.o
CC qmp.o
CC hmp.o
CC libdis/i386-dis.o
CC qemu-ga.o
CC qga/guest-agent-commands.o
CC qga/guest-agent-command-state.o
CC qemu-tool.o
CC qemu-error.o
CC qemu-sockets.o
CC module.o
CC qemu-option.o
CC cutils.o
CC osdep.o
CC oslib-posix.o
CC qapi-generated/qga-qapi-types.o
CC libcacard/cac.o
CC libcacard/vcard.o
CC libcacard/event.o
CC libcacard/vreader.o
CC libcacard/vcard_emul_nss.o
CC libcacard/card_7816.o
CC libcacard/vcard_emul_type.o
CC libcacard/vscclient.o
LINK qemu-ga
LINK qemu-nbd
LINK qemu-img
LINK qemu-io
LINK vscclient
GEN config-target.h
GEN x86_64-softmmu/hmp-commands.h
GEN x86_64-softmmu/qmp-commands-old.h
CC x86_64-softmmu/arch_init.o
CC x86_64-softmmu/machine.o
CC x86_64-softmmu/cpus.o
CC x86_64-softmmu/gdbstub.o
CC x86_64-softmmu/balloon.o
CC x86_64-softmmu/ioport.o
CC x86_64-softmmu/pci.o
CC x86_64-softmmu/virtio.o
CC x86_64-softmmu/virtio-blk.o
CC x86_64-softmmu/virtio-balloon.o
CC x86_64-softmmu/virtio-serial-bus.o
CC x86_64-softmmu/virtio-net.o
CC x86_64-softmmu/vhost_net.o
CC x86_64-softmmu/vhost.o
CC x86_64-softmmu/9pfs/virtio-9p-device.o
CC x86_64-softmmu/kvm.o
CC x86_64-softmmu/kvm-all.o
CC x86_64-softmmu/memory.o
CC x86_64-softmmu/xen-stub.o
CC x86_64-softmmu/ivshmem.o
CC x86_64-softmmu/exec.o
CC x86_64-softmmu/cpu-exec.o
CC x86_64-softmmu/translate-all.o
CC x86_64-softmmu/translate.o
CC x86_64-softmmu/tcg/tcg.o
CC x86_64-softmmu/tcg/optimize.o
CC x86_64-softmmu/fpu/softfloat.o
CC x86_64-softmmu/op_helper.o
CC x86_64-softmmu/helper.o
CC x86_64-softmmu/cpuid.o
CC x86_64-softmmu/kvm-tpr-opt.o
CC x86_64-softmmu/disas.o
CC x86_64-softmmu/vga.o
CC x86_64-softmmu/mc146818rtc.o
CC x86_64-softmmu/pc.o
CC x86_64-softmmu/cirrus_vga.o
CC x86_64-softmmu/sga.o
CC x86_64-softmmu/apic.o
CC x86_64-softmmu/ioapic.o
CC x86_64-softmmu/piix_pci.o
CC x86_64-softmmu/vmport.o
CC x86_64-softmmu/device-hotplug.o
CC x86_64-softmmu/pci-hotplug.o
CC x86_64-softmmu/smbios.o
CC x86_64-softmmu/wdt_ib700.o
CC x86_64-softmmu/debugcon.o
rm vapic.o multiboot.o linuxboot.raw linuxboot.img vapic.raw vapic.img multiboot.raw multiboot.img linuxboot.o
CC x86_64-softmmu/multiboot.o
CC x86_64-softmmu/pc_piix.o
CC x86_64-softmmu/kvmclock.o
CC x86_64-softmmu/testdev.o
CC x86_64-softmmu/acpi.o
CC x86_64-softmmu/acpi_piix4.o
CC x86_64-softmmu/pcspk.o
CC x86_64-softmmu/i8254.o
CC x86_64-softmmu/i8254-kvm.o
CC x86_64-softmmu/device-assignment.o
CC x86_64-softmmu/monitor.o
LINK x86_64-softmmu/qemu-system-x86_64
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 2:56 [qemu bug] device assignment doesn't work: "error: requires KVM support" Ren, Yongjie
@ 2011-10-27 3:04 ` Alex Williamson
2011-10-27 3:17 ` Ren, Yongjie
0 siblings, 1 reply; 10+ messages in thread
From: Alex Williamson @ 2011-10-27 3:04 UTC (permalink / raw)
To: Ren, Yongjie; +Cc: KVM General, Avi Kivity
On Thu, 2011-10-27 at 10:56 +0800, Ren, Yongjie wrote:
> Hi,
> When doing device assignment with qemu and kvm upstream, I met "error: requires KVM support".
> Please also refer to the bug in qemu bugzilla.
> https://bugs.launchpad.net/qemu/+bug/882358
>
> qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890
>
> I met the following error when doing device assignment with qemu in kvm host.
> ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/rhel6u1.img
> qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error: requires KVM support
> qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could not be initialized
>
> ./x86_64-softmmu/qemu-system-x86_64 -device ? 2>&1 | grep -i pci-assign
> name "pci-assign", bus PCI, desc "pass through host pci devices to the guest"
>
> When configuring the qemu, it prints "KVM support yes". My qemu configuration log and compiling log are attached.
>
> But commit edbb7c0d doesn't have this issue.
Note these are qemu-kvm.git commit IDs.
The error message is correct, device assignment requires kvm support.
What does 'info kvm' in the monitor report?
Alex
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 3:04 ` Alex Williamson
@ 2011-10-27 3:17 ` Ren, Yongjie
2011-10-27 6:49 ` Markus Armbruster
0 siblings, 1 reply; 10+ messages in thread
From: Ren, Yongjie @ 2011-10-27 3:17 UTC (permalink / raw)
To: Alex Williamson; +Cc: KVM General, Avi Kivity
> -----Original Message-----
> From: Alex Williamson [mailto:alex.williamson@redhat.com]
> Sent: Thursday, October 27, 2011 11:04 AM
> To: Ren, Yongjie
> Cc: KVM General; Avi Kivity
> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
> support"
>
> On Thu, 2011-10-27 at 10:56 +0800, Ren, Yongjie wrote:
> > Hi,
> > When doing device assignment with qemu and kvm upstream, I met "error:
> requires KVM support".
> > Please also refer to the bug in qemu bugzilla.
> > https://bugs.launchpad.net/qemu/+bug/882358
> >
> > qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890
> >
> > I met the following error when doing device assignment with qemu in kvm
> host.
> > ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device
> pci-assign,host=0e:00.0 -hda /root/rhel6u1.img
> > qemu-system-x86_64: -device pci-assign,host=0e:00.0: pci-assign: error:
> requires KVM support
> > qemu-system-x86_64: -device pci-assign,host=0e:00.0: Device 'pci-assign' could
> not be initialized
> >
> > ./x86_64-softmmu/qemu-system-x86_64 -device ? 2>&1 | grep -i pci-assign
> > name "pci-assign", bus PCI, desc "pass through host pci devices to the guest"
> >
> > When configuring the qemu, it prints "KVM support yes". My qemu
> configuration log and compiling log are attached.
> >
> > But commit edbb7c0d doesn't have this issue.
It's edbb7c0de56692868e6126c7ff7e8bf917f8d0e7. "edbb7c0d" is unique in git log, so it may stand for its full commit ID.
> Note these are qemu-kvm.git commit IDs.
They are commit IDs in master branch of git://github.com/avikivity/qemu.git
>
> The error message is correct, device assignment requires kvm support.
> What does 'info kvm' in the monitor report?
It shows "kvm support: disabled".
But when configuring qemu, I get this message " KVM support yes". See details in my attachment configure.log
yongjie
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 3:17 ` Ren, Yongjie
@ 2011-10-27 6:49 ` Markus Armbruster
2011-10-27 7:03 ` Ren, Yongjie
0 siblings, 1 reply; 10+ messages in thread
From: Markus Armbruster @ 2011-10-27 6:49 UTC (permalink / raw)
To: Ren, Yongjie; +Cc: Alex Williamson, KVM General, Avi Kivity
"Ren, Yongjie" <yongjie.ren@intel.com> writes:
>> -----Original Message-----
>> From: Alex Williamson [mailto:alex.williamson@redhat.com]
>> Sent: Thursday, October 27, 2011 11:04 AM
>> To: Ren, Yongjie
>> Cc: KVM General; Avi Kivity
>> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
>> support"
[...]
>> The error message is correct, device assignment requires kvm support.
>> What does 'info kvm' in the monitor report?
> It shows "kvm support: disabled".
> But when configuring qemu, I get this message " KVM support yes". See details in my attachment configure.log
Try running with --enable-kvm.
Check /dev/kvm permissions.
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 6:49 ` Markus Armbruster
@ 2011-10-27 7:03 ` Ren, Yongjie
2011-10-27 7:12 ` Ren, Yongjie
2011-10-27 7:18 ` Markus Armbruster
0 siblings, 2 replies; 10+ messages in thread
From: Ren, Yongjie @ 2011-10-27 7:03 UTC (permalink / raw)
To: Markus Armbruster; +Cc: Alex Williamson, KVM General, Avi Kivity
> -----Original Message-----
> From: Markus Armbruster [mailto:armbru@redhat.com]
> Sent: Thursday, October 27, 2011 2:50 PM
> To: Ren, Yongjie
> Cc: Alex Williamson; KVM General; Avi Kivity
> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
> support"
>
> "Ren, Yongjie" <yongjie.ren@intel.com> writes:
>
> >> -----Original Message-----
> >> From: Alex Williamson [mailto:alex.williamson@redhat.com]
> >> Sent: Thursday, October 27, 2011 11:04 AM
> >> To: Ren, Yongjie
> >> Cc: KVM General; Avi Kivity
> >> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires
> KVM
> >> support"
> [...]
> >> The error message is correct, device assignment requires kvm support.
> >> What does 'info kvm' in the monitor report?
> > It shows "kvm support: disabled".
> > But when configuring qemu, I get this message " KVM support yes". See details
> in my attachment configure.log
>
> Try running with --enable-kvm.
I added '--enable-kvm' when configuring qemu. I got the same configure output. And I compiled and ran qemu, then I met the same issue as I describled before.
> Check /dev/kvm permissions.
I have the permission for /dev/kvm. I use 'root' account.
ls -l /dev/kvm
crw-rw---- 1 root root 10, 232 Oct 26 22:48 /dev/kvm
yongjie
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 7:03 ` Ren, Yongjie
@ 2011-10-27 7:12 ` Ren, Yongjie
2011-10-27 7:20 ` Markus Armbruster
2011-10-27 7:18 ` Markus Armbruster
1 sibling, 1 reply; 10+ messages in thread
From: Ren, Yongjie @ 2011-10-27 7:12 UTC (permalink / raw)
To: Ren, Yongjie, Markus Armbruster; +Cc: Alex Williamson, KVM General, Avi Kivity
> -----Original Message-----
> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On
> Behalf Of Ren, Yongjie
> Sent: Thursday, October 27, 2011 3:03 PM
> To: Markus Armbruster
> Cc: Alex Williamson; KVM General; Avi Kivity
> Subject: RE: [qemu bug] device assignment doesn't work: "error: requires KVM
> support"
>
> > -----Original Message-----
> > From: Markus Armbruster [mailto:armbru@redhat.com]
> > Sent: Thursday, October 27, 2011 2:50 PM
> > To: Ren, Yongjie
> > Cc: Alex Williamson; KVM General; Avi Kivity
> > Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
> > support"
> >
> > "Ren, Yongjie" <yongjie.ren@intel.com> writes:
> >
> > >> -----Original Message-----
> > >> From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > >> Sent: Thursday, October 27, 2011 11:04 AM
> > >> To: Ren, Yongjie
> > >> Cc: KVM General; Avi Kivity
> > >> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires
> > KVM
> > >> support"
> > [...]
> > >> The error message is correct, device assignment requires kvm support.
> > >> What does 'info kvm' in the monitor report?
> > > It shows "kvm support: disabled".
> > > But when configuring qemu, I get this message " KVM support yes". See
> details
> > in my attachment configure.log
> >
> > Try running with --enable-kvm.
>
> I added '--enable-kvm' when configuring qemu. I got the same configure output.
> And I compiled and ran qemu, then I met the same issue as I describled before.
Oh, adding '--enable-kvm' when running qemu will work. The following command line enables kvm when qemu starting.
./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/rhel6u1.img --enable-kvm
But it didn't need to add '--enable-kvm' two weeks ago. Must we add this parameter from now on if we want to use kvm ?
> > Check /dev/kvm permissions.
> I have the permission for /dev/kvm. I use 'root' account.
> ls -l /dev/kvm
> crw-rw---- 1 root root 10, 232 Oct 26 22:48 /dev/kvm
>
> yongjie
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 7:03 ` Ren, Yongjie
2011-10-27 7:12 ` Ren, Yongjie
@ 2011-10-27 7:18 ` Markus Armbruster
1 sibling, 0 replies; 10+ messages in thread
From: Markus Armbruster @ 2011-10-27 7:18 UTC (permalink / raw)
To: Ren, Yongjie; +Cc: Alex Williamson, KVM General, Avi Kivity
"Ren, Yongjie" <yongjie.ren@intel.com> writes:
>> -----Original Message-----
>> From: Markus Armbruster [mailto:armbru@redhat.com]
>> Sent: Thursday, October 27, 2011 2:50 PM
>> To: Ren, Yongjie
>> Cc: Alex Williamson; KVM General; Avi Kivity
>> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
>> support"
>>
>> "Ren, Yongjie" <yongjie.ren@intel.com> writes:
>>
>> >> -----Original Message-----
>> >> From: Alex Williamson [mailto:alex.williamson@redhat.com]
>> >> Sent: Thursday, October 27, 2011 11:04 AM
>> >> To: Ren, Yongjie
>> >> Cc: KVM General; Avi Kivity
>> >> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires
>> KVM
>> >> support"
>> [...]
>> >> The error message is correct, device assignment requires kvm support.
>> >> What does 'info kvm' in the monitor report?
>> > It shows "kvm support: disabled".
>> > But when configuring qemu, I get this message " KVM support yes". See details
>> in my attachment configure.log
>>
>> Try running with --enable-kvm.
>
> I added '--enable-kvm' when configuring qemu. I got the same configure output. And I compiled and ran qemu, then I met the same issue as I describled before.
Sorry, I meant run qemu --enable-kvm.
>> Check /dev/kvm permissions.
> I have the permission for /dev/kvm. I use 'root' account.
> ls -l /dev/kvm
> crw-rw---- 1 root root 10, 232 Oct 26 22:48 /dev/kvm
>
> yongjie
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 7:12 ` Ren, Yongjie
@ 2011-10-27 7:20 ` Markus Armbruster
2011-10-27 7:38 ` Jan Kiszka
0 siblings, 1 reply; 10+ messages in thread
From: Markus Armbruster @ 2011-10-27 7:20 UTC (permalink / raw)
To: Ren, Yongjie; +Cc: Alex Williamson, KVM General, Avi Kivity
"Ren, Yongjie" <yongjie.ren@intel.com> writes:
>> -----Original Message-----
>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On
>> Behalf Of Ren, Yongjie
>> Sent: Thursday, October 27, 2011 3:03 PM
>> To: Markus Armbruster
>> Cc: Alex Williamson; KVM General; Avi Kivity
>> Subject: RE: [qemu bug] device assignment doesn't work: "error: requires KVM
>> support"
>>
>> > -----Original Message-----
>> > From: Markus Armbruster [mailto:armbru@redhat.com]
>> > Sent: Thursday, October 27, 2011 2:50 PM
>> > To: Ren, Yongjie
>> > Cc: Alex Williamson; KVM General; Avi Kivity
>> > Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
>> > support"
>> >
>> > "Ren, Yongjie" <yongjie.ren@intel.com> writes:
>> >
>> > >> -----Original Message-----
>> > >> From: Alex Williamson [mailto:alex.williamson@redhat.com]
>> > >> Sent: Thursday, October 27, 2011 11:04 AM
>> > >> To: Ren, Yongjie
>> > >> Cc: KVM General; Avi Kivity
>> > >> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires
>> > KVM
>> > >> support"
>> > [...]
>> > >> The error message is correct, device assignment requires kvm support.
>> > >> What does 'info kvm' in the monitor report?
>> > > It shows "kvm support: disabled".
>> > > But when configuring qemu, I get this message " KVM support yes". See
>> details
>> > in my attachment configure.log
>> >
>> > Try running with --enable-kvm.
>>
>> I added '--enable-kvm' when configuring qemu. I got the same configure output.
>> And I compiled and ran qemu, then I met the same issue as I describled before.
> Oh, adding '--enable-kvm' when running qemu will work. The following command line enables kvm when qemu starting.
> ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/rhel6u1.img --enable-kvm
> But it didn't need to add '--enable-kvm' two weeks ago. Must we add this parameter from now on if we want to use kvm ?
Use of KVM should still be the default. If it isn't anymore, can you
use bisect to finger the commit that broke it?
[...]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 7:20 ` Markus Armbruster
@ 2011-10-27 7:38 ` Jan Kiszka
2011-10-27 12:36 ` Marcelo Tosatti
0 siblings, 1 reply; 10+ messages in thread
From: Jan Kiszka @ 2011-10-27 7:38 UTC (permalink / raw)
To: Markus Armbruster; +Cc: Ren, Yongjie, Alex Williamson, KVM General, Avi Kivity
[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]
On 2011-10-27 09:20, Markus Armbruster wrote:
> "Ren, Yongjie" <yongjie.ren@intel.com> writes:
>
>>> -----Original Message-----
>>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On
>>> Behalf Of Ren, Yongjie
>>> Sent: Thursday, October 27, 2011 3:03 PM
>>> To: Markus Armbruster
>>> Cc: Alex Williamson; KVM General; Avi Kivity
>>> Subject: RE: [qemu bug] device assignment doesn't work: "error: requires KVM
>>> support"
>>>
>>>> -----Original Message-----
>>>> From: Markus Armbruster [mailto:armbru@redhat.com]
>>>> Sent: Thursday, October 27, 2011 2:50 PM
>>>> To: Ren, Yongjie
>>>> Cc: Alex Williamson; KVM General; Avi Kivity
>>>> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires KVM
>>>> support"
>>>>
>>>> "Ren, Yongjie" <yongjie.ren@intel.com> writes:
>>>>
>>>>>> -----Original Message-----
>>>>>> From: Alex Williamson [mailto:alex.williamson@redhat.com]
>>>>>> Sent: Thursday, October 27, 2011 11:04 AM
>>>>>> To: Ren, Yongjie
>>>>>> Cc: KVM General; Avi Kivity
>>>>>> Subject: Re: [qemu bug] device assignment doesn't work: "error: requires
>>>> KVM
>>>>>> support"
>>>> [...]
>>>>>> The error message is correct, device assignment requires kvm support.
>>>>>> What does 'info kvm' in the monitor report?
>>>>> It shows "kvm support: disabled".
>>>>> But when configuring qemu, I get this message " KVM support yes". See
>>> details
>>>> in my attachment configure.log
>>>>
>>>> Try running with --enable-kvm.
>>>
>>> I added '--enable-kvm' when configuring qemu. I got the same configure output.
>>> And I compiled and ran qemu, then I met the same issue as I describled before.
>> Oh, adding '--enable-kvm' when running qemu will work. The following command line enables kvm when qemu starting.
>> ./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device pci-assign,host=0e:00.0 -hda /root/rhel6u1.img --enable-kvm
>> But it didn't need to add '--enable-kvm' two weeks ago. Must we add this parameter from now on if we want to use kvm ?
>
> Use of KVM should still be the default. If it isn't anymore, can you
> use bisect to finger the commit that broke it?
Might be "qemu-kvm: set default accelerator via target.conf". Unless you
fully install qemu, that conf is not picked up (or an older version is
used). I'd still like to see this working with qemu started from a build
directory...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [qemu bug] device assignment doesn't work: "error: requires KVM support"
2011-10-27 7:38 ` Jan Kiszka
@ 2011-10-27 12:36 ` Marcelo Tosatti
0 siblings, 0 replies; 10+ messages in thread
From: Marcelo Tosatti @ 2011-10-27 12:36 UTC (permalink / raw)
To: Jan Kiszka
Cc: Markus Armbruster, Ren, Yongjie, Alex Williamson, KVM General,
Avi Kivity
On Thu, Oct 27, 2011 at 09:38:02AM +0200, Jan Kiszka wrote:
> >> But it didn't need to add '--enable-kvm' two weeks ago. Must we add this parameter from now on if we want to use kvm ?
> >
> > Use of KVM should still be the default. If it isn't anymore, can you
> > use bisect to finger the commit that broke it?
>
> Might be "qemu-kvm: set default accelerator via target.conf". Unless you
> fully install qemu, that conf is not picked up (or an older version is
> used). I'd still like to see this working with qemu started from a build
> directory...
>
> Jan
Actually it was lack of 0eb2a7e9010f2 since he was using 8843cf40.
But you're right, reverted a5c40eb1aa9 for now, thanks.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-10-27 12:37 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-27 2:56 [qemu bug] device assignment doesn't work: "error: requires KVM support" Ren, Yongjie
2011-10-27 3:04 ` Alex Williamson
2011-10-27 3:17 ` Ren, Yongjie
2011-10-27 6:49 ` Markus Armbruster
2011-10-27 7:03 ` Ren, Yongjie
2011-10-27 7:12 ` Ren, Yongjie
2011-10-27 7:20 ` Markus Armbruster
2011-10-27 7:38 ` Jan Kiszka
2011-10-27 12:36 ` Marcelo Tosatti
2011-10-27 7:18 ` Markus Armbruster
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.