virt June 2016

virt@lists.centos.org

8 participants
6 discussions

Cannot allocate Memory
by Shaun Reitan 25 Jul '16

25 Jul '16

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to update the host to latest Xen 4.4 now hoping this is a old bug. Here's from xen logs [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:105) XendDomainInfo.create(['vm', ['name', 'xxx'], ['memory', 2048], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 2], ['oos', 1], ['image', ['linux', ['kernel', '/kernels/vmlinux-2.6.18.8-4'], ['videoram', 4], ['args', 'root=/dev/xvda ro xencons=tty console=tty1 '], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd', ['uname', 'phy:vg/fs_6818'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:vg/fs_6819'], ['dev', 'xvdb'], ['mode', 'w']]], ['device', ['vif', ['rate', '40mb/s'], ['mac', 'FE:FD:48:01:F1:E7']]]]) [2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:2504) XendDomainInfo.constructDomain [2016-06-22 09:13:50 1958] DEBUG (balloon:187) Balloon: 7602632 KiB free; need 16384; done. [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:2566) (12, 'Cannot allocate memory') Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2561, in _constructDomain target = self.info.target()) Error: (12, 'Cannot allocate memory') [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:490) VM start failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2572, in _constructDomain raise VmError(failmsg) VmError: Creating domain failed: name=xxx [2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:110) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 108, in create vm.start() File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(0, 30, self._constructDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2572, in _constructDomain raise VmError(failmsg) VmError: Creating domain failed: name=xxx -- Shaun

3 5

PCI Passthrough not working
by Francis Greaves 04 Jul '16

04 Jul '16

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the May Emails: pci=['00:1a.0,rdm_policy=relaxed'] and in the DomU, which starts fine, I get the following information: lspci 00:00.0 USB controller: Intel Corporation Wellsburg USB Enhanced Host Controller #2 (rev 05) lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub However when I plug in a device to this USB port (Am sure it is the correct port in the Dom0) I see nothing in the DomU at all. What can I do now? Many thanks Francis

2 7

[Virt SIG] status of virt7-docker repository?
by Haïkel 22 Jun '16

22 Jun '16

Hi, I'm considering to add virt7-docker repository as a dependency for the openstack repo from Cloud SIG. It seems that it's not consumable yet and some packages like Kubernetes are outdated. Could you update me with the current status and if there is anything we can do to help? Regards, H.

1 0

Re: [CentOS-virt] [CentOS-devel] docker and docker-latest packages on CentOS Virt SIG
by Lokesh Mandvekar 13 Jun '16

13 Jun '16

Moving this discussion to centos-virt@ as it's upto the SIG to decide on how this moves ahead. I'm hoping to have 2 new koji tag sets: virt7-docker-fedora-* (will have fedora rpms rebuilt) virt7-docker-el-* (will have rhel candidate builds before they are released or land in centos extras) The -el-* repos will help to have Virt SIG as sort of an upstream and early QA for both RHEL and CentOS extras. If the SIG is ok with it, I'll check with CBS guys to create these 2 tags. See below message to centos-devel@ and http://centos-devel.1051824.n5.nabble.com/CentOS-devel-docker-and-docker-la… for background ----- Forwarded message from Lokesh Mandvekar <lsm5(a)fedoraproject.org> ----- > I could potentially build both upcoming RHEL and Fedora rpms for Virt. > > We could have koji tag separation like: > > virt7-docker-rhel-* > virt7-docker-fedora-* > > and maybe then deprecate the virt7-docker-common-* in favor of the two > above?? That could ensure clear separation between the 2 versions. > > Enabling both rhel and fedora repos and then upgrading docker from the fedora > repo with a docker-latest pre-installed can and will give you nightmares, but as > a close friend always says, "We'll cross that bridge..." > > wdyt? > Thanks, -- Lokesh Freenode: lsm5 GPG: 0xC7C3A0DD

3 4

Xen 4.7rc4 packages available for testing
by George Dunlap 07 Jun '16

07 Jun '16

As per our policy, the next officially supported Virt SIG Xen version will be 4.8. However, with 4.7 coming soon, I've ported the patchqueue over to 4.7rc4 and given it a spin. If you want to help testing for the upstream 4.7 release, do give it a spin and report any regressions. Please note that this version WILL NOT SUPPORTED. 4.6 is still the officially-supported version until 4.8 comes out (probably in around 6 month's time). Thanks, -George

1 0

[x-post] Upstream possible patches to libvirt to enable building upstream libvirt packages with libxl
by Le Nucksi 06 Jun '16

06 Jun '16

On 05/14/2016 07:16 AM, Le Nucksi wrote: > Hello list, > > is there a way to get more recent libvirt builds for CentOS 7 that include > support for the xl (modern Xen) toolstack? > > I tried to build libvirt from the SRPM, which succeeded, however, without > the mentioned Xen parts. > I have also found two repos from people who provide upstream libvirt builds > for CentOS 7, again, without the Xen parts. > - https://copr.fedorainfracloud.org/coprs/jmliger/virt7-upstream/ and > - https://build.opensuse.org/package/show/home:aevseev/libvirt > > Within the CentOS virtualization SIG builds for Xen there is a 1.3.x build > of libvirt that includes support for the modern Xen toolstack. > Would it be possible to inline this into the upstream to enable building it > with Xen features on CentOS 7 such that the aforementioned people's RPMs > would contain it? > > I appreciate any enlightment on the topic. I think you should either contact the owners of those libvirt repos, or contact the centos virt sig. I don't know if anyone on these lists is directly involved with those repos - Cole Hello list, I emailed the libvirt-users list to see if there would be a way to get more recent libvirt builds into my CentOS 7 + VIRT SIG/Xen packages. Here's what Cole Robinson from RedHat replied on that matter. Also the initial email. I'd appreciate your feedback on this. The more recent libvirt builds appear to include quite some improvements especially for the libxl parts. Best regards, Le

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt June 2016