[libvirt-users] point-to-point connection between vm and host
by Jorge Somavilla
Hi! hopefully someone can give me a hint with this:
I need to create a vm with a point-to-point connection to the host
using a /30 subnet. Right now i have this in the vm's xml for libvirt:
<interface type="network" name="eth0" onboot="yes">
<source network="default"/>
<mac address="02:fd:00:00:01:00"/>
</interface>
Which brings up an interface in the vm that is configured later by a a
daemon, getting to this:
vnx@r2:~$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 02:fd:00:00:01:00
inet addr:10.250.0.2 Bcast:10.250.0.3 Mask:255.255.255.252
While in the host the other interface is created:
root@tau:/home/jorge/workspace/vnx# ifconfig r2-e0
r2-e0 Link encap:Ethernet HWaddr 0a:81:b6:3c:24:15
inet addr:10.250.0.1 Bcast:10.250.0.3 Mask:255.255.255.252
However there is no connectivity between them, probably because of
some mistake in the <interface> tag, perhaps a wrong 'type' attribute,
but i haven't found out yet. I wouldn't want to create a bridge and
connect both interfaces (vm's and host's) to the bridge, but to have
this ptp, if possible. How would i go about doing that?
thanks!
Jorge
13 years, 6 months
[libvirt-users] Listing machines as non-root user
by Maciej Gałkiewicz
I have a problem with virsh. I'm using eucalyptus software on top of xen 4
(debian squeeze). The problem is that unix user "eucalyptus" cannot see vm
machines when it executes "virsh list". My libvirt version is 0.8.8-3 from
debian sid repository. The same
problem occurs with older versions.
What is more I have tried to change unix_sock_ro_perms to "2777". After
libvirt restart it started to work. Even when I reverted this change it was
still working. Unfortunately after server restart virsh still does not work
(I am not sure but I cannot restart my production servers right now).
Everything is fine when I run virsh as root. I have the same issue on 7
machines.
regards
M. Galkiewicz
13 years, 6 months
[libvirt-users] [Libvir] libvirt & vde_switch
by Robert Šmol
Hi,
I would like to ask about status of VDE and libvirt. I found a thread
from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html.
I am not interested in connecting the VDE to the outside world. I have
created a FW machine using macvtap. To this machine I would like to
attach machines from different zones (dmz, prod, cust). I was thinking
on using VDE and vlans (FW would have 1 interface in each vlan -
machines also), but I am not aware how to configure this in libvirt.
I now assume I can do the same setup with regular bridges for the moment
(benefit of VDE would be only 1 switch for many vlans).
Regards,
Robert
--
stereoIT - Open Source Technology Partners
http://www.stereoit.com
mobile: +420 776 762378
13 years, 7 months
[libvirt-users] port forwarding
by Ireneusz Szcześniak
Hi,
I'm using CentOS release 5.6 (Final) and Xen 3.1. I'm writing to ask
how to configure port forwarding. With virt-manager 0.6.1 I added the
machines, but there I don't see an option for port forwarding.
I would like to reach the VM on a specific port of the host machine.
Once the machinces are running, I can configure iptables so that the
port forwarding works, but after host reboots, other rules are
inserted (put in front of my rules), which disable my rules. I guess
these rules are put by libvirt, and so I'm writing to this list.
These are the rules inserted:
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere 192.168.122.0/24 state
RELATED,ESTABLISHED
ACCEPT all -- 192.168.122.0/24 anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere
reject-with icmp-port-unreachable
REJECT all -- anywhere anywhere
reject-with icmp-port-unreachable
I need to have a different rules for 192.168.122.0/24: the states
RELATED,ESTABLISHED are fine, but I need the NEW state put there too,
so that the new forwards can go through.
Thanks,
Irek
--
Ireneusz (Irek) Szczesniak
http://www.irkos.org
13 years, 7 months
[libvirt-users] Disk not bootable from yesterday resolved
by David Brown
Just an update and a thanks.
The not bootable issue I was having yesterday ended up being for some odd reason the disk type in the domain define xml file had been switched to the disk being "raw" rather than qcow2 format. When I changed:<driver name='qemu' type='raw'/>
to <driver name='qemu' type='qcow2'/>
It booted without issue. I'm not clear how that got changed on the original domain. It was in use without issue about a week ago. :/
I then ran the clone again and it cloned fine, but had the boot issueagain. I checked the cloned domain.xml file and again it said typeraw. I changed it again to qcow2 and it booted fine.
Bug? Shouldn't it keep the type in the config the same?
Anyway, thanks for help and especially the quick responses!
Dave
13 years, 7 months
[libvirt-users] problem installing libvirt from source
by Lars Nordin
I'm trying to compile and install libvirt-0.9.0 on Ubuntu v10.04. The make and install went fine and I don't see any errors but there isn't a libvirt directory created in /usr/local/lib/python2.6/dist-packages.
I specified configure --with-vmware -with-esx (and later --with-python), then make, then sudo make install.
>From config.log:
prefix = /usr/local
exec_prefix = ${prefix}
pyexecdir = ${exec_prefix}/lib/python2.6/dist-packages
pythondir = ${prefix}/lib/python2.6/dist-packages
pkgpyexecdir = ${pyexecdir}/libvirt
pkgpythondir = ${pythondir}/libvirt
13 years, 7 months
Re: [libvirt-users] virt-clone: clone not bootable
by David Brown
It says:
booting from hard disk
Booting failed device not bootable
FATAL: failed to boot from device.
Or something very similar.
Whit Blauvelt <whit.virt(a)transpect.com> wrote:
>On Tue, Apr 26, 2011 at 01:45:23PM -0700, David Brown wrote:
>> The clone was made with the following command: virt-clone -o centos -n
>> centosclone -f /path/to/new/image.img
>> I've attempted it several times and get the same result.
>> Has anyone seen this or know how to resolve it?
>
>I've often cloned CentOS 5.5 KVM VMs with that same invocation, and no
>problem.
>
>When you say it's "not bootable," what exactly do you see at time of
>failure?
>
>Whit
13 years, 7 months
[libvirt-users] virt-image issue
by Zvi Dubitzky
Hi
Does anybody work with the virt-image utility.
- I do not see where/how one specifies the pre-defned image or the CD
iso image to produce the image from
- what is the .xml file requested for ? I guess it is the output xml
file
I just used the command with an existing .xml file (thought the utility
will modify it according to the specified flags)
but got the error message :
"ERROR Cannot parse 'vmTest3.xml': Root element is not 'image"
Any idea what is missing ?
thanks
Zvi Dubitzky
Email:dubi@il.ibm.com
13 years, 7 months
[libvirt-users] virt-clone: clone not bootable
by David Brown
Hi,
Not sure if this is the right mailing list, but...
I have a Linux VM (CentOS 5.4) VM. I cloned it with virt-clone, but the clone isn't bootable. When I attempt to boot it says:
Booting from hard diskBoot failed: not a bootable diskFATAL: No bootable device
The clone was made with the following command: virt-clone -o centos -n centosclone -f /path/to/new/image.img
I've attempted it several times and get the same result.
Has anyone seen this or know how to resolve it?
Thanks,Dave
13 years, 7 months
[libvirt-users] Adding more disks...
by Dale Amon
I need a VM with about 6-8 qcow2 disk images, but it
seems to only allow 4 disks on the ide, like the real
hardware. What lines do you need to add on to the xml
definition file to get hde, hdf, hdg, etc?
13 years, 7 months
