[libvirt-users] libvirt on Debian - can I safely upgrade?
by Thomas Lutz
Hi there,
I'm currently using libvirt 0.4.6 from the Debian sources with 6 VMs running
and since I'm getting random crashes of one of the VMs without any logfile
entry in either host or guest (libvirt debugging not turned on as I found
out about it just today) I want to upgrade to the latest version (0.7.7 - I
guess) from Debian backports.
Is this huge upgrade safely possible with just switching sources to
backports? Or can I expect problems? Rebooting the VMs is obligatory at the
end of the upgrade?
Thanks in advance and best regards,
Thomas Lutz
15 years
Re: [libvirt-users] question
by mattias
same error about a missed certificate
but the text are in my native language swedish
something like CA certificate
On Sat, 2010-04-03 at 21:11 +0300, Danel Ahman wrote:
> Try to use openvz:///system or openvz://localhost/system
>
> Danel
>
> On 03.04.2010, at 21:05, mattias wrote:
>
> > i try to connect to my local libvirt to use openvz
> > openvz://localhost
> > but i get an error about a missed certificate
> > and when i use
> > openvz:///localhost
> > only a eror message says could not connect
> > libvirt error
> >
> > _______________________________________________
> > libvirt-users mailing list
> > libvirt-users(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/libvirt-users
>
15 years
[libvirt-users] question
by mattias
i try to connect to my local libvirt to use openvz
openvz://localhost
but i get an error about a missed certificate
and when i use
openvz:///localhost
only a eror message says could not connect
libvirt error
15 years
[libvirt-users] Creating a private network
by Brown, Matt D.
I am trying to create a separate private network between the host (domain 0) and the guests. Using virsh, I created a bridge network, virbr1. I can successfully add guest interfaces to the bridge network and communicate between the guests. However, I am unable to communicate between the host and any of the guests. I created eth0:1 on the host and configured virbr1 to forward to eth0:1 (mode="route" dev="eth0:1"), but there is still no communication.
I don't think creating eth0:1 is the right thing to do. I think I need to create a virtual interface on domain 0 that is part of the bridge network, virbr1. However, when I run virsh attach-interface with domain-0, it fails.
What am I missing??
Matt
OS: RHEL 5, Xen kernel
virbr1 Bridge Network (First attempt)
<network>
<name>private</name>
<bridge name="virbr2" />
<ip address="169.254.1.1" netmask="255.255.0.0">
</ip>
</network>
virbr1 Bridge Network (First attempt)
<network>
<name>private</name>
<bridge name="virbr2" />
<ip address="169.254.1.1" netmask="255.255.0.0" />
<forward mode="route" dev="eth0:1" />
</network>
15 years
[libvirt-users] connect libvirt and virtualbox
by angelo alfano
conn = libvirt.open("vbox:///session")
return this error:
libvir: VBOX error : internal error unable to initialize VirtualBox driver API
Traceback (most recent call last):
File "prova.py", line 5, in <module>
conn = libvirt.open("vbox:///session")
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 163, in open
if ret is None:raise libvirtError('virConnectOpen() failed')
libvirt.libvirtError: internal error unable to initialize VirtualBox driver API
why?
15 years
