virt August 2013

virt@lists.fedoraproject.org

15 participants
8 discussions

[KVM] Calculation of the number of virtual machines on a single node.
by Vladimir Parf 30 Aug '13

30 Aug '13

Hello! I'm starting to deploy a private cloud on OpenStack! As the hypervisor I use nova+KVM on Fedora-19. Tell me how to count how many virtual machines can be placed on a single KVM node. How to count the number of virtual machines on single node to get everything working perfectly? Hardware configuration: CPU: 2x Intel(R) Xeon(R) CPU E5-2609 @ 2.40GHz - 4 core RAM: 96 GB HDD:Unlimited HW: ProLiant BL460c

2 1

why isnt loop mounted iso not been seen/used
by fp.to.anomalyst＠xoxy.net 27 Aug '13

27 Aug '13

the local path on the host is "/media/cdrom" and an ls shows the expected files/directories. I get a "no boot device" error on the console from the following script: http://www.fpaste.org/34713/86971137/ am trying to do a minimal Centos 6.4 unattended install. Using --cdrom tells me I can use extra-args to supply the kickstart. Without the kickstart I have to respond on the console. TIA, Bob

2 1

device='disk' and DISCARD
by Ian Pilcher 27 Aug '13

27 Aug '13

I just noticed the new "Virtio SCSI disk" and "Virtio SCSI lun" storage types in virt-manager (and their libvirt XML device=... equivalents). Reading up on them, I see that "generic" SCSI commands are only accepted when device='lun', but this only works when the source is an "actual raw device" -- not an LVM LV or partition. Does this mean that DISCARD commands are rejected when device='disk'? I've been using SSD-backed LVs as virtio-scsi disks, with the idea that this would cause DISCARD commands to be passed through from the guests. It would be a real bummer if there were no way to do this. Thanks! -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================

2 1

Current Status of LVM Snapshots & Libvirt
by Jorge Fábregas 26 Aug '13

26 Aug '13

Hi, What's the current status of LVM snapshots? Can you create/revert/commit them with virsh? Or is this an out of band operation (I have to manually use lvcreate etc...)? I've never used LVM-based images mainly because you couldn't overcommit the storage subsystem but now, with the new thin-provisioning capabilities of LVM, I'm willing to give it a try. That is, of course, *only* If I can still have all the nice snapshot capabilities I currently have with qcow2-based images :) Thanks, Jorge p.d I know you can create qcow2 overlays out of an LVM. My question really is whether libvirt can use/manipulate native LVM snapshots these days.

2 1

Nested KVM help
by James Slagle 20 Aug '13

20 Aug '13

Hi, When I try to use nested KVM with Fedora 19, I'm experiencing a hang of the L1 vm. I eventually have to do a "Force Off" from virt-manager on L0 since the L1 vm is completely unresponsive. Both my L0 and L1 are F19, x86_64. L2 doesn't really seem to matter as I can't even get the guest to start before L1 completely locks up. Even just attempting to define a L2 guest that uses kvm virtualization locks up L1 completely. Here are some more details. On L0 (i've rebooted L0 after enabling the nested parameter): [root@dublin ~]# uname -a Linux dublin 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@dublin ~]# cat /sys/module/kvm_intel/parameters/nested Y [root@dublin ~]# rpm -q libvirt libvirt-1.0.5.5-1.fc19.x86_64 [root@dublin ~]# lsmod | grep kvm kvm_intel 138528 3 kvm 422809 1 kvm_intel cpu section of libvirt xml for L1 vm: <cpu mode='custom' match='exact'> <model fallback='allow'>Nehalem</model> <feature policy='require' name='vmx'/> </cpu> On L1: [root@localhost jslagle]# uname -a Linux localhost.localdomain 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@localhost jslagle]# rpm -q libvirt libvirt-1.0.5.5-1.fc19.x86_64 [root@localhost jslagle]# lsmod | grep kvm kvm_intel 138528 0 kvm 422809 1 kvm_intel I've looked in dmesg output, /var/log/messages, and libvirt logs on both L0 and L1 and can't see any errors. Any ideas on how to debug this further? Let me know if should file a bugzilla, I wasn't sure I had enough to go on to go ahead and do that yet. Thanks for any help. -- -- James Slagle --

6 9

KVM bridge wonkiness in Fedora19
by Lonni J Friedman 07 Aug '13

07 Aug '13

Greetings, I'm attempting to get several virtual machines setup on a Fedora19 host system, with the traditional bridge network devices (br0, br1, etc). I've done this many times before with older versions of Fedora (16, 14, etc), and it just works. However, for reasons that I cannot figure out, the bridge doesn't seem to be working in Fedora19. While I can successfully connect to the outside world (local network + internet) from inside a VM, nothing can communicate with the VM from outside (local network). I'm referring to something as trivial as pinging. From inside the VM, I can ping anything successfully (0% packet loss). However, from outside the VM (on the host, or any other system on the same network), I see 100% packet loss when pinging the IP address of the VM. My first question is simply, does anyone else have this working successfully in F19? And if so, what steps did you need to follow? I'm not using NetworkManager at all, its all the network service. There are no firewalls involved anywhere (iptables & firewall services are currently disabled). Here's the current host configuration: # brctl show bridge name bridge id STP enabled interfaces br0 8000.38eaa792efe5 no em2 vnet1 br1 8000.38eaa792efe6 no em3 br2 8000.38eaa792efe7 no em4 vnet0 virbr0 8000.525400db3ebf yes virbr0-nic # more /etc/sysconfig/network-scripts/ifcfg-em2 TYPE=Ethernet BRIDGE="br0" NAME=em2 DEVICE="em2" UUID=aeaa839e-c89c-4d6e-9daa-79b6a1b919bd ONBOOT=yes HWADDR=38:EA:A7:92:EF:E5 NM_CONTROLLED="no" # more /etc/sysconfig/network-scripts/ifcfg-br0 TYPE=Bridge NM_CONTROLLED="no" BOOTPROTO=dhcp NAME=br0 DEVICE="br0" ONBOOT=yes # ifconfig em2 ;ifconfig br0 em2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::3aea:a7ff:fe92:efe5 prefixlen 64 scopeid 0x20<link> ether 38:ea:a7:92:ef:e5 txqueuelen 1000 (Ethernet) RX packets 100093 bytes 52354831 (49.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 25321 bytes 15791341 (15.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xf7d00000-f7e00000 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.31.99.226 netmask 255.255.252.0 broadcast 10.31.99.255 inet6 fe80::3aea:a7ff:fe92:efe5 prefixlen 64 scopeid 0x20<link> ether 38:ea:a7:92:ef:e5 txqueuelen 0 (Ethernet) RX packets 19619 bytes 1963328 (1.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11 bytes 1074 (1.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Relevant section from /etc/libvirt/qemu/foo.xml (one of the VMs with this problem): <interface type='bridge'> <mac address='52:54:00:26:22:9d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> I can provide additional information, if requested. thanks!

4 5

Re: [fedora-virt] [virt-tools-list] Missing networks & Virt-Manager
by Jorge Fábregas 05 Aug '13

05 Aug '13

On 08/05/2013 05:22 PM, Cole Robinson wrote: > Okay, I was a bit confused before since you mentioned restarting the host. But > the above makes more sense. virt-manager only refreshes the forward device > list in that wizard when it is first run, we should be at least doing it every > time the wizard is launched. I've fixed that upstream now but it likely won't > ever trickle into RHEL6 FWIW. There you go. Thanks for fixing it upstream. I'm really looking forward to Fedora 20 ... and specially the upcoming snapshot functionality :) Regards, Jorge

1 0

Fedora virt status July 2013
by Cole Robinson 01 Aug '13

01 Aug '13

Hi all, here are some Fedora virt status bits for July. Fedora 20 ========= The 'Change' submission deadline came and went, and 3 virt changes were accepted: https://fedoraproject.org/wiki/Changes/Virt_ACLs https://fedoraproject.org/wiki/Changes/Virt_Manager_Snapshots https://fedoraproject.org/wiki/Changes/Virt_ARM_on_x86 Here's the remaining schedule: https://fedoraproject.org/wiki/Releases/20/Schedule Aug 06: Change freeze, must be functional Aug 20: Alpha deadline Sep 03: Alpha release Sep 24: Beta deadline Oct 08: Beta release Nov 12: GA release The change freeze next week is also when F20 branches off from rawhide, so F20 will start to get some differentiation. Fedora 17 EOL ============= Fedora 17 is End-of-Life now, which means no more updates are being shipped. If you're still on Fedora 17, now's a good time make the jump to F19! libvirt 1.1.0 and 1.1.1 ======================= Two libvirt releases this month: 1.1.0 on July 1st 2013 and 1.1.1 on July 30th 2013. Highlights: 1.1.0: * Extensible migration APIs (Jiri Denemark) * Add a policy kit access control driver (Daniel P. Berrange) * various improvements in the Xen driver (Jim Fehlig and Marek Marczykowski-Górecki) * improve networking support on BSD (Roman Bogorodskiy) * agent based vCPU hotplug support (Peter Krempa) 1.1.1: * Adding device removal or deletion events (Jiri Denemark), * Introduce new domain create APIs to pass pre-opened FDs to LXC (Daniel P. Berrange), * Add interface versions for Xen 4.3 (Stefan Bader), * Add new public API virDomainSetMemoryStatsPeriod (John Ferlan), * Various LXC improvements (Daniel P. Berrange and Gao feng) seabios 1.7.3 ============= seabios 1.7.3 was released on July 7th and is currently in rawhide and virt-preview. - Initial support for using SeaBIOS as a UEFI CSM - Support for detecting and using ACPI reboot ports. - Non-standard floppy sizes now work again with recent QEMU versions. - Several bug fixes and code cleanups Bug stats ========= Bug count on Jul 1 2013 : 266 Bug count on Aug 1 2013 : 218 Quite the substantial drop this month, but that's largely due to the F17 EOL mass closings, and some housekeeping keeping throughout the month in anticipation of the mass closing. By release: * Fedora 18 : 86 * Fedora 19 : 102 * Fedora rawhide : 30 By package: * gnome-boxes : 33 * ipxe : 2 * libguestfs : 8 * libosinfo : 7 * libvirt : 38 * libvirt-sandbox : 21 * netcf : 7 * qemu : 34 * seabios : 1 * spice-gtk : 2 * spice-vdagent : 1 * usbredir : 1 * virt-dmesg : 1 * virt-manager : 29 * virt-viewer : 7 * virt-what : 3 * virtio-win : 3 * xen : 4 * xorg-x11-drv-cirrus: 4 * xorg-x11-drv-qxl : 12 By status: * ASSIGNED : 18 * MODIFIED : 2 * NEW : 188 * POST : 10 Bugs of note ============ https://bugzilla.redhat.com/show_bug.cgi?id=980254 Host crash when shutting down KVM VMs A bad patch for 880035 was causing pretty reliable host crashes when shutting down VMs. At least F18 and F19 were affected. - Cole

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt August 2013