- Users - libvirt List Archives

[libvirt-users] overriding shutdown for LXC
by erkan yanar 31 Oct '12

31 Oct '12

Moin Im using lxc@libvirt for LXC-applicationcontainer. Works quite nice for now, beside shutting down the container, which is not implemented. Hooks don't help here, as far as I found out. Is there a way to override/define the shutdown function? Regards Erkan -- über den grenzen muß die freiheit wohl wolkenlos sein

1 0

Re: [libvirt-users] libvirt-users Digest, Vol 34, Issue 35
by Chandana De Silva 30 Oct '12

30 Oct '12

You _can_ do NAT. Set up a different libvirt network on each machine, like this; 10.128.80.65 will have a libvirt network 192.168.65.0/24 10.128.80.66 will have a libvirt network 192.168.66.0/24 Set up each of these networks as routed networks. Now set up routing/iptables rules on each host to send traffic to each other, and NAT into the internal routed network On 31/10/12 01:46, libvirt-users-request(a)redhat.com wrote: > Message: 1 > Date: Tue, 30 Oct 2012 07:10:55 +0000 > From: ??<zhang_zhang(a)live.com> > To:<libvirt-users(a)redhat.com> > Subject: [libvirt-users] Can VMs on different machines communicate > with each other without IP? > Message-ID:<BLU172-W4666B32A6C9C8E75734C67FC620(a)phx.gbl> > Content-Type: text/plain; charset="gb2312" > > > Dear all, > I confront a somehow strange situation: > I have two machines configured with ip 10.128.80.65 and 10.128.80.66 respectively. Each has several VMs running on it. The problem is that I have no more ip ( such as 10.128.80.67...) to allocate to VMs, but VMs need to communicate with each other even when they are on different machines. > Two network options exist: NAT and bridge. > 1) NAT > But VMs on different machine cannot communicate with each other. > 2)bridge > But there is no more ip for vm to be bridged to host machine. > Is there any other way to work around this problem? > > > many thanks!

1 0

[libvirt-users] error: Cannot open network interface control socket
by 何鑫 30 Oct '12

30 Oct '12

Hi all， I try to use gdb to debug libvirt's source code, but when I tend to create a domain with xml, it shows "error: internal error Network 'default' is not active", so I use the net-related commands as below."virsh # net-start defaulterror: Failed to start network defaulterror: Cannot open network interface control socket: Operation not permitted" Then I check my URI, which is "qemu:///session", because adding "sudo virsh". I try to change URI to "qemu:///system" by clicking "virsh # connect qemu:///system". The following logs shown below:virsh # connect qemu:///systemerror: Failed to connect to the hypervisorerror: Failed to connect socket to '/usr/local/libvirt/var/run/libvirt/libvirt-sock': No such file or directory Could you please tell me the reason? Thanks a lot! Corey

2 1

[libvirt-users] Failed to connect socket to '/usr/local/libvirt/var/run/libvirt/libvirt-sock':
by 何鑫 30 Oct '12

30 Oct '12

Hi all, When I tend to use "virsh # connect qemu:///system", the debug info shown below:Failed to connect socket to '/usr/local/libvirt/var/run/libvirt/libvirt-sock': No such file or directory I use libvirt-bin's file "libvirt-sock" linking to the directory(usr/local/libvirt/var/run/libvirt) where virsh needs to search it, then the problem solved. But I need to debug libvirt with gdb tracing libvirt's source code, to avoid the effects of libvirt-bin, I should remove libvirt-bin. As a result, the symbolic of libvirt-sock is missed. Also I can't copy "libvirt-sock", because "cp: cannot open `/var/run/libvirt/libvirt-sock' for reading: No such device or address". So could you please give me some advise to add the file "libvirt-sock" after the source installation in ubuntu? Thanks a lot! Corey

2 1

Re: [libvirt-users] virtual machine seems to run, but can't connect to it
by Douglas Russell 30 Oct '12

30 Oct '12

Thanks, I just figured it out. It turns out that my institution issues 192. addresses to MAC addresses it doesn't recognize. I had not realized this so assumed that the IP address was coming from the VM setup somehow. Onto the next problem now! But I'll post separately about that. Thanks for the help On 30 October 2012 04:11, Rudy Godoy <rudy(a)stone-head.org> wrote: > On Mon, Oct 29, 2012 at 10:53:29AM +0000, Douglas Russell wrote: > > I'm using ubuntu 12.04LTS > > > > I setup a bridged network: > > > > <snip> > > > > > It generates fine and starts up seemingly without a problem as well when > I > > run > > > > virsh start myvm > > > > I am then able to resolve it's IP with MDNS and try > > > > ping myvm.local > > > > So presumably the VM is running? But for some reason I can't communicate > > with it, I can't SSH in, I don't even get a response to my ping. > > > > What does displays: > # virsh dominfo myvm > > Can you connect to the console? > > # virsh console myvm > > regards > > > -- > Rudy Godoy > http://stone-head.org >

1 0

[libvirt-users] libvirt and cgroups/blkio
by erkan yanar 29 Oct '12

29 Oct '12

Hi, is there a way to configure blkio via libvirt (xml)? Regards Erkan -- über den grenzen muß die freiheit wohl wolkenlos sein

2 4

[libvirt-users] Re-sizing qcow2 images
by Chandana De Silva 29 Oct '12

29 Oct '12

Hello All, I am using Centos 6.3 with libvirt 0.910 and qemu-kvm 0.12 I had to resize a qcow2 disk, and came across several issues; I used this command to resize the image: sudo -i /usr/bin/qemu-img /var/lib/libvirt/images/mydisk.img resize +100G . The disk is attached using virtio. I then tried to use parted from within the guest to resize the partition. The first problem was that the guest os did not see the increase disk size. Is there something that I need to do, to force the guest to see the higher disk size ? I got round this by re-starting the guest, but it would be better if there is some way to force the guest to see the new size. The second problem was that parted gave an error : Error: Filesystem has an incompatible feature enable. Some reading showed that this was caused by the "resize_inode" feature on the file system. I removed this feature using debugfs, and rans fsck, but parted still gave the same error: Error: Filesystem has an incompatible feature enable. I would like some advice on how this is supposed to be done. Thanks in advance. Chandana

3 3

[libvirt-users] Re-sizing qcow2 images
by Chandana De Silva 29 Oct '12

29 Oct '12

Hello Hristo, Thanks for your comments. I was really looking for an on-line resizing tool. Eric Blake's later response seem to cover this. Regards Chandana On 30/10/12 03:00, Hristo Deshev<hristo(a)deshev.com> > For my resizes I use libguestfs's virt-resize [1] tool. It's been > working flawlessly so far -- it resizes both the image file/device and > partitions inside that image. I can't recommend it enough. > > Best, > Hristo

1 0

[libvirt-users] virt-manager fails to connect to dbus
by sean darcy 29 Oct '12

29 Oct '12

On Fedora 17 updated: virt-manager-0.9.4-2.fc17.noarch libvirt-0.10.2.1-1.fc17.x86_64 after a reboot, virt-manager no longer starts. Used to! virt-manager & [1] 1676 [root@sixcore ~]# (virt-manager:1676): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-0v4E2bXlqf: Connection refused Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 386, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 321, in main config = virtManager.config.vmmConfig(appname, appversion, ui_dir) File "/usr/share/virt-manager/virtManager/config.py", line 98, in __init__ self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE) GError: No D-BUS daemon running [root@sixcore ~]# systemctl status dbus.service dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; enabled) Active: active (running) since Mon, 29 Oct 2012 16:53:41 -0400; 2s ago Process: 1669 ExecStartPre=/bin/rm -f /var/run/messagebus.pid (code=exited, status=0/SUCCESS) Process: 1666 ExecStartPre=/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS) Main PID: 1672 (dbus-daemon) CGroup: name=systemd:/system/dbus.service └ 1672 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation Any help appreciated, sean

1 0

[libvirt-users] libvirt and thin provisionned LVM
by Daniel Berteaud 29 Oct '12

29 Oct '12

Hi there. I'm trying to use thin provisionned LVM for som eguests, and I'm having a problem. Until now, I use LVM pool with success. Here's my pool definition: <pool type='logical'> <name>data</name> <uuid>7f18e030-9d2d-805e-c65f-d12d0681b0a9</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> <name>data</name> <format type='lvm2'/> </source> <target> <path>/dev/data</path> <permissions> <mode>0700</mode> <owner>-1</owner> <group>-1</group> </permissions> </target> </pool> Everything is working, until I create a thin privisionned pool like this: lvcreate --thin data/pool -L 50G Now, as soon as this is created, I cannot refresh my pool from libvirt POV: LANG=C_ALL virsh pool-refresh data error: Failed to start pool sys error: erreur interne Child process (/sbin/vgchange -aln vg_gerard) status unexpected: exit status 5 If I remove this LV, everything is working again. I'm using libvirt 0.9.10, the default one in CentOS 6.3 (x86_64). Has anybody managed to get it working ? Is this something fixed in more recent release ? Regards, Daniel -- Daniel Berteaud FIREWALL-SERVICES SARL. Société de Services en Logiciels Libres Technopôle Montesquieu 33650 MARTILLAC Tel : 05 56 64 15 32 Fax : 05 56 64 15 32 Web : http://www.firewall-services.com

1 0

[libvirt-users] virtual machine seems to run, but can't connect to it
by Douglas Russell 29 Oct '12

29 Oct '12

I'm using ubuntu 12.04LTS I setup a bridged network: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_fd 0 bridge_maxwait 0 Seems to work. Then I created a virtual machine using Ubuntu's vmbuilder tool like so: vmbuilder kvm ubuntu \ --suite 'precise' \ --flavour 'virtual' \ --arch 'amd64' \ --dest 'myvm' \ --hostname 'myvm' \ --mem '2048' \ --rootsize '4096' \ --swapsize '1024' \ --mirror 'http://archive.ubuntu.com/ubuntu' \ --name 'MyName' \ --user 'myuser' \ --pass 'password' \ --bridge 'br0' \ --addpkg acpid \ --addpkg vim \ --addpkg openssh-server \ --addpkg avahi-daemon \ --libvirt 'qemu:///system' \ --ip '192.168.0.100' It generates fine and starts up seemingly without a problem as well when I run virsh start myvm I am then able to resolve it's IP with MDNS and try ping myvm.local So presumably the VM is running? But for some reason I can't communicate with it, I can't SSH in, I don't even get a response to my ping. Any ideas? I'd be happy to provide further information. Thanks.

2 1

[libvirt-users] Health check
by Ali Nikzad 28 Oct '12

28 Oct '12

Hi, I want to write an application that Health checks a virtual machine to see whether the VM is up and running or not. I am using ESXi as my hypervisor. Are there any libvirt API functions that I can use for this purpose? Regards, Ali

1 0

Re: [libvirt-users] Re-sizing qcow2 images
by Rajesh Kumar Mallah 28 Oct '12

28 Oct '12

----- "Chandana De Silva" <chandana(a)desilva.id.au> wrote: | From: "Chandana De Silva" <chandana(a)desilva.id.au> | To: "Rajesh Kumar Mallah" <mallah(a)tradeindia.com> | Cc: libvirt-users(a)redhat.com | Sent: Sunday, October 28, 2012 3:35:05 PM | Subject: Re: [libvirt-users] Re-sizing qcow2 images | | Hello Rajesh, | | Thanks for the the suggestions. | | | On 28/10/12 17:43, Rajesh Kumar Mallah wrote: | > If you have a spare guest you may consider temporarily attaching the | said cow2 image to that guest | Do you mean detach from guest A and attach to guest B ? Yes. | > and use the partition tools (like parted , fdisk,cfdisk etc) | > and filesystem tools (like xfs_grow , resize2fs etc) to grow the | filesystem. | Assuming it will be possible to detach and attach, I still have the | problem of parted giving the incompatible feature error. These disk | have GPT partitions so I can use fdisk I am not sure about the "incompatible feature error" . May be you could try fdisk or cfdisk. It is usually a good idea to "free" the device before doing partition resizes. We had done it (resizing cow2) once and it was successful , we had to although convert from cow2 to raw , append a new dd'ed file and user fdisk over the raw image. eventually it worked. what is the size of your cow2 device if its not huge you may consider backing it up and restore to a larger device. hope it helps. mallah.

1 0

Re: [libvirt-users] Re-sizing qcow2 images
by Rajesh Kumar Mallah 28 Oct '12

28 Oct '12

Hi, If you have a spare guest you may consider temporarily attaching the said cow2 image to that guest and use the partition tools (like parted , fdisk,cfdisk etc) and filesystem tools (like xfs_grow , resize2fs etc) to grow the filesystem. use partprobe to reread the partition table into the kernel once partition editing tools are used. re-read of mounted root partions mostly do not work for me. hence i suggested using a separte vm for the image. Regards, Rajesh Kumar Mallah Tel. 91-11-46710500 (Ext:303) Cell +919811255597 Website: http://www.tradeindia.com/ \|/ \|/ \|/ stop printing \|/ \|/ \|/ | | | start planting | | | ----- "Chandana De Silva" <chandana(a)desilva.id.au> wrote: | From: "Chandana De Silva" <chandana(a)desilva.id.au> | To: libvirt-users(a)redhat.com | Sent: Sunday, October 28, 2012 8:13:50 AM | Subject: [libvirt-users] Re-sizing qcow2 images | | Hello All, | | I am using Centos 6.3 with libvirt 0.910 and qemu-kvm 0.12 | | I had to resize a qcow2 disk, and came across several issues; | | I used this command to resize the image: | | sudo -i /usr/bin/qemu-img /var/lib/libvirt/images/mydisk.img resize | +100G . The disk is attached using virtio. | | I then tried to use parted from within the guest to resize the | partition. | | The first problem was that the guest os did not see the increase disk | size. | Is there something that I need to do, to force the guest to see the | higher disk size ? | I got round this by re-starting the guest, but it would be better if | there is some way to force the guest to see the new size. | | The second problem was that parted gave an error : Error: Filesystem | has | an incompatible feature enable. | Some reading showed that this was caused by the "resize_inode" feature | | on the file system. I removed this feature using debugfs, and rans | fsck, | but parted still gave the same error: Error: Filesystem has an | incompatible feature enable. | | I would like some advice on how this is supposed to be done. | | Thanks in advance. | | Chandana | | | _______________________________________________ | libvirt-users mailing list | libvirt-users(a)redhat.com | https://www.redhat.com/mailman/listinfo/libvirt-users

2 1

[libvirt-users] hypervisor driver not found
by p.venkatasrinivas＠tcs.com 26 Oct '12

26 Oct '12

Hi, I installed Virtual box software in linux open suse. Unable to connect to the vbox hypervisor driver. Version-Release number of selected component (if applicable): libvirt-0.9.0 How reproducible: when i am giving the following command for virsh: virsh -connect vbox:///session then the following error is coming. error: no hypervisor driver available for vbox:///session error: failed to connect to the hypervisor Even I installed virtualbox the above error is coming. I am not able to find vbox hypervisor driver. Can anyone suggest where can i find vbox dirver. Awaiting Response Thanks and Regards, Srinivas. =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 5

[libvirt-users] virsh responds slowly
by Chun-Hung Chen 26 Oct '12

26 Oct '12

Dear all, I have observed the virsh responds slowly with "virsh list" and used "strace virsh list" will find that it is waiting on the socket. I also use "netstat |grep libvirt" and see an opened socket /var/run/libvirt-sock-ro is always on and will not disappear. Is it caused by an abnormal termination of virsh API? Otherwise, if there is any possible issue? I have checked the cpu utilization, it is low and no waiting io. Regards, Chun-Hung

1 0

[libvirt-users] KVM raw on DRDB on LVM logical volume?
by Whit Blauvelt 25 Oct '12

25 Oct '12

Hi, I'm trying to get KVM VMs set up right on top of DRBD, with a dedicated DRBD mirror instance on top of a dedicated pair of LVM LVs per VM - allowing, for instance, primary-secondary DRBD assignments at the same granularity as the VMs. In other words, I want to put VMs in raw format directly to the DRBD block device, just as they are commonly put to an LV block device, with the DRBD block device stacked on the LV block device. DRBD is happy to stack on an LV (just as libvirt-KVM-QEMU is happy to). But when I take an existing KVM LV, set up DRBD for it (DRBD can typically be placed on a partition with an existing file system, which it inherits), and then use "virsh edit" to replace the source dev, like so: <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/VolumeGroup/SomeVolume'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> changing the center line to <source dev='/dev/drbd/by-res/SomeDom'/> (or /dev/drbdN - to which that's a symlink), then I get # virsh start sql error: Failed to start domain SomeDom error: unable to open disk path /dev/drbd/by-res/SomeDom: Wrong medium type If this were a normal file system, setting up DRBD with it, then remounting it through the DRBD device would work. But libvirt doesn't want to "mount" it. This is with virsh 0.9.12. I don't know what constitutes "Wrong medium type" here. I had thought it the general case that raw files for KVM can be written to block devices generally, which is what a DRBD device is, just as much as an LV device is. Is this then a case where I have to change something else in the XML? Or a case where it would work except that libvirt doesn't recognize that this is a media type that will work, yet is is, so that the answer would be to alter libvirt's source and recompile? Or would getting this scheme to work require the trouble of stacking things like VM LV VG PV DRBD LV VG PV DISK instead of simply like VM DRBD LV VG PV DISK Since there's a strict 1 VM-1 DRBD-1 LV correspondence, I'm hoping those extra layers won't be necessary to get DRBD into the stack. Thanks, Whit

1 0

[libvirt-users] Please help: Libvirt event for disk change is not being registered by DomainEventRegisterAny()
by Abhishek Srivastava 25 Oct '12

25 Oct '12

Hi, I am writing an application which would monitor the changes on the domain on the KVM hypervisor through libvirt events. Recently I have upgraded my libvirt from 9.4 to 9.10 and I have this issue. While *de-registering* for DomainEventDiskChangeCallback, I get a libvirt error saying 'libvirtError: internal error domain event 2 not registered;' where 2 is the callbackid returned by virConnectDomainEventRegisterAny() for the disk change event type. This error didn’t occur when I used libvirt 0.9.4-23.el6_2.6 Can you please enlighten me on the recent changes that has been made? Also, is the diskchange event a part of the domains life cycle event? Any help on this issue will be highly appreciated. Thanks and regards, Abhishek

1 0

[libvirt-users] Disk-only internal snapshot
by Davide Guerri 25 Oct '12

25 Oct '12

Hi all, it's possible to do an internal snapshot with the --disk-only option (for qcow2 images)? The following command virsh snapshot-create-as my-dom my-snap my-description creates an internal snapshot but the following virsh snapshot-create-as my-dom my-snap my-description --disk-only creates an external snapshot. Thanks, Davide.

4 7

[libvirt-users] cannot start domain with SR-IOV interface
by Radhika Niranjan 24 Oct '12

24 Oct '12

Hi, I've been using libvirt (versions 0.9.11.5, and recently upgraded to 0.10.2), and have been attaching an SR-IOV VF to my VM with the following device configuration: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x07' slot='0x10' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> I had no problems with bringing up the VM and using the VF with this configuration. Recently I noticed that I would be able to assign a mac address to the SR-IOV VF if I used the interface configuration and changed over to using: <interface type='hostdev'> <mac address='52:54:00:d3:23:4f'/> <source> <address type='pci' domain='0x0000' bus='0x07' slot='0x10' function='0x0'/> </source> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> My VM fails to start up with this interface configuration. The error reported is: error: Failed to start domain exp85-1 error: An error occurred, but the cause is unknown When I look into /var/log/messages I see the following messages: Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.145+0000: 17713: error : virFileReadAll:457 : Failed to open file '/var/run/libvirt/qemu/p1p1_vf0': No such file or directory Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.146+0000: 17713: error : qemuRemoveCgroup:740 : internal error Unable to find cgroup for exp85-1 Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.146+0000: 17713: warning : qemuProcessStop:4136 : Failed to remove cgroup for exp85-1 I was wondering if anyone else has faced this problem or has a solution to this. I'm using Fedora17, KVM, and an 82599EB Intel NIC. Thanks much in advance. With best regards Radhika

2 1

[libvirt-users] Failed to query file context on : No data available
by #█er 24 Oct '12

24 Oct '12

Hi:I downloaded a cirros-0.3.0-x86_64-rootfs.img and mount it to /tmp/bak then I edit a xml file ,here is the content: <domain type='lxc'> <name>vm1</name> <memory>500000</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <vcpu>1</vcpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount'> <source dir='/tmp/bak'/> <target dir='/'/> </filesystem> <interface type='network'> <source network='default'/> </interface> <console type='pty' /> </devices> </domain> I defined it and no error , but when I start it , it comes with error: Failed to start domain vm1 error: internal error guest failed to start: 2012-10-24 13:08:14.684+0000: 16935: info : libvirt version: 0.9.10, package: 21.el6_3.4 (CentOS BuildSystem <http://bugs.centos.org>, 2012-08-23-18:28:26, c6b9.bsys.dev.centos.org) 2012-10-24 13:08:14.684+0000: 16935: error : lxcControllerRun:1484 : Failed to query file context on /tmp/bak: No data available here is the ls -al /tmp/bak total 92 drwxr-xr-x 21 root root 4096 Oct 24 20:43 . drwxrwxrwt. 5 root root 4096 Oct 24 21:08 .. drwxr-xr-x 2 root root 4096 Oct 24 20:43 bin drwxr-xr-x 3 root root 4096 Oct 24 20:43 boot drwxr-xr-x 3 root root 4096 Oct 24 20:43 dev drwxr-xr-x 7 root root 4096 Oct 24 20:43 etc drwxr-xr-x 4 root root 4096 Oct 24 20:43 home -rwxr-xr-x 1 root root 2785 Oct 24 20:43 init lrwxrwxrwx 1 root root 32 Oct 24 20:43 initrd.img -> boot/initrd.img-3.0.0-12-virtual drwxr-xr-x 4 root root 4096 Oct 24 20:43 lib lrwxrwxrwx 1 root root 11 Oct 24 20:43 linuxrc -> bin/busybox drwx------ 2 root root 4096 Oct 24 20:43 lost+found drwxr-xr-x 2 root root 4096 Oct 24 20:43 mnt drwxr-xr-x 2 root root 4096 Oct 24 20:43 .oldroot drwxr-xr-x 2 root root 4096 Oct 24 20:43 old-root drwxr-xr-x 2 root root 4096 Oct 24 20:43 opt drwxr-xr-x 2 root root 4096 Oct 24 20:43 proc drwx------ 2 root root 4096 Oct 24 20:43 root drwxr-xr-x 2 root root 4096 Oct 24 20:43 run drwxr-xr-x 2 root root 4096 Oct 24 20:43 sbin drwxr-xr-x 2 root root 4096 Oct 24 20:43 sys drwxr-xr-t 3 root root 4096 Oct 24 20:43 tmp drwxr-xr-x 6 root root 4096 Oct 24 20:43 usr drwxr-xr-x 8 root root 4096 Oct 24 20:43 var lrwxrwxrwx 1 root root 29 Oct 24 20:43 vmlinuz -> boot/vmlinuz-3.0.0-12-virtual How can I solve this problem? Thanks :-)

1 0

[libvirt-users] Libvirt event for disk change is not being registered by DomainEventRegisterAny()
by Abhishek Srivastava 24 Oct '12

24 Oct '12

Hi, I am writing an application which would monitor the changes on the domain on the KVM hypervisor through libvirt events. Recently I have upgraded my libvirt from 9.4 to 9.10 and I have this issue. While *de-registering* for DomainEventDiskChangeCallback, I get a libvirt error saying 'libvirtError: internal error domain event 2 not registered;' where 2 is the callbackid returned by virConnectDomainEventRegisterAny() for the disk change event type. This error didn’t occur when I used libvirt 0.9.4-23.el6_2.6 Can you please enlighten me on the recent changes that has been made? Also, is the diskchange event a part of the domains life cycle event? Any help on this issue will be highly appreciated. Thanks and regards, Abhishek

1 0

[libvirt-users] Questions and a blockpull issue
by Abbas 23 Oct '12

23 Oct '12

Coming off of xen environment; still testing with kvm, just a few questions: 1. What is the roadmap for release of qemu-kvm 1.1 and libvirt 0.10.2 for el6, cause I had to compile from upstream to get the latest stuff. 2. Should not virt-manager show the sparsed disk size instead of actual reserved size of a vm? 3. Where is the virsh bash_completion conf.d file from upstream; since el6 rpm for it seems have tab completion built right into virsh shell. 4. Created a disk-only snapshot of a vm CO1 called capture1 but the syntax of blockpulling seems to be opposite from what has been advertised on Fedora and other relative wikis. Check below and the error with first blockpull command. [root@KVM libvirt]# virsh snapshot-create-as CO1 capture1 "CO1s first snapshot test" --disk-only --atomic [root@KVM libvirt]# virsh -d 0 blockpull CO1 --path /home/vms/co1.img --bandwidth 500 --base /home/vms/co1.capture1 blockpull: domain(optdata): CO1 blockpull: path(optdata): /home/vms/co1.img blockpull: bandwidth(optdata): 500 blockpull: base(optdata): /home/vms/co1.capture1 blockpull: found option <domain>: CO1 blockpull: <domain> trying as domain NAME error: invalid argument: No device found for specified path [root@KVM libvirt]# virsh -d 0 blockpull --domain CO1 --path /home/vms/co1.capture1 --base /home/vms/co1.img --verbose --wait blockpull: domain(optdata): CO1 blockpull: path(optdata): /home/vms/co1.capture1 blockpull: base(optdata): /home/vms/co1.img blockpull: verbose(bool): (none) blockpull: wait(bool): (none) blockpull: found option <domain>: CO1 blockpull: <domain> trying as domain NAME Block Pull: [100 %] Pull complete Best, Abbas.

2 9

[libvirt-users] Unable to start guest
by Jeremy Johnston 23 Oct '12

23 Oct '12

I have been picking away at this problem and I have not been able to resolve it yet and it appears quite puzzling to me, I am attempting to start a guest on KVM and receive 'error: An error occurred, but the cause is unknown'. I have a feeling this may be something simple I am overlooking. I have included log files and the xml of the guest at http://node4.smart-serv.net/~jeremy/libvirt/

2 1

[libvirt-users] using vbox driver hypervisor support
by p.venkatasrinivas＠tcs.com 23 Oct '12

23 Oct '12

Hi, I installed Libvirt. We need virtualbox support for libvirt. But we are unable to see the vbox option in virt-manager. How we can find vbox hypervisor driver? And also we already compiled libvirt with vbox option.(--with-vbox). But that didn't work. And also when we are creating the new virtual machine through virt-manager we are getting the following error: internal error cannot parse QEMU version number in "" Can you please suggest on this what we need to do as soon as possible? Thanks in advance. Srinivas =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 1