[libvirt-users] Missing target dev for interface
by jeremy avnet
I have over 20 guests running on a particular host and the three
longest running ones are missing the network device information in
their XML description:
<interface type='network'>
<mac address='54:52:10::f2:c5'/>
<source network='local'/>
</interface>
Compared to the others which have:
<interface type='network'>
<mac address='54:52:d1:32:0a:a1'/>
<source network='local'/>
<target dev='vnet13'/>
</interface>
This is problematic as I wanted to use domifstat on the domains. Using
the packet counts shown via ifconfig on the host, I was able to
determine what the vnet interface should be, but passing that to
domifstat doesn't work:
$ virsh domifstat maki221 vnet13
Connecting to uri: qemu:///system
error: Failed to get interface stats guest19 vnet13
error: invalid argument in invalid path, 'vnet13' is not a known interface
How did this happen? Is there a way I can get libvirt to know about
the interfaces?
And the guest OS's network connections work fine.
Thanks!
.:. jeremy
15 years
[libvirt-users] Multipath pools - practical for use?
by Justin Clift
Hi all,
Writing up some Fedora documentation, and looking to figure out the best
way of mapping multipath network(!) LUNs to pools in libvirt.
ie Infiniband SRP LUNs, but would probably apply to Fibre Channel
equally as well.
There are two approaches I can think of easily:
a) Large LUNs (ie TB+) that are mapped to a host server as disk, with
each LUN being configured as an LVM pool. This lets the host
slice the pool up into volumes with the libvirt volume creation
commands.
b) Pre-purposed LUNs mapped to a host server as disk, but passed
through directly to their respective guests.
ie Something like Oracle, with 3 SAN LUNs mapped to guest FOO for
its database data
In a non-libvirt world I'd look at configuring the LUNs on the host
with persistent name using multipath, then present them appropriately to
whatever needs them from there.
However, libvirt has a pool type called "multipath". Looking at the
docs online, it doesn't appear to be all that fully featured at this
point. Seems more of a brief mention and footnote, so I'm wondering
whether to use it or skip it for now in the Fedora docs.
Anyone have thoughts/suggestions/etc? :)
Regards and best wishes,
Justin Clift
--
Salasaga - Open Source eLearning IDE
http://www.salasaga.org
15 years, 1 month
[libvirt-users] unknown procedure: 159
by DevOs Virt
Hi,
I started using libvirt few days back...while using virDomainMemoryStats
API, got "unknown procedure: 159" runtime error
code is
-------------------------------------------------------------------------------------------------------------------------------------
virDomainMemoryStatPtr statPtr;
statPtr = malloc(VIR_DOMAIN_MEMORY_STAT_NR* sizeof
(virDomainMemoryStatStruct));
unsigned int flags=0;
int Ret;
Ret = virDomainMemoryStats(domPtr,statPtr, VIR_DOMAIN_MEMORY_STAT_NR,flags);
-------------------------------------------------------------------------------------------------------------------------------------
Machine details:
------------------------------------------------------------------------------------------------------------------------------------
[root@wlng-ppcore-nd3 hellolibvirt]# uname -a
Linux wlng-ppcore-nd3 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010
x86_64 x86_64 x86_64 GNU/Linux
[root@wlng-ppcore-nd3 hellolibvirt]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
------------------------------------------------------------------------------------------------------------------------------------
virsh details:
[root@wlng-ppcore-nd3 hellolibvirt]# virsh version
Compiled against library: libvir 0.8.1
Using library: libvir 0.8.1
Using API: QEMU 0.8.1
Running hypervisor: QEMU 0.9.1
------------------------------------------------------------------------------------------------------------------------------------
There are two libvirtd installations here..
------------------------------------------------------------------------------------------------------------------------------------
[root@wlng-ppcore-nd3 sbin]# pwd
/usr/sbin
[root@wlng-ppcore-nd3 sbin]# ls -l libvirtd
-rwxr-xr-x 1 root root 380064 Jun 10 02:33 libvirtd
[root@wlng-ppcore-nd3 sbin]# ./libvirtd --version
./libvirtd (libvirt) 0.6.3
------------------------------------------------------------------------------------------------------------------------------------
[root@wlng-ppcore-nd3 sbin]# pwd
/usr/local/sbin
[root@wlng-ppcore-nd3 sbin]# ls -l
total 3084
-rwxr-xr-x 1 root root 3152977 Jun 10 01:25 libvirtd
[root@wlng-ppcore-nd3 sbin]# ./libvirtd --version
./libvirtd (libvirt) 0.8.1
------------------------------------------------------------------------------------------------------------------------------------
found a link which mentions libvirtd can be old hence this error is
possible... not sure how to configure the latest libvirtd?
How to solve "unknown procedure: 159" runtime error?
Thanks,
osvdev
15 years, 1 month
Re: [libvirt-users] upgrading from 0.7.2 to 0.8.1
by Todd, John A
I'm still interested in knowing what vbox:///system is, but I figured
out that I have manually specify -with-xen when building to get
Xen support.
If after I get the Xen development package and rebuild it still doesn't
work, I'll drop a line here.
- JT
From: Todd, John A
Sent: Tuesday, June 08, 2010 1:39 PM
To: 'libvirt-users(a)redhat.com'
Subject: upgrading from 0.7.2 to 0.8.1
Hi, I had 0.7.2 running as an out-of-the-box version of libvirtd
I ran xend and it could connect to xen:/// (with virsh)
I'm trying to build a eucalyptus cloud and its not working, saying
'cannot connect to xen:///' and I don't know why.
So I figure I'd get the source and try and figure it out....and upgrade
while I was at it.
I got 0.8.1 from source, built it and installed it.
First of all, it installed everything using /usr/local as its root, is
this configurable?
I mean doing that it left my 0.7.2 still there and I had to do some
magic to replace it with the new stuff.
Now it connects to vbox:///system fine, but can't see xen:///
What's vbox:///system anyway?
Could it be my xend is talking to old binaries? (though I don't know
what they would be exactly)
Is there some configuration (beyond the certificate stuff which I did to
get libvirt actually up and running) with 0.8.1 (or in general as
configuration for 0.7.2 was done behind the scene as part of OS install)
That I need to do so it can connect to xen:/// again?
I'm not subscribed to the list, please email responses directly to me at
todjo06(a)ca.com
Thanks.
- Q
15 years, 1 month
[libvirt-users] upgrading from 0.7.2 to 0.8.1
by Todd, John A
Hi, I had 0.7.2 running as an out-of-the-box version of libvirtd
I ran xend and it could connect to xen:/// (with virsh)
I'm trying to build a eucalyptus cloud and its not working, saying
'cannot connect to xen:///' and I don't know why.
So I figure I'd get the source and try and figure it out....and upgrade
while I was at it.
I got 0.8.1 from source, built it and installed it.
First of all, it installed everything using /usr/local as its root, is
this configurable?
I mean doing that it left my 0.7.2 still there and I had to do some
magic to replace it with the new stuff.
Now it connects to vbox:///system fine, but can't see xen:///
What's vbox:///system anyway?
Could it be my xend is talking to old binaries? (though I don't know
what they would be exactly)
Is there some configuration (beyond the certificate stuff which I did to
get libvirt actually up and running) with 0.8.1 (or in general as
configuration for 0.7.2 was done behind the scene as part of OS install)
That I need to do so it can connect to xen:/// again?
I'm not subscribed to the list, please email responses directly to me at
todjo06(a)ca.com
Thanks.
- Q
15 years, 1 month
[libvirt-users] Best practices on backingup/restore VMs
by Arthur Pemberton
I just moved from F11 to F13 and I'm find no information on the best
way to restore VMs. I had just copied /var/lib/libvirt (with the VMs
off) as part of my backup (I already backup all of /etc). But
virt-manager doesn't allow creations of VMs without installing.
Also, as a side note, the search feature on the website doesn't seem
to allow me to search using documentation only.
--
Fedora 13
(www.pembo13.com)
15 years, 1 month
[libvirt-users] Dual-boot and also use raw disk in virtual machine
by Richard Walker
I've got a new computer with two SATA disks.
I installed a minimal Fedora 13 64-bit on the first disk.
I shut down the computer, unplugged the first disk,
booted up and installed Windows 7 on the second disk.
Then I shut down, and plugged the first disk back in.
I added a grub option to boot Windows from the second disk.
All fine so far - I had a working dual boot system.
Then in F13 using virt-manager I created a virtual machine using the second
disk as a raw disk. Well, the only option I had (using
virt-manager, at least) was to configure it as an IDE disk.
Booting this virtual machine gets as far as "Starting Windows",
and the animation appears (a dot or two), and then BSOD.
Running the Windows diagnosis didn't help.
I gave up. Then, keeping the same virtual machine configuration,
I installed Windows 7 again into the virtual machine.
I shut down the computer and booted from the second disk.
Saw "Starting Windows", and the animation got a bit further,
but got a BSOD again.
Now running sfdisk -l /dev/sdb in the F13 host shows:
Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 * 0+ 12- 13- 102400 7 HPFS/NTFS
start: (c,h,s) expected (0,32,33) found (2,0,33)
end: (c,h,s) expected (12,223,19) found (205,3,19)
/dev/sdb2 12+ 121601- 121589- 976657408 7 HPFS/NTFS
start: (c,h,s) expected (12,223,20) found (205,3,20)
end: (c,h,s) expected (1023,254,63) found (1023,15,63)
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
So there is some obvious disagreement about the
partition table.
Am I going to be able to get this to work?
15 years, 1 month
[libvirt-users] host OS can't access internet but guest OS with bridge can
by scar
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
i have a desktop with ubuntu 9.04 on it... it needs to be updated but i
can't access the internet since its last reboot. it has linux
2.6.28-18-generic on it, and libvirt 0.6.1-0ubuntu5.1.
i setup libvirt for bridging, and a guest OS i have running can access
the internet fine.
when i try to ping someplace from the host, it can resolve the hostname
but i get "Destination Host Unreachable" errors. it uses the router for
DNS, and i can access the router and other local computers fine.
$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
virbr0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 br0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 br0
$
-----BEGIN PGP SIGNATURE-----
iEYEAREIAAYFAkwKkZMACgkQXhfCJNu98qCt3wCffrY0VvAL0eA+uoVjHOIgnBax
5isAoPJTwxX/KLSOxA9UZDwO6a4ALkLx
=LE+h
-----END PGP SIGNATURE-----
15 years, 1 month
[libvirt-users] libvirt with opennebula
by marwen marwen
hello
I'm currently using libvirt and opennebula. I have installed the libvirt
with the driver of opennebule "ONE" and I test the installation.
/********************************************************/
oneadmin@node016 ~]$ virsh -c one:///
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list
Id Name State
----------------------------------
virsh #
/********************************************************/
but I can not see the list of machines that run in the cluster node (Xen and
KVM)
I want to know if this is a problem of configuration files ( libvirtd.conf and
oned.conf).
can you help me to overcome this problem
thank you
15 years, 1 month
