virt

virt@lists.centos.org

2 participants
1612 discussions

xen and spice problem
by Christoph 01 Oct '15

01 Oct '15

Hi it is possible to use xen and spice already? If yes is there any howto or doc how? If I turn on spice in cfg of a hvm domU, I get this error: Parsing config from /etc/xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: time_ref_count group enabled xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xbad04 xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1bad04 xc: detail: VIRTUAL MEMORY ARRANGEMENT: xc: detail: Loader: 0000000000100000->00000000001bad04 xc: detail: Modules: 0000000000000000->0000000000000000 xc: detail: TOTAL: 0000000000000000->000000007f000000 xc: detail: ENTRY: 0000000000100610 xc: detail: PHYSICAL MEMORY ALLOCATION: xc: detail: 4KB PAGES: 0x0000000000000200 xc: detail: 2MB PAGES: 0x00000000000003f7 xc: detail: 1GB PAGES: 0x0000000000000000 xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1959:kill_device_model: Device Model already exited libxl: error: libxl.c:1580:libxl__destroy_domid: non-existant domain 29 libxl: error: libxl.c:1538:domain_destroy_callback: unable to destroy guest with domid 29 libxl: error: libxl.c:1465:domain_destroy_cb: destruction of domain 29 failed (xen-4.6rc3-4.el7.x86_64) -- --------- Greetz

2 2

CentOS 6 Xen virt* issues
by Pasi Kärkkäinen 29 Sep '15

29 Sep '15

Hello, I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and dom0 3.18.17 rpms, and noticed these new problems: 1) virt-manager fails to start with an error: "D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory" And indeed.. there was no such file. Running command "dbus-uuidgen --ensure" fixed it, and virt-manager starts OK after that. So this was more for the mailinglist archives, if someone else meets the same issue. 2) virt-viewer doesn't work anymore. It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 2.0-7, with a lot of changes.. If I try to use virt-viewer and run "virt-viewer <testvm>" command, I get an error popup dialog saying "Failed to connect: Display can only be attached through libvirt with --attach". verbose debug output: # virt-viewer -v --debug -c "xen://" testvm (virt-viewer:9420): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 [root@fdell01 rpm]# less testvm01.txt (virt-viewer:9374): virt-viewer-DEBUG: connecting ... (virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with URI xen:// Opening connection to libvirt with URI xen:// (virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520 (virt-viewer:9374): virt-viewer-DEBUG: initial connect (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f0000 (virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212 (virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f0000 (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining display Guest testvm is running, determining display (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display Guest testvm has a vnc display (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphics (virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1 (virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7 (virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820 (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 And trying with the "attach" option: # virt-viewer -v --debug -c "xen://" -a testvm (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 [root@fdell01 rpm]# less testvm02.txt (virt-viewer:9389): virt-viewer-DEBUG: connecting ... (virt-viewer:9389): virt-viewer-DEBUG: Opening connection to libvirt with URI xen:// Opening connection to libvirt with URI xen:// (virt-viewer:9389): virt-viewer-DEBUG: Add handle 7 1 0x13ef580 (virt-viewer:9389): virt-viewer-DEBUG: initial connect (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000 (virt-viewer:9389): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212 (virt-viewer:9389): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000 (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm is running, determining display Guest testvm is running, determining display (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm has a vnc display Guest testvm has a vnc display (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing is not supported by this connection (virt-viewer:9389): virt-viewer-DEBUG: After open connection callback fd=-1 (virt-viewer:9389): virt-viewer-DEBUG: Remove handle 1 7 (virt-viewer:9389): virt-viewer-DEBUG: Disposing window 0x136b820 (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 So it seems both connection types/methods now fail.. I'm not sure if the issue is in our custom libvirt build, or in Xen's qemu.. (googling for those errors reveals some related patches which also have patches for qemu: http://comments.gmane.org/gmane.comp.emulators.virt-tools/9185) Error from the first attempt: (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphics Error from the second attempt: (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing is not supported by this connection Thanks, -- Pasi

3 8

xen and centos7
by Christoph 29 Sep '15

29 Sep '15

Hi is there already a release of xen for centos7? If not it is on roadmap? If yes when could it be done? -- ------ Greetz

4 7

memory balloon on XenServer 6.5 does not work for CentOS 6.X with default kernel 2.6.32.XX .
by Kieran Alen 28 Sep '15

28 Sep '15

Hello All, We have noticed that memory balloon feature on Citrix XenServer 6.5 does not work for guest CentOS 6.X with default kernel 2.6.32.XX. Is there any known issue for the same ? Regards, Kieran A. //

2 1

CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing
by George Dunlap 27 Sep '15

27 Sep '15

Updated Xen 4.4.3 packages have passed my local smoke tests, and are now available. Full C7 release is still waiting on suitable testing for the libvirt packages. If someone wants to step up to give the libvirt packages a decent smoke test, that will speed the C7 release process significantly. Otherwise it will have to wait until I get a chance to write some automated smoke tests. In the mean time, here's how to install the core Xen packages: rpm -ivh http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-… This will set up yum repositories for both the eventual release repositories (enabled by default), and the community build system repositories (disabled by default). At the moment, all packages will be stored in the virt-xen-44-testing repository. You can either enable this by default by editing /etc/yum.repos.d/VirtSIG-Xen.repo, or by adding "--enablerepo=virt-xen-44-testing". If you want, you can edit defaults /etc/sysconfig/xen-kernel Next, run 'yum update' to get the new kernel: yum --enablerepo=virt-xen-44-testing update kernel Now install xen: yum --enablerepo=virt-xen-44-testing install xen This should grab both xen and the updated kernel package. It should also automatically: * Add default commandline parameters for Xen and Linux when booting under Xen * Arrange for xen to come up first in the grub * Set the default boot entry to Xen. That's it! Reboot and you should be good to go. Please report any problems or feedback to this list. -George

2 8

Re: [CentOS-virt] OT: adding a wifi adapter to openvswitch
by Dmitry E. Mikhailov 24 Sep '15

24 Sep '15

On 09/24/2015 08:31 PM, C. L. Martinez wrote: > Simple, Windows 2012 creates a virtual bridge with the same MAC > address as wlan has. Ok. Windows does just the same. Thanks for the ARP table. [For ML readers - it was sent directly]. Now we know what the money are paid for :) > But, I think it could not be possible to bridge > wlan interfaces with brctl or openvswitch according what I am. seeing > and reading Quite possible with the invalulable help of Nux: Parprouted + NetworkManager scripting should do the trick. > Ok, I will try a different approach. I can see two possible solutions: > > a) Pass wlan via PCI-Passthrough to fw vm Would work even better but I don't think the laptop would suspend. > b) Using iptables+iproute2 rules in laptop and redirect/nat all > traffic from/to fw vm. > > > I will try b) option first. I know what type of iptables I need to use > and what type of config I need to do to iproute2 works as I need. > > But I see one problem: I need to redirect ALL traffic from outside to > inside: ip, ipv6, tcp, tcp6, igmp, etc ... and I don't know what type > of iptables I need to configure. > > Any tip?? Try the aforementioned unnumbered option first. Can't say anything about IPv6 - sadly not proficient. For IPv4 you won't need iptables, only iproute: 1)save and delete the current wireless default gateway IP 2)create a source-based policy routing rule so traffic from the fw VM IP address would have the earlier saved IP as a gateway IP 3)set the default gateway IP to the another interface's (it's a requirement) IP address of a fw VM.

1 0

OT: adding a wifi adapter to openvswitch
by C.L. Martinez 24 Sep '15

24 Sep '15

Hi all, Finally, I have installed openvswitch from source to two CentOS hosts: one 6.x and other 7.x. I will do some tests using openvswitch bridges to my KVM machines. One of these tests is to add a wlan0 adapter from comandline but only when this wlan0 is associated with a ssid without assign an IP. Is this posible? Do I nees to add some ebtables like, for example, Debian's wiki says here: https://wiki.debian.org/BridgeNetworkConnections#Bridging_with_a_wireless_N… Thanks

5 10

Re: [CentOS-virt] xen-4.4.3-1 packages released
by Keith Roberts 24 Sep '15

24 Sep '15

