Re: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
9:47 a.m.
[On the topic of qemu 1.1.0 in Fedora 17]
I'm seeing some very peculiar problems with virt-install that might be
due to libvirt. Is libvirt in F17 too old for qemu 1.1.0?
-------
(1) Just installing qemu-system-x86 isn't enough for libvirt to
recognize any hypervisors:
ERROR Host does not support any virtualization options
virsh capabilities doesn't show any <guest> section at all. Of course
qemu-kvm *is* installed and working.
Solution: install the qemu meta-package. Unfortunately that means I
have to have qemu-system-{cris,sh4,arm,mips} which I didn't want.
(2) If I use virt-install --cpu=host, I get:
ERROR unsupported configuration: CPU specification not supported by hypervisor
Solution was to not use this option.
(3) Now virt-install says:
ERROR internal error process exited while connecting to monitor: char device redirected
to /dev/pts/19
Error: Cirrus VGA not available
Solution was to use --graphics=spice.
(4) Now virt-install says:
ERROR internal error process exited while connecting to monitor: char device redirected
to /dev/pts/19
do_spice_init: starting 0.10.1
spice_server_add_interface: SPICE_INTERFACE_MIGRATION
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
Kernel image must be specified
The error here is "Kernel image must be specified".
By this point it was getting very strange, so I decided to look
at the libvirt log files for the qemu command line ...
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none
/usr/bin/qemu-system-arm -S -M integratorcp -no-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name OpenSUSE113x64 -uuid
4f959395-9203-7e3d-09e6-e43369286a2c -nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/OpenSUSE113x64.monitor,server,nowait -mon
chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci,addr=0x1.0x2 -drive
file=/dev/vg_pin/OpenSUSE113x64,if=none,id=drive-ide0-0-0,format=raw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive
file=/mnt/media/installers/OpenSUSE-11.3-x86_64/openSUSE-11.3-NET-x86_64.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev
tap,fd=21,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:0d:16:de,bus=pci,addr=0x3 -chardev
pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -k
en-gb -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci,addr=0x4
Yikes. ???? qemu-system-arm ????
-------
The version of libvirt is libvirt-0.9.11.4-3.fc17.x86_64, and this is
a mostly up to date F17 system, except that I've installed qemu-kvm
1.1.0 + ceph from Rawhide.
Suggestions welcome.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
9:51 a.m.
New subject: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
Here is the output of virsh capabilities. It seems to make no sense.
But it might indicate that something about detection of the
qemu-kvm-1.1.0 binary fails, so libvirt assumes that it's not working.
Rich.
$ sudo virsh capabilities
<capabilities>
<host>
<uuid>2b8c6f80-b15c-11df-9cfd-b727e82cf6bb</uuid>
<cpu>
<arch>x86_64</arch>
<model>Westmere</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='2' threads='2'/>
<feature name='rdtscp'/>
<feature name='pdcm'/>
<feature name='xtpr'/>
<feature name='tm2'/>
<feature name='est'/>
<feature name='smx'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='monitor'/>
<feature name='dtes64'/>
<feature name='pclmuldq'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
<feature name='vme'/>
</cpu>
<power_management>
<suspend_mem/>
<suspend_disk/>
<suspend_hybrid/>
</power_management>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<cpus num='4'>
<cpu id='0'/>
<cpu id='1'/>
<cpu id='2'/>
<cpu id='3'/>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<model>selinux</model>
<doi>0</doi>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name='arm'>
<wordsize>32</wordsize>
<emulator>/usr/bin/qemu-system-arm</emulator>
<machine>integratorcp</machine>
<machine>collie</machine>
<machine>nuri</machine>
<machine>smdkc210</machine>
<machine>connex</machine>
<machine>verdex</machine>
<machine>highbank</machine>
<machine>mainstone</machine>
<machine>musicpal</machine>
<machine>n800</machine>
<machine>n810</machine>
<machine>sx1</machine>
<machine>sx1-v1</machine>
<machine>cheetah</machine>
<machine>realview-eb</machine>
<machine>realview-eb-mpcore</machine>
<machine>realview-pb-a8</machine>
<machine>realview-pbx-a9</machine>
<machine>akita</machine>
<machine>spitz</machine>
<machine>borzoi</machine>
<machine>terrier</machine>
<machine>lm3s811evb</machine>
<machine>lm3s6965evb</machine>
<machine>tosa</machine>
<machine>versatilepb</machine>
<machine>versatileab</machine>
<machine>vexpress-a9</machine>
<machine>vexpress-a15</machine>
<machine>xilinx-zynq-a9</machine>
<machine>z2</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='mips'>
<wordsize>32</wordsize>
<emulator>/usr/bin/qemu-system-mips</emulator>
<machine>malta</machine>
<machine>magnum</machine>
<machine>pica61</machine>
<machine>mipssim</machine>
<machine>mips</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='mipsel'>
<wordsize>32</wordsize>
<emulator>/usr/bin/qemu-system-mipsel</emulator>
<machine>malta</machine>
<machine>magnum</machine>
<machine>pica61</machine>
<machine>mipssim</machine>
<machine>mips</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
</capabilities>
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
10:06 a.m.
New subject: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
On Fri, Jul 06, 2012 at 03:51:58PM +0100, Richard W.M. Jones wrote:
Here is the output of virsh capabilities. It seems to make no sense.
But it might indicate that something about detection of the
qemu-kvm-1.1.0 binary fails, so libvirt assumes that it's not working.
With luck libvirt should have said what's wrong via syslog. Can
you see if there were any log messages ?
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
10:13 a.m.
New subject: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
On Fri, Jul 06, 2012 at 04:06:13PM +0100, Daniel P. Berrange wrote:
On Fri, Jul 06, 2012 at 03:51:58PM +0100, Richard W.M. Jones wrote:
>
> Here is the output of virsh capabilities. It seems to make no sense.
> But it might indicate that something about detection of the
> qemu-kvm-1.1.0 binary fails, so libvirt assumes that it's not working.
With luck libvirt should have said what's wrong via syslog. Can
you see if there were any log messages ?
Ah, thanks, I was looking in /var/log/libvirt/libvirtd.log. Here is
syslog from the point that I restart libvirtd:
Jul 6 16:07:54 spin libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such
file or directory
Jul 6 16:07:56 spin libvirtd[2157]: 2012-07-06 15:07:56.745+0000: 2172: info : libvirt
version: 0.9.11.4, package: 3.fc17 (Fedora Project, 2012-06-28-13:50:28,
x86-05.phx2.fedoraproject.org)
Jul 6 16:07:56 spin libvirtd[2157]: 2012-07-06 15:07:56.745+0000: 2172: error :
virCommandWait:2315 : internal error Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin /usr/bin/qemu-system-x86_64 -device
? -device pci-assign,? -device virtio-blk-pci,? -device virtio-net-pci,? -device
scsi-disk,?) status unexpected: exit status 1
Jul 6 16:07:56 spin libvirtd[2157]: 2012-07-06 15:07:56.811+0000: 2172: error :
virCommandWait:2315 : internal error Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin /usr/bin/qemu-system-x86_64 -device
? -device pci-assign,? -device virtio-blk-pci,? -device virtio-net-pci,? -device
scsi-disk,?) status unexpected: exit status 1
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.087+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.087+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.087+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.088+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.088+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.088+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.088+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.088+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.089+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.089+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.089+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.089+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.089+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.090+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.090+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.090+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.090+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.091+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.091+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.091+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.091+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.091+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.092+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin libvirtd[2157]: 2012-07-06 15:07:57.092+0000: 2172: error :
virDomainDefParseXML:8249 : internal error No guest options available for arch
'x86_64'
Jul 6 16:07:57 spin udevd[499]: RUN+="socket:..." support will be removed from
a future udev release. Please remove it from: /etc/udev/rules.d/90-hal.rules:2 and use
libudev to subscribe to events.
Jul 6 16:07:57 spin udevd[499]: RUN+="socket:..." support will be removed from
a future udev release. Please remove it from: /etc/udev/rules.d/90-hal.rules:2 and use
libudev to subscribe to events.
The full output of that failing command is:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
/usr/bin/qemu-system-x86_64 -device ? -device pci-assign,? -device virtio-blk-pci,?
-device virtio-net-pci,? -device scsi-disk,?
KVM not supported for this target
No accelerator found!
Adding the option '-machine accel=kvm:tcg' fixes the output.
A quick look through upstream libvirt commits doesn't come up with
anything obvious.
BTW I think (for libvirt AND libguestfs) we'd find these bugs a lot
quicker if Rawhide tracked qemu-kvm git revisions more closely.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs, test, and build Windows installers. Over 70 libraries supprt'd
http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
10:16 a.m.
New subject: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
On Fri, Jul 06, 2012 at 04:13:26PM +0100, Richard W.M. Jones wrote:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
/usr/bin/qemu-system-x86_64 -device ? -device pci-assign,? -device virtio-blk-pci,?
-device virtio-net-pci,? -device scsi-disk,?
Actually, this command works fine if run as root, but not as me. I
assume libvirtd is running as qemu.qemu by this point?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
10:26 a.m.
New subject: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
On Fri, Jul 06, 2012 at 04:13:26PM +0100, Richard W.M. Jones wrote:
On Fri, Jul 06, 2012 at 04:06:13PM +0100, Daniel P. Berrange wrote:
> On Fri, Jul 06, 2012 at 03:51:58PM +0100, Richard W.M. Jones wrote:
> >
> > Here is the output of virsh capabilities. It seems to make no sense.
> > But it might indicate that something about detection of the
> > qemu-kvm-1.1.0 binary fails, so libvirt assumes that it's not working.
>
> With luck libvirt should have said what's wrong via syslog. Can
> you see if there were any log messages ?
The full output of that failing command is:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
/usr/bin/qemu-system-x86_64 -device ? -device pci-assign,? -device virtio-blk-pci,?
-device virtio-net-pci,? -device scsi-disk,?
KVM not supported for this target
No accelerator found!
Adding the option '-machine accel=kvm:tcg' fixes the output.
Sigh, qemu-kvm.git has done a broken merge yet again. Binaries built from
qemu.git work fine when /dev/kvm is missing & this shoud not be changed
by qemu-kvm.git I've previously fixed it with
commit ce967f6610dcd7b7762dbad5a639fecf42d5c76d
Author: Daniel P. Berrange <berrange(a)redhat.com>
Date: Fri Aug 5 09:50:29 2011 +0100
Fix default accelerator when configured with --disable-kvm
The default accelerator is hardcoded to 'kvm'. This is a fine
default for qemu-kvm normally, but if the user built with
./configure --disable-kvm, then the resulting binaries will
not work by default
* vl.c: Default to 'tcg' unless CONFIG_KVM is defined
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti(a)redhat.com>
but this code seems to have changed somewhat
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
10:33 a.m.
New subject: [libvirt] [fedora-virt] qemu 1.1.0 in Rawhide, and planned backport to F17 (was: Re: Upgrading qemu to 1.1 in rawhide)
On Fri, Jul 06, 2012 at 04:26:22PM +0100, Daniel P. Berrange wrote:
On Fri, Jul 06, 2012 at 04:13:26PM +0100, Richard W.M. Jones wrote:
> On Fri, Jul 06, 2012 at 04:06:13PM +0100, Daniel P. Berrange wrote:
> > On Fri, Jul 06, 2012 at 03:51:58PM +0100, Richard W.M. Jones wrote:
> > >
> > > Here is the output of virsh capabilities. It seems to make no sense.
> > > But it might indicate that something about detection of the
> > > qemu-kvm-1.1.0 binary fails, so libvirt assumes that it's not
working.
> >
> > With luck libvirt should have said what's wrong via syslog. Can
> > you see if there were any log messages ?
> The full output of that failing command is:
>
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
/usr/bin/qemu-system-x86_64 -device ? -device pci-assign,? -device virtio-blk-pci,?
-device virtio-net-pci,? -device scsi-disk,?
> KVM not supported for this target
> No accelerator found!
>
> Adding the option '-machine accel=kvm:tcg' fixes the output.
Sigh, qemu-kvm.git has done a broken merge yet again. Binaries built from
qemu.git work fine when /dev/kvm is missing & this shoud not be changed
by qemu-kvm.git I've previously fixed it with
commit ce967f6610dcd7b7762dbad5a639fecf42d5c76d
Author: Daniel P. Berrange <berrange(a)redhat.com>
Date: Fri Aug 5 09:50:29 2011 +0100
Fix default accelerator when configured with --disable-kvm
The default accelerator is hardcoded to 'kvm'. This is a fine
default for qemu-kvm normally, but if the user built with
./configure --disable-kvm, then the resulting binaries will
not work by default
* vl.c: Default to 'tcg' unless CONFIG_KVM is defined
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti(a)redhat.com>
but this code seems to have changed somewhat
It was broken by this commit
commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d
Author: Jan Kiszka <jan.kiszka(a)siemens.com>
Date: Fri Mar 2 10:30:43 2012 +0100
qemu-kvm: Use machine options to configure qemu-kvm defaults
Upstream is moving towards this mechanism, so start using it in qemu-kvm
already to configure the specific defaults: kvm enabled on, just like
in-kernel irqchips.
Signed-off-by: Jan Kiszka <jan.kiszka(a)siemens.com>
Signed-off-by: Avi Kivity <avi(a)redhat.com>
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
4553
days inactive
4553
days old
6 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Richard W.M. Jones