Re: [fedora-virt] [Xen-devel] Re: Virtualization Test Day for F16 and Xen

[Pasi Kärkkäinen]

On Wed, Sep 14, 2011 at 10:25:23AM -0400, Konrad Rzeszutek Wilk wrote:
>  On Wed, Sep 14, 2011 at 02:25:52PM +0300, Pasi Kärkkäinen wrote:
>  > On Sat, Sep 10, 2011 at 01:33:54AM +0300, Myroslav Opyr wrote:
>  > >    Hi,
>  > 
>  > Hello,
>  > 
>  > >    Virtualization Test day is expected to be on September 15th this year
>  > >    ([1]https://fedorahosted.org/fedora-qa/ticket/232).
>  
>  Cool.
>  > >
>  > 
>  > So that's tomorrow!
>  > 
>  > Luckily Xen Hackathon (@Munich) event is just happening,
>  > so hopefully we can get some more testing from people in that event.
>  > 
>  > >    We are willing to help test
>  > >    [2]http://fedoraproject.org/wiki/Features/XenPvopsDom0 but find too little
>  > >    information about test methods
>  
>  It really ought to be parallel to what you would do with KVM/QEMU. Basically
>  the same steps - but I am not sure how well does libvirt work with xm/xl nowadays.
>  Or the virt-manager - but it suppose to interact with magically.
>   
libvirt support for xm/xend *should* work, and there's also the libvirt libxl driver
written by Jim Fehlig from Novell/SUSE.


>  Is there a KVM/QEMU/libvirt help test Wiki? I saw this:
>  https://fedoraproject.org/wiki/Getting_started_with_virtualization
>  and it kind of parallels it, albeit I didn't see anything about setting the network
>  which sometimes is the biggest pain point:
>  
>  http://www.fedoraforum.org/forum/showthread.php?t=268427
>   
When you install libvirt it'll automatically create/start a bridge called
"virbr0",
which is an host-internal bridge with "dnsmasq" running and configured to
provide dhcp server
with private ip range, dns relay and NAT on that bridge.

So that's good enough for trying some VMs or running VM netboot installs.


>  
>  > >    ([3]https://fedorahosted.org/fedora-qa/ticket/219). It takes time for us
>  > >    to setup test environment, and would be good to have some info in advance.
>  
>  
>  There are known bugs in FC15/FC16 that have been filled some time ago that
>  folks will sadly run into: 728775, 658387  and 668063
>  
>  Fortunatly the bugs have patches attached and the files to be modified are shell
> scripts.
>   
Yep, links here:

https://bugzilla.redhat.com/show_bug.cgi?id=728775
https://bugzilla.redhat.com/show_bug.cgi?id=658387
https://bugzilla.redhat.com/show_bug.cgi?id=668063


-- Pasi


>  > >    Regards,
>  > >
>  > 
>  > I just added some Xen related mailinglists to the CC list,
>  > so we can get more feedback.
>  > 
>  > Thanks,
>  > 
>  > -- Pasi
>  > 
>  > 
>  > _______________________________________________
>  > Xen-devel mailing list
>  > Xen-devel(a)lists.xensource.com
>  > http://lists.xensource.com/xen-devel

Virtualization Test Day for F16 and Xen

[W. Michael Petullo]

> > There are known bugs in FC15/FC16 that have been filled some time
> ago that
> > folks will sadly run into: 728775, 658387  and 668063
> > 
> > Fortunatly the bugs have patches attached and the files to be modified are shell
> scripts. 
 
>  Yep, links here:
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=728775 
The Fedora update system reports this is fixed in grub2-1.99-6.fc16.

>  https://bugzilla.redhat.com/show_bug.cgi?id=658387 
Peter Jones submitted a new grubby package yesterday. This seems to fix
bug #658387 (i.e., new-kernel-pkg creates a Dom0-style grub.cfg entry
if /etc/sysconfig/kernel contains "HYPERVISOR=/boot/xen.gz").

I have not yet tested this on Fedora 16. However, I did test on Fedora
15. In this case, bug #668063 is still in effect. That is, grubby creates
most of a GRUB record, but the "module initramfs-..." entry is missing.

Has anyone yet tested this new grubby package on Fedora 16 yet? Does
using GRUB 2 makes #668063 irrelevant?

>  https://bugzilla.redhat.com/show_bug.cgi?id=668063 
I just added some more description to this bug.

-- 
Mike

:wq

[Xen-devel] Re: Virtualization Test Day for F16 and Xen / dom0 testing instructions

[Pasi Kärkkäinen]

On Wed, Sep 14, 2011 at 05:45:39PM +0300, Pasi Kärkkäinen wrote:
>  > 
>  > > >    ([3]https://fedorahosted.org/fedora-qa/ticket/219). It takes time for
> us
>  > > >    to setup test environment, and would be good to have some info in
> advance.
>  >  
Ok, so some basic steps to test Xen dom0 functionality in Fedora 16:

- Install Fedora 16 Beta TC2 host, to become Xen dom0. Installable ISO images available
here:
  http://alt.fedoraproject.org/pub/alt/stage/16-Beta.TC2/Fedora/ 

  (and LIVE ISO's here:
http://alt.fedoraproject.org/pub/alt/stage/16-Beta.TC2/Live/).

- Disk partitioning on the host: First partition should be /boot as ext3, 
  for the rest of the disk use LVM volume group, and remember to leave free space in the 
  volume group so you can later after installation create LVM volumes for the VMs.
  See these tutorials for an example about disk partitioning:

  http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial
  http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial

- After Fedora 16 is installed and everything works properly on baremetal, including
Internet access,
  proceed to installing Xen and virtualization related packages:

  yum install xen xen-hypervisor xen-runtime libvirt virt-manager virt-viewer
xorg-x11-xauth

- Enable automatic start of xend and libvirtd

  chkconfig xend on
  chkconfig libvirtd on

  chkconfig --list xend
  chkconfig --list libvirtd

- Add a suitable grub entry for Xen.

This grub entry is just an example, keep your own root device uuids/names etc and modify
to suit your setup:

menuentry 'Xen dom0, Fedora Linux 3.1.0-rc6' --class fedora --class gnu-linux
--class gnu --class os {
        load_video
        insmod part_gpt
        insmod ext2
        set root='(hd0,gpt2)'
        search --no-floppy --fs-uuid --set=root 6b84e53a-8a3a-4465-ac5a-c1c98758e448
        multiboot       /xen-4.1.gz placeholder dom0_mem=1024M loglvl=all guest_loglvl=all
console_to_ring cpuidle=xen
        echo    'Loading Linux 3.1.0-rc6 ...'
        module  /vmlinuz-3.1.0-rc6 root=/dev/mapper/VolGroup00-lv_root ro rd.md=0 rd.dm=0 
KEYTABLE=us debug loglvel=8 rd.lvm.lv=VolGroup00/lv_swap SYSFONT=latarcyrheb-sun16 
rd.luks=0 rd.lvm.lv=VolGroup00/lv_root LANG=en_US.UTF-8
        echo    'Loading initial ramdisk ...'
        module  /initramfs-3.1.0-rc6.img
}

grub entries will be automatically generated later, but currently grub/grubby does not
have all required patches to do it automatically.


- Reboot to Xen dom0!

- Verify Xen and xend works:

  xm info
  xm list

- Verify you have a bridge called "virbr0" (use: "brctl show"). It
should get created by libvirtd.
  There should be a "dnsmasq" process running for virbr0 providing that bridge a
DHCP server with private IPs,
  dns relay and NAT to internet, so you can use it for VM network installations.

- Install a Fedora 15 Xen PV domU:

  First create a new LVM volume for the VM:
  lvcreate -L30G -nf15_disk1 /dev/VolGroup00

  (Replace VolGroup00 with your VG name.. use "vgdisplay" to check.)

  Start actual installation:
  virt-install -d -n f15 -r 1024 --vcpus=1 -f /dev/VolGroup00/f15_disk1 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64/os/"

  (replace the URL with your local Fedora mirror site).
  virt-install will open a virt-viewer (VNC) graphical window of the guest console (pvfb)
where you can do the Fedora installation as usual.

- Install and test various other types of VMs, both PV and HVM.
- Try using file: disk backend (image files) aswell.
- Try using graphical "virt-manager" GUI to install Xen VMs.

- Disable automatic start of xend, reboot, and test xl / libxl, 
  also with virt-manager/virt-install.


That should get you started with testing. 

Btw. I noticed some issues installing F16 Alpha Xen PV domU, so F16 needs some more
investigation/debugging before F16 final.

-- Pasi