On 24 Sep 2015, at 14:38, Johnny Hughes <johnny(a)centos.org> wrote: > On 09/24/2015 04:11 AM, Keith Roberts wrote: >> Forwarding this to the list as I had a problem with our domain being >> blacklisted: >> >> <centos-virt(a)centos.org <mailto:centos-virt@centos.org>>: >> host mail.centos.org <http://mail.centos.org>[72.26.200.203] said: 554 5.7.1 >> Service unavailable; Client host [62.208.144.128] blocked using >> ix.dnsbl.manitu.net <http://ix.dnsbl.manitu.net>; Your e-mail service >> was detected by mx-ha.web.de <http://mx-ha.web.de> (NiX >> Spam) as spamming at Thu, 24 Sep 2015 05:14:02 +0200. >> >> Begin forwarded message: >> >>> *From: *Keith Roberts <keith.roberts(a)ecric.nhs.uk >>> <mailto:keith.roberts@ecric.nhs.uk>> >>> *Subject: **Re: [CentOS-virt] xen-4.4.3-1 packages released* >>> *Date: *24 September 2015 09:45:32 BST >>> *To: *Discussion about the virtualization on CentOS >>> <centos-virt(a)centos.org <mailto:centos-virt@centos.org>> >>> >>> On 23 Sep 2015, at 21:54, Johnny Hughes <johnny(a)centos.org >>> <mailto:johnny@centos.org>> wrote: >>> >>>> I have signed and released the xen4centos CentOS-6 packages to our main >>>> mirrors, the following are released: >>>> >>>> x86_64: >>>> xen-4.4.3-1.el6.x86_64.rpm >>>> xen-devel-4.4.3-1.el6.x86_64.rpm >>>> xen-doc-4.4.3-1.el6.x86_64.rpm >>>> xen-hypervisor-4.4.3-1.el6.x86_64.rpm >>>> xen-libs-4.4.3-1.el6.x86_64.rpm >>>> xen-licenses-4.4.3-1.el6.x86_64.rpm >>>> xen-ocaml-4.4.3-1.el6.x86_64.rpm >>>> xen-ocaml-devel-4.4.3-1.el6.x86_64.rpm >>>> xen-runtime-4.4.3-1.el6.x86_64.rpm >>>> >>>> src: >>>> xen-4.4.3-1.el6.src.rpm >>> >>> Hi Johnny. >>> >>> That’s great news and thanks for all the effort with this. >>> >>> I currently have issues with upgrading a xen VM host server from >>> openSUSE 12.3 to 13.1 and one of the options I’d like to consider >>> is installing Centos 6 or 7 using xen on the VM host. >>> >>> I only want to replace the xen VM host server OS with another Linux >>> distro with LTS that also uses the xen hypervisor. >>> >>> So not having a 64 bit base installation of xen on Centos 6 or 7 has >>> been a blocker for me doing this. >>> >>> I’m watching the mailing list like a hawk now, (and have been for some >>> time) for when xen is available for production use on Centos 6 or 7. >>> >>> Thanks again Johnny for all your effort with this. >>> >>> Kind Regards, >>> >>> Keith Roberts > > We have released xen (4.4.x) for CentOS-6 in production and we maintain > it via the Virtualization SIG, which uses this list. The released > version lives on mirror.centos.org and the RPMs are here: > > http://mirror.centos.org/centos/6/xen4/x86_64/ > > We also have a TESTING branch of xen 4.4 and 4.6rc for CentOS-7 in our > Community Build System (CBS) here: > > 4.4: > http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/ > > 4.6rc: > http://cbs.centos.org/repos/virt7-xen-46-testing/x86_64/os/ > > Those are not really production ready .. but do currently work. Hi Johnny. It’s nice to know Centos 6 is production ready now. I might give it a spin on another OS partition, and see what results I get on a test server. Kind Regards, Keith

1 0

Fwd: xen-4.4.3-1 packages released
by Keith Roberts 24 Sep '15

24 Sep '15

Forwarding this to the list as I had a problem with our domain being blacklisted: <centos-virt(a)centos.org>: host mail.centos.org[72.26.200.203] said: 554 5.7.1 Service unavailable; Client host [62.208.144.128] blocked using ix.dnsbl.manitu.net; Your e-mail service was detected by mx-ha.web.de (NiX Spam) as spamming at Thu, 24 Sep 2015 05:14:02 +0200. Begin forwarded message: > From: Keith Roberts <keith.roberts(a)ecric.nhs.uk> > Subject: Re: [CentOS-virt] xen-4.4.3-1 packages released > Date: 24 September 2015 09:45:32 BST > To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> > > On 23 Sep 2015, at 21:54, Johnny Hughes <johnny(a)centos.org> wrote: > >> I have signed and released the xen4centos CentOS-6 packages to our main >> mirrors, the following are released: >> >> x86_64: >> xen-4.4.3-1.el6.x86_64.rpm >> xen-devel-4.4.3-1.el6.x86_64.rpm >> xen-doc-4.4.3-1.el6.x86_64.rpm >> xen-hypervisor-4.4.3-1.el6.x86_64.rpm >> xen-libs-4.4.3-1.el6.x86_64.rpm >> xen-licenses-4.4.3-1.el6.x86_64.rpm >> xen-ocaml-4.4.3-1.el6.x86_64.rpm >> xen-ocaml-devel-4.4.3-1.el6.x86_64.rpm >> xen-runtime-4.4.3-1.el6.x86_64.rpm >> >> src: >> xen-4.4.3-1.el6.src.rpm > > Hi Johnny. > > That’s great news and thanks for all the effort with this. > > I currently have issues with upgrading a xen VM host server from openSUSE 12.3 to 13.1 and one of the options I’d like to consider > is installing Centos 6 or 7 using xen on the VM host. > > I only want to replace the xen VM host server OS with another Linux distro with LTS that also uses the xen hypervisor. > > So not having a 64 bit base installation of xen on Centos 6 or 7 has been a blocker for me doing this. > > I’m watching the mailing list like a hawk now, (and have been for some time) for when xen is available for production use on Centos 6 or 7. > > Thanks again Johnny for all your effort with this. > > Kind Regards, > > Keith Roberts

2 1

kernel-3.18.21-13.el7 is now in virt7-xen-44-testing and virt7-xen-46-testing
by Johnny Hughes 24 Sep '15

24 Sep '15

I have pushed kernel-3.18.21-13.el7 to both virt7-xen-44-testing and virt7-xen-46-testing.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt