Xen devel - Sep 2011 - Re: Virtualization Test Day for F16 and Xen

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).
>
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
>    ([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.
>    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@lists.xensource.com
http://lists.xensource.com/xen-devel

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.

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

> >    ([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.
> >    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@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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@lists.xensource.com
> > http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

KFT (KVM Faul Tolernace):
=======================
How it works:
-------------
* Provide Continuous availability to Mission Critical Applications with 
a ''Always Available'' environment preventing any downtime or
Data-loss in
the event of server-failures.
* RFT when enabled for a Virtual Machine creates a secondary copy of it 
on another physical server running KVM.
* The two copies are continuously synchronized by replaying the contents 
of the Memory from the primary VM to the Secondary (copy) VM. The 
Primary and the Secondary VM access the same storage device (shared 
storage) between the 2 servers.
* For example: If a user is playing a Youtube video on VM1, and the KVM 
Guest VM-1 crashes (due to some reason), The Secondary-slave copy 
becomes Active and promotes itself as Primary immediately when the 
vdsm-agent (communicating between the KVM-Host and the KVM-GuestVM-1) 
detects the server crash. This leads to creation of another secondary 
copy on the Next available physical server (obviously sharing the same 
storage with the now-active Primary-VM).
* Thus the GuestVM-2 (which was the secondary copy before the crash) 
---> is now known as VM-1 (and the new secondary copy on the newly 
available server is now known as VM-2).
* This can be achieved over qemu+ssh connections being managed by a 
single virt-manager as well.

Advantages:
-----------
* Zero Downtime: Fault Tolerance provides absolutely no downtime as that 
comapred to HA wherein the VM restarts completely on a different server.
* Immunity from Server crashes/panic/OOM situations.
* Extremely Fast Disaster Recover Mechanism.

Disadvantages:
--------------
* If a panic/crash takes place on the GuestVM being hosted on the KVM, 
This will be replicated on its Secondary-Copy, which is being hosted on 
other KVM''s.
   [ This can easily be avoided by having periodic snapshots of the 
Primary-VM ]

Currently Available Technologies:
---------------------------------
* Kemari: Fault Tolerance

Xen source: 
http://www.xen.org/files/xensummitboston08/tamura_xen_summit_presentation_final.pdf
KVM source: 
http://www.linux-kvm.org/wiki/images/0/0d/0.5.kemari-kvm-forum-2010.pdf
Kemari Project: http://www.osrg.net/kemari/

Please leave your valuable feedback for this.

Sincerely,
Anand Nande



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

>> 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 mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thu, 2011-09-15 at 10:10 -0500, W. Michael Petullo
wrote:
> >> 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.
So, there''s a meta-point here: we currently ''require''
Beta releases to
boot as guests on Xen hosts:

"The release must boot successfully as a virtual guest in a situation
where the virtual host is running a supported Xen implementation"

I really don''t have much knowledge of Xen and haven''t followed
this
discussion closely, but do any currently-known bugs prevent this? If so,
please flag them up so they can be considered as Beta blockers...thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Sep 15, 2011 at 03:38:09PM -0700, Adam Williamson
wrote:
> On Thu, 2011-09-15 at 10:10 -0500, W. Michael Petullo wrote:
> > >> 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?
I believe so (the irrelevant part). But the functionality part of grubby picking
up /etc/sysconfig/kernel and making that kernel the default is not in Grub2 - so
not sure how that can be addressed.
> > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=668063
> > 
> > I just added some more description to this bug.
> 
> So, there''s a meta-point here: we currently
''require'' Beta releases to
> boot as guests on Xen hosts:
> 
> "The release must boot successfully as a virtual guest in a situation
> where the virtual host is running a supported Xen implementation"
> 
> I really don''t have much knowledge of Xen and haven''t
followed this
> discussion closely, but do any currently-known bugs prevent this? If so,
> please flag them up so they can be considered as Beta blockers...thanks!
Somehow the xen-kbdfront driver is not included in the initrd image
(I think) - and we end with anaconda but can''t type anything. 
I''ve been trying
to figure out how to inject said module in the install initrd to see if that is
really the problem but running in roadblocks (like xz 5.1.1alpha or 5.0.3
complains
about corrupt image, or I''ve no idea how to make driver disks).

Any ideas?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi,

What Xen implementation is considered "supported" for FC16 DomU?
I''m asking
because on "Xen implementation" we were testing yesterday FC16 DomU
installation failed compared to FC15 DomU success on the very same Dom0. Are
failures like we''ve encountered candidates for bugreports?

Is there a place (wikipage, bugzilla keyword, etc.) to collect Fedora 16 Xen
issues?

Regards,

m.

On Fri, Sep 16, 2011 at 01:38, Adam Williamson <awilliam@redhat.com>
wrote:
> On Thu, 2011-09-15 at 10:10 -0500, W. Michael Petullo wrote:
> > >> 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.
>
> So, there''s a meta-point here: we currently
''require'' Beta releases to
> boot as guests on Xen hosts:
>
> "The release must boot successfully as a virtual guest in a situation
> where the virtual host is running a supported Xen implementation"
>
> I really don''t have much knowledge of Xen and haven''t
followed this
> discussion closely, but do any currently-known bugs prevent this? If so,
> please flag them up so they can be considered as Beta blockers...thanks!
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>


-- 
.....................................................................................................
Myroslav Opyr   ▪   CTO   ▪    Quintagroup   ▪   http://quintagroup.com
˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Fri, Sep 16, 2011 at 12:14:23PM +0300, Myroslav Opyr
wrote:
> Hi,
> 
> What Xen implementation is considered "supported" for FC16 DomU?
Any commonly available upstream Xen releases.

Fedora itself
(ie. https://fedoraproject.org/wiki/Features/XenPvopsDom0).

Also Xen in RHEL 5, although that''s more of a thing for Red Hat to
worry about.
> I''m asking because on "Xen implementation" we were
testing yesterday
> FC16 DomU installation failed compared to FC15 DomU success on the
> very same Dom0. Are failures like we''ve encountered candidates for
> bugreports?
Yes.
> Is there a place (wikipage, bugzilla keyword, etc.) to collect
> Fedora 16 Xen issues?
https://bugzilla.redhat.com/

Product: Fedora.  Component: depends on what is failing but common
ones would be "kernel", "anaconda", "grubby",
"grub2", "xen", and
"libvirt".

There is also a Fedora Xen mailing list where you can get more
detailed help:

https://lists.fedoraproject.org/mailman/listinfo/xen

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Fri, Sep 16, 2011 at 12:08:40PM +0100, Richard W.M. Jones
wrote:
> On Fri, Sep 16, 2011 at 12:14:23PM +0300, Myroslav Opyr wrote:
> > Hi,
> > 
> > What Xen implementation is considered "supported" for FC16
DomU?
> 
> Any commonly available upstream Xen releases.
> 
> Fedora itself
> (ie. https://fedoraproject.org/wiki/Features/XenPvopsDom0).
> 
I think Fedora itself currently has Xen 4.1.1 in F15 and F16.
> Also Xen in RHEL 5, although that''s more of a thing for Red Hat to
> worry about.
> 
Actually F16 PV domU fails to start with vfb (graphical console) on RHEL5 dom0,
the vfb never gets to fully initialized state.. so vncviewer won''t work
for the console.

F15 and earlier versions do work OK with pvfb on the same RHEL5 dom0.

I''ll report to redhat bugzilla soon..
> > I''m asking because on "Xen implementation" we were
testing yesterday
> > FC16 DomU installation failed compared to FC15 DomU success on the
> > very same Dom0. Are failures like we''ve encountered
candidates for
> > bugreports?
> 
> Yes.
> 
Yeah.. it could be the xen-kbdfront issue.. 
(it''s missing from the F16 installer kernel/initrd).

> > Is there a place (wikipage, bugzilla keyword, etc.) to collect
> > Fedora 16 Xen issues?
> 
> https://bugzilla.redhat.com/
> 
> Product: Fedora.  Component: depends on what is failing but common
> ones would be "kernel", "anaconda", "grubby",
"grub2", "xen", and
> "libvirt".
> 
> There is also a Fedora Xen mailing list where you can get more
> detailed help:
> 
> https://lists.fedoraproject.org/mailman/listinfo/xen
> 

-- Pasi

> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
> Read my programming blog: http://rwmj.wordpress.com
> Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
> http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 09/16/2011 01:43 AM, Konrad Rzeszutek Wilk wrote:
> On Thu, Sep 15, 2011 at 03:38:09PM -0700, Adam Williamson wrote:
>> On Thu, 2011-09-15 at 10:10 -0500, W. Michael Petullo wrote:
>>>>> 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?
> I believe so (the irrelevant part). But the functionality part of grubby
picking
> up /etc/sysconfig/kernel and making that kernel the default is not in Grub2
- so
> not sure how that can be addressed.
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=668063
>>> I just added some more description to this bug.
>> So, there''s a meta-point here: we currently
''require'' Beta releases to
>> boot as guests on Xen hosts:
>>
>> "The release must boot successfully as a virtual guest in a
situation
>> where the virtual host is running a supported Xen implementation"
>>
>> I really don''t have much knowledge of Xen and haven''t
followed this
>> discussion closely, but do any currently-known bugs prevent this? If
so,
>> please flag them up so they can be considered as Beta
blockers...thanks!
> Somehow the xen-kbdfront driver is not included in the initrd image
> (I think) - and we end with anaconda but can''t type anything. 
I''ve been trying
> to figure out how to inject said module in the install initrd to see if
that is
> really the problem but running in roadblocks (like xz 5.1.1alpha or 5.0.3
complains
> about corrupt image, or I''ve no idea how to make driver disks).
I saw the same thing and worked around it by booting with "vnc
lang=en_US.UTF-8 keymap=us" which eliminiates the need to enter anything
before it starts X on a vnc server.  But it doesn''t really address the
original problem.

I spent last Friday trying to get it to do an HVM install, but that
seemed to be very much a Xen problem.  It wouldn''t accept keyboard
input
or find its emulated devices properly until I added "acpi=off", or set
"acpi=0" in the Xen config.  But even then it refused to see my HD
image, even though the BIOS could list it.

I got stuck at that point, and am now (successfully) doing a PV install
(with the above workaround).

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> >> So, there''s a meta-point here: we currently
''require'' Beta releases to
> >> boot as guests on Xen hosts:
> >>
> >> "The release must boot successfully as a virtual guest in a
situation
> >> where the virtual host is running a supported Xen
implementation"
> >>
> >> I really don''t have much knowledge of Xen and
haven''t followed this
> >> discussion closely, but do any currently-known bugs prevent this?
If so,
> >> please flag them up so they can be considered as Beta
blockers...thanks!
I filled Bug 740378 - F16: Can''t use keyboard when installing F16-Alpha
under Xen (regression) as guest
which is pretty descripting what is below.

Also adding in Jeremy''s workaround in it.

Besides that, there is also
738085 - Patch to reduce spurious Xen entries in grub menu 

which has a patch to fix the grub2 menu-thingy..
> > Somehow the xen-kbdfront driver is not included in the initrd image
> > (I think) - and we end with anaconda but can''t type anything.
I''ve been trying
> > to figure out how to inject said module in the install initrd to see
if that is
> > really the problem but running in roadblocks (like xz 5.1.1alpha or
5.0.3 complains
> > about corrupt image, or I''ve no idea how to make driver
disks).
> 
> I saw the same thing and worked around it by booting with "vnc
> lang=en_US.UTF-8 keymap=us" which eliminiates the need to enter
anything
> before it starts X on a vnc server.  But it doesn''t really address
the
> original problem.
> 
> I spent last Friday trying to get it to do an HVM install, but that
> seemed to be very much a Xen problem.  It wouldn''t accept keyboard
input
> or find its emulated devices properly until I added "acpi=off",
or set
> "acpi=0" in the Xen config.  But even then it refused to see my
HD
> image, even though the BIOS could list it.
> 
> I got stuck at that point, and am now (successfully) doing a PV install
> (with the above workaround).
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 09/21/2011 01:03 PM, Konrad Rzeszutek Wilk wrote:
>>>> So, there''s a meta-point here: we currently
''require'' Beta releases to
>>>> boot as guests on Xen hosts:
>>>>
>>>> "The release must boot successfully as a virtual guest in
a situation
>>>> where the virtual host is running a supported Xen
implementation"
>>>>
>>>> I really don''t have much knowledge of Xen and
haven''t followed this
>>>> discussion closely, but do any currently-known bugs prevent
this? If so,
>>>> please flag them up so they can be considered as Beta
blockers...thanks!
> I filled Bug 740378 - F16: Can''t use keyboard when installing
F16-Alpha under Xen (regression) as guest
> which is pretty descripting what is below.
>
> Also adding in Jeremy''s workaround in it.
Though I couldn''t repro the general problems I was having - I later did
a clean F14 install with no problems.  So I don''t really know
what''s
going on here; I might try another F16 hvm install to see how it goes.

But there is a bona-fide bug that F16 doesn''t include xen-platform-pci
by default in its initramfs, so it ends up unplugging its emulated
devices without discovering the PV ones to replace them...
> Besides that, there is also
> 738085 - Patch to reduce spurious Xen entries in grub menu 
>
> which has a patch to fix the grub2 menu-thingy..
I''d noticed that - though at present I haven''t managed to get
F16 Xen to
boot in an hvm domain (it hangs when setting up interrupts in the nested
dom0).

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, Sep 21, 2011 at 03:46:31PM -0700, Jeremy Fitzhardinge
wrote:
> On 09/21/2011 01:03 PM, Konrad Rzeszutek Wilk wrote:
> >>>> So, there''s a meta-point here: we currently
''require'' Beta releases to
> >>>> boot as guests on Xen hosts:
> >>>>
> >>>> "The release must boot successfully as a virtual
guest in a situation
> >>>> where the virtual host is running a supported Xen
implementation"
> >>>>
> >>>> I really don''t have much knowledge of Xen and
haven''t followed this
> >>>> discussion closely, but do any currently-known bugs
prevent this? If so,
> >>>> please flag them up so they can be considered as Beta
blockers...thanks!
> > I filled Bug 740378 - F16: Can''t use keyboard when installing
F16-Alpha under Xen (regression) as guest
> > which is pretty descripting what is below.
> >
> > Also adding in Jeremy''s workaround in it.
> 
> Though I couldn''t repro the general problems I was having - I
later did
> a clean F14 install with no problems.  So I don''t really know
what''s
> going on here; I might try another F16 hvm install to see how it goes.
> 
> But there is a bona-fide bug that F16 doesn''t include
xen-platform-pci
> by default in its initramfs, so it ends up unplugging its emulated
> devices without discovering the PV ones to replace them...
Can you open a BZ at bugzilla.redhat.com please?

It might need to be assigned to the kernel team.
> 
> > Besides that, there is also
> > 738085 - Patch to reduce spurious Xen entries in grub menu 
> >
> > which has a patch to fix the grub2 menu-thingy..
> 
> I''d noticed that - though at present I haven''t managed to
get F16 Xen to
> boot in an hvm domain (it hangs when setting up interrupts in the nested
> dom0).
> 
>     J
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Sep 21, 2011 at 06:59:57PM -0400, Konrad Rzeszutek Wilk
wrote:
> On Wed, Sep 21, 2011 at 03:46:31PM -0700, Jeremy Fitzhardinge wrote:
> > On 09/21/2011 01:03 PM, Konrad Rzeszutek Wilk wrote:
> > >>>> So, there''s a meta-point here: we currently
''require'' Beta releases to
> > >>>> boot as guests on Xen hosts:
> > >>>>
> > >>>> "The release must boot successfully as a virtual
guest in a situation
> > >>>> where the virtual host is running a supported Xen
implementation"
> > >>>>
> > >>>> I really don''t have much knowledge of Xen
and haven''t followed this
> > >>>> discussion closely, but do any currently-known bugs
prevent this? If so,
> > >>>> please flag them up so they can be considered as Beta
blockers...thanks!
> > > I filled Bug 740378 - F16: Can''t use keyboard when
installing F16-Alpha under Xen (regression) as guest
> > > which is pretty descripting what is below.
> > >
> > > Also adding in Jeremy''s workaround in it.
> > 
> > Though I couldn''t repro the general problems I was having - I
later did
> > a clean F14 install with no problems.  So I don''t really know
what''s
> > going on here; I might try another F16 hvm install to see how it goes.
> > 
> > But there is a bona-fide bug that F16 doesn''t include
xen-platform-pci
> > by default in its initramfs, so it ends up unplugging its emulated
> > devices without discovering the PV ones to replace them...
> 
> Can you open a BZ at bugzilla.redhat.com please?
> 
Also should we change the default xen-platform-pci to =y in upstream Linux
.config to avoid having problems with every distro ?

-- Pasi

> It might need to be assigned to the kernel team.
> > 
> > > Besides that, there is also
> > > 738085 - Patch to reduce spurious Xen entries in grub menu 
> > >
> > > which has a patch to fix the grub2 menu-thingy..
> > 
> > I''d noticed that - though at present I haven''t
managed to get F16 Xen to
> > boot in an hvm domain (it hangs when setting up interrupts in the
nested
> > dom0).
> > 
> >     J
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thu, Sep 22, 2011 at 12:47:57PM +0300, Pasi Kärkkäinen
wrote:
> On Wed, Sep 21, 2011 at 06:59:57PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Wed, Sep 21, 2011 at 03:46:31PM -0700, Jeremy Fitzhardinge wrote:
> > > On 09/21/2011 01:03 PM, Konrad Rzeszutek Wilk wrote:
> > > >>>> So, there''s a meta-point here: we
currently ''require'' Beta releases to
> > > >>>> boot as guests on Xen hosts:
> > > >>>>
> > > >>>> "The release must boot successfully as a
virtual guest in a situation
> > > >>>> where the virtual host is running a supported
Xen implementation"
> > > >>>>
> > > >>>> I really don''t have much knowledge of
Xen and haven''t followed this
> > > >>>> discussion closely, but do any currently-known
bugs prevent this? If so,
> > > >>>> please flag them up so they can be considered as
Beta blockers...thanks!
> > > > I filled Bug 740378 - F16: Can''t use keyboard when
installing F16-Alpha under Xen (regression) as guest
> > > > which is pretty descripting what is below.
> > > >
> > > > Also adding in Jeremy''s workaround in it.
> > > 
> > > Though I couldn''t repro the general problems I was
having - I later did
> > > a clean F14 install with no problems.  So I don''t really
know what''s
> > > going on here; I might try another F16 hvm install to see how it
goes.
> > > 
> > > But there is a bona-fide bug that F16 doesn''t include
xen-platform-pci
> > > by default in its initramfs, so it ends up unplugging its
emulated
> > > devices without discovering the PV ones to replace them...
> > 
> > Can you open a BZ at bugzilla.redhat.com please?
> > 
> 
> Also should we change the default xen-platform-pci to =y in upstream Linux
> .config to avoid having problems with every distro ?
Or some form of it. Stefano is working to provide a patch that will latch
on CONFIG_PVONHVM and make that work.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thu, Sep 22, 2011 at 03:08:41PM -0400, Konrad Rzeszutek Wilk
wrote:
> On Thu, Sep 22, 2011 at 12:47:57PM +0300, Pasi Kärkkäinen wrote:
> > On Wed, Sep 21, 2011 at 06:59:57PM -0400, Konrad Rzeszutek Wilk wrote:
> > > On Wed, Sep 21, 2011 at 03:46:31PM -0700, Jeremy Fitzhardinge
wrote:
> > > > On 09/21/2011 01:03 PM, Konrad Rzeszutek Wilk wrote:
> > > > >>>> So, there''s a meta-point here: we
currently ''require'' Beta releases to
> > > > >>>> boot as guests on Xen hosts:
> > > > >>>>
> > > > >>>> "The release must boot successfully as
a virtual guest in a situation
> > > > >>>> where the virtual host is running a
supported Xen implementation"
> > > > >>>>
> > > > >>>> I really don''t have much knowledge
of Xen and haven''t followed this
> > > > >>>> discussion closely, but do any
currently-known bugs prevent this? If so,
> > > > >>>> please flag them up so they can be
considered as Beta blockers...thanks!
> > > > > I filled Bug 740378 - F16: Can''t use keyboard
when installing F16-Alpha under Xen (regression) as guest
> > > > > which is pretty descripting what is below.
> > > > >
> > > > > Also adding in Jeremy''s workaround in it.
> > > > 
> > > > Though I couldn''t repro the general problems I was
having - I later did
> > > > a clean F14 install with no problems.  So I don''t
really know what''s
> > > > going on here; I might try another F16 hvm install to see
how it goes.
> > > > 
> > > > But there is a bona-fide bug that F16 doesn''t
include xen-platform-pci
> > > > by default in its initramfs, so it ends up unplugging its
emulated
> > > > devices without discovering the PV ones to replace them...
> > > 
> > > Can you open a BZ at bugzilla.redhat.com please?
> > > 
> > 
> > Also should we change the default xen-platform-pci to =y in upstream
Linux
> > .config to avoid having problems with every distro ?
> 
> Or some form of it. Stefano is working to provide a patch that will latch
> on CONFIG_PVONHVM and make that work.
>
Ok, great!

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, Sep 21, 2011 at 04:03:49PM -0400, Konrad Rzeszutek Wilk
wrote:
> > >> So, there''s a meta-point here: we currently
''require'' Beta releases to
> > >> boot as guests on Xen hosts:
> > >>
> > >> "The release must boot successfully as a virtual guest
in a situation
> > >> where the virtual host is running a supported Xen
implementation"
> > >>
> > >> I really don''t have much knowledge of Xen and
haven''t followed this
> > >> discussion closely, but do any currently-known bugs prevent
this? If so,
> > >> please flag them up so they can be considered as Beta
blockers...thanks!
> 
> I filled Bug 740378 - F16: Can''t use keyboard when installing
F16-Alpha under Xen (regression) as guest
> which is pretty descripting what is below.
> 
> Also adding in Jeremy''s workaround in it.
> 
> Besides that, there is also
> 738085 - Patch to reduce spurious Xen entries in grub menu 
> 
> which has a patch to fix the grub2 menu-thingy..
> 
I also filed the F16 Xen pvfb problem on rhel5 dom0:

"Fedora 16 beta Xen pvfb graphical console does not work on rhel5
dom0":
https://bugzilla.redhat.com/show_bug.cgi?id=740657

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel