virt February 2014

virt@lists.centos.org

18 participants
10 discussions

MS-Win7 kvm guest gets dhcp from host bridge
by James B. Byrne 23 Jun '14

23 Jun '14

CentOS-6.5 i86_64 qemu-kvm-0.12.1.2-2.415.el6_5.4 MS-Windows v7proSP1 We have installed a MicroSoft Win7 system as a guest and have joined it to our MS AD domain. The system runs and has internet access. However, the IPv4 address it obtains and the gateway it is assigned are both sourced from the virtual machine host system and not from our AD DC DHCP server. To clarify, the virbr0 IP address is 192.168.122.1 and the Windows guest has that address as its gateway and an IP address in the 192.168.122.0/24 netblock. This is not as we desire as the internal addresses we regularly assign to MS workstations via DHCP are supposed to belong to a different netblock entirely. This permit filtering on incoming and outgoing traffic at the gateway. I realize that there is a DHCP service running on virbr0 for the purpose of provisioning guests with system control traffic but I do not know how to limit that to its intended purpose and allow another DHCP server to provide the IP address to the windows guests. I hope that problem description is not too confusing. Can anyone provide me with some guidance on the matter? Are kvm guests required to have either static ip addresses or dhcp addresses provided by the host system? Thanks in advance. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

4 3

Xen Security patching
by Chris Elliott 07 Jun '14

07 Jun '14

Hi Guys When is the next update of Hypervisor packages going to be released? There appears to be no changes to the main hypervisor RPMs since September (Even in the BETA / RC1 tree) and there are 5+ Xen Security Advisories with patches which need to be added. "Security issues are handled and released in sync with public disclosure upstream with zero lag" I can rebuild my own, but that's not really the point. In other news I've been doing some testing of the 3.10 kernel and so far so good! Thanks - Chris

3 7

AWS Images updated for new instance types
by Karanbir Singh 22 Apr '14

22 Apr '14

hi, · CentOS 6.3 (x86_64) – Release Media: https://aws.amazon.com/marketplace/pp/B00A6L6F9I · CentOS 6.4 (x86_64) – Release Media: https://aws.amazon.com/marketplace/pp/B00DGYP804 are now marked for and updated to run with the m3 and c3 instance types. I'm still working with the amazon crew to get the 6.5 images online and an automated pipeline proposed ( hopefully, also adopted ) to get this image injection speeded up in the future. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 6

Xen updates / TODO
by Pasi Kärkkäinen 25 Mar '14

25 Mar '14

Hello, A couple of TODO items/suggestions: 1) Xen 4.2.4 was just released: http://lists.xen.org/archives/html/xen-devel/2014-02/msg01624.html I think we should first update Xen4Centos6 rpms to Xen 4.2.4 to have a "known good" release from the stable branch currently in use in Xen4Centos6. 2) After that, we should start packaging/testing Xen 4.3.2: http://lists.xen.org/archives/html/xen-devel/2014-02/msg01622.html Xen 4.3 brings much improved XL toolstack in addition to a lot of other changes/fixes. 3) After updating to Xen 4.3.2 rpms start troubleshooting/debugging the libvirt libxl driver and get it working with Xen4Centos6 system.. How does that sound like? :) -- Pasi

6 34

Problems with Windows on KVM machine
by engineer＠colocat.ru 20 Mar '14

20 Mar '14

Hello. We've started a virtualisation project and got stuck in one moment. Currently we are using the following: Intel 2312WPQJR as a node Intel R2312GL4GS as a storage with Intel Infiniband 2 ports controller Infiniband Mellanox SwitchX IS5023 for commutation. The nodes run CentOS 6.5 with built-in Infiniband package (Linux v0002 2.6.32-431.el6.x86_64), the storage - CentOS 6.4 also built-in drivers (Linux stor1.colocat.ru 2.6.32-279.el6.x86_64). On the storage is made an array, that is shown in system as /storage/s01. Then it is exported via NFS. The nodes connect to NFS by: /bin/mount -t nfs -o rdma,port=20049,rw,hard,timeo=600,retrans=5,async,nfsvers=3,intr 192.168.1.1:/storage/s01 /home/storage/sata/01 mount shows: 192.168.1.1:/storage/s01 on /home/storage/sata/01 type nfs (rw,rdma,port=20049,hard,timeo=600,retrans=5,nfsvers=3,intr,addr=192.168.1.1) Then we create a virtual machine with virsh with a disk bus virtio. All is OK, until we don't start Windows on KVM. It may work for 2 hours or 2 days, but under heavy load it hangs the mount (i.e. /sata/02 and 03 are accessible, but requesting 01 will result in a total hang of console). This can be beaten only by hardware reset of the node. If we mount without rdma - all is fine. What can we do in such case? If any debugs or info needed - please ask. Best regards, Nikolay.

3 8

Xen4CentOS issue with running xen domains and a restart
by Johnny Hughes 25 Feb '14

25 Feb '14

There is an error in libvirt when rebooting or shutting down with a running xen domain on Xen4Centos6 When libvirtd tries to shutdown, it tries to suspend the running machine and fails with: VirDomainManagedSave error: this function is not supported by the connection driver Does anyone know how to patch libvirt 0.10.2.x to work around this issue.

1 0

disk io in guests causes soft lockups in guests and host processes
by Dennis Jacobfeuerborn 20 Feb '14

20 Feb '14

Hi, I have a strange phenomenon that I cannot readily explain so I wonder if anyone here can shed a light on this. The host system is a Dell r815 with 64 cores and 256G ram and has centos 6 installed. The five guests are also running centos 6 and are running as a hadoop cluster. The problem is that I see disk-io spikes in the vm's which then cause soft lockups in the guest but I also see hanging processes on the host as if the entire machine locks up for 30-60 seconds. Now I know that having all cluster members running on the same system isn't efficient and that I cannot expect good performance but what I was not expecting is that a guest make host processes hang. Does anyone have an idea what the issue could be here or how I can find out what cause for this behavior is? Regards, Dennis

3 2

Problem with cdrom device on guest
by James B. Byrne 13 Feb '14

13 Feb '14

I have a kvm guest running MS-WinV7 on a CentOS-6.5 host. The WinV7 guest was installed from a CD. It installed correctly and was updated and added to an MS Active Domain without difficulty. I was able to do work on it through the virt-manager console and I was able to shut the system down from the console without problem. I cannot get it to restart however. virsh start brws-ms-v7-37v.brockley.harte-lyne.ca error: Failed to start domain brws-ms-v7-37v.brockley.harte-lyne.ca error: cannot open file '/dev/sr0': No medium found I found this bugzilla report. https://bugzilla.redhat.com/show_bug.cgi?id=709585 Which is curiously marked as CLOSED DEFERRED. The last comment in that bug contains this: > Summary of findings so far: > > format=raw doesn't work with /dev/sr0. Omitting format=raw works. > format=host_device works. > > Apparently, virt-manager specifically asks for "raw". > > Things are different in RHEL-6: format=raw works, > format=host_device doesn't, format=host_cdrom does > (doesn't exist in RHEL-5). Now, in my configuration files there is no 'format' attribute found in any tag. I find 'type=raw' inside of many <device/> tags but it seems strange to me that a RedHat bug report would use such imprecise language so as to confuse the attribute 'type' with one named 'format' so I wonder if a syntax change has occurred and if that has introduced a regression? virsh edit brws-ms-v7-37v.brockley.harte-lyne.ca show this configuration entry for device sr0: 30 <disk type='block' device='cdrom'> 31 <driver name='qemu' type='raw'/> 32 <source dev='/dev/sr0'/> 33 <target dev='hdc' bus='ide'/> 34 <readonly/> 35 <address type='drive' controller='0' bus='1' target='0' unit='0'/> 36 </disk> Despite the inference I draw from the bug report, that format ~= type, one cannot in fact change the driver attribute 'type' to any value other than raw. Any attempt to do so results in this message: unsupported configuration: unknown driver format value 'host_cdrom' Failed. Try again? [y,n,f,?]: Further, the value 'f' is not permitted so one cannot forcibly save the configuration to determine if in fact it might work. Has anyone else run into this? What is the fix? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

documentation of snapshots
by Bill Campbell 06 Feb '14

06 Feb '14

I am looking for documentation on handling snapshots. The main tasks are: 1. Create a snapshot 2. Roll back a snapshot 3. Merge the snapshot into the base to start the cycle over. Currently I've done steps 1 and 2 into a single qcow2 image. I'm running a relatively old version of libvirtd on CentOS 5, libvirt-0.8.2-29.el5_9.1. Thanks. Bill -- INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax: (206) 232-9186 Skype: jwccsllc (206) 855-5792 The question is, why are politicians so eager to be president? What is it about the job that makes it worth revealing, on national television, that you have the ethical standards of a slime-coated piece of industrial waste? -- Dave Barry, "On Presidential Politics"

1 0

Problem with lvm disks assigned to kvm guests
by C. L. Martinez 06 Feb '14

06 Feb '14

Hi all, I have a strange problem when I use lvm disks to expose to virtual guests (host is CentOS 6.5 x86_64). If I remove a kvm guest and all lvm disks attached to it, and I create a new kvm with another lvm disks that use the same disk space previously assigned to the previous kvm guest, this new guest sees all partitions and data. Creating new lvm volumes with different names to this new kvm doesn't resolves the problem. Any idea why?? Thanks.

6 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt February 2014