virt

virt@lists.centos.org

2 participants
1612 discussions

optimal windows xml config for xen
by Christoph 14 Apr '17

14 Apr '17

Hi I use this config to start win7 64bit via virsh: <domain type='xen' id='21'> <name>marax</name> <uuid>6df7f16c-50e1-4541-b5b1-a91ff675a7c2</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>8</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib64/xen/boot/hvmloader</loader> <boot dev='cdrom'/> </os> <features> <acpi/> <apic/> <pae/> <viridian/> </features> <clock offset='variable' adjustment='0' basis='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <disk type='block' device='disk'> <driver name='phy'/> <source dev='/dev/vg_lilith/lv_marax_c'/> <backingStore/> <target dev='hda'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='disk'> <driver name='phy'/> <source dev='/dev/vg_lilith/lv_marax_d'/> <backingStore/> <target dev='hdb'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='ide' index='0'/> <interface type='bridge'> <mac address='00:16:3e:05:01:10'/> <source bridge='xenbr5'/> <script path='vif-bridge'/> <model type='e1000'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='spice' port='6000' autoport='no' keymap='de'/> <video> <model type='xen' vram='16384' heads='1'/> </video> </devices> </domain> it is optimal for win7? does someone see any options what I could make better? -- ---------- Greetz Christoph

1 0

Pair-bonding on virtualized servers, particularly on CentOS 7
by Nico Kadel-Garcia 14 Apr '17

14 Apr '17

Is anyone out there using pair-bonding on CentOS 7? I'm particularly looking at systems where one VM network port is tied to one bridge, tied to one port on the hypervisor, and one network port on the VM tied to t he other bridge tied to th e other port on the hypervisor, for failover in a VM that can be exposed directly to the local network. I'm also dealing with pair bonding of they hypervisor, even if the VM's are NAT'ed, and wonder if anyone wants to share testing confgs and notes for CentOS 7. I published notes on KVM bridging, pair bonding, and even tagged VLAN's for CentOS 5 and 6 years ago, but CentOS 7 has proven to be trickier, and I'm wondering if anyone else doing virtualization has spent cycles on this. I think I've gotten the setup on the hypervisor automated, but don't have much space or time to run tests. I'm happy to share tools and access to tools under an open source license.

1 0

Centos 6.9 AWS Images and c4-8xlarge
by John Peacock 14 Apr '17

14 Apr '17

I asked back in September: https://lists.centos.org/pipermail/centos-virt/2016-September/005219.html and again in November: https://lists.centos.org/pipermail/centos-virt/2016-November/005257.html about getting c4.8xlarge enabled for the official image in AWS Marketplace: https://aws.amazon.com/marketplace/pp/B00NQAYLWO?ref=cns_srchrow Now that the 6.9 release is coming, it would be nice to have that last checkbox enabled. We want to be able to usethe 10G networking that c4.8xlarge instances provide and we want to base all of our images directly on the official Centos6 release AMI. Please advise if there is anything I can do to assist in this effort. Thanks John Peacock

4 4

unable to execute QEMU command 'migrate': this feature or command is not currently supported
by Valentin Guggiana 11 Apr '17

11 Apr '17

Hi all I'm trying to do a live migration with non-shared storage on CentOS 7. It was working well doing it from CentOS 6 to CentOS 7 but not between to CentOS 7 machines. I read that this feature was removed in RHEL/CentOS 7 but should be available in the CentOS-QEMU-EV repository. But I still get the error using qemu-kvm-ev: error: internal error: unable to execute QEMU command 'migrate': this feature or command is not currently supported My installed libvirt and qemu packets are: libvirt-2.0.0-10.el7_3.5.x86_64 libvirt-client-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64 libvirt-glib-0.2.3-1.el7.x86_64 libvirt-python-2.0.0-2.el7.x86_64 qemu-img-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-common-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-tools-ev-2.6.0-28.el7_3.6.1.x86_64 My command is: virsh migrate --live --copy-storage-all --persistent --undefinesource --tunnelled --p2p --verbose --xml server.xml server qemu+ssh://xxx@a.b.c.d/system Any help would be greatly appreciated. Thanks, Valentin

3 5

Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
by PJ Welsh 07 Apr '17

07 Apr '17

Updating my CentOS 6.8 Xen server with new 4.9.13 kernel yields a kernel boot message of a few like "APIC ID MISMATCH" and the system reboots immediately without any other bits of info. This is on a Dell R710 with 64GB RAM and 2x 6-core Intel CPU's. As an additional test, I installed and attempted to run the current "testing" kernel of 4.9.16 with the exact same results. Anyone have an idea? The 3.18.x series runs without issue of course. Thanks PJ

8 23

Clocksource boot issues 4.9.13
by Chris Elliott 07 Apr '17

07 Apr '17

Hi all I’ve got a few Intel Z87 chipset machines with Adaptec 5405 raid cards (latest firmware), they work fine on 3.18 but during Dom0 boot using kernel 4.9.13 it hangs at “Using clocksource tsc” and the aacraid driver keeps trying to reset Has anyone seen anything like this? I’ve tried specifying clocksource=xen in grub instead of the default of tsc, and that has the same issue. HPET is enabled and Xen is seeing it: (XEN) ACPI: HPET D9649CB0, 0038 (r1 ALASKA A M I 1072009 AMI. 5) (XEN) Platform timer is 14.318MHz HPET Thanks Chris

4 4

Network isolation for KVM guests
by C. L. Martinez 04 Apr '17

04 Apr '17

Hi all, What options exists under CentOS hosts to work with isolated networks?. For example, on BSD systems it is really trivial. In FreeBSD you can use setfib tools and on OpenBSD it is possible to use rdomain options. In 30 secs it is possible to work with isolated networks and assign process, ip address and routes (hidden from the main route table and ip addresses), etc. But I can't find a similar solution for CentOS environments. I have found two similar options: a/ Network namespaces (but doesn't provides a real network isolation) b/ VRF (but it is supported only for kernels 4.8 and up) Any ideas? Thanks. -- Greetings, C. L. Martinez

6 12

Xen 4.6.3-9 release
by Brandon Shoemaker 03 Apr '17

03 Apr '17

Hi list, Xen 4.6.3-9 will be general release soon?

2 2

2.6.0-28.el7_3.6.1 e1000 problem
by Dmitry Melekhov 31 Mar '17

31 Mar '17

Hello! We tried to move Windows 2003 VM with e1000 driver from Centos 7 which runs qemu-kvm-0.12.1.2-2.491.el6_8.7.x86_64 to Centos 7 with qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 and we got problems- tcp sessions, namely smb connections, randomly drops. We didn't test previous qemu-rhev with this VM, so we don't know how it works in them. Could you tell me is this known problem? Any workaround except switching to virtio? Thank you!

2 2

NIC Stability Problems Under Xen 4.4 / CentOS 6 / Linux 3.18
by Kevin Stange 29 Mar '17

29 Mar '17

I have three different types of CentOS 6 Xen 4.4 based hypervisors (by hardware) that are experiencing stability issues which I haven't been able to track down. All three types seem to be having issues with NIC and/or PCIe. In most cases, the issues are unrecoverable and require a hard boot to resolve. All have Intel NICs. Often the systems will remain stable for days or weeks, then suddenly encounter one of these issues. I have yet to tie the error to any specific action on the systems and can't reproduce it reliably. - Supermicro X8DT3, Dual Xeon E5620, 2x 82575EB NICs, 2x 82576 NICs Kernel messages upon failure: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018 pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, id=0018(Receiver ID) pcieport 0000:00:03.0: device [8086:340a] error status/mask=00002000/00001001 pcieport 0000:00:03.0: [13] Advisory Non-Fatal pcieport 0000:00:03.0: Error of this Agent(0018) is reported first igb 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0400(Receiver ID) igb 0000:04:00.0: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.0: [ 0] Receiver Error (First) igb 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp <12e6bc0b6> next_to_watch <ffff880006aa7440> jiffies <12e6bc8dc> desc.status <1c8210> This spams to the console continuously until hard booting. - Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB e1000e 0000:04:00.0 eth2: Detected Hardware Unit Hang: TDH <ff> TDT <33> next_to_use <33> next_to_clean <fd> buffer_info[next_to_clean]: time_stamp <138230862> next_to_watch <ff> jiffies <138231ac0> next_to_watch.status <0> MAC Status <80383> PHY Status <792d> PHY 1000BASE-T Status <3c00> PHY Extended Status <3000> PCI Status <10> This type of system, the NIC automatically recovers and I don't need to reboot. So far I tried using pcie_aspm=off to see that would help, but it appears that the 3.18 kernel turns off ASPM by default on these due to probing the BIOS. Stability issues were not resolved by the changes. On the latter system type I also turned off all offloading setting. It appears the stability increased slightly but it didn't fully resolve the problem. I haven't adjusted offload settings on the first two server types yet. I suspect this problem is related to the 3.18 kernel used by the virt SIG, as we had these running Xen on CentOS 5's kernel with no issues for years, and systems of these types used elsewhere in our facility are stable under CentOS 6's standard kernel. This affects more than one server of each type, so I don't believe it is a hardware failure, or else it's a hardware design flaw. Has anyone experienced similar issues with this configuration, and if so, does anyone have tips on how to resolve the issues? -- Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 800 S Wells, Suite 190 | Chicago, IL 60607 312.602.2689 X203 | Fax: 312.602.2688 kevin(a)steadfast.net | www.steadfast.net

8 35

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt