[libvirt-users] hardware error 0x80000021 on Ubuntu 12.10, need advice
by Sebastien Douche
Hi,
On a DELL r610 (Intel Xeon L5520) and a Windows guest I have an
hardware error. The bug is well known[1][2] and seems fixed with the
package 3.5.0-16-generic. But I use 3.5.0-30-generic. Do I need to
upgrade to 13.10? Or just the kernel ? Or modify the options of the
kvm module?
Thanks.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=854983
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1045027
logs:
2013-05-23 15:54:02.306+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name windows1 -S -M pc-1.2
-enable-kvm -m 3500 -smp 2,sockets=2,cores=1,threads=1 -uuid
d170225e-7367-4ece-4338-6b1811c10c0c -no-user-config -nodefaults
-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/windows1.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
-no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive file=/srv/kvm/windows1.img,if=none,id=drive-ide0-0-0,format=qcow2
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-drive file=/srv/iso/windows7ultimate.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
-netdev tap,fd=18,id=hostnet0,vhost=on,vhostfd=19 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:49:32:cc,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0
-vnc 127.0.0.1:0 -vga std -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
char device redirected to /dev/pts/1
KVM: entry failed, hardware error 0x80000021
If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.
EAX=00000010 EBX=00000080 ECX=00000000 EDX=00000080
ESI=0025da4a EDI=0007da4a EBP=00001f20 ESP=00000200
EIP=0000009b EFL=00000002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0020 00000200 0000ffff 00009300
CS =b000 002b0000 0000ffff 0000f300
SS =0020 00000200 0000ffff 0000f300
DS =0020 00000200 0000ffff 00009300
FS =0020 00000200 0000ffff 00009300
GS =0020 00000200 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT= 002b0000 00000027
IDT= 00000000 000003ff
CR0=00000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=02 00 00 ea 91 00 00 00 18 00 0f 20 c0 66 83 e0 fe 0f 22 c0 <66>
31 c0 8e d8 8e c0 8e d0 66 bc 00 04 00 00 8e e0 8e e8 ea 00 00 00 20
00 00 00 20 4a da
--
Sebastien Douche <sdouche(a)gmail.com>
Twitter: @sdouche / G+: +sdouche
12 years, 1 month
[libvirt-users] snapshot create error, unable to find cgroup for vm
by Gao Yongwei
Hello:
Yesterday I yum update libvirt from 0.9.10 to 0.10.2 ,after update I got
some error in libvirtd.log
like this:
2013-05-10 07:39:09.440+0000: 18824: warning : virCgroupMoveTask:885 : no
vm cgroup in controller 3
2013-05-10 07:39:09.440+0000: 18824: warning : virCgroupMoveTask:885 : no
vm cgroup in controller 4
2013-05-10 07:39:09.440+0000: 18824: warning : virCgroupMoveTask:885 : no
vm cgroup in controller 6
so,I restarted cgconfig and libvirtd daemon :
service cgconfig restart ;
service libvirtd restart
after that ,I cannot create snapshot for vm anymore.and error log message
below:
2013-05-16 01:13:23.638+0000: 28848: error :
qemuDomainSnapshotCreateDiskActive:11299 : internal error Unable to find
cgroup for vm1
my version info :
# rpm -q libvirt
libvirt-0.10.2-18.el6_4.4.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.295.el6_3.1.x86_64
in /cgroup dir I cannot find anything about vm1.how can I recover the
missing cgroup for vm ?
thanks !
12 years, 1 month
[libvirt-users] USB passthrough not working
by Dale Amon
I just updated an Ubuntu Oneiric to Raring and the VM that works fine on one
fails to start a VM with this passthrough:
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x055f'/>
<product id='0x040b'/>
<address bus='3' device='8'/>
</source>
</hostdev>
It just dies at boot time.
12 years, 1 month
[libvirt-users] Two VF cards
by Dominik Mostowiec
Hi,
I try to add 2 VF functions to VM via network.
Livirt networks:
vnet0:
<network>
<name>vnet0</name>
<forward mode='hostdev' managed='yes'>
<pf dev='eth0'/>
</forward>
</network>
vnet1:
<network>
<name>vnet0</name>
<forward mode='hostdev' managed='yes'>
<pf dev='eth1'/>
</forward>
</network>
In VM configuration:
<interface type="network">
<source network="vnet0"/>
<mac address="52:54:0a:b1:48:07"/>
</interface>
<interface type="network">
<source network="vnet1"/>
<mac address="52:54:0a:b1:48:07"/>
</interface>
VM can't start because:
kvm: -device
pci-assign,configfd=24,host=01:10.1,id=hostdev0,bus=pci.0,addr=0x4:
Duplicate ID 'hostdev0' for device
libvirt version 1.0.5.
What i am doing wrong?
--
Regards
Dominik
12 years, 1 month
[libvirt-users] How to use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04?
by Gizmo Chicken
QUESTION: What, if anything, can I do so that I can use xl (in place of
xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04?
BACKGROUND: I am testing a fully updated (as of March 27) installation of
Ubuntu 13.04 that includes the following packages:
libvirt - version 1.0.2-0ubuntu9
xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1
Upon setting TOOLSTACK=xm in /etc/default/xen (as well as making a few
needed tweaks to /etc/xen/xend-config.sxp), libvirt and virt-manager worked
great. Yippee!
I guess that I should be happy that the xm toolstack still works with Xen
4.2.1 and quit while I'm ahead, but...
According to libvirt's documentation:
"libxl: Starting with Xen 4.2, the legacy XenD/xm toolstack is deprecated
in favor of libxl, also commonly called libxenlight. libvirt supports this
new Xen toolstack via the libxl driver. If XenD is enabled, the legacy xen
driver consisting of the above mentioned channels will be used. If XenD is
disabled, the libxl driver will be used."
See http://libvirt.org/drvxen.html.
In view of the above, I attempted to use xl in place xm by setting
TOOLSTACK=xl in /etc/default/xen. And after doing so (both with and
without, the above mentioned tweaks to /etc/xen/xend-config.sxp), I
recieved the following error when attempting to start virt-manager:
Unable to connect to libvirt.
unable to connect to 'localhost:8000': Connection refused
Verify that:
- A Xen host kernel was booted
- The Xen service has been started
Libvirt URI is: xen:///
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 1027, in
_open_thread
self.vmm = self._try_open()
File "/usr/share/virt-manager/virtManager/connection.py", line 1009, in
_try_open
flags)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: unable to connect to 'localhost:8000': Connection refused
12 years, 1 month
[libvirt-users] libvirtd using 11GB
by Alex Leonhardt
Hi All,
Am new to this list, and have asked in #ovirt / ovirt-users list and they
pointed me to here ... I've seen libvirtd using ~11 GB of resident memory
after the host has been running for about 60+ days with about 40 VMs
running on it.
The versions I'm currently running are :
libvirt.x86_64 0.9.10-21.el6_3.7
libvirt-client.x86_64 0.9.10-21.el6_3.7
libvirt-lock-sanlock.x86_64
libvirt-python.x86_64 0.9.10-21.el6_3.7
I know I can just restart libvirtd and "all should be fine" (and hopefully
I'll regain the 11GB of memory) - however, is there an updated version that
maybe fixes a memory leak ??
Thanks in advance,
Alex
--
| RHCE | Sen Sys Engineer / Platform Architect | www.vcore.co |
www.vsearchcloud.com |
12 years, 1 month
[libvirt-users] How to see the console output of an EXE session?
by Jon Taylor
Hi,
I am having trouble with a libvirt lxc EXE container which is starting
another EXE container itself, and I need to see the console output of
(hopefully) both containers. How do I do this? I have searched the net a
lot, but the answers I found were either out of date, wrong or didn't work.
Has anyone else here done this?
Jon
12 years, 1 month
[libvirt-users] nova compute libvirt driver and libvirt compatibility
by arvind viswanathan
Hi,
>From my reading about nova interface to libvirt, I came to know it uses a
libvirt driver module to communicate with host libvirt. I was wondering if
there are any compatibility matrix available between the nova libvirt
driver and the libvirt installed in the host ?
Thanks
Arvind
12 years, 1 month
[libvirt-users] connect to esx: Could not find HostSystem with name '(null)'
by Dimitri Nilsen
Hi all,
I am trying to connect to esx vi libvirt 0.10.2.
virsh # connect esx://hostname?no_verify=1&auto_answer=1
error: Failed to connect to the hypervisor
error: internal error Could not find HostSystem with name '(null)'
could you give me a hint, what could be a reason for that problem
in a debug log of libvirt I see:
14447: debug : virAuthGetConfigFilePath:77 : Checking for readability of
'/root/.libvirt/auth.conf'
14447: debug : virAuthGetConfigFilePath:86 : Checking for readability of
'/etc/libvirt/auth.conf'
14447: debug : virAuthGetConfigFilePath:95 : Using auth file '(null)'
14447: error : esxVI_LookupManagedObjectHelper:4854 : internal error
Could not find HostSystem with name '(null)'
14447: debug : do_open:1180 : driver 1 ESX returned ERROR
Regards
Dimitri
12 years, 1 month
