virt

virt@lists.centos.org

1608 discussions

XEN ISO ?
by Günther J. Niederwimmer 07 Jul '16

07 Jul '16

Hello, I have to install on a older server CentOS 7.2 with XEN. I search and cant found a stable repo for this. Can any give me a hint for this Problem? Thanks for a answer, -- mit freundlichen Grüßen / best regards, Günther J. Niederwimmer

2 1

PCI Passthrough not working
by Francis Greaves 04 Jul '16

04 Jul '16

I am having trouble getting PCI Passthrough to work from Dom0 running CentOS 7 to DomU runnning Debian 8 I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64 on a Dell Poweredge T430. I think I have set it all up correctly, but I see no message when putting a USB device into any of the USB slots on the DomU There are three other DomUs running, but I have no need of PCI Passthrough set up for them. kernel command line on Dom0 from /etc/default/grub GRUB_CMDLINE_LINUX="crashkernel=auto intremap=no_x2apic_optout" GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=13312M,max:14336M dom0_max_vcpus=6 dom0_vcpus_pin xen-pciback.passthrough=1 irqpoll GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen" lspci on Dom0 filtered for USB 00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05) 00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05) lsmod on Dom0 filtered for xen xenfs 12978 1 xen_privcmd 13243 12 xenfs xen_pciback 52127 0 xen_netback 45777 6 xen_blkback 31807 0 xen_gntalloc 13144 0 xen_gntdev 17468 2 xen_evtchn 13033 5 config file for DomU ============================================================== # Kernel command line options extra = "root=/dev/xvda1 swiotlb=force" memory = 2048 vcpus = 2 vif = ['mac=00:16:3E:00:00:35, bridge=xenbr5', 'mac=00:16:3E:00:00:36, bridge=xenbr6'] disk = ['phy:/dev/xen_vg/metsat_disk,xvda,w', 'phy:/dev/xen_vg/metsat_swap,xvdb,w', 'phy:/dev/xen_vg/metsat_receive,xvdc,w'] pci=['00:1a.0,rdm_policy=relaxed,permissive=1,seize=1'] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' # Run section ============================================================== bootloader = "/usr/lib/xen/bin/pygrub" ============================================================== In the Dom0 I get this when booting the DomU, even with irqpoll in the DomU kernel line xen_pciback: xen-pciback[0000:00:1a.0] IRQ line is not shared with other domains. Turning ISR off Jul 03 11:31:23 myDom0.mynetwork.net kernel: irq 18: nobody cared (try booting with the "irqpoll" option) Jul 03 11:31:23 myDom0.mynetwork.net kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.34-20.el7.x86_64 #1 Jul 03 11:31:23 myDom0.mynetwork.net kernel: Hardware name: Dell Inc. PowerEdge T430/0975F3, BIOS 1.5.4 10/05/2015 Jul 03 11:31:23 myDom0.mynetwork.net kernel: 0000000000000000 ffff8803bc603d88 ffffffff81653783 ffff8803b223e400 Jul 03 11:31:23 myDom0.mynetwork.net kernel: ffff8803b223e48c ffff8803bc603db8 ffffffff810c6776 ffff8803bc613340 Jul 03 11:31:23 myDom0.mynetwork.net kernel: ffff8803b223e400 0000000000000012 0000000000000000 ffff8803bc603e08 Jul 03 11:31:23 myDom0.mynetwork.net kernel: Call Trace: Jul 03 11:31:23 myDom0.mynetwork.net kernel: <IRQ> [<ffffffff81653783>] dump_stack+0x64/0x82 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810c6776>] __report_bad_irq+0x36/0xd0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810c6c86>] note_interrupt+0x226/0x270 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff813e71cc>] ? add_interrupt_randomness+0x3c/0x1f0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810c43ec>] handle_irq_event_percpu+0xcc/0x1e0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810c453b>] handle_irq_event+0x3b/0x60 Message from syslogd@myDom0 at Jul 3 11:31:23 ... kernelisabling IRQ #18 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810c709a>] handle_fasteoi_irq+0x7a/0x130 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810c394b>] generic_handle_irq+0x2b/0x40 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff813a2102>] evtchn_fifo_handle_events+0x162/0x170 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8139efb0>] __xen_evtchn_do_upcall+0x50/0x90 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff813a0d67>] xen_evtchn_do_upcall+0x37/0x50 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8165c05e>] xen_do_hypervisor_callback+0x1e/0x40 Jul 03 11:31:23 myDom0.mynetwork.net kernel: <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8100b330>] ? xen_safe_halt+0x10/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8101ea94>] ? default_idle+0x24/0xf0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8101f49f>] ? arch_cpu_idle+0xf/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810adc92>] ? cpu_startup_entry+0x312/0x3e0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff816445c7>] ? rest_init+0x77/0x80 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d77130>] ? start_kernel+0x4d0/0x4dd Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d76a50>] ? set_init_arg+0x55/0x55 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d765ee>] ? x86_64_start_reservations+0x2a/0x2c Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d7a7cc>] ? xen_start_kernel+0x5a9/0x5b5 Jul 03 11:31:23 myDom0.mynetwork.net kernel: handlers: Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff814b0f50>] usb_hcd_irq Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffffa050d3e0>] xen_pcibk_guest_interrupt [xen_pciback] Jul 03 11:31:23 myDom0.mynetwork.net kernel: Disabling IRQ #18 ========================================================================= on the DomU 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 dmesg | grep usb [ 3.190569] usbcore: registered new interface driver usbfs [ 3.190584] usbcore: registered new interface driver hub [ 3.190606] usbcore: registered new device driver usb [ 3.220057] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.220062] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.220067] usb usb1: Product: EHCI Host Controller [ 3.220070] usb usb1: Manufacturer: Linux 3.2.0-4-686-pae ehci_hcd [ 3.220073] usb usb1: SerialNumber: 0000:00:00.0 [ 3.532049] usb 1-1: new high-speed USB device number 2 using ehci_hcd [ 19.088071] usb 1-1: device not accepting address 2, error -110 [ 19.200069] usb 1-1: new high-speed USB device number 3 using ehci_hcd [ 34.756077] usb 1-1: device not accepting address 3, error -110 [ 34.868111] usb 1-1: new high-speed USB device number 4 using ehci_hcd [ 45.300055] usb 1-1: device not accepting address 4, error -110 [ 45.412076] usb 1-1: new high-speed USB device number 5 using ehci_hcd [ 55.844113] usb 1-1: device not accepting address 5, error -110 lsmod | grep xen xen_pcifront 17330 0 xen_blkfront 17198 6 xen_netfront 21736 0 ----------------------------------------------------------------------------------------- Does anyone have any ideas about this? Many thanks Francis

1 0

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

Xen4CentOS 6 64bit - domUs don't shutdown on dom0 after "yum upgrade" to 4.6.1
by exvito here 25 May '16

25 May '16

Hello all, I'm addressing the mailing list following the suggestion of gwd on #centos-virt @freenode IRC. The subject says most of it. Here are the details : - Was running 4.4.x and configured such that /etc/xen/auto domUs would be saved/restored on dom0 shutdown/bootup. - Installation was based on "centos-release-xen" such that "yum upgrade" brough Xen to 4.6.1. After upgrade observed behavior: - dom0 boot starts up the domUs in /etc/xen/auto. - dom0 shutdown does not save/shutdown domUs (the command is "shutdown -h now" via ssh). Diagnostics: - Running /etc/init.d/xendomains stop/start does the right thing. - chkconfig --list shows "xendomains 0:off 1:off 2:on 3:on 4:on 5:on 6:off" which looks nice. - The rc link is in place: /etc/rc.d/rc0.d/K00xendomains -> ../init.d/xendomains - Edited /etc/init.d/xendomains such that the lines: start) $LIBEXEC_BIN/xendomains start ;; stop) $LIBEXEC_BIN/xendomains stop ;; become (added "2>&1 | tee FILE" to the underlying start/stop command) start) $LIBEXEC_BIN/xendomains start 2>&1 | /usr/bin/tee -a /tmp/xd-start.log ;; stop) $LIBEXEC_BIN/xendomains stop 2>&1 | /usr/bin/tee -a /tmp/xd-stop.log ;; - The /tmp/xd-stop.log file is not created on dom0 shutdown (make sense, but why?!). - The /tmp/xd-stop.log is created on dom0 boot, as expected. - Both files are created on manual /etc/init.d/xendomains start/stop - Manually added an rc link: /etc/rc.d/rc0.d/K01xendomains -> ../init.d/xendomains - The behavior remains unchanged. This is looking much more of an upstart/sysvinit issue that a Xen 4.6 issue. However, I believe others may have been through this experience. Can anyone provide any pointers in further diagnosing this? Thanks in advance. Regards, -- exvito

2 6

oVirt 3.6.6 packages available for testing
by Rafael Martins 24 May '16

24 May '16

Hi, We have just finished building packages for oVirt 3.6.6 release in Virt SIG. They are tagged virt7-ovirt-36-testing. Please help us testing this release and submitting feedback! Thanks, Rafael Martins

1 0

kvm: centos 7 guest on centos 6 host network problems
by Matthias Leopold 23 May '16

23 May '16

Hi, i'm rather new to kvm. now i set up a centos 7 guest on a centos 6 kvm host. when i try to use bridged networking in the centos7 guest this works for the interface that uses eth1/br1 on the host. when i try to use a second interface in the guest with eth0/br0 on the host this brings the host interface down as soon as i do ip configuration in the guest (so it seems). eth0 shall have the default route in host and guest. three other centos 6 guests (not set up by me) use both interfaces in bridged mode with no problems. both interfaces on the host are intel cards (e1000e). driver in the kvm guest configuration is "virtio". dmesg on the kvm host (centos 6) says: device vnet9 entered promiscuous mode br0: port 5(vnet9) entering forwarding state device vnet10 entered promiscuous mode br1: port 5(vnet10) entering forwarding state vnet10: no IPv6 routers present vnet9: no IPv6 routers present kvm: 17778: cpu0 disabled perfctr wrmsr: 0xc2 data 0xffff e1000e: eth0 NIC Link is Down ... ethtool -k output differs in "rx-vlan-filter" (off for eth0) centos 6 kernel is 2.6.32-573.22.1.el6.x86_64 what could be wrong? thx matthias

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt