similar to: Open graphics connection with virt-manager problem

Hello, I posted a question over at xenproject.org but it was recommended that I send out a message here for help. My post there: http://www.xenproject.org/help/questions-and-answers/vanilla-pv-centos-guest-via-kickstart-centos-6-6,-xen-4-4.html The TL;DR is: Everything I've found to kickstart a new vanilla rhel/centos guest points to specifying a kernel & and initrd- for RHEL/Centos 5.

In honor of Xen Doc Day, I've put up some basic HOWTOs for setting up bridging on CentOS 6 and 7. I'm far from an expert, so I'd appreciate any feedback. The howtos can be found here: https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Networking6 https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Networking7 -George

Hi, I installed CentOS 7.4 on a modern Lenovo ThinkSystem SR630 server which uses UEFI. So far so good CentOS 7.4 works fine so then I went on to install the Xen hypervisor by following the instructions from the wiki (https://wiki.centos.org/HowTos/Xen/Xen4QuickStart). Unfortunately when I reboot after having installed the xen package the system does not boot into "CentOS Linux, with Xen

Hello, we have a strange problem on a fresh install of CentOS 6.5. On the server we want to use Xen to host paravirtualised guests (the system has no hardware virtualization support). To manage the domain we would like to use libvirt. Xen and libvirt are set up as described here: http://wiki.centos.org/HowTos/Xen/Xen4QuickStart http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt When

Hi all, I'm trying to install libvirt for xen on a brand new, minimal installation of CentOS 7.5.1804. After installing the OS, I did a 'yum update' and followed the basic how-tos at https://wiki.centos.org/HowTos/Xen/Xen4QuickStart and https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt From previous experience, I know that the above steps worked fine. However,

Hi, after migrating to libvirt/libxl according to: https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt I've noticed that my Xen PV domains are being launched by qemu-system-i386 running under root privileges. I am wondering why is this? Previously no qemu process was used. If qemu is needed for some reason, are there any guidelines for non-root operation? Thanks -- Karel

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. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Why do you need UEFI? It does not add to security "a lot" but was designed to block booting software like a "hypervisor". I used my Dell notebooks to test our hypervisor identification software (HyperCatcher if you are interested) which is bootable image. However, I was unable to boot it until I disabled UEFI. As I understand it, it will block anything from booting excepting

Hi, spot on! On 6.9.2015 12:56, Pasi K?rkk?inen wrote: > On Sun, Sep 06, 2015 at 09:08:50AM +0200, Karel Hendrych wrote: >> Hi, after migrating to libvirt/libxl according to: >> > > Hi, > >> https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt >> >> I've noticed that my Xen PV domains are being launched by >> qemu-system-i386 running

I'm trying create a virtual machine using Xen as hypervisor and virt-manager (libvirt) as the management module. When trying to create the virtual machine I am getting the following error: " Unable to complete install: 'internal error: unsupported input bus usb' " ERROR DETAILS: Unable to complete install: 'internal error: unsupported input bus usb' Traceback

On Mon, Sep 07, 2015 at 05:47:39PM +0200, Karel Hendrych wrote: > ... > > changing from: <driver name='file'/> to: <driver name='tap2'/> makes > the domain start without QEMU. > > However I see much better performance with QEMU (close to dom0, > tested using simple dd writes) than with tap2 driver. Is that > expected? > How did you measure

Hi, After following the instructions here http://wiki.centos.org/HowTos/Xen/Xen4QuickStart and installing the kernel from Xen4 CentOS project (kernel-3.4.61-9.el6.centos.alt.x86_64) I can't use any networking because the firmware for my NIC is not available: Bringing up interface eth0.3: bnx2x 0000:02:00.0: firmware: requesting bnx2x/bnx2x-e1h-7.2.51.0.fw bnx2x:

On Fri, Feb 21, 2020 at 09:16:01AM +0100, Ján Tomko wrote: > [adding Anthony PERARD to cc since his name is next to > xen-4.12.2-1.el7's ChangeLog entry] > > Hi, Anthony! > > On Thu, Feb 20, 2020 at 07:10:38PM +0100, Christoph wrote: > > https://wiki.centos.org/HowTos/Xen/Xen4QuickStart > > > > configure:53501: checking for LIBXL > >

Hi, I have used this http://wiki.centos.org/HowTos/Xen/Xen4QuickStart and everything works like a charm then I installed a VM using http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt only to realize later that I don't want NAT. I would want to use PCI passthrough and so i used virsh net-destroy default virsh net-undefine default and net-create /home/kartik/passthrough.xml

Hi, I have a server with Supermicro X7DVL-3 (P9) motherboard, 16G ECC RAM and LSI SAS 1068e RAID controller. I installed CentOS 6.5 64bit on the machine without any problems, but after following the Xen setup steps at http://wiki.centos.org/HowTos/Xen/Xen4QuickStart which installed me the kernel 3.10.32-11.el6.centos.alt.x86_64, I encountered a problem: After "Starting certmonger

If you'd like to extend that a little bit, here's example configs on how to do LACP and vlan tagging on c6: host network-scripts # cat ifcfg-eth0 DEVICE=eth0 ONBOOT=yes USEERCTL=no BOOTPROTO=none IPV6INIT=no MTU=1500 MASTER=bond0 SLAVE=yes host network-scripts # cat ifcfg-eth1 DEVICE=eth1 ONBOOT=yes USEERCTL=no BOOTPROTO=none IPV6INIT=no MTU=1500 MASTER=bond0 SLAVE=yes host

https://wiki.centos.org/HowTos/Xen/Xen4QuickStart configure:53501: checking for LIBXL configure:53508: $PKG_CONFIG --exists --print-errors "xenlight >= 4.6.0" Package xenblktapctl was not found in the pkg-config search path. Perhaps you should add the directory containing `xenblktapctl.pc' to the PKG_CONFIG_PATH environment variable Package 'xenblktapctl', required by

R Verzonden met mijn Windows Phone ________________________________ Van: centos-virt-request at centos.org<mailto:centos-virt-request at centos.org> Verzonden: ?6-?12-?2013 09:35 Aan: centos-virt at centos.org<mailto:centos-virt at centos.org> Onderwerp: CentOS-virt Digest, Vol 76, Issue 3 Send CentOS-virt mailing list submissions to centos-virt at centos.org To subscribe or

HI, We've started to see several issues with the Xen releases. Going back to basics I've used this guide https://wiki.centos.org/HowTos/Xen/Xen4QuickStart Once the install process is complete the grub.conf looks like this: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /boot/xen.gz

I normally use the network-script parameter in the '/etc/xen/xend-config.sxp' configuration file to configure network bridges. However, the latest release of Xen4CentOS (which comes with Xen 4.4.1) has xend disabled by default. Can I continue to use network-script without xend? If not what is the recommended method for automatically configuring network bridges with the latest release of