- Users - libvirt List Archives

[libvirt-users] question about process power which has MCSx
by yue 17 Apr '13

17 Apr '13

hi,all a qemu-kvm process and its disk(image file) have the same MCS(s0:c111,c555). it express this process have access to this image. i do not know the power to access its image file is the max or min? if any other power this process(domain) has?how much? i want to know the exact power a qemu-kvm process has besides access its image file ,other kinds of files,dirs etc. my test case: after start a guestVM(its disk xml ,cache='none' error_policy='stop'), make some modification on its files and save them. then go to hypervisor, modify the MCS of guestVM's image file. 1.i can read those files(cache=none)?it should not be so. why? 2.then modify files and save, the guestVM hang, it is paused on UI. this is right qeum process can not write again. why this guestVM is hang? and can not be resumed 3.look at audit info. denied { write } for pid=52162 comm="qemu-kvm". that pid is 52162, is not my qemu-kvm's pid? why? thanks so much.

2 1

[libvirt-users] libvirt support for qcow2 rebase?
by Skardal, Harald 17 Apr '13

17 Apr '13

I have not found support in libvirt (nor virsh) for doing the equivalent of "qemu-img rebase ....". The use case: You have copied a qcow2 stack and the new files have different names or reside in a different directory. Therefore you need to change the backing file. Is there a way to do this? Is this a planned addition to libvirt? Harald

3 2

[libvirt-users] Any good writeups of using libvirt with LXC
by brian mullan 17 Apr '13

17 Apr '13

I've been experimenting a bit with using libvirt and LXC. But have not found many good examples of use so far. Anyone got any they can point me to. thanks brian

3 2

[libvirt-users] Update request: When support for live snapshot delete incl coalesce
by Skardal, Harald 17 Apr '13

17 Apr '13

Does the libvirt development team have a sense of when/which version of libvirt will support the deletion of live snapshots, incl. the coalesce. With the restriction that you cannot delete the most recent snapshot! Harald

2 1

[libvirt-users] Shouldn't vol-upload / virStorageVolUpload() be doing some format conversion?
by Guido Winkelmann 15 Apr '13

15 Apr '13

Hi, I just tried using vol-update to copy an image file to a storage pool, and I noticed that, at least in my configuration (qemu backend, storage pool of type "dir"), this command does not appear to be doing any kind of format conversion. It simply copied the source file as-is over the file in which the target volume was stored with no checks whether that even makes sense. The help text to this command says it supports offset and length, which - kinda, sorta - implies that I can write a block of bytes at offset n to a volume, attach that volume to a domain, and then the OS in the guest domain will find exactly the bytes I just wrote at exactly offset n in its newly attached harddisk/CDROM/whatever. Instead, trying to this with anything but raw images would probably just break the image file. AFAICS, in its current form, this command and this API-call are only useful in exactly two scenarios: - Both the source and target image are in raw format - Source and target image are in the same non-raw format (like qcow2 or vmdk) AND you are copying the entire volume at once. In all other cases - source and target are in different formats, source and target are in non-raw and you are trying to write only parts of a volume - this can only lead to a broken image file. As far as I see it, at the layer of abstraction libvirt offers, "volume" should not be synonymous with "the file the file the volume is stored in on disk", but rather with "the volume as a guest machine will get to see it". Regards, Guido

2 3

[libvirt-users] network under session
by Evaggelos Balaskas 15 Apr '13

15 Apr '13

Perhaps a stupid question, but i will give it a try: I have two machines on libvirtd session and network on usermod. Can i (somehow) cross these two machines ? machineA: ip addr add 10.10.10.101/24 dev eth0 ip route add default via 10.10.10.102 dev eth0 machineB: ip addr add 10.10.10.102/24 dev eth0 ip route add default via 10.10.10.101 dev eth0 -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas

2 1

[libvirt-users] using transport protocol in live migration
by digvijay chauhan 15 Apr '13

15 Apr '13

Hello, I am working on live migration of virtual machine using xen and kvm.If i use qemu+ssh:///system then is the transport protocol used during live migration tcp or ssh?I mean i want to evaluate the performance of transport protocil during live migration using wireshark and netperf tool,so using this command will show tcp performance? Orelse i will have to use qemu+tcp:/// ?

2 2

[libvirt-users] how to start virbr0-nic when start NAT network virbr0
by yue 15 Apr '13

15 Apr '13

in my case each ethernet must in UP status even it is a NAT network where is the point i can start its virt-ethernet when i start a NAT-network? thanks

2 1

[libvirt-users] after snapshot-delete, the qcow2 image file size doesn't decrease
by me,apporc 15 Apr '13

15 Apr '13

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root@test1 ]# virsh list Id Name State ---------------------------------------------------- 32 bfbe8ca8-8579-11e2-844a-001018951f48 running [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.6G cluster_size: 65536 [root@test1 ]# ls -lh total 3.6G -rw------- 1 qemu qemu 3.6G Apr 12 17:13 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------ [root@test1 8]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758005 created [root@test1 ]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758022 created [root@test1 bfbe8ca8-8579-11e2-844a-001018951f48]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------ 1365758005 2013-04-12 17:13:25 +0800 running 1365758022 2013-04-12 17:13:42 +0800 running [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758005 127M 2013-04-12 17:13:25 00:00:53.141 2 1365758022 127M 2013-04-12 17:13:42 00:01:09.508 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:14 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758022 Domain snapshot 1365758022 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 0 1970-01-01 08:00:00 00:00:00.000 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:14 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758005 Domain snapshot 1365758005 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:14 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758311 created [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 3.8G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 [root@test1 ]# ls -lh total 3.9G -rw------- 1 qemu qemu 3.9G Apr 12 17:18 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-create bfbe8ca8-8579-11e2-844a-001018951f48 Domain snapshot 1365758338 created [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 2 1365758338 252M 2013-04-12 17:18:58 00:06:24.272 [root@test1 ]# ls -lh total 4.1G -rw------- 1 qemu qemu 4.1G Apr 12 17:19 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------ 1365758311 2013-04-12 17:18:31 +0800 running 1365758338 2013-04-12 17:18:58 +0800 running [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 2 1365758338 252M 2013-04-12 17:18:58 00:06:24.272 [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758338 Domain snapshot 1365758338 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1365758311 252M 2013-04-12 17:18:32 00:05:58.136 [root@test1 ]# ls -lh total 4.1G -rw------- 1 qemu qemu 4.1G Apr 12 17:20 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-delete bfbe8ca8-8579-11e2-844a-001018951f48 1365758311 Domain snapshot 1365758311 deleted [root@test1 ]# qemu-img info d0.qcow image: d0.qcow file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 4.1G cluster_size: 65536 [root@test1 ]# ls -lh total 4.1G -rw------- 1 qemu qemu 4.1G Apr 12 17:20 d0.qcow drwx------ 2 root root 4.0K Apr 12 17:12 held [root@test1 ]# virsh snapshot-list bfbe8ca8-8579-11e2-844a-001018951f48 Name Creation Time State ------------------------------------------------------------

3 2

[libvirt-users] virt-install on powerpc64 issues
by Alexey Kardashevskiy 15 Apr '13

15 Apr '13

Hi! I am trying to setup a guest using virt-install script: /usr/bin/virt-install -n fc18guest5 -r 1024 \ --disk path=/home/aik/virtimg/fc18guest,size=8 \ -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso \ --video vga --arch=ppc64 -d --machine=pseries And it fails. I could not find any relevant log in /var/log/libvirt/ so I simply hacked /usr/local/bin/qemu-system-ppc64 to print all the parameters passed into it. So I got the command line (below, after the second question) where the "-device scsi-cd" parameter is cut in a middle so QEMU fails to start. 788 chars long - is there a limit? The second question is - where does virt-install store those xmls? I have to choose a new name for a machine even if virt-install failed, in the example it is "fc18guest5" (5 at the end). "virsh -c qemu:///system list" prints an empty list with no domains. Thanks! /usr/local/bin/qemu-system-ppc64 -name fc18guest5 -S -M pseries -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid 71f8b17f-ca48-80fe-db58-4d933c66fe2d -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -device pci-ohci,id=usb,bus=pci,addr=0x1.0x2 -device spapr-vscsi,id=scsi0,reg=0x2000 -drive file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 -drive file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,ch The full log is here: [aik@vpl2 ~]$ ./start_installation.sh ++ /usr/bin/virt-install -n fc18guest5 -r 1024 --disk path=/home/aik/virtimg/fc18guest,size=8 -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso --video vga --arch=ppc64 -d --machine=pseries [Wed, 10 Apr 2013 15:06:10 virt-install 9880] DEBUG (cli:221) Launched with command line: /usr/bin/virt-install -n fc18guest5 -r 1024 --disk path=/home/aik/virtimg/fc18guest,size=8 -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso --video vga --arch=ppc64 -d --machine=pseries [Wed, 10 Apr 2013 15:06:10 virt-install 9880] DEBUG (cli:326) Requesting libvirt URI default [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:328) Received libvirt URI qemu:///session [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:259) Requesting virt method 'default', hv type 'default'. [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:469) Received virt method 'hvm' [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:470) Hypervisor name is 'kvm' [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:935) DISPLAY is set: graphics defaulting to VNC. [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:953) --graphics compat generated: vnc [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (DistroInstaller:209) DistroInstaller location is a local file/path: /home/aik/virtimg/Fedora-18-ppc64-DVD.iso [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:626) Guest.has_install_phase: True Starting install... [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (Guest:1296) Generated install XML: <domain type='kvm'> <name>fc18guest5</name> <uuid>56b64ac6-9596-6e8e-5321-4fc583960065</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type arch='ppc64' machine='pseries'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <features> <acpi/><apic/><pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/bin/qemu-system-ppc64</emulator> <disk type='file' device='disk'> <driver name='qemu'/> <source file='/home/aik/virtimg/fc18guest'/> <target dev='sda' bus='scsi'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu'/> <source file='/home/aik/virtimg/Fedora-18-ppc64-DVD.iso'/> <target dev='sdb' bus='scsi'/> <readonly/> </disk> <interface type='user'> <mac address='52:54:00:ca:ed:7a'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1'/> <console type='pty'/> <video> <model type='vga'/> </video> </devices> </domain> [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (Guest:1297) Generated boot XML: <domain type='kvm'> <name>fc18guest5</name> <uuid>56b64ac6-9596-6e8e-5321-4fc583960065</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type arch='ppc64' machine='pseries'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/><apic/><pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/bin/qemu-system-ppc64</emulator> <disk type='file' device='disk'> <driver name='qemu'/> <source file='/home/aik/virtimg/fc18guest'/> <target dev='sda' bus='scsi'/> </disk> <disk type='block' device='cdrom'> <target dev='sdb' bus='scsi'/> <readonly/> </disk> <interface type='user'> <mac address='52:54:00:ca:ed:7a'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1'/> <console type='pty'/> <video> <model type='vga'/> </video> </devices> </domain> [Wed, 10 Apr 2013 15:06:12 virt-install 9880] ERROR (cli:439) internal error process exited while connecting to monitor: char device redirected to /dev/pts/4 (label charserial0) [0]/usr/local/bin/qemu-system-ppc64 [1]-name [2]fc18guest5 [3]-S [4]-M [5]pseries [6]-enable-kvm [7]-m [8]1024 [9]-smp [10]1,sockets=1,cores=1,threads=1 [11]-uuid [12]56b64ac6-9596-6e8e-5321-4fc583960065 [13]-no-user-config [14]-nodefaults [15]-chardev [16]socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait [17]-mon [18]chardev=charmonitor,id=monitor,mode=control [19]-rtc [20]base=utc [21]-no-reboot [22]-no-shutdown [23]-device [24]pci-ohci,id=usb,bus=pci,addr=0x1.0x2 [25]-device [26]spapr-vscsi,id=scsi0,reg=0x2000 [27]-drive [28]file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw [29]-device [30]scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 [31]-drive [32]file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw [33]-device [34]scsi-cd,bus=scsi0.0,ch [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:442) Traceback (most recent call last): File "/usr/bin/virt-install", line 636, in start_install noboot=options.noreboot) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1249, in start_install noboot) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1317, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2775, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error process exited while connecting to monitor: char device redirected to /dev/pts/4 (label charserial0) [0]/usr/local/bin/qemu-system-ppc64 [1]-name [2]fc18guest5 [3]-S [4]-M [5]pseries [6]-enable-kvm [7]-m [8]1024 [9]-smp [10]1,sockets=1,cores=1,threads=1 [11]-uuid [12]56b64ac6-9596-6e8e-5321-4fc583960065 [13]-no-user-config [14]-nodefaults [15]-chardev [16]socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait [17]-mon [18]chardev=charmonitor,id=monitor,mode=control [19]-rtc [20]base=utc [21]-no-reboot [22]-no-shutdown [23]-device [24]pci-ohci,id=usb,bus=pci,addr=0x1.0x2 [25]-device [26]spapr-vscsi,id=scsi0,reg=0x2000 [27]-drive [28]file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw [29]-device [30]scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 [31]-drive [32]file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw [33]-device [34]scsi-cd,bus=scsi0.0,ch [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:451) Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///session start fc18guest5 otherwise, please restart your installation. Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///session start fc18guest5 otherwise, please restart your installation. [aik@vpl2 ~]$ virsh -c qemu:///system list Id Name State ---------------------------------------------------- [aik@vpl2 ~]$ -- Alexey

2 9