virt

virt@lists.centos.org

1608 discussions

qemu-kvm-ev-2.6.0-28.el7_3.9.1 now available for testing
by Sandro Bonazzola 20 Apr '17

20 Apr '17

Hi, just pushed to testing a new build of qemu-kvm-ev, here's the ChangeLog: * Thu Apr 20 2017 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.6.0-28.el7_3.9.1 - Removing RH branding from package name * Fri Mar 24 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.9 - kvm-block-gluster-memory-usage-use-one-glfs-instance-per.patch [bz#1413044] - kvm-gluster-Fix-use-after-free-in-glfs_clear_preopened.patch [bz#1413044] - kvm-fix-cirrus_vga-fix-OOB-read-case-qemu-Segmentation-f.patch [bz#1430061] - kvm-cirrus-vnc-zap-bitblit-support-from-console-code.patch [bz#1430061] - kvm-cirrus-add-option-to-disable-blitter.patch [bz#1430061] - kvm-cirrus-fix-cirrus_invalidate_region.patch [bz#1430061] - kvm-cirrus-stop-passing-around-dst-pointers-in-the-blitt.patch [bz#1430061] - kvm-cirrus-stop-passing-around-src-pointers-in-the-blitt.patch [bz#1430061] - kvm-cirrus-fix-off-by-one-in-cirrus_bitblt_rop_bkwd_tran.patch [bz#1430061] - kvm-file-posix-Consider-max_segments-for-BlockLimits.max.patch [bz#1431149] - kvm-file-posix-clean-up-max_segments-buffer-termination.patch [bz#1431149] - kvm-file-posix-Don-t-leak-fd-in-hdev_get_max_segments.patch [bz#1431149] - Resolves: bz#1413044 (block-gluster: use one glfs instance per volume) - Resolves: bz#1430061 (CVE-2016-9603 qemu-kvm-rhev: Qemu: cirrus: heap buffer overflow via vnc connection [rhel-7.3.z]) - Resolves: bz#1431149 (VMs pause when writing to Virtio-SCSI direct lun with scsi passthrough enabled via an Emulex HBA) * Tue Mar 21 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.8 - kvm-target-i386-present-virtual-L3-cache-info-for-vcpus.patch [bz#1430802] - Resolves: bz#1430802 (Enhance qemu to present virtual L3 cache info for vcpus) * Wed Mar 15 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.7 - kvm-block-check-full-backing-filename-when-searching-pro.patch [bz#1425125] - kvm-qemu-iotests-Don-t-create-fifos-pidfiles-with-protoc.patch [bz#1425125] - kvm-qemu-iotest-test-to-lookup-protocol-based-image-with.patch [bz#1425125] - kvm-target-i386-Don-t-use-cpu-migratable-when-filtering-.patch [bz#1413897] - Resolves: bz#1413897 (cpu flag nonstop_tsc is not present in guest with host-passthrough and feature policy require invtsc) - Resolves: bz#1425125 (qemu fails to recognize gluster URIs in backing chain for block-commit operation) In order to test it: # yum install centos-release-qemu-ev # yum-config-manager --enable centos-qemu-ev-test # yum install qemu-kvm-ev Or just yum update if you already have qemu-kvm-ev installed and test repository enabled. If you test it, please provide feedback. I'm going to release it on April 26th if no negative feedback is provided. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

qemu-kvm-ev ppc64le release builds
by Lance Albertson 20 Apr '17

20 Apr '17

Hi, We're using qemu-kvm-ev on ppc64le and I've noticed that it's included in the extras repo for ppc64le but in the qemu-kvm-ev repo for x86_64. I also noticed the version in ppc64le is lagging behind x86. I see that ppc64le is being built for this, however isn't tagged for virt7-kvm-common-release and thus showing up under /virt/kvm-common on the mirrors. Is there any particular reason why this is happening? If possible, I can certainly provide some testing to get this moving along. Thank you! [1] http://cbs.centos.org/koji/packageinfo?packageID=539 -- Lance Albertson Director Oregon State University | Open Source Lab

2 1

Testing kernel crash: 4.9.23-26.el6.x86_64
by Piotr Gackiewicz 20 Apr '17

20 Apr '17

Hello CentOS Xen Heroes, Yesterday, I have installed testing kernel 4.9.23-26.el6.x86_64 from virt-xen-testing repo. It crashed today morning. Hardware is a pretty ancient, testing machine (CO6 PV guests only), but had no problems yet. It was stable on 4.9*, including testing 4.9.15-22.el6.x86_64 Console output: [59826.069427] general protection fault: 0000 [#1] SMP [59826.069463] Modules linked in: xt_physdev br_netfilter xt_mac ebt_arp xen_pciback xen_gntalloc ebtable_filter ebtables bridge 8021q mrp garp stp llc xt_CT xt_addrtype iptable_raw nf_log_ ipv4 nf_log_common xt_LOG xt_limit xt_owner iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_sta te nf_conntrack ip6table_filter ip6_tables blktap xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd ppdev parport_pc parport fjes 3c59x asus_atk0110 pcspkr serio_raw k8temp vi a_rhine mii i2c_viapro shpchp raid1 pata_via pata_acpi ata_generic sata_via [59826.069842] CPU: 0 PID: 32443 Comm: sshd Not tainted 4.9.23-26.el6.x86_64 #1 [59826.069860] Hardware name: System manufacturer System Product Name/K8V-VM, BIOS 0201 06/13/2006 [59826.069882] task: ffff880014c8c900 task.stack: ffffc90043820000 [59826.069896] RIP: e030:[<ffffffff812405d6>] [<ffffffff812405d6>] kmem_cache_alloc_node+0xa6/0x1c0 [59826.070019] RSP: e02b:ffffc90043823b08 EFLAGS: 00010246 [59826.070019] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000ec741e [59826.070019] RDX: 0000000000ec741d RSI: 00000000024000c0 RDI: ffff0000ffff0000 [59826.070019] RBP: ffffc90043823b68 R08: 000000000001cd00 R09: 0000000000000000 [59826.070019] R10: 0000000000007ff0 R11: ffffc900407ebe88 R12: ffff88001a8013c0 [59826.070019] R13: ffff88001a8013c0 R14: 00000000ffffffff R15: 00000000024000c0 [59826.070019] FS: 00007f652071e7c0(0000) GS:ffff88001f800000(0000) knlGS:0000000000000000 [59826.070019] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [59826.070019] CR2: 00007fff0870ad60 CR3: 000000000f940000 CR4: 0000000000000660 [59826.070019] Stack: [59826.070019] ffffc90043823b38 ffffffff818d5e36 ffff880016711758 ffffffff81792687 [59826.070019] ffff880015d1ec10 ffff880015d1ec00 ffffc90043823c38 ffff880015d1ec00 [59826.070019] 00000000024000c0 00000000ffffffff ffff88001a8013c0 0000000000000024 [59826.070019] Call Trace: [59826.070019] [<ffffffff818d5e36>] ? mutex_lock+0x16/0x40 [59826.070019] [<ffffffff81792687>] ? __alloc_skb+0x57/0x200 [59826.070019] [<ffffffff81792687>] __alloc_skb+0x57/0x200 [59826.070019] [<ffffffff817e2af0>] ? netlink_attachskb+0x1b0/0x1b0 [59826.070019] [<ffffffff817df900>] ? netlink_overrun+0x50/0x50 [59826.070019] [<ffffffff817e319c>] netlink_ack+0x6c/0x170 [59826.070019] [<ffffffff8115526b>] audit_receive+0x8b/0xa0 [59826.070019] [<ffffffff817e30aa>] netlink_unicast+0x19a/0x220 [59826.070019] [<ffffffff817e3ed2>] netlink_sendmsg+0x302/0x380 [59826.070019] [<ffffffff81787ba9>] sock_sendmsg+0x49/0x60 [59826.070019] [<ffffffff8178a006>] SYSC_sendto+0x116/0x170 [59826.070019] [<ffffffff81287efc>] ? __alloc_fd+0x4c/0x1b0 [59826.070019] [<ffffffff810033c1>] ? syscall_trace_enter+0x201/0x2c0 [59826.070019] [<ffffffff8115b199>] ? __audit_syscall_exit+0x229/0x2b0 [59826.070019] [<ffffffff8178a06e>] SyS_sendto+0xe/0x10 [59826.070019] [<ffffffff81003e7a>] do_syscall_64+0x7a/0x240 [59826.070019] [<ffffffff8106f1a7>] ? do_page_fault+0x37/0x90 [59826.070019] [<ffffffff818d83eb>] entry_SYSCALL64_slow_path+0x25/0x25 [59826.070019] Code: e8 36 41 39 c6 74 17 48 8b 4d b8 44 89 f2 44 89 fe 4c 89 e7 e8 2c f7 ff ff 48 89 c3 eb 2c 49 63 44 24 20 4d 8b 04 24 48 8d 4a 01 <48> 8b 1c 07 48 89 f8 49 8d 30 e8 eb b 4 1e 00 3c 01 75 95 49 63 [59826.070019] RIP [<ffffffff812405d6>] kmem_cache_alloc_node+0xa6/0x1c0 [59826.070019] RSP <ffffc90043823b08> [59826.076823] general protection fault: 0000 [#2] SMP [59826.077009] Modules linked in: xt_physdev br_netfilter xt_mac ebt_arp xen_pciback xen_gntalloc ebtable_filter ebtables bridge 8021q mrp garp stp llc xt_CT xt_addrtype iptable_raw nf_log_ ipv4 nf_log_common xt_LOG xt_limit xt_owner iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_sta te nf_conntrack ip6table_filter ip6_tables blktap xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd ppdev parport_pc parport fjes 3c59x asus_atk0110 pcspkr serio_raw k8temp vi a_rhine mii i2c_viapro shpchp raid1 pata_via pata_acpi ata_generic sata_via [59826.077733] CPU: 0 PID: 32443 Comm: sshd Tainted: G D 4.9.23-26.el6.x86_64 #1 [59826.077733] Hardware name: System manufacturer System Product Name/K8V-VM, BIOS 0201 06/13/2006 [59826.077733] task: ffff880014c8c900 task.stack: ffffc90043820000 [59826.077733] RIP: e030:[<ffffffff81241ad5>] [<ffffffff81241ad5>] kmem_cache_alloc+0x85/0x1b0 [59826.077733] RSP: e02b:ffff88001f803ba8 EFLAGS: 00010286 [59826.077733] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000ec741e [59826.077733] RDX: 0000000000ec741d RSI: 0000000002080020 RDI: 000000000001cd00 [59826.077733] RBP: ffff88001f803bf8 R08: ffff88001f81cd00 R09: ffff0000ffff0000 [59826.077733] R10: 0000000000000003 R11: 0000000000000000 R12: ffff88001a8013c0 [59826.077733] R13: ffff88001a8013c0 R14: ffffffff8179240e R15: 0000000002080020 [59826.077733] FS: 00007f652071e7c0(0000) GS:ffff88001f800000(0000) knlGS:0000000000000000 [59826.077733] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [59826.077733] CR2: 00007fff0870ad60 CR3: 000000000f940000 CR4: 0000000000000660 [59826.077733] Stack: [59826.077733] ffff88001f803bb8 ffffffff81025105 ffff88001f803bc8 ffff88001f816760 [59826.077733] 0000000000000780 0000000000000780 ffff8800144af880 0000000000000000 [59826.077733] 0000000000000200 ffff8800144af880 ffff88001f803c38 ffffffff8179240e [59826.077733] Call Trace: [59826.077733] <IRQ> [59826.077733] [<ffffffff81025105>] ? xen_clocksource_read+0x15/0x20 [59826.077733] [<ffffffff8179240e>] __build_skb+0x2e/0xe0 [59826.077733] [<ffffffff817929fa>] __netdev_alloc_skb+0xda/0x120 [59826.077733] [<ffffffff810d0a5a>] ? activate_task+0x7a/0x90 [59826.077733] [<ffffffffc0027368>] rhine_rx+0x2b8/0x530 [via_rhine] [59826.077733] [<ffffffffc00276be>] rhine_napipoll+0xde/0x190 [via_rhine] [59826.077733] [<ffffffff817abfdb>] napi_poll+0xdb/0x1f0 [59826.077733] [<ffffffff81119aae>] ? process_timeout+0xe/0x10 [59826.077733] [<ffffffff81119732>] ? call_timer_fn+0x42/0x140 [59826.077733] [<ffffffff817ac1b5>] net_rx_action+0xc5/0x240 [59826.077733] [<ffffffff8111b1d6>] ? run_timer_softirq+0x276/0x2c0 [59826.077733] [<ffffffff810d833c>] ? sched_clock_local+0x1c/0x90 [59826.077733] [<ffffffff810d844a>] ? sched_clock_cpu+0x9a/0xb0 [59826.077733] [<ffffffff818db0ce>] __do_softirq+0xce/0x2bf [59826.077733] [<ffffffff810d844a>] ? sched_clock_cpu+0x9a/0xb0 [59826.077733] [<ffffffff810ab1d5>] irq_exit+0x105/0x110 [59826.077733] [<ffffffff8150e3f9>] xen_evtchn_do_upcall+0x39/0x50 [59826.077733] [<ffffffff818d93de>] xen_do_hypervisor_callback+0x1e/0x40 [59826.077733] <EOI> [59826.077733] [<ffffffff8100122a>] ? xen_hypercall_xen_version+0xa/0x20 [59826.077733] [<ffffffff8100122a>] ? xen_hypercall_xen_version+0xa/0x20 [59826.077733] [<ffffffff81103fff>] ? console_unlock+0x2ff/0x3e0 [59826.077733] [<ffffffff81024c5d>] ? xen_force_evtchn_callback+0xd/0x10 [59826.077733] [<ffffffff810253b6>] ? check_events+0x16/0x30 [59826.077733] [<ffffffff81025393>] ? xen_restore_fl_direct_reloc+0x4/0x4 [59826.077733] [<ffffffff81032b3d>] ? oops_end+0x7d/0xe0 [59826.077733] [<ffffffff81032cab>] ? die+0x5b/0x90 [59826.077733] [<ffffffff81030084>] ? do_general_protection+0xe4/0x170 [59826.077733] [<ffffffff818d97a8>] ? general_protection+0x28/0x30 [59826.077733] [<ffffffff812405d6>] ? kmem_cache_alloc_node+0xa6/0x1c0 [59826.077733] [<ffffffff812406c5>] ? kmem_cache_alloc_node+0x195/0x1c0 [59826.077733] [<ffffffff818d5e36>] ? mutex_lock+0x16/0x40 [59826.077733] [<ffffffff81792687>] ? __alloc_skb+0x57/0x200 [59826.077733] [<ffffffff81792687>] ? __alloc_skb+0x57/0x200 [59826.077733] [<ffffffff817e2af0>] ? netlink_attachskb+0x1b0/0x1b0 [59826.077733] [<ffffffff817df900>] ? netlink_overrun+0x50/0x50 [59826.077733] [<ffffffff817e319c>] ? netlink_ack+0x6c/0x170 [59826.077733] [<ffffffff8115526b>] ? audit_receive+0x8b/0xa0 [59826.077733] [<ffffffff817e30aa>] ? netlink_unicast+0x19a/0x220 [59826.077733] [<ffffffff817e3ed2>] ? netlink_sendmsg+0x302/0x380 [59826.077733] [<ffffffff81787ba9>] ? sock_sendmsg+0x49/0x60 [59826.077733] [<ffffffff8178a006>] ? SYSC_sendto+0x116/0x170 [59826.077733] [<ffffffff81287efc>] ? __alloc_fd+0x4c/0x1b0 [59826.077733] [<ffffffff810033c1>] ? syscall_trace_enter+0x201/0x2c0 [59826.077733] [<ffffffff8115b199>] ? __audit_syscall_exit+0x229/0x2b0 [59826.077733] [<ffffffff8178a06e>] ? SyS_sendto+0xe/0x10 [59826.077733] [<ffffffff81003e7a>] ? do_syscall_64+0x7a/0x240 [59826.077733] [<ffffffff8106f1a7>] ? do_page_fault+0x37/0x90 [59826.077733] [<ffffffff818d83eb>] ? entry_SYSCALL64_slow_path+0x25/0x25 [59826.077733] Code: 05 91 86 dc 7e 4d 8b 08 49 8b 40 10 4d 85 c9 0f 84 24 01 00 00 48 85 c0 0f 84 1b 01 00 00 49 63 44 24 20 49 8b 3c 24 48 8d 4a 01 <49> 8b 1c 01 4c 89 c8 48 8d 37 e8 ec 9 f 1e 00 3c 01 75 b6 49 63 [59826.077733] RIP [<ffffffff81241ad5>] kmem_cache_alloc+0x85/0x1b0 [59826.077733] RSP <ffff88001f803ba8> [59826.100347] ---[ end trace 58d7c3379dbe9d6a ]--- [59826.100533] Kernel panic - not syncing: Fatal exception in interrupt [59826.100721] Kernel Offset: disabled (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. Regards, -- Piotr Gackiewicz Intertele S.A. - operator systemów ITL.PL i DOMENY.ITL.PL al. T. Rejtana 10, 35-310 Rzeszów TEL: +48 17 8507580, FAX: +48 17 8520275 http://www.itl.pl - niezawodne usługi hostingowe http://domeny.itl.pl - tanie domeny internetowe http://www.intertele.pl

1 0

virsh error: driver is not whitelisted
by Marco Aurelio L. Gomes 19 Apr '17

19 Apr '17

Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <hugepages> <page size='2' unit='M' nodeset='0'/> </hugepages> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <shares>4096</shares> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <emulatorpin cpuset='4,5'/> </cputune> <os> <type arch='x86_64' machine='pc'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-model'> <model fallback='allow'/> <topology sockets='2' cores='1' threads='1'/> <numa> <cell id='0' cpus='0-1' memory='4194304' unit='KiB' memAccess='shared'/> </numa> </cpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/root/cirros-0.3.5-x86_64-disk.img'/> <target dev='vda' bus='virtio'/> </disk> <disk type='dir' device='disk'> <driver name='qemu' type='fat'/> <source dir='/usr/src/dpdk-stable-16.11.1'/> <target dev='vdb' bus='virtio'/> <readonly/> </disk> <interface type='vhostuser'> <mac address='00:00:00:00:00:01'/> <source type='unix' path='/var/run/openvswitch/dpdkvhostuser0' mode='client'/> <model type='virtio'/> <driver queues='2'> <host mrg_rxbuf='off'/> </driver> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> </devices> </domain> When I run: virsh create domain.xml I got the following error: error: Failed to create domain from domain.xml error: internal error: qemu unexpectedly closed the monitor: 2017-04-17T17:00:37.012369Z qemu-kvm: -drive file=fat:/usr/src/dpdk-stable-16.11.1,if=none,id=drive-virtio-disk1,readonly=on: Driver 'vvfat' is not whitelisted If I comment the disk that cause this error, the instance starts without error. Is there a way to whitelist this vvfat driver to instance this VM? And the strange thing about this error is that when I check the available drives, there is vvfat in the list: /usr/libexec/qemu-kvm -drive format=? Supported formats: ftps http null-aio null-co file quorum blkverify vvfat blkreplay qed raw qcow2 bochs dmg vmdk parallels vhdx vpc https sheepdog host_cdrom ssh host_device nbd gluster qcow iscsi rbd tftp ftp vdi blkdebug luks cloop Here some information about the environment: cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) virsh --version 2.0.0 /usr/libexec/qemu-kvm --version QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-28.el7_3.6.1), Copyright (c) 2003-2008 Fabrice Bellard Thanks in advance for the help Marco Aurelio Gomes NCC - UNESP

2 2

Is Xen on CentOS 7 production ready?
by redundantl y 17 Apr '17

17 Apr '17

I see the announcement from February that it's available, but is it considered to be safe for Production use? The documentation in the SIG still only references CentOS 6. https://wiki.centos.org/Manuals/ReleaseNotes/Xen4-01 https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Thanks.

2 2

qemu-kvm-ev 2.6 + libvirtd 3.0
by FeldHost Admin 17 Apr '17

17 Apr '17

Hello, it is safe to use centos 7 qemu-kvm-ev repo with new one for libvirt 3.0 https://cbs.centos.org/repos/virt7-libvirt-latest-release/x86_64/os/Package… Anybody using it? Thanks. -- S pozdravem Kristián Feldsam

1 0

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt