Re: [libvirt-users] [virt-tools-list] error creating NFS storage pool
by Cole Robinson
On 12/16/2011 05:32 PM, Grant Siebrecht wrote:
> Virtual Machine Manager 0.9.0
> OS = Ubuntu 11.10
> I've tried changing permissions on my_nfs_server to 777 with still no luck.
>
>
>
> Error creating pool: Could not start storage pool: cannot open volume
> '/var/lib/libvirt/images/my_nfs_server/.$EXTEND': Permission denied
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/createpool.py", line 480, in
> _async_pool_create
> poolobj = self._pool.install(create=True, meter=meter, build=build)
> File "/usr/lib/pymodules/python2.7/virtinst/Storage.py", line 489, in install
> raise RuntimeError(errmsg)
> RuntimeError: Could not start storage pool: cannot open volume
> '/var/lib/libvirt/images/my_nfs_server/.$EXTEND': Permission denied
>
moving to libvirt-users
What is the .$EXTEND file? Is it a socket or something strange like that?
- Cole
12 years, 11 months
[libvirt-users] Error when creating domain with virsh+qemu
by Stefano Ghio
Cheers,
I'm working on Ubuntu server 11.10 32 bit with libvirt 0.9.2 and
qemu-kvm 0.14.1. I have a user oneadmin:oneadmin who also belongs to kvm
and libvirtd groups. I have set qemu.conf and libvirtd.conf with
user/group oneadmin.
I have disk.0 and deployment.0 files owned by oneadmin. My system does
not support hardware virtualization so I don't have /dev/kvm. I'm able
to start VM with qemu anyways but when issuing the command:
virsh -c qemu:///system create deployment.0
I get:
error: Failed to create domain from deployment.0
error: internal error process exited while connecting to monitor:
13:00:52.354:1291: info: libvirt version: 0.9.2
13:00:52.371: 1291: debug : virCommandHook:1826 : Waiting on parent for
handshake complete on 23
13:00:52.371: 1291: debug : virCommandHook:1842 : Hook is done 0
open /dev/kvm: No such file or directory
failed to initialize KVM: Operation not permitted
"error while connecting to monitor" looks to me as something
permission-related but I tried a lot of combinations between the qemu
and libvirt conf files and nothing worked (yes, I always restarted the
system after every change).
If I start the same image with sudo /usr/bin/qemu-system-i386 -hda
disk.img -boot d -m 384 it works
Any help?
Thanks
--
Dr. Stefano Ghio - ENG Engineering Italy
Website: http://groglogs.blogspot.com/
*If you received this message but you are not its recipient, please
ignore it and warn me, thank you.*
12 years, 11 months
[libvirt-users] Issue with IPMI (and KVM) on RHEL 6
by Jawahar Tadipatri
Hi folks,
We experiencing some difficulties in getting IPMI to work on RHEL 6 running
as Guest using KVM. We have verified that IPMI works on RHEL 6 if installed
on bare metal.
Is this a known issue? Can anyone please suggest a fix or work-around for
this problem?
*RHEL 6 as guest os with kvm on RHEL 6 as host os -- doesn't work*
RHEL 6 (client) on bare metal (i.e., the above mentioned host os)-- works
Below is the the output of the command (just an indication that it failed)
and relevant part of dmesg .
# service ipmi start
Starting ipmi drivers: [FAILED]
# dmesg | tail -12
ipmi message handler version 39.2
IPMI System Interface driver.
ipmi_si: Adding default-specified kcs state machine
ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2,
slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Adding default-specified smic state machine
ipmi_si: Trying default-specified smic state machine at i/o address 0xca9,
slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Adding default-specified bt state machine
ipmi_si: Trying default-specified bt state machine at i/o address 0xe4,
slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Unable to find any System Interface(s)
Please revert if any more information is needed.
Thanks and Regards,
Jawahar
12 years, 11 months
[libvirt-users] Virt-Manager + IDE Controller
by Paul K. Alabi
Hi ,
i m currently running CentOS 5.4 on a Dell C2100 . I have virt-manger , livirt
installed but i can't get my VMs to mount more than 4 IDE disk ( i have 8) . I
would like to know how to mount ALL 8 Disk on my VM .
P
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
12 years, 11 months
[libvirt-users] Using libvirt networking properly.
by Andrew Spiers
Hi, I'm interested in a setup in which one guest receives all its
networking services (routed IPv4, dhcp, tftp, dns) from another, which
is connected via a routing through the hypervisor. I think this is a
lot like Guest C and Guest B in the diagram at
http://libvirt.org/archnetwork.html.
I have experimented with setting the network between Guest B and the
hypervisor as a routed network, and the network between Guest B and
Guest C as an isolated network. The problems I am having is that I am
not sure how to set up a persistent static route to Guest C via Guest
B, (I created a file with the route called route-virbr3 in
/etc/sysconfig/network-scripts on the hypervisor, but it doesn't seem
to do anything), and the changes I need to make to allow traffic with
Guest C's source IP to come from Guest B's interface with the
hypervisor seems to get overwritten or superceded by additional rules
that are created when I start my machine.)
I can see something about a qemu-ifup script mentioned at
http://www.linux-kvm.org/page/Networking. Should I create something
like that and put some sort of `ip route add` command in it? When
should that script be called?
Is there a way to specify the necessary firewall and routing rules in
the xml network configuration?
I am working with a Fedora 16 hypervisor and Guest B is a Centos 6
machine. I'd like to use all sorts of different distributions where
Guest C is.
Regards,
Andrew.
12 years, 11 months
[libvirt-users] network problems with some cloned vm
by xuteng
Hi,All:
Using KVM + libvirt + virt-manager, I meet a strange problem , some cloned vm cannot get correct ip address via bridge network, but some vm can.
My host ip is 192.168.1.8 , a bridge interface br0 , an ethernet interface eth0
When the vm(win7) started ,I got the information like " ip 169.254.XXX.XXX netmask 255.255.0.0" by ipconfig
Here is the host network settings:
[root@kvm-8 ~]# ifconfig
br0 Link encap:Ethernet HWaddr BC:AE:C5:21:C8:FB
inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::beae:c5ff:fe21:c8fb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:59381 errors:0 dropped:0 overruns:0 frame:0
TX packets:52495 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7078092 (6.7 MiB) TX bytes:50729969 (48.3 MiB)
eth0 Link encap:Ethernet HWaddr BC:AE:C5:21:C8:FB
inet6 addr: fe80::beae:c5ff:fe21:c8fb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:60238 errors:0 dropped:0 overruns:0 frame:0
TX packets:76409 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8037333 (7.6 MiB) TX bytes:52546222 (50.1 MiB)
Memory:fbee0000-fbf00000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11312 errors:0 dropped:0 overruns:0 frame:0
TX packets:11312 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36054480 (34.3 MiB) TX bytes:36054480 (34.3 MiB)
virbr0 Link encap:Ethernet HWaddr D2:38:52:7D:0D:5D
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vnet0 Link encap:Ethernet HWaddr FE:54:00:A1:A1:90
inet6 addr: fe80::fc54:ff:fea1:a190/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:134 errors:0 dropped:0 overruns:0 frame:0
TX packets:247 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:24091 (23.5 KiB) TX bytes:15846 (15.4 KiB)
[root@kvm-8 ~]#
brctl shows:
[root@kvm-8 ~]# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.bcaec521c8fb yes eth0
vnet0
virbr0 8000.000000000000 yes
[root@kvm-8 ~]#
Any information would be appreciated
Thank you!
wade
xuteng via foxmail
12 years, 11 months
[libvirt-users] Qemu restore error
by Dennis Householder
Hello,
I'm not sure if I am having a kvm/qemu issue, a virt-manager issue, or a
libvirt issue, so if I am asking the wrong crowd please let me know! In
short, restoring some suspended kvm guests via virt-manager is failing
because libvirt cannot read the qemu header. I cannot find any
documentation on what this means. From virsh's limited documentation I
was able to gather that there is probably something wrong with an xml
file somewhere, but I cannot find it. Any advice is greatly appreciated!
Synopsis:
I have 5 KVM guests on a Fedora 16 laptop host. I manage them locally
through virt-manager. These guests are JUNOS 10.1R1 (installed over
FreeBSD 4.1 mini-inst) on a patched bios (SeaBIOS
pre-0.6.1-20100805_064324-Compaq8510w). One time I suspended my laptop
and the kvm domains were suspended as well. Trying to restore yields the
following error:
Error restoring domain: operation failed: failed to read qemu header
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in
startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 510, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: operation failed: failed to read qemu header
#end error output
Package version info:
libvirt-python-0.9.6-2.fc16.x86_64
libvirt-0.9.6-2.fc16.x86_64
libvirt-client-0.9.6-2.fc16.x86_64
gpxe-roms-qemu-1.0.1-4.fc16.noarch
qemu-system-x86-0.15.1-3.fc16.x86_64
qemu-common-0.15.1-3.fc16.x86_64
qemu-kvm-0.15.1-3.fc16.x86_64
qemu-img-0.15.1-3.fc16.x86_64
virt-manager-0.9.0-7.fc16.noarch
virt-manager-common-0.9.0-7.fc16.noarch
virt-viewer-0.4.1-3.fc16.x86_64
Again, any advice is appreciated. I hope I have provided enough info.
Thank you for your time!
-- Dennis
CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.
12 years, 11 months
[libvirt-users] Adding a public static IP address to the guest
by Sudheer Satyanarayana
Hello,
The host runs on CentOS 6. I have installed a guest, CentOS 5.7, using
libvirt.
I am having difficulty understanding how to assign a public static IP
address to the guest. From what I understand by reading the Wiki, I
think I require routed mode.
The ISP has provided a 'portable' IP routed to the VLAN of our servers.
I want to assign this IP address to the guest. From the virtual machine
hardware details window, I see that "Virtual network 'default' : NAT" is
selected for the source device field.
Can someone offer a helping hand and instruct and educate me on how to
proceed from here?
Thanks.
--
With warm regards,
Sudheer. S
12 years, 11 months
[libvirt-users] acceptable SASL mechanisms/can libvirt authenticate against PAM
by Dave Allan
I was playing with SASL authentication a bit today and I wasn't able
to get libvirt to authenticate against PAM (or anything else except
the sasldb, although I didn't try Kerberos). Does anybody know off
the top of their head what mechanisms/password check options work?
I'm trying to figure out if I'm attempting the impossible.
Dave
12 years, 11 months
[libvirt-users] Temporary use of disk space when deploying KVM with qcow2 ?
by Jorge Somavilla
Hello,
I'm using libvirt to deploy a series of 7 KVM (in qcow2 format)
sequentially. The base image of the qcow2 is an ubuntu server of around
1.6GB.
The environment where i am doing this is a Live USB Ubuntu with a
persistence file (so that changes made remain).
So, the problem:
* If the persistence file (i.e. free disk space in the live ubuntu) is up
to around 1.6GB, the qemu process of launching the first one of the KVM
gets stuck, and a few seconds later an Ubuntu message pops up saying there
is no disk space left.
* If the persistence file is a bit bigger (100 MB more), it can launch the
7 KVM machines without any disk space problems.
This would suggest that during the deployment of one virtual machine, there
is a short period of time where a big amount of disk space (similar to the
size of the base image) is used (even if i am using qcow2 vms) and
afterwards released, so it can be used to launch the second vm, released,
used for the third, and so on.
If this is correct, i would like to know who is using that space, since my
intention would be to, if possible, redirect this temporary disk usage to a
RAM filesystem such as tmpfs, so that i don't need such a huge persistence
file in the USB.
I'm aware that this might be related to qemu-kvm rather than to
libvirtitself, but i can't find information about it and i would
appreciate if
anyone could point me in the right direction. More details or clarification
can be provided if needed.
Best regards,
Jorge
12 years, 11 months
