Hello, I'm working on setting up a nested Xen hypervisor and I'm having difficulty, and I'm hoping someone can help. I am using the current version of Xen in the Fedora 20 repositories (4.3.2-6). I've been able to successfully set up the L0 dom0, and install an HVM L1 domU using virt-install (both are using Fedora 20). My virt-install command was: virt-install --hvm --name <domU name> --ram 4096 --vcpus 2 -f /dev/fedora/<lv name> --network bridge=virbr0 --cdrom <path to Fedora 20 live iso> --livecd Without the hypervisor, L1 acts fine -- I can connect to the network through L0 using the bridge, I can vnc to the desktop, and xl info shows virt_caps as hvm. However, once I install Xen through yum (again 4.3.2-6) and reboot with the hypervisor, L1 "works" (i.e. boots) but I lose some functionality. First, the desktop no longer starts, I lose networking, and virt_caps in xl info is blank. I can still do a command line login using virt-viewer. I'm new to virtualization with Xen, so I believe my problem may be due to missing some key step(s) during the installation of L1. So, here are my questions: 1. Can L1 be installed correctly for use with a nested hypervisor using virt-install, or do I need to use xl directly? If so, what do I need to be aware of when installing? 2. I see from the Xen wiki that nested virtualization requires a couple extra parameters to the config file (hap=1 and nestedhvm=1). Is it possible to specify these options with virt-install, since it doesn't seem to use the config files that xl does? 3. Can I expect to get the desktop and networking in a L1 hypervisor setup? 4. Do I need Xen 4.4 or should Xen 4.3.2-6 work? I am using an Intel CPU with virtualization support, so I believe this should be possible for me. Please let me know what other information I need to provide, and thanks in advance! David _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users