virt

virt@lists.centos.org

1608 discussions

Can't block-attach a file on a read only volume?
by Nathan March 19 Mar '15

19 Mar '15

Hi All, One more weird issue, this works on old xen but fails on 4.4: xendev01 ~ # mkdir /mnt/test xendev01 ~ # mount -t tmpfs - /mnt/test xendev01 ~ # dd if=/dev/null of=/mnt/test/disk seek=100M bs=1 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000201809 s, 0.0 kB/s xendev01 ~ # /usr/sbin/xl block-attach nathannx "file:/mnt/test/disk" "xvdd4" DEBUG libxl__blktap_devpath 37 aio:/mnt/test/disk DEBUG libxl__blktap_devpath 40 /dev/xen/blktap-2/tapdev20 xendev01 ~ # xl block-detach nathannx 51764 DEBUG libxl__device_destroy_tapdisk 66 type=aio:/mnt/test/disk disk=:/mnt/test/disk xendev01 ~ # mount -o remount,ro /mnt/test xendev01 ~ # /usr/sbin/xl block-attach nathannx "file:/mnt/test/disk" "xvdd4" DEBUG libxl__blktap_devpath 37 aio:/mnt/test/disk libxl: error: libxl.c:2149:device_disk_add: failed to get blktap devpath for 0xd3abd0 libxl: error: libxl.c:1727:device_addrm_aocomplete: unable to (null) device libxl_device_disk_add failed. I'm not sure why xen would care if the disk is writable? Would be nice to be able to mount these since many NFS storage arrays provide read only access to snapshots. - Nathan

2 4

CentOS 6 VM image for paravirtualizaton on CentOS Xen server
by Nico Kadel-Garcia 19 Mar '15

19 Mar '15

I'm looking at a CentOS 5 Xen server that I'd really like to put some more recent VM's. There are reasons not to touch it at the moment, so I can't upgrade it in place today. Has anyone successfully installed a CentOS 6 VM, paravirtualized, on a CentOS 5 Xen server , without significant Xen upgrades? If so, can I get a copy from a reputable source, or one that I can review before using? I'm having a bit of difficulty arranging a PXE enironment to do a paraviirtualized installation with, and there are apparently difficulties doing a paravirtualzed system with CD or DVD installation with Xen. Nico Kadel-Garcia <nkadel(a)gmail.com>

6 12

golang 1.4.2 in virt7-testing
by Lokesh Mandvekar 18 Mar '15

18 Mar '15

golang-1.4.2 is now available in the virt7-testing repo. More build info here: https://cbs.centos.org/koji/taskinfo?taskID=8901 docker seems to work fine with golang 1.4 on fedora rawhide and I heard the latest etcd needs at least 1.4. So hopefully, the latest build ^ takes care of this. -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

1 0

Virt SIG Meeting minutes for 10 Mar 2015
by Sandro Bonazzola 16 Mar '15

16 Mar '15

======================= #centos-devel: Virt SIG ======================= Meeting started by gwd-laptop at 14:01:55 UTC. The full logs are available at http://www.centos.org/minutes/2015/march/centos-devel.2015-03-10-14.01.log.… . Meeting summary --------------- * Xen updates (gwd-laptop, 14:03:52) * ACTION: gwd-laptop See if there was a conclusion to the docker / xen dom0 kernel discussion (i.e., separate repos or no) (gwd-laptop, 14:08:02) * Docker update (gwd-laptop, 14:08:32) * Docker 1.5.0 in virt7-testing. Public call for testing made, no timeline for official publication yet. (gwd-laptop, 14:16:35) * oVirt update (gwd-laptop, 14:17:46) * oVirt 3.5.2 RC1 has been released upstream, 3.5.2 GA scheduled for first week of April (sbonazzo, 14:17:58) * since CentOS 7.1 will be out sooner, we'll provide early testing and feedback to CentOS (sbonazzo, 14:18:11) * how to test page has been created updating the exisiting legacy how-to (sbonazzo, 14:18:30) * LINK: http://wiki.centos.org/HowTos/oVirt (sbonazzo, 14:18:38) * and linked in main SIG page on Projects - oVirt (sbonazzo, 14:18:48) * LINK: http://wiki.centos.org/SpecialInterestGroup/Virtualization (sbonazzo, 14:19:02) * slowly progressing with dependencies building due to limited human / time resources (sbonazzo, 14:19:12) * LINK: http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap (sbonazzo, 14:19:21) * reached an agreement on qemu-kvm-rhev re-branding, it will be qemu-kvm-ev. (sbonazzo, 14:19:29) * the new package has CentOS 7.1 dependencies so it has to wait. (sbonazzo, 14:19:35) * AOB (gwd-laptop, 14:28:34) * George checked the e-mail discussion and it had been concluded that we'd have separate tags for different project within the SIG (gwd-laptop, 14:29:19) Meeting ended at 14:33:30 UTC. Action Items ------------ * gwd-laptop See if there was a conclusion to the docker / xen dom0 kernel discussion (i.e., separate repos or no) Action Items, by person ----------------------- * gwd-laptop * gwd-laptop See if there was a conclusion to the docker / xen dom0 kernel discussion (i.e., separate repos or no) * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * gwd-laptop (38) * sbonazzo (25) * lsm5 (13) * centbot (5) * nshaikh (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Tapdisk processes being left behind when hvm domu's migrate/shutdown
by Nathan March 13 Mar '15

13 Mar '15

Hi All, I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown or migrated away. I don't see this problem with linux paravirt domu's, just windows hvm ones. xl.cfg: name = 'nathanwin' memory = 4096 vcpus = 2 disk = [ 'file:/mnt/gtc_disk_p1/nathanwin/drive_c,hda,w' ] vif = [ 'mac=00:16:3D:01:03:E0,bridge=vlan208' ] builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" localtime = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "destroy" vnc = 1 vncunused = 1 cpuid = [ '0:eax=00000000000000000000000000001011', '1:eax=00000000000000100000011011000010,ecx=10000011101110100010001000000011,edx=00010111100010111111101111111111', '2:eax=01010101000000110101101000000001', '7,0:eax=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,ebx=00000000000000000000000000000000,ecx=00000000000000000000000000000000,edx=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', '13,1:eax=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx0', '10:ebx=00000000000000000000000000000000', '11:edx=00000000000000000000000000000000', '2147483650:eax=01100101011101000110111001001001,ebx=00101001010100100010100001101100,ecx=01101111011001010101100000100000,edx=00101001010100100010100001101110', '2147483651:eax=01010101010100000100001100100000,ebx=00100000001000000010000000100000,ecx=00100000001000000010000000100000,edx=01001100001000000010000000100000', '2147483652:eax=00110000001101000011011000110101,ebx=00100000010000000010000000100000,ecx=00110111001100100010111000110010,edx=00000000011110100100100001000111', '2147483656:eax=00000000000000000011000000101000', ] Starting with the VM running initially on another host, I migrate it in: migration target: Ready to receive domain. Saving to migration stream new xl format (info 0x0/0x0/1450) Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/1450) Savefile contains xl domain config WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware xc: progress: Reloading memory pages: 56320/1114193 5% xc: progress: Reloading memory pages: 1003520/1114193 90% DEBUG libxl__blktap_devpath 37 aio:/mnt/gtc_disk_p1/nathanwin/drive_c DEBUG libxl__blktap_devpath 40 /dev/xen/blktap-2/tapdev0 DEBUG libxl__blktap_devpath 37 aio:/mnt/gtc_disk_p1/nathanwin/drive_c DEBUG libxl__blktap_devpath 40 /dev/xen/blktap-2/tapdev2 migration target: Transfer complete, requesting permission to start domain. migration sender: Target has acknowledged transfer. migration sender: Giving target permission to start. migration target: Got permission, starting domain. migration target: Domain started successsfully. migration sender: Target reports successful startup. DEBUG libxl__device_destroy_tapdisk 66 type=aio:/mnt/gtc_disk_p1/nathanwin/drive_c disk=:/mnt/gtc_disk_p1/nathanwin/drive_c Migration successful. and now I have 2 tapdisk procs: gtc-vana-005 ~ # ps auxf | grep tapdisk root 32491 0.1 0.2 20364 4636 ? SLs 11:06 0:00 tapdisk root 32520 0.0 0.2 20364 4636 ? SLs 11:06 0:00 tapdisk Which seems odd given that the VM in question only has a single disk attached to it and the qemu proc indicates it's using tapdev2: root 32524 0.4 0.7 323208 15040 ? SLsl 11:06 0:00 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 3 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-3,server,nowait -mon chardev=libxl-cmd,mode=control -nodefaults -name nathanwin--incoming -vnc 127.0.0.1:0,to=99 -device cirrus-vga -global vga.vram_size_mb=8 -boot order=cda -smp 2,maxcpus=2 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3d:01:03:e0 -netdev type=tap,id=net0,ifname=vif3.0-emu,script=no,downscript=no -incoming fd:13 -machine xenfv -m 4088 -drive file=/dev/xen/blktap-2/tapdev2,if=ide,index=0,media=disk,format=raw,cache=writeback gtc-vana-005 ~ # lsof -p 32520 | grep blktap-2 tapdisk 32520 root mem CHR 246,2 886671 /dev/xen/blktap-2/blktap2 tapdisk 32520 root 19u CHR 246,2 0t0 886671 /dev/xen/blktap-2/blktap2 gtc-vana-005 ~ # lsof -p 32491 | grep blktap-2 tapdisk 32491 root mem CHR 246,0 903999 /dev/xen/blktap-2/blktap0 tapdisk 32491 root 14u CHR 246,0 0t0 903999 /dev/xen/blktap-2/blktap0 I then migrate this VM off to another host: migration target: Ready to receive domain. Saving to migration stream new xl format (info 0x0/0x0/1450) Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/1450) Savefile contains xl domain config WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware xc: progress: Reloading memory pages: 56320/1114193 5% xc: progress: Reloading memory pages: 1003520/1114193 90% DEBUG libxl__blktap_devpath 37 aio:/mnt/gtc_disk_p1/nathanwin/drive_c DEBUG libxl__blktap_devpath 40 /dev/xen/blktap-2/tapdev2 DEBUG libxl__blktap_devpath 37 aio:/mnt/gtc_disk_p1/nathanwin/drive_c DEBUG libxl__blktap_devpath 40 /dev/xen/blktap-2/tapdev3 migration target: Transfer complete, requesting permission to start domain. migration sender: Target has acknowledged transfer. migration sender: Giving target permission to start. migration target: Got permission, starting domain. migration target: Domain started successsfully. migration sender: Target reports successful startup. DEBUG libxl__device_destroy_tapdisk 66 type=aio:/mnt/gtc_disk_p1/nathanwin/drive_c disk=:/mnt/gtc_disk_p1/nathanwin/drive_c Migration successful. and I'm down to one tapdisk proc that didn't get cleaned up: gtc-vana-005 ~ # ps auxf | grep tapdisk root 32520 0.0 0.2 20364 4636 ? SLs 11:06 0:00 tapdisk So it seems like xen is creating a second tapdisk proc on startup for some reason when it doesn't need to, then on cleanup it's only killing one of the two procs. Any thoughts? This is on the latest 4.4.1-7.el6 packages. Thanks! - Nathan

2 2

Re: [CentOS-virt] docker 1.5 in virt7-testing
by Lokesh Mandvekar 13 Mar '15

13 Mar '15

On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > KB, Just curious what's the latest re: docker testing and release? Also, where do people report bugs/issues for docker on centos? (can't find any in my view on bugs.c.o) -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

1 0

Disable/stop nic in a virtual guest with virsh
by C. L. Martinez 11 Mar '15

11 Mar '15

Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched.

9 15

Reminder: CentOS Virt SIG meeting on IRC today (10 Mar), 2pm GMT
by Sandro Bonazzola 10 Mar '15

10 Mar '15

Hey all, Just a reminder that we'll be resuming our bi-weekly Virt SIG meeting on IRC today at 2pm. Basic agenda: * Xen update * Docker update * oVirt update * Action items from previous meeting [1] * Other topics Please reply if you have any other topics you'd like to bring up. [1] http://www.centos.org/minutes/2015/february/centos-devel.2015-02-24-14.07.h… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

Virt SIG meeting on March 10th - I am on holiday
by Lars Kurth 04 Mar '15

04 Mar '15

I would need a volunteer to kick off and start the meeting Lars

2 2

Managing virt-manager's ever growing log file
by Robert Nichols 26 Feb '15

26 Feb '15

I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt