[libvirt-users] disable-ticketing
by mhd
hi...
where usually disable-ticketing is avaliable in vm xml ????
i use this command virsh edit vmname
and i can edit any options and added but when add this option to <graphics>
as example : <graphics disable-ticketing='yes'> or
<graphics>
<disable-ticketing />
</graphics>
nothing happened the file return to first status only this option ...
if i add passwd in <graphics> is took as example: <graphics
passwd='111111'>
it's work and vm xml is edited...
10 years, 2 months
[libvirt-users] virt-install: failed to initialize KVM: Permission denied
by arnaud gaboury
As a regular user, member of the libvirt group, I run this command to
create a basic VM:
virt-install --connect qemu:///system --name=test --ram 2048 --cpu
host-model-only --os-variant=win7 --disk /myVM/test --boot cdrom,hd
--virt-type kvm --graphics spice --controller scsi,model=virtio-scsi
--cdrom=/drawer/myIso/w8.iso
It returns an error :
---------------------------------
Starting install...
ERROR internal error: process exited while connecting to monitor:
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied
---------------------------------
$ getfacl /dev/kvm
# file: dev/kvm
# owner: root
# group: kvm
user::rw-
user:martinus:rw-
group::rw-
mask::rw-
other::---
The command return seems to indicate rights are correct.
$ lsmod return kvm & kvm_intel are loaded.
If I run the virt-install with qemu:///session, I do not have this
issue and can create the VM.
I found many entries about the KVM permission issue, but with no clear
answer to solve it.
Thank you for any suggestion
--
google.com/+arnaudgabourygabx
10 years, 2 months
[libvirt-users] Guest vlan trunk port networking issues
by Dennis Jacobfeuerborn
Hi,
I'm having trouble getting networking to work and I'm not sure what I'm
doing wrong.
The network interface of the host is connected to a switch-port that is
configured as trunk and allows tagged traffic for vlan id 10.
The host itself has the interfaces eth1.10 and eth1 defined. eth1.10 is
configured with the primary ip address of the host system and eth1 is
slave of the bridge br1.
I installed a guest with a virtual network interface that is added to
br1 the idea being that I can define an interface eth0.10 in the guest
and have the tagged traffic forwarded this way:
(guest) eth0.10 (packet gets tagged with id 10) -> (host) vnet0 ->
(host) br1 -> (host) eth1 -> network
The issue is that when I do a ping in the guest I see the arp request on
eth1 with tcpdump but no response as if the packet doesn't reach its target.
Normaly at this poing I would suspect the switchport configuration but
when I ping the same IP from the host (which has an IP in the same
network on interface eth1.10) this ping works fine.
Does anybody have experience with this and maybe an idea why the host
can reach the ip in vlan 10 but the guest can not? Could this be a
routing issue that the system somehow discards the packets flowing
through eth1 directly because there also is an interface eth1.10 present?
Regards,
Dennis
10 years, 2 months
[libvirt-users] How to install libvirt-python from source code?
by Can Zhang
Hi,
I’d like to install a latest version libvirt on CentOS 6.5. I compiled libvirt, it worked well and then I tried to install libvirt-python.
The version is libvirt-python-1.2.7, and I used `python setup.py build` and `sudo python setup.py install` to install.
But in python, I get errors like:
==========
>>> import libvirt
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 28, in <module>
raise lib_e
ImportError: /usr/lib64/python2.6/site-packages/libvirtmod.so: undefined symbol: virTypedParamsAddBoolean
==========
Someone would help?
Best regards,
Can Zhang
10 years, 2 months
[libvirt-users] Libvirt-install w8 iso
by arnaud gaboury
I am using this command to install a w8 guest on my Archlinux host:
virt-install --connect qemu:///system --name=tintinVM --ram 4096 --cpu
host-model-only --os-variant=win7 --disk
/dev/vg0/tintin,size=120,bus=virtio,sparse=false,format=raw
--name="tintinVM" --network bridge=virbr0,model=virtio --graphics
spice --cdrom /dev/cdrom
The virtual machine window open and show the blue windows logo. But
then nothing happens and I can't start the install process. I hav eno
idea why.
The w8 iso file is clean. I test booting from it and I can start the install.
What is wrong with my command? How can I try another way (like
mounting the ISO on a dir). I dual boot arch and w8, so there is
already a w8 installed on my ssd. Maybe can make an .img of the
installed w8 then use this img ? Or directly use the partiton?
I must add my machine boots in EUFI, not sure it has something to do.
Then, I have issue when loading KVM kernel modules: permission denied.
The user is in the KVM & qemu group, and /dev/kvm belongs to user:kvm. I need to
# rmmod kvm_intel before I start $ virt-install .....
Last, I don't understand well if I need to use qemu///system or
qemu///session ? My goal is to let users start a VM when in their arch
session.
Thank you for any suggesuions.
--
google.com/+arnaudgabourygabx
10 years, 2 months
[libvirt-users] virt-manager and libvirt-python
by Фарит Мутугуллин
Hello! I'm trying to work with virt-manager but getting SIGTRAP signal.
It is done with gdb under MinGW32 on Windows 7 64-bit. I have Python 2.7.8. 32-bit.
As I can see from backtrace ( http://pastebin.com/JhN6XgYb ), there is something wrong with libvirtmod.pyd.
Also I couldn't find how to solve " typelib for AppIndicator3" error.
So I try to debug libvirt-python. For doing this, I building libvirt-python with -g flag.
python setup.py build --compiler=mingw32 -g install
But I have undefined reference to _imp__Py_InitModule4. http://pastebin.com/9gw1zsmw
Earlier I built Python with debug info as -lpython27_d was needed.
I tried to build with python_d, but got the same error.
Nevertheless, when I build without -g, everything builds just fine.
Could you tell me what am I doing wrong? Or is SIGTRAP coming from somewhere else?
What SIGTRAP can be caused by?
10 years, 2 months
[libvirt-users] virt-manager/ GTK & py issue
by arnaud gaboury
Sorry to post here, but filling a bug @ bugzilla is impossible. There
seems to be a bug there and it was impossible for me to log with the
newly created account.
OS : Archlinux x86_64
libvirt 1.2.7-1
libvirt-glib 0.1.8-2
libvirt-python 1.2.7-1
pygtk 2.24.0-4
gtk2 2.24.24-1
gtk2-perl 1.2492-1
gtk3 3.12.2-1
python 3.4.1-1
python2 2.7.8-1
ISSUE :
virt-manager GUI. Create a mew machine.
> Display > Spice server
Returns error
Error refreshing hardware page: Must be string, not TreeModelRow
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/details.py", line 1197, in
hw_selected
self.refresh_graphics_page()
File "/usr/share/virt-manager/virtManager/details.py", line 2755, in
refresh_graphics_page
title = self.gfxdetails.set_dev(gfx)
File "/usr/share/virt-manager/virtManager/gfxdetails.py", line 197, in set_dev
uiutil.set_combo_entry(self.widget("graphics-type"), gtype, 0)
File "/usr/share/virt-manager/virtManager/uiutil.py", line 140, in
set_combo_entry
combo.get_child().set_text(value or "")
TypeError: Must be string, not TreeModelRow
10 years, 2 months
[libvirt-users] Ubuntu 14.04 LTS KVM issue: setdev ioctl failed on blockpoll: Device or resource busy
by Jianfeng Tang
>
Hi,
I ran into a strange issue when I brought up my virtual device on KVM
after I upgraded my box to Ubuntu 14.04 LTS.
My virtual device has two disks: one boot disk and one empty disk. It was
able to boot up, but ioctl on the second disk image failed with error
messages like:
setdev ioctl failed on blockpoll: Device or resource busy
Any thoughts what happened. It worked fine with Ubuntu 12. Our virtual
device called open_bdev_exclusive and failed. AppArmor seems not the
problem because I saw the same issue with app armor disabled.
Thanks.
>
10 years, 2 months
[libvirt-users] esx: upload the volume
by Matwey V. Kornilov
Hi,
I am running virsh 1.0.2 with standalone esxi 5.5up1
I would like to upload iso image to the esxi. I am executing commands
vol-create followed by vol-upload, that leads me to success for
libvirt/qemu.
But with esx driver I get the following.
virsh # vol-create-as --pool datastore2 --name
coreos_production_iso_image.iso --format raw --capacity 139460608
error: Failed to create vol coreos_production_iso_image.iso
error: internal error Volume name 'coreos_production_iso_image.iso'
doesn't have expected format '<directory>/<file>'
virsh # vol-create-as --pool datastore2 --name
'coreos/coreos_production_iso_image.iso' --format raw --capacity 139460608
error: Failed to create vol coreos/coreos_production_iso_image.iso
error: internal error Volume name
'coreos/coreos_production_iso_image.iso' has unsupported suffix,
expecting '.vmdk'
The error messages lead me to idea that I am doing something wrong.
10 years, 2 months
[libvirt-users] Behavior of disk caching with qcow2 disks
by Andrew Martin
Hello,
I am running several virtualization servers with QEMU 1.4.x and libvirt 1.0.2 on
Ubuntu 12.04 and am working on optimizing the cache= and aio= options for the
virtual machines. These VM images are mostly qcow2, and are served both from a
local ext4 filesystem (with data=ordered,barrier) and from an NFS mountpoint
(with sync). The local filesystem sits on top of an md software RAID of SATA
HDDs.
I have read some conflicting information about which cache option is used by
default. This documentation states that cache=writethrough is the default:
http://www-01.ibm.com/support/knowledgecenter/linuxonibm/liaat/liaatbpkvm...
However this SuSE documentation claims that QEMU 1.2.x and newer allows the
driver to select which cache mode, and it often defaults to cache=writeback:
https://www.suse.com/documentation/sles11/book_kvm/data/sect1_1_chapter_b...
Which is correct? How is the cache mode set by default (if cache= is not
specified)?
My second question is can cache=none be used safely on a local ext4 filesystem
with no BBU? Since ext4 uses barriers, would writing to these qcow2 image files
be safe? The kernel documentation about barriers states that "Write barriers
enforce proper on-disk ordering of journal commits, making volatile disk write
caches safe to use, at some performance penalty". Does this apply to qcow2 VM
images?
Thanks,
Andrew Martin
10 years, 2 months