[libvirt-users] Error connecting to console
by Anthony Davis
Hi,
i have KVM running at the moment and im trying to do a text based
install of centos, so i need to connect to the console via virsh
virsh console servername
but i get this error:
error: Failed to get local hostname
How do i resolve this issue to get a consol connection to the server?
I have tried to put it into the /etc/hosts file, but to no avail.
Hope someone can help or suggest another method of doing a headless
and X less install of a guest?
Kind Regards
Tony
14 years
[libvirt-users] Building & Installing on OpenSolaris
by gary mazzaferro
Hi,
I'm revisiting my libVirt install for opensolaris. I downloaded libvirt
0.8.0..
This is a bit embarassing, but I forgot how to build libVirt on opensolaris.
(It's been a while) I'm currently stuck with the configure script failing
to find linux kernel headers.
Error:
"configure: error: You must install kernel-headers in order to compile
libvirt"
Can anyone post the instructions to build under opensolaris?
cheers,
gary
14 years
[libvirt-users] Windows Vista Client Fails to Connect to Ubuntu libvirtd
by Tim McLeod
Requesting urgent assistance if I may?
Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on
a Windows Vista machine. Using insecure TCP simply to prove a concept to a
client. However, cannot connect; situation as follows:
Edited /etc/libvirt/libvirt.conf as follows:
listen_tcp = 1
auth_tcp = "none"
Edited /etc/default//libvirt-bin as follows:
libvirt-opts="-d -l"
Running virsh on Vista client fails as follows:
$ virsh -c qemu+tcp://192.168.1.101/system
error: unable to connect to libvirtd at '192.168.1.101': errno=10061
error: failed to connect to the hypervisor
Running virsh on Ubuntu server fails as follows:
$ virsh -c qemu+tcp:///system
Connecting to uri: qemu+tcp:///system
error: unable to connect to libvirtd at 'localhost': Connection refused
error: failed to connect to the hypervisor
Indeed, with libvirt-opts="-d -l" in etc/default//libvirt-bin the 'default'
command also fails:
$ virsh -c qemu:///system
Connecting to uri: qemu:///system
error: unable to connect to 'var/run/libvirt/libvirt-sock': Connection
refused
error: failed to connect to the hypervisor
Suggestions very welcome...
Tim McLeod
14 years
[libvirt-users] using shared storage with libvirt/KVM?
by David Ehle
Hello,
I've spent a few days googling and reading documentation, but I'm looking
for clarification and advise on setting up KVM/libvirt with shared
storage.
I have 2 (for now) Ubuntu Karmic systems with KVM/virsh/virt-manager set
up and running.
I have a storage server that can do NFS/iSCSI/samba/ etc.
I am trying to figure out the best way to set things up so that I can run
several (eventually) production linux guests (mostly debian stable) on the
2 KVM host systems and be able to migrate them when maintenance is
required on their hosts.
Performance is of medium importance, stability/availibilty is pretty high
priority.
A common opinion seems to be that using LVs to hold disk images gives
possibly the best IO performance, followed by raw, then qcow2.
Would you agree or disagree with this? What evidence can you provide?
I am also rather confused about using shared storage, and what options can
be combined with this.
I have succesfully made an iscsi device available to
libvirt/virsh/virt-manager via an XML file + pool-define + pool-start.
However the documentation states that while you can create pools through
libvirt, volumes have to be pre-allocated:
http://libvirt.org/storage.html
"Volumes must be pre-allocated on the iSCSI server, and cannot be created
via the libvirt APIs."
I'm very unclear on what this means in general, and specifically how you
preallocate the the Volumes.
When I make a iscsi pool available via something like this:
<pool type="iscsi">
<name>virtimages</name>
<source>
<host name="iscsi.example.com"/>
<device path="demo-target"/>
</source>
<target>
<path>/dev/disk/by-path</path>
</target>
</pool>
In virt-manger I can see it as a pool, but when I try to select it for
where to create an image, it uses the pool AS A Volume (I think).
That brings me to my next question/misunderstanding...
If you are using shared storage (via NFS or iSCSI) does that also mean you
MUST use a file based image rather than an LVM LV? NFS makes directories
available, not devices. You can make an unformated "raw" LV available via
iSCSI, but its not seen on the far side as a LV but instead as a scsi disk
which you need to partition. You can make a PV>VG>LV out of that and then
make your new LV available to libvirt/KVM but then your stacking a heck of
a lot of LVM/LVs/partion tables up which seems pretty dubious. I'm also
not sure that the stack would be visable/available to the second system
using that iSCSI device. (I'm pretty new to using iSCSI as well.)
Redhat provides pretty good documentation on doing shared storage/live
migration for NFS:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Virtua...
But unfortunately the section on Shared Storage with iSCSI is a bit
lacking:
"9.1. Using iSCSI for storing guests
This section covers using iSCSI-based devices to store virtualized
guests." and thats it.
For maybe 6-10 guests, should I simply just be using NFS? Is its
performance that much worse than iSCSI for this task?
So since KVM/libvirt is getting used quite often in production now - but
some simple things are not making any sense to me - I'm guessing that I
have some really basic misunderstandings of how to do shared storage /
Pools/ Volumes for migration.
Would one of the kind readers of this least be willing to correct me?
Please CC to my original email address as well as I am not yet a regular
subscriber.
Thanks again!
David.
14 years
[libvirt-users] attach-device broken?
by steven765＠yahoo.com
Hi,
Just installed a new FC12 box with all new updates. Figured out to delete the CDROM so the images actually boot now.
However, after the upgrade, I can no longer attach my network interfaces to running images? Was this capability removed? Is there some new setting that has to be configured?
It's a very simple configuration that hasn't changed and still works on the pre-update box.
<interface type='network'>
<mac address='52:54:00:58:9c:00'/>
<source network='mynetwork'/> yes it's defined and active
</interface>
Thanks in advance,
Steve
14 years
[libvirt-users] Ignoring invalid update watch -1
by jeremy avnet
Hello,
I've started to get these in my logs every now and then:
libvirtd: 18:50:29.792: warning : virEventUpdateHandleImpl:149 : Ignoring
invalid update watch -1
What does it mean?
Thanks!
.:. jeremy
14 years
[libvirt-users] libvirt client certificate location
by Vadym Chepkov
Hi,
I was really surprised to find that location of client certificate, key and CA is hardcoded into libvirt.
What if I need to manage servers with certificates issued by different CA? Or why do everybody has to use the same private key? Doesn't make it much of a private.
It seems so strange I wonder if I am mistaken and it is possible to provide alternative location for the CA, key and certificate?
Thank you,
Vadym Chepkov
14 years
Re: [libvirt-users] Windows Client
by Matthias Bolte
2010/4/28 Tim McLeod <tim.mcleod(a)simulamen.eu>:
> Having newly compiled a Libvirt on a Windows Vista machine (many thanks to
> Matthias Bolte)
Nine :)
> I have attempted to connect to a remote Ubuntu machine using
> virsh.exe. However, the connection fails as follows:
>
>
>
> $ virsh -c qemu+tcp:///system
You need to specify the server in this URI using a hostname or IP
address: qemu+tcp://ubuntu-server.com/system
> error: unable to connect to libvirtd at 'localhost': errno=10061
>
> error: failed to connect to the hypervisor
>
>
>
> 1. I have modified /etc/libvirt/libvirt.conf to set listen_tcp=1.
You also need to change this
#auth_tcp = "sasl"
to
auth_tcp = "none"
to disable SASL authentication/encryption for TCP connections, because
your libvirt on Windows is compiled without SASL support. If you need
the libvirt connections to be encrypted you can switch from TCP to TLS
connections using: qemu+tls://ubuntu-server.com/system
> 2. I cannot find /etc/sysconfig/libvirtd so I am unable to set
> LIBVIRTD_ARGS="--listen".
>
For Ubuntu packaged libvirt see /etc/default/libvirt-bin and change
libvirtd_opts="-d"
to
libvirtd_opts="-d -l"
as the comment suggest and restart libvirtd using
/etc/init.d/libvirt-bin restart
Now you should be able to connect to the libvirtd on your Ubuntu server.
Matthias
14 years
[libvirt-users] Cloning very slow?
by Tom Hughes
Yesterday I cloned one of my VMs and, somewhat implausibly, it took
virt-clone something like 8-9 hours to clone the 8Gb disk image...
Copying it from the command line took a mere 6.5 minutes.
I assume this is a bug, and it's not expected to take this long ;-)
This was using virt-clone from python-virtinst-0.500.2-1.fc12.noarch in
the virt-preview repository.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
14 years
[libvirt-users] ruby-libvirt equiv of virsh list --all
by Mick Pollard
Hi all,
I have a working KVM system managed with virsh and virt-install.
I am currently playing with ruby-libvirt-0.1.0.
I am wanting to build a simple sinatra/ruby app to show the VE's on a node and their state.
I have ruby 1.8.5 on CentOS 5.4.
I have the basics of it worked out but am a little stuck.
Is there a way of retrieving a list of all VM's on a host using ruby-libvirt. ie: virsh list --all ?
@conn.list_defined_domains only shows VE's not started (lists VE names)
@conn.list_domains only shows VE's running (lists VE id's)
What I ultimately would like is to retrieve a full list of the uuid's of all defined VE's(running or not).
--
Regards
Mick Pollard ( lunix )
------------------------------------------------
BOFH Excuse of the day:
Extraneous Configuration Invalidation
14 years
