On Tue, Jul 28, 2009 at 12:39:17AM +0300, Pasi K?rkk?inen wrote: > On Tue, Mar 24, 2009 at 07:28:46PM +0000, Daniel P. Berrange wrote: > > On Tue, Mar 24, 2009 at 09:25:02PM +0200, Pasi K?rkk?inen wrote: > > > Hello! > > > > > > I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with > > > virt-install and/or virt-manager on Fedora 10, and now it seems I got things > > > working. > > > > > > If you want to play with this you need: > > > > > > 1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included > > > - Compile with CONFIG_HIGHPTE=n since it seems to be broken still > > > 2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing > > > > > > In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10. > > > > > > With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and > > > I had some other issues with virt-install console window not opening but stalling etc.. > > > > > > Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0: > > > > > > - CentOS 5.3 32bit PAE PV domU > > > - Fedora 10 32bit PAE PV domU > > > - Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart > > > to force PAE kernel installation to avoid the anaconda BUG which installs > > > wrong non-PAE kernel as a default). > > > > > > Fedora 11 (rawhide) installation most probably works too. > > > > FYI, I've just testing i686 and x86_64 Fedora 11 guest installs on a > > RHEL5 Xen host and they both work flawlessly out of the box - including > > a sane mouse pointer running in absolute, so no dual-cursor problems, > > and installing correect PAE kernels > > > > Replying to old thread.. today I tried installing F11 i386 domU with > virt-install on centos 5.3 x86_64 dom0, and it doesn't seem to work.. > > The graphical VNC console doesn't show up, and it seems the domU kernel > crashes. > > x86_64 domU installation on x86_64 dom0 seems to work though. > Are you sure i386 on x86_64 worked for you? Yep, just checked my RHEL-5 box and it has this config name = "f11i686xen" uuid = "1417ac4b-bd9a-61cc-6faf-8e842cd72cb9" maxmem = 900 memory = 500 vcpus = 1 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1" ] disk = [ "tap:aio:/var/lib/xen/images/f11i686.img,xvda,w" ] vif = [ "mac=00:16:3e:71:38:63,bridge=xenbr0" ] And the guest disk is fully instlaled # ls -lhs /var/lib/xen/images/f11i686.img 3.4G -rwxr-xr-x 1 root root 5.1G Jun 4 06:33 /var/lib/xen/images/f11i686.img FWIW, the guest kernel here is 2.6.29-0.258.rc8.git2.fc11.i686.PAE So its possible things have changed since I did my install .... Also my x86_64 host only has 2 GB of RAM, so if there's any bugs with i686 guests at the >4GB phys RAM mark I wouldn't have seen them Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
