[Fedora-xen] Re: Windows guest networking
Hi, On Fri, Feb 10, 2017 at 09:34:57PM -0500, W. Michael Petullo wrote: > Is anyone running a Windows HVM guest with networking? I recently tried > to connect a Windows 7 HVM guest to my network using vif-nat. For some > reason, the setup does not work. Oddly, Dom0 lists the vif interface > associated with the guest as "NO-CARRIER" even though the DomU Windows > guest seems to recognize its virtual network interface (RTL8139C+). > > I have no problem with a similarly configured guest running Linux. > > I am using: > > xen-4.7.1-6.fc25.x86_64 > > The guest configuration is: > > name = "windows64" > memory= 2048 > vcpus = 1 > builder = "hvm" > altp2mhvm = 1 > vif = [ "script=vif-nat,ip=10.0.0.2/32,gatewaydev=wlp3s0" ] > disk = [ "tap2:tapdisk:aio:/path/to/disk-windows64.img,xvda,w", > "tap2:tapdisk:aio:/path/to/spare-vfat.img,xvdb,w" ] > serial= "pty" > sdl = 1 > Does it work if you use the default vif bridge? If it does, then you could let libvirt setup virbr0 bridge which provides NAT without having to use vif-nat, or you could setup dnsmasq nat bridge yourself too. > -- > Mike > > :wq -- Pasi ___ xen mailing list -- xen@lists.fedoraproject.org To unsubscribe send an email to xen-le...@lists.fedoraproject.org
Re: [Fedora-xen] Upgrading from F20 to F21 domU are disappeared
On Thu, Feb 26, 2015 at 09:23:09AM +0100, Roberto Fichera wrote: On 02/25/2015 07:18 PM, Pasi Kärkkäinen wrote: Hi Pasi, On Wed, Feb 25, 2015 at 10:19:31AM +0100, Roberto Fichera wrote: Hi All, Hello, I've upgraded my F20 installation to F21, but all my xen domains are just disappeared against the new xl interface. BTW the domains are present in /var/lib/xend/domains/uuid/config.sxp, so my question is how can I migrate such domain to the new xen version? Well with xl you need to have the vm cfgfiles under /etc/xen/, so migrate the configs there, and create (start) the VMs. Yes! I know! But as you certain know using virt-manager this is not the case. In fact I don't have any cfg file with my /etc/xen directory. To export from libvirt to xen you can do (while still running xend+libvirt): virsh dumpxml vm vm.xml virsh domxml-to-native xen-xm vm.xml vm.cfg Note that with xl there's no similar mode as the xend managed mode was. Yep! BTW I've sorted out the problem by recreating by hand all the DomU starting from the related .sxp configuration files. Was a little boring, but now everything works ok. OK. -- Pasi Cheers, Roberto Fichera. -- Pasi Thanks in advance, Roberto Fichera. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Upgrading from F20 to F21 domU are disappeared
On Wed, Feb 25, 2015 at 10:19:31AM +0100, Roberto Fichera wrote: Hi All, Hello, I've upgraded my F20 installation to F21, but all my xen domains are just disappeared against the new xl interface. BTW the domains are present in /var/lib/xend/domains/uuid/config.sxp, so my question is how can I migrate such domain to the new xen version? Well with xl you need to have the vm cfgfiles under /etc/xen/, so migrate the configs there, and create (start) the VMs. Note that with xl there's no similar mode as the xend managed mode was. -- Pasi Thanks in advance, Roberto Fichera. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] f20 guest on centos5 xen host
On Fri, Jan 24, 2014 at 08:51:46AM +, Bruno Postle wrote: On Wed 22-Jan-2014 at 22:35 +, Bruno Postle wrote: On Tue 21-Jan-2014 at 21:57 +, Bruno Postle wrote: Though it now fails to come back up after yum update and reboot: [2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262) Domain has crashed: name=honk id=28. [2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM honk restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid loops. I have some more info on this second problem, the first problem is clearly the same as described in this patch/workaround: http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b298b8776d7ffc5fb1261e176f4 Now the system will come back up on reboot, but not if I upgrade the kernel on the guest (I can upgrade everything else). Any ideas? it is either that there is some new incompatibility between kernel 3.11.10 and 3.12.8 on f20, or pygrub on centos5 can't cope with two kernel entries. Further info, I did the obvious test here: I installed this new f20 kernel and removed the old f20 kernel entry from the grub.cfg file. The guest crashes, so I suppose the f20 3.12.8 kernel is incompatible with centos5 xen. Can you please paste the full domU kernel verbose debug output, so we can see what goes wrong? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] pci passthrough
On Tue, Apr 16, 2013 at 10:24:01AM -0700, Mike Wright wrote: Hi all, I need help debugging this situation. Running xen-4.2.1 with kernel 3.8.5-201.fc18.x86_64. I have successfully passed an on-board audio adapter to a VM running f14 but it does not work. When f14 runs on bare metal it has full audio capability. lspci on VM-f14 correctly shows: 1) Please compare lspci -vvv between baremetal and the VM 2) Is this a PV or HVM guest? 3) Any errors in the Xen dmesg (xm dmesg, or xl dmesg) 4) Did you try using pci-alignment for the audio card? -- Pasi 00:00.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40) lsmod | grep snd shows: snd_hda_codec_realtek 322852 1 snd_hda_intel 23945 2 snd_hda_codec 83791 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 6288 1 snd_hda_codec snd_seq52985 0 snd_seq_device 5969 1 snd_seq snd_pcm79886 2 snd_hda_intel,snd_hda_codec snd_timer 19363 2 snd_seq,snd_pcm snd63685 12 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer soundcore 6329 1 snd snd_page_alloc 7359 2 snd_hda_intel,snd_pcm All the pieces seem to be there. However, System-Preferences-Sound-Hardware is empty and System-Preferences-Sound-Output shows only Dummy Output, Stereo. Anybody know how to debug this? Right now I have to use Domain0 for multimedia, which seems to pervert the whole concept of keeping Domain0 away from general users. Please, Thanks, All of the above :) Mike Wright -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] howto hide pci devices?
On Wed, Mar 13, 2013 at 12:03:28PM +0100, Dario Faggioli wrote: On lun, 2013-03-11 at 15:54 -0400, Tom Horsley wrote: On Mon, 11 Mar 2013 12:15:47 -0700 Mike Wright wrote: Am I missing a step or is recompiling the kernel the only alternative? I don't know if this works, but often you have to re-run dracut so stuff like this gets copied into the initrd. Yes, I'm not an expert of initial ramdisks either, but I'd at least recommend rebuilding the initrd. Also, as Konrad is saying, I don't think one should expect for the device to disappear from lspci's output... It's just the driver that handles them which is different. Yeah, if you do lspci -vvv you'll see that driver in use changes to xen-pciback. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 18 and EFI
On Sat, Dec 15, 2012 at 06:47:29PM -0600, W. Michael Petullo wrote: I have successfully installed Fedora 18 Beta as Dom0 on one computer, and am now trying to do the same on another. I am using all of the standard Fedora 18 packages, including xen-4.2.0-6.fc18.x86_64. On the second computer, I ended up with an EFI grub2 install. I used yum to install xen, and noted that the package installation did not update /etc/grub2-efi.cfg. I ran grub2-mkconfig by hand, and this added Xen entries to /etc/grub2-efi.cfg. However, booting failed: grub2 complained that it did not know the multiboot keyword. Does anyone have experience getting EFI grub2 to boot Xen/Fedora 18? Is my trouble expected? Did you try native UEFI boot? So booting the xen.efi binary directly from UEFI ? Also note that F18 kernel doesn't have proper UEFI support for dom0 (yet), because it hasn't been upstreamed yet.. I eventually figured out how to install Fedora 18 using the MBR-style grub2. My Fedora 18 install media was a thumbdrive; what I discovered was that if I did *not* instruct my motherboard firmware's UEFI menu to boot from this USB device, then it seemed to pick it up as an old-style MBR boot instead. From that point on, Anaconda seemed to assume the computer had a BIOS, not UEFI. It appears the Fedora 18 install image supports both BIOS/MBR and UEFI, and the motherboard's firmware picks up the MBR if not explicitly asked to boot the device as UEFI. After picking through Anaconda and finding no option (i.e., a way to install using an MBR boot instead of a UEIF boot), I suspect I could achieve the same effect by manually creating an msdos partition table on the target hard drive instead of a GPT partition table. I think there's also nogpt boot/kernel cmdline option for the installer.. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 18 and EFI
On Fri, Dec 14, 2012 at 01:36:57PM -0600, W. Michael Petullo wrote: I have successfully installed Fedora 18 Beta as Dom0 on one computer, and am now trying to do the same on another. I am using all of the standard Fedora 18 packages, including xen-4.2.0-6.fc18.x86_64. On the second computer, I ended up with an EFI grub2 install. I used yum to install xen, and noted that the package installation did not update /etc/grub2-efi.cfg. I ran grub2-mkconfig by hand, and this added Xen entries to /etc/grub2-efi.cfg. However, booting failed: grub2 complained that it did not know the multiboot keyword. Does anyone have experience getting EFI grub2 to boot Xen/Fedora 18? Is my trouble expected? Did you try native UEFI boot? So booting the xen.efi binary directly from UEFI ? Also note that F18 kernel doesn't have proper UEFI support for dom0 (yet), because it hasn't been upstreamed yet.. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen 4.2 in rawhide
On Fri, Nov 30, 2012 at 10:53:12AM +0100, Dario Faggioli wrote: On Wed, 2012-11-28 at 00:25 +, M A Young wrote: I noticed today that a patch for libvirt to work with libxl from xen 4.2 has been sent to the libvir-list https://www.redhat.com/archives/libvir-list/2012-November/msg01119.html Cool! Although, changelog (and my recollection of a previous discussion about this) seems to suggest it is more about avoiding using the libxl-driver when Xen=4.1 than other things... Maybe Jim can give us more insights about it? Also Jim posted libvirt libxl Xen 4.2 patch V2: http://lists.xen.org/archives/html/xen-devel/2012-11/msg01973.html -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Fedora 18 virt test day rescheduled to Nov 01
On Sun, Sep 23, 2012 at 06:57:03PM -0400, Cole Robinson wrote: Hi all, The Fedora 18 virtualization test day has been moved to Thursday November 01. Given the 3 weeks of F18 delay, we readjusted the date to once again put us after the Beta, so we should have a solid base for testing. The (in progress) landing page for the test day is here: https://fedoraproject.org/wiki/Test_Day:2012-11-01_Virtualization So if think you can scrounge up a few cycles that day to try out F18 and all the virt goodness, please mark your calendars! Added xen@lists.fedoraproject.org to CC aswell. -- Pasi Thanks, Cole ___ virt mailing list v...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] Xen PCI passthru supported reset methods (d3d0, FLR, bus reset, link reset)
On Tue, Sep 18, 2012 at 01:19:31PM +0200, Robin Axelsson wrote: With a pvops dom0 Xen resets devices by writing to its reset node in sysfs so it will reset the device using whatever method the dom0 kernel supports for that device. And if you use Xen PCI-back it has this enabled so you don't even need the 'reset' functionality. The version of Linux I have to hand has, in __pci_dev_reset, calls to the following in this order and stops after the first one which succeeds: * pci_dev_specific_reset (AKA per device quirks) * pcie_flr * pci_af_flr * pci_pm_reset * pci_parent_bus_reset See drivers/pci/pci.c in the kernel for more info. IIRC classic Xen kernels had similar code in pciback, although I don't know which specific sets of actions or in which order they were tried. Ian. That sounds like great news, that means that FLR is not a requirement to successfully pass through hardware without errors, as is stated in the VTdHowTo page. So it seems that the VTdHowTo page needs to be updated with this information. Do you want to update the wiki page? :) -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 4.2 released!
On Mon, Sep 17, 2012 at 10:21:51PM +0100, M A Young wrote: I have a temporary build of xen-4.2.0 at http://koji.fedoraproject.org/koji/taskinfo?taskID=4493396 I would like to know a bit more about libvirt support for 4.2 before I do any proper releases as I know a lot of people use xen via libvirt. Great, thanks! That was fast :) -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 4.2 released!
- Forwarded message from Keir Fraser k...@xen.org - From: Keir Fraser k...@xen.org To: xen-de...@lists.xen.org Date: Mon, 17 Sep 2012 12:34:00 +0100 Subject: [Xen-devel] [ANNOUNCE] Xen 4.2 released! The Xen team is pleased to announce the release of Xen 4.2. The result of *18 months* of development, new features include: * Paging/sharing improvements for high-density VM environments (eg. VDI) * Enhancements to PV-HVM guest performance * Improved memaccess (guest introspection) support * EFI boot support, replacing the legacy BIOS boot environment * Improved RAS support * XL as the default toolstack; XEND officially deprecated * Upstream QEMU support, with its up-to-date feature list Detailed release notes, including a more extensive feature list: http://wiki.xen.org/wiki/Xen_4.2_Release_Notes To download tarballs: http://xen.org/download/index_4.2.0.html Or the Mercurial source repository (tag 'RELEASE-4.2.0'): http://xenbits.xen.org/hg/staging/xen-4.2-testing.hg And the announcement on the Xen blog: http://blog.xen.org/index.php/2012/09/17/xen-4-2-0-released/ Thanks to the many people who have contributed to this release! Regards, The Xen Team ___ Xen-devel mailing list xen-de...@lists.xen.org http://lists.xen.org/xen-devel - End forwarded message - -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Xen PCI passthru supported reset methods (d3d0, FLR, bus reset, link reset)
On Mon, Sep 17, 2012 at 01:51:03PM +0200, Robin Axelsson wrote: There is one thing I wonder though when it comes to PCI passthrough: Can Xen reset hardware through the d3d0 in the ACPI interface and/or through a 'bus reset' or a 'link reset'? Or can it reset hardware that is marked for passthrough only through FLR? For details see e.g. http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf I added xen-devel to the CC-list. Hopefully someone there can reply this question. -- Pasi Regards Robin. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 4.2.0-rc2 available to test
On Fri, Aug 17, 2012 at 09:44:56AM -0500, W. Michael Petullo wrote: I have done a temporary build of 4.2.0-rc2 for testing which is at http://koji.fedoraproject.org/koji/taskinfo?taskID=4386920 This also adds the efi hypervisor back in for x86_64. Note to other people: fedora kernels still don't have xen dom0 EFI patches included, mainly because dom0 EFI patches are not yet ported to pvops or merged to upstream Linux. So actually testing xen.efi hypervisor on UEFI systems is a bit tricky atm.. (you need to manually build a kernel based on the suse xenlinux sles11sp2 or opensuse patches). I have tried the 4.2.0-rc packages on three machines: one with an AMD Athlon X2, one with an AMD FX 4170 [1], and a MacBook with a Core 2 Duo. The first machine works fine. The FX 4170 and MacBook are unable to load Dom0. I see Xen print its boot messages, but the machines spontaneously reboot before Dom0 prints any output. [1] Same machine referenced at https://bugzilla.redhat.com/show_bug.cgi?id=841330 So did you use the stock Fedora kernel as dom0 kernel? Did you capture the boot/crash logs from the two machines? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen/Linux 3.4.2 performance
On Mon, Jul 02, 2012 at 04:50:42PM -0500, W. Michael Petullo wrote: We have seen a significant reduction in performance in our research DomU OS kernel when running on Fedora 16 with Linux 3.4.2 vs. 3.3.7. We run a series of benchmarks which are DomU-kernel-space-CPU-heavy; many of these run 10x slower when using the 3.4.2 Linux kernel as Dom0. This is a little surprising---we've been tracking the Fedora kernels for a long time with no problem like this. Did anyone else notice any changes? Just to verify.. both the 3.3.7 and 3.4.2 Linux kernel are 'release' builds? and not debug-versions from rawhide? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Not Displayed in Boot Menu
On Wed, Jun 27, 2012 at 10:40:01PM -0500, Jerry Amundson wrote: On Sat, Jun 9, 2012 at 6:37 AM, Pasi Kärkkäinen pa...@iki.fi wrote: On Fri, Jun 08, 2012 at 12:00:44AM -0700, sorabh hamirwasia wrote: Hi, I have installed Xen on Fedora16 host using yum install xen command and it has been installed properly. I can see the changes in /etc/grub2.cfg file too. But when I reboot then the entry for Xen is not listed in the boot menu. On further analyzing I found that in /etc/grub.conf there is no entry related to Xen. Do we need to modify grub.conf manually ? If yes then how to do that. ? Please help me with this. You can tweak the Xen hypervisor cmdline options in: /etc/default/grub file, like this: GRUB_DEFAULT=Xen The only thing I see in fc17 (also) is a set default=Xen line in /boot/grub2/grub.cfg I've been waiting, hoping, and did a fresh install of Fedora 17, then yum install xen, in anticipation (again) of Fedora/Xen/dom0 boot magic. Disappointment. And did you run grub2-mkconfig -o /boot/grub2/grub.cfg ? What's the problem? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-users] provisioning virtual machine
On Wed, Jun 27, 2012 at 05:51:13PM +0200, Arindam Choudhury wrote: I am using xen hypervisor in fedora 17. I want to use LVM storage for domU. LVM volumes work very well out-of-the-box as disks for Xen domUs. -- Pasi On Wed, Jun 27, 2012 at 5:12 PM, Joseph Hom [1]j...@softlayer.com wrote: What Xen are you using? OS? XCP? XenServer? Also what storage are you using? From: [2]xen-users-boun...@lists.xen.org [mailto:[3]xen-users-boun...@lists.xen.org] On Behalf Of Arindam Choudhury Sent: Wednesday, June 27, 2012 5:42 AM To: xen users Subject: [Xen-users] provisioning virtual machine Hi, I am trying to provision virtual machines to create a virtual machine cluster. If I try to transfer a pre-build virtual machine, its too time consuming and hard on network. So the idea of using bootstrap or kickstart seems better. Can any body point a good tutorial how to do this? Actually I have a master image and I have to copy it on all the nodes and create virtual machines. Is there any other way to do it? Regards, Arindam References Visible links 1. mailto:j...@softlayer.com 2. mailto:xen-users-boun...@lists.xen.org 3. mailto:xen-users-boun...@lists.xen.org -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] dom0 free memory and grub2
On Wed, Jun 27, 2012 at 05:58:56PM +0200, Arindam Choudhury wrote: Hi, I have installed xen on fedora 17 using yum. I have the well known problem on dom0 total_memory : 6075 free_memory: 644 I know I have to set dom0_mem=XXXG,max:XXXG and by recover the memory released. [1]link But how to do it with grub2? edit /etc/default/grub file add/edit lines: GRUB_DEFAULT=Xen GRUB_CMDLINE_XEN=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all Run grub2-mkconfig -o /boot/grub2/grub.cfg to update the configuration. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] provisioning virtual machines
On Wed, Jun 27, 2012 at 02:45:02PM +0300, Pasi Kärkkäinen wrote: On Wed, Jun 27, 2012 at 12:41:06PM +0200, Arindam Choudhury wrote: Hi, I am trying to provision virtual machines to create a virtual machine cluster. If I try to transfer a pre-build virtual machine, its too time consuming and hard on network. So the idea of using bootstrap or kickstart seems better. Can any body point a good tutorial how to do this? Actually I have a master image and I have to copy it on all the nodes and create virtual machines. Is there any other way to do it? A bit old but: http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial The stuff about installing VMs still applies to current Fedora versions. Oh, and of course you can pass a kickstart script for the domU installer so the installation is automatic. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Not Displayed in Boot Menu
On Fri, Jun 08, 2012 at 12:00:44AM -0700, sorabh hamirwasia wrote: Hi, I have installed Xen on Fedora16 host using yum install xen command and it has been installed properly. I can see the changes in /etc/grub2.cfg file too. But when I reboot then the entry for Xen is not listed in the boot menu. On further analyzing I found that in /etc/grub.conf there is no entry related to Xen. Do we need to modify grub.conf manually ? If yes then how to do that. ? Please help me with this. You can tweak the Xen hypervisor cmdline options in: /etc/default/grub file, like this: GRUB_DEFAULT=Xen GRUB_CMDLINE_XEN=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all .. or whatever options you want to use. After that update the grub menu: grub2-mkconfig -o /boot/grub2/grub.cfg -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 17 testing as Xen VM / Xorg issue
On Tue, May 29, 2012 at 11:15:52AM -0400, Konrad Rzeszutek Wilk wrote: On Mon, May 28, 2012 at 10:45:37PM +0300, Pasi Kärkkäinen wrote: Hello, I just did some installs with F17 RC4 (the GA version) as a Xen VM. Xen host/dom0: RHEL 5.8 x86_64 with the included Xen rpms. Tested F17 RC4 VMs: - 32bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb but Xorg fails to start during normal boot after installation. - 64bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb but Xorg fails to start during normal boot after installation. - 32bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC. Xorg fails to start during normal boot after installation. - 64bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC. Xorg fails to start during normal boot after installation. (PVHVM == HVM fully virtualized guest with optimized Xen PV drivers. Optimized Xen PVHVM drivers are nowadays included and used as a default with recent upstream Linux kernel versions (2.6.36+), so disk/net IO doesn't have to be emulated by Xen Qemu-dm.) I wonder if the problem with X failing to start is related to: http://fedoraproject.org/wiki/Features/DRI2DriversOnly Xen HVM guests have Qemu-dm emulated Cirrus VGA adapter (or stdvga) visible to the VM.. which doesn't have DRM/KMS drivers, and I think it's the same for xen-fbfront. I think I saw Cirrus (Qemu) DRM/KMS driver being worked on dri-devel mailinglist.. You are hitting https://bugzilla.redhat.com/show_bug.cgi?id=810040 I think. Yes, that was the problem with F17 PV domUs! After I remove fprintd and fprintd-pam rpms GDM works OK on the Xen pvfb and I can login to the desktop. However there's a different problem with F17 HVM guests. There Xorg doesn't start at all. X startup failed, falling back to text mode when I try to boot the F17 DVD installer .iso. Also Starting Show Plymouth Boot Screen... is [FAILED]. When I run X manually from the console I get this in Xorg.0.log: LoadModule: xaa Warning, couldn't open module xaa UnloadModule: xaa Unloading: xaa CIRRUS: Failed to load module xaa (module does not exist, 0) UnloadModule: cirrus .. Fatal server error: no screens found .. Server terminated with error (1). So it looks like Xorg requires xaa module for cirrus, but it's not there anymore. I guess this is related to the DRI2Only-feature in F17 ? http://fedoraproject.org/wiki/Features/DRI2DriversOnly -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Kernel Update for Xen Dom0
On Mon, May 28, 2012 at 04:22:50PM +0200, Steven G. Smith wrote: Hi, Is there a best practices procedure for updating the xen Dom0 environment (kernel)? The installation of Fedora 16 with xen 4 was a breeze and it has been running and performing well for ~ eight Months. Performing an update on the Dom0 kernel, however, does not seem to be covered in the standard documentation. Using Yum to update the kernel does not rebuild or change the xen.gz and the new kernel will not boot the xen dom0. Does anyone have any experience with this? I think you need to edit /etc/default/grub GRUB_DEFAULT=Xen GRUB_CMDLINE_XEN=dom0_mem=1024M loglvl=all guest_loglvl=all Or whatever settings you need for your environment. Then run: grub2-mkconfig -o /boot/grub2/grub.cfg That should do it. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Fedora 17 testing as Xen VM / Xorg issue
Hello, I just did some installs with F17 RC4 (the GA version) as a Xen VM. Xen host/dom0: RHEL 5.8 x86_64 with the included Xen rpms. Tested F17 RC4 VMs: - 32bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb but Xorg fails to start during normal boot after installation. - 64bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb but Xorg fails to start during normal boot after installation. - 32bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC. Xorg fails to start during normal boot after installation. - 64bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC. Xorg fails to start during normal boot after installation. (PVHVM == HVM fully virtualized guest with optimized Xen PV drivers. Optimized Xen PVHVM drivers are nowadays included and used as a default with recent upstream Linux kernel versions (2.6.36+), so disk/net IO doesn't have to be emulated by Xen Qemu-dm.) I wonder if the problem with X failing to start is related to: http://fedoraproject.org/wiki/Features/DRI2DriversOnly Xen HVM guests have Qemu-dm emulated Cirrus VGA adapter (or stdvga) visible to the VM.. which doesn't have DRM/KMS drivers, and I think it's the same for xen-fbfront. I think I saw Cirrus (Qemu) DRM/KMS driver being worked on dri-devel mailinglist.. Any ideas/comments? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 17 testing as Xen VM / Xorg issue
On Mon, May 28, 2012 at 10:45:37PM +0300, Pasi Kärkkäinen wrote: Hello, I just did some installs with F17 RC4 (the GA version) as a Xen VM. Xen host/dom0: RHEL 5.8 x86_64 with the included Xen rpms. Tested F17 RC4 VMs: - 32bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb but Xorg fails to start during normal boot after installation. - 64bit F17 PV domU: graphical GUI install works OK using the Xen vfb/pvfb but Xorg fails to start during normal boot after installation. - 32bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC. Xorg fails to start during normal boot after installation. - 64bit F17 PVHVM guest: X fails to start so VNC install must be used, install works OK thru VNC. Xorg fails to start during normal boot after installation. and I forgot to mention that all the installs above worked OK, and all the tested F17 Xen VMs do work OK, with text-mode console. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Boot errors, https://bugzilla.redhat.com/show_bug.cgi?id=804347
On Mon, May 14, 2012 at 08:11:24PM +0300, Marko Ristola wrote: Michael Young's latest Xen hypervisor build 4.1.3-rc1 seems to fix my Dom0 NFS server crash problem. Dom0 NFS server is as stable as with vanilla kernel. That's good to hear. Xen 4.1.3 fixes many bugs, and obviously those fixes include something you were hitting :) I booted Dom0 (standard Fedora 17 kernel) with serial console, with all debug flags turned on. Old problematic Xen hypervisor was the current Fedora 17 one. Yeah, the default version currently is Xen 4.1.2. -- Pasi Regards, Marko On 05/13/2012 08:42 PM, Marko Ristola wrote: ... So I took the Dom0 server as the NFS server and it has now Fedora 17. Motherboard: FUJITSU SIEMENS A8NE-FM 1011-005, two CPUs. On Fedora 17, without Dom0 the computer seems to work fine (once locked up during software RAID5 resync). While running as Dom0, using the NFSv4 kernel server (with idmap) will cause a kernel oops and reboot instantly. ... Regards, Marko ... -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Reminder: Fedora 17 virt test day going on right now!
On Thu, May 03, 2012 at 11:04:49AM -0400, Gordon McLellan wrote: Greetings, Is anyone running FC 17 beta as a Dom0 / DomU on Xen 4, on Sandy Bridge hardware? I've been trying and trying to get xen going on my new sandy-e system and have gotten the hypervisor to load but the dom0 kernel panics during boot. I dug up an old copy of FC 15, will try my luck there next. You probably should set up a serial console so you can actually capture the error/crash logs. http://wiki.xen.org/wiki/Xen_Serial_Console -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Installing Fedora 16 in Xen PV DomU under Debian Squeeze
On Mon, Dec 05, 2011 at 10:27:04PM -0500, Konrad Rzeszutek Wilk wrote: On Sun, Dec 04, 2011 at 02:36:46PM -0500, David Howland wrote: Hi, I recently installed Fedora 16 in a Xen PV DomU and since I didn't find a lot of information online, I wanted to share my procedure in case it helps anyone else. My Dom0 is Debian Squeeze, which uses a kernel at version 2.6.32. The pygrub issues you described were fixed and I believe are now in Xen 4.1.2. F16 PV domU pygrub support patches are in xen-unstable, but not yet in xen-4.1-testing.hg Fedora's xen 4.1.2 rpms do have those pygrub patches included, though. -- Pasi But that won't work for you since Debian is 4.0 I think. I think they can be back-ported. Would you be up for trying to back-port those patches and submit them to Debian Squeeze? (Just search for M A Young and pygrub on this mailing list - he posted the patches two months ago or so). Because I deal with varying operating systems and because I prefer fine-grained control over configuration, I don't use virt-* tools or GUI front ends. I wanted to install the OS the regular way. The basic install path was to use the live DVD to install in an HVM, then switch to a PV with pygrub. I want to use pygrub so that I don't have to copy kernels and init images around everytime the OS updates itself. pygrub caused me some trouble because the version in my system can't handle GPT partitions, grub2, or ext4 - all of which are used by default in Fedora 16. What follows isn't perfect, but should be useful for people who want to install Fedora 16 in an environment similar to mine. Note that I'm using x86_64 with VT-x, and that matters. Use your brain, and be careful to recognize newlines that email may introduce. *** Create hard drive image *** dom0# mkdir -p /img/fedora - you can put it anywhere you want! This is just what I used. dom0# cd /img/fedora dom0# dd if=/dev/zero of=xen-fedora-16.img bs=1M count=2 *** Download DVD image *** dom0# cd /img/fedora dom0# wget http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-DVD.iso *** Create HVM config file *** dom0# cd /etc/xen dom0# (edit fedora-16.hvm) -/etc/xen/fedora-16.hvm-- name = 'fedora-16' vif = [ 'mac=aa:00:00:50:02:f0, bridge=xenbr0' ] disk = [ 'file:/img/fedora/xen-fedora-16.img,hda,w', 'file:/img/fedora/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r', ] boot = 'dca' kernel = '/usr/lib64/xen-4.0/boot/hvmloader' device_model = '/usr/lib64/xen-4.0/bin/qemu-dm' builder = 'hvm' memory = 2048 shadow_memory = 8 vcpus = 2 #pae = 1 acpi = 1 apic = 1 vnc = 1 vncconsole = 1 sdl = 0 stdvga = 0 usbdevice = 'tablet' serial = 'pty' on_poweroff = 'destroy' on_reboot = 'destroy' on_crash= 'destroy' - *** Install Fedora 16 *** dom0# xm create fedora-16.hvm domU# (connect to new VM with a VNC viewer - Quickly!) domU# (press TAB at boot menu to edit the kernel command line) domU# (add nogpt to command line, without quotes) domU# (install fedora) - disable lvm - in partition list, change /boot to ext2 instead of ext4 - after install finishes, let it shut down dom0# (edit fedora-16.hvm) - comment out 'file:/img/fedora/Fedora-16-x86_64-DVD.iso,hdc:cdrom,r', dom0# xm create fedora-16.hvm domU# (complete install) - should be at desktop now *** Enable SSH *** domU# (open root shell) domU# systemctl enable sshd.service domU# systemctl start sshd.service *** Make a grub menu *** domU# cd /boot/grub domU# (edit menu.lst, using /boot/grub2/grub.cfg as a guide) - be sure to use your own kernal, init, and UUIDs from your own grub2 config -/boot/grub/menu.lst- -/etc/xen/fedora-16.hvm-- timeout 3 default 0 title Fedora Linux root (hd0,0) kernel /vmlinuz-3.1.2-1.fc16.x86_64 root=UUID=fc5702b1-65d9-426d-81d7-e52f31cb6a4a ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 initrd /initramfs-3.1.2-1.fc16.x86_64.img title Fedora Linux (recovery mode) root (hd0,0) kernel /vmlinuz-3.1.2-1.fc16.x86_64 root=UUID=fc5702b1-65d9-426d-81d7-e52f31cb6a4a ro single rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 initrd /initramfs-3.1.2-1.fc16.x86_64.img - *** Make PV domU *** domU# (shutdown VM) dom0# cd /etc/xen dom0# (edit fedora-16.pv) -/etc/xen/fedora-16.pv--- name = 'fedora-16' vif = [ 'mac=aa:00:00:50:02:f0, bridge=xenbr0' ] disk = [
Re: [Fedora-xen] xen broke my system
On Tue, Dec 06, 2011 at 07:14:57AM -0800, Carlos Felipe Santacruz wrote: This is what happened: normally ran 'yum install xen' and that gave no problems, but then i rebooted to get to the xen kernel, it resulted on black screen (could change consoles with Alt + F2 etc.) so i rebooted and tried the regular 3.1.2 kernel with same results. uninstalled xen with 'yum history undo' so it would also remove all dependencies then rebooted. nothing. anyone knows what could have caused this? im running f16 x86_64 on an asus g74sx-bbk7(core i7-2630qm, geforce gtx560m, 8GB DDR3 ram) So read your grub settings from /boot/grub2/ and figure out if you have some wrong or leftover entries there. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen build for testing
On Tue, Nov 08, 2011 at 12:56:57AM +, M A Young wrote: I have done a temporary test build xen-4.1.2-1.1 at http://koji.fedoraproject.org/koji/taskinfo?taskID=3495905 which contains patches from http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00218.html http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00321.html which I would like to test before putting them into a released version. If anyone else wants to test it, please let me know whether it works. There's an updated version of the second patch in here: http://old-list-archives.xen.org/archives/html/xen-devel/2011-11/msg01257.html and http://xenbits.xen.org/hg/staging/xen-4.1-testing.hg/rev/5a00ccfc6391 It fixes a bug with Linux 2.6.32 dom0 kernels. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [PATCH] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out)
On Wed, Nov 16, 2011 at 05:53:47PM +0200, Pasi Kärkkäinen wrote: On Wed, Nov 16, 2011 at 03:00:25PM +, Keir Fraser wrote: On 16/11/2011 13:33, Pasi Kärkkäinen pa...@iki.fi wrote: On Mon, Nov 14, 2011 at 05:47:11PM +, Ian Jackson wrote: Pasi Kärkkäinen writes (Re: [Xen-devel] [PATCH] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out)): So please go ahead and commit the fix to xen-4.1-testing.hg. Keir, will you do this ? If you prefer I can do it, but I need the blessing of a hypervisor maintainer. Ping? I responded on 3rd November: This looks like a backport of Stefano's xen-unstable c/s 24007. I would like him to submit/ack the backport, as it is not a trivial backport of the xen-unstable patch. Stefano already submitted a new patch for this.. .. which is here (Nov 7th): http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00321.html Both Konrad and I tested that patch with Xen 4.1.2, and it fixes the bug. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] [PATCH] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out)
On Tue, Nov 01, 2011 at 10:56:06PM +0200, Pasi Kärkkäinen wrote: On Mon, Oct 31, 2011 at 09:29:24PM +0200, Pasi Kärkkäinen wrote: On Mon, Oct 31, 2011 at 12:24:14PM -0700, Boris Derzhavets wrote: Seems to related https://bugs.launchpad.net/ubuntu/+source/xen/+bug/854829 Thanks, that seems to be the same bug. Is the bugfix patch from xen-unstable going to backported to xen-4.1-testing.hg ? (4.1 backported patch available on ubuntu's launchpad above..) So the Ubuntu backport from xen-unstable to Xen 4.1.1 is here: https://launchpadlibrarian.net/81948978/xen-pirq-resubmit-irq.patch It seems to be shipping in Ubuntu 11.10 xen 4.1.1-2ubuntu4.1 packages. Does that patch look suitable to be applied to xen-4.1-testing.hg ? This bug should be fixed for Xen 4.1.3. Any comments? -- Pasi Boris. --- On Mon, 10/31/11, Pasi Kärkkäinen pa...@iki.fi wrote: From: Pasi Kärkkäinen pa...@iki.fi Subject: [Xen-devel] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) To: xen-de...@lists.xensource.com Date: Monday, October 31, 2011, 2:49 PM Hello, While testing Xen 4.1.2 and HVM guests I noticed the following problem with Fedora 16 HVM guests (using Linux 3.1.0 kernel in the VM): The errors (call trace) happens pretty much immediately when there's some network traffic going on.. Simple yum update in the VM triggers the problem.. [0.00] Linux version 3.1.0-5.fc16.x86_64 ([1]mockbu...@x86-10.phx2.fedoraproject.org) (gcc version 4.6.1 20111003 (Red Hat 4.6.1-10) (GCC) ) #1 SMP Thu Oct 27 03:46:50 UTC 2011 [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.1.0-5.fc16.x86_64 root=/dev/mapper/vg_f16test64hvm-lv_root ro rd.lvm.lv=vg_f16test64hvm/lv_root rd.dm=0 SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=fi rd.md=0 rd.luks=0 rd.lvm.lv=vg_f16test64hvm/lv_swap LANG=en_US.UTF-8 console=ttyS0,38400 console=tty0 snip [ 28.998481] 8139cp :00:03.0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [ 149.712071] [ cut here ] [ 149.717216] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf0/0x150() [ 149.724709] Hardware name: HVM domU [ 149.728738] NETDEV WATCHDOG: eth0 (8139cp): transmit queue 0 timed out [ 149.735537] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_state ip6_tables nf_conntrack 81 39too 8139cp ppdev parport_pc mii parport i2c_piix4 i2c_core joydev [last unloaded: scsi_wait_scan] [ 149.768028] Pid: 0, comm: swapper Not tainted 3.1.0-5.fc16.x86_64 #1 [ 149.774639] Call Trace: [ 149.65] IRQ [81057a56] warn_slowpath_common+0x83/0x9b [ 149.784024] [81057b11] warn_slowpath_fmt+0x46/0x48 [ 149.790141] [813ef49d] ? netif_tx_lock+0x4a/0x7c [ 149.799007] [813ef613] dev_watchdog+0xf0/0x150 [ 149.806361] [81064b51] run_timer_softirq+0x19b/0x280 [ 149.814392] [81014fec] ? sched_clock+0x9/0xd [ 149.821650] [813ef523] ? netif_tx_unlock+0x54/0x54 [ 149.828926] [8105d6b3] __do_softirq+0xc9/0x1b5 [ 149.836803] [81014fec] ? sched_clock+0x9/0xd [ 149.843422] [814be5ec] call_softirq+0x1c/0x30 [ 149.850067] [81010b45] do_softirq+0x46/0x81 [ 149.856760] [8105d97b] irq_exit+0x57/0xb1 [ 149.863035] [812a39d3] xen_evtchn_do_upcall+0x31/0x3e [ 149.871144] [814be76e] xen_hvm_callback_vector+0x6e/0x80 [ 149.879494] EOI [8102f2f1] ? native_safe_halt+0xb/0xd [ 149.888220] [81015b7e] default_idle+0x4e/0x86 [ 149.894962] [8100e2ed] cpu_idle+0xae/0xe8 [ 149.901461] [814934ee] rest_init+0x72/0x74 [ 149.908949] [81b76b7d] start_kernel+0x3ab/0x3b6 [ 149.916617] [81b762c4] x86_64_start_reservations+0xaf/0xb3 [ 149.929148] [81b76140] ? early_idt_handlers+0x140/0x140 [ 149.936797] [81b763ca] x86_64_start_kernel+0x102/0x111 [ 149.944336] ---[ end trace d8786cb7d6a57f8a ]--- [ 149.950406] 8139cp :00:03.0: eth0: Transmit timeout, status d 3b 15 80ff [ 149.961879] [ cut here ] [ 149.962245] WARNING: at kernel/softirq.c:159 _local_bh_enable_ip+0x44/0x8e() [ 149.962245] Hardware name: HVM domU [ 149.962245] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4
Re: [Fedora-xen] F16 Xen dom0 SElinux problems with LVM volumes for domUs
On Tue, Nov 01, 2011 at 03:50:32PM +0200, Pasi Kärkkäinen wrote: On Mon, Oct 17, 2011 at 11:40:01AM -0600, Tim Flink wrote: On Sun, 16 Oct 2011 14:30:22 +0300 Pasi Kärkkäinen pa...@iki.fi wrote: Hello, I need to do setenforce 0 before I'm able to install Xen VMs with LVM volumes as disk backends.. Should I file a bugzilla entry about this? I wonder if you're hitting the same thing that I filed last week: - 745996 - AVC denials preventing start of Xen domain [1] I'm generating my DomUs outside of Xen, so I don't see it at install time but I'm wondering if they might be related. Are the AVC denials the same as the ones I listed there? Tim [1] https://bugzilla.redhat.com/show_bug.cgi?id=745996 So it looks different to your errors.. I'll file a new bug. Done: SElinux prevents installation of Xen PV domU with virt-install or virt-manager: https://bugzilla.redhat.com/show_bug.cgi?id=750535 Is the component xen correct one for that bug? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) [PATCH]
On Mon, Oct 31, 2011 at 09:29:24PM +0200, Pasi Kärkkäinen wrote: On Mon, Oct 31, 2011 at 12:24:14PM -0700, Boris Derzhavets wrote: Seems to related https://bugs.launchpad.net/ubuntu/+source/xen/+bug/854829 Thanks, that seems to be the same bug. Is the bugfix patch from xen-unstable going to backported to xen-4.1-testing.hg ? (4.1 backported patch available on ubuntu's launchpad above..) So the Ubuntu backport from xen-unstable to Xen 4.1.1 is here: https://launchpadlibrarian.net/81948978/xen-pirq-resubmit-irq.patch It seems to be shipping in Ubuntu 11.10 xen 4.1.1-2ubuntu4.1 packages. Does that patch look suitable to be applied to xen-4.1-testing.hg ? This bug should be fixed for Xen 4.1.3. -- Pasi Boris. --- On Mon, 10/31/11, Pasi Kärkkäinen pa...@iki.fi wrote: From: Pasi Kärkkäinen pa...@iki.fi Subject: [Xen-devel] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) To: xen-de...@lists.xensource.com Date: Monday, October 31, 2011, 2:49 PM Hello, While testing Xen 4.1.2 and HVM guests I noticed the following problem with Fedora 16 HVM guests (using Linux 3.1.0 kernel in the VM): The errors (call trace) happens pretty much immediately when there's some network traffic going on.. Simple yum update in the VM triggers the problem.. [0.00] Linux version 3.1.0-5.fc16.x86_64 ([1]mockbu...@x86-10.phx2.fedoraproject.org) (gcc version 4.6.1 20111003 (Red Hat 4.6.1-10) (GCC) ) #1 SMP Thu Oct 27 03:46:50 UTC 2011 [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.1.0-5.fc16.x86_64 root=/dev/mapper/vg_f16test64hvm-lv_root ro rd.lvm.lv=vg_f16test64hvm/lv_root rd.dm=0 SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=fi rd.md=0 rd.luks=0 rd.lvm.lv=vg_f16test64hvm/lv_swap LANG=en_US.UTF-8 console=ttyS0,38400 console=tty0 snip [ 28.998481] 8139cp :00:03.0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [ 149.712071] [ cut here ] [ 149.717216] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf0/0x150() [ 149.724709] Hardware name: HVM domU [ 149.728738] NETDEV WATCHDOG: eth0 (8139cp): transmit queue 0 timed out [ 149.735537] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_state ip6_tables nf_conntrack 81 39too 8139cp ppdev parport_pc mii parport i2c_piix4 i2c_core joydev [last unloaded: scsi_wait_scan] [ 149.768028] Pid: 0, comm: swapper Not tainted 3.1.0-5.fc16.x86_64 #1 [ 149.774639] Call Trace: [ 149.65] IRQ [81057a56] warn_slowpath_common+0x83/0x9b [ 149.784024] [81057b11] warn_slowpath_fmt+0x46/0x48 [ 149.790141] [813ef49d] ? netif_tx_lock+0x4a/0x7c [ 149.799007] [813ef613] dev_watchdog+0xf0/0x150 [ 149.806361] [81064b51] run_timer_softirq+0x19b/0x280 [ 149.814392] [81014fec] ? sched_clock+0x9/0xd [ 149.821650] [813ef523] ? netif_tx_unlock+0x54/0x54 [ 149.828926] [8105d6b3] __do_softirq+0xc9/0x1b5 [ 149.836803] [81014fec] ? sched_clock+0x9/0xd [ 149.843422] [814be5ec] call_softirq+0x1c/0x30 [ 149.850067] [81010b45] do_softirq+0x46/0x81 [ 149.856760] [8105d97b] irq_exit+0x57/0xb1 [ 149.863035] [812a39d3] xen_evtchn_do_upcall+0x31/0x3e [ 149.871144] [814be76e] xen_hvm_callback_vector+0x6e/0x80 [ 149.879494] EOI [8102f2f1] ? native_safe_halt+0xb/0xd [ 149.888220] [81015b7e] default_idle+0x4e/0x86 [ 149.894962] [8100e2ed] cpu_idle+0xae/0xe8 [ 149.901461] [814934ee] rest_init+0x72/0x74 [ 149.908949] [81b76b7d] start_kernel+0x3ab/0x3b6 [ 149.916617] [81b762c4] x86_64_start_reservations+0xaf/0xb3 [ 149.929148] [81b76140] ? early_idt_handlers+0x140/0x140 [ 149.936797] [81b763ca] x86_64_start_kernel+0x102/0x111 [ 149.944336] ---[ end trace d8786cb7d6a57f8a ]--- [ 149.950406] 8139cp :00:03.0: eth0: Transmit timeout, status d 3b 15 80ff [ 149.961879] [ cut here ] [ 149.962245] WARNING: at kernel/softirq.c:159 _local_bh_enable_ip+0x44/0x8e() [ 149.962245] Hardware name: HVM domU [ 149.962245] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_state ip6_tables nf_conntrack 8139too 8139cp ppdev parport_pc mii parport i2c_piix4 i2c_core joydev [last unloaded: scsi_wait_scan] [ 149.962245] Pid: 0, comm
Re: [Fedora-xen] [Xen-devel] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out)
On Mon, Oct 31, 2011 at 12:24:14PM -0700, Boris Derzhavets wrote: Seems to related https://bugs.launchpad.net/ubuntu/+source/xen/+bug/854829 Thanks, that seems to be the same bug. Is the bugfix patch from xen-unstable going to backported to xen-4.1-testing.hg ? (4.1 backported patch available on ubuntu's launchpad above..) -- Pasi Boris. --- On Mon, 10/31/11, Pasi Kärkkäinen pa...@iki.fi wrote: From: Pasi Kärkkäinen pa...@iki.fi Subject: [Xen-devel] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) To: xen-de...@lists.xensource.com Date: Monday, October 31, 2011, 2:49 PM Hello, While testing Xen 4.1.2 and HVM guests I noticed the following problem with Fedora 16 HVM guests (using Linux 3.1.0 kernel in the VM): The errors (call trace) happens pretty much immediately when there's some network traffic going on.. Simple yum update in the VM triggers the problem.. [0.00] Linux version 3.1.0-5.fc16.x86_64 ([1]mockbu...@x86-10.phx2.fedoraproject.org) (gcc version 4.6.1 20111003 (Red Hat 4.6.1-10) (GCC) ) #1 SMP Thu Oct 27 03:46:50 UTC 2011 [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.1.0-5.fc16.x86_64 root=/dev/mapper/vg_f16test64hvm-lv_root ro rd.lvm.lv=vg_f16test64hvm/lv_root rd.dm=0 SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=fi rd.md=0 rd.luks=0 rd.lvm.lv=vg_f16test64hvm/lv_swap LANG=en_US.UTF-8 console=ttyS0,38400 console=tty0 snip [ 28.998481] 8139cp :00:03.0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [ 149.712071] [ cut here ] [ 149.717216] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf0/0x150() [ 149.724709] Hardware name: HVM domU [ 149.728738] NETDEV WATCHDOG: eth0 (8139cp): transmit queue 0 timed out [ 149.735537] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_state ip6_tables nf_conntrack 81 39too 8139cp ppdev parport_pc mii parport i2c_piix4 i2c_core joydev [last unloaded: scsi_wait_scan] [ 149.768028] Pid: 0, comm: swapper Not tainted 3.1.0-5.fc16.x86_64 #1 [ 149.774639] Call Trace: [ 149.65] IRQ [81057a56] warn_slowpath_common+0x83/0x9b [ 149.784024] [81057b11] warn_slowpath_fmt+0x46/0x48 [ 149.790141] [813ef49d] ? netif_tx_lock+0x4a/0x7c [ 149.799007] [813ef613] dev_watchdog+0xf0/0x150 [ 149.806361] [81064b51] run_timer_softirq+0x19b/0x280 [ 149.814392] [81014fec] ? sched_clock+0x9/0xd [ 149.821650] [813ef523] ? netif_tx_unlock+0x54/0x54 [ 149.828926] [8105d6b3] __do_softirq+0xc9/0x1b5 [ 149.836803] [81014fec] ? sched_clock+0x9/0xd [ 149.843422] [814be5ec] call_softirq+0x1c/0x30 [ 149.850067] [81010b45] do_softirq+0x46/0x81 [ 149.856760] [8105d97b] irq_exit+0x57/0xb1 [ 149.863035] [812a39d3] xen_evtchn_do_upcall+0x31/0x3e [ 149.871144] [814be76e] xen_hvm_callback_vector+0x6e/0x80 [ 149.879494] EOI [8102f2f1] ? native_safe_halt+0xb/0xd [ 149.888220] [81015b7e] default_idle+0x4e/0x86 [ 149.894962] [8100e2ed] cpu_idle+0xae/0xe8 [ 149.901461] [814934ee] rest_init+0x72/0x74 [ 149.908949] [81b76b7d] start_kernel+0x3ab/0x3b6 [ 149.916617] [81b762c4] x86_64_start_reservations+0xaf/0xb3 [ 149.929148] [81b76140] ? early_idt_handlers+0x140/0x140 [ 149.936797] [81b763ca] x86_64_start_kernel+0x102/0x111 [ 149.944336] ---[ end trace d8786cb7d6a57f8a ]--- [ 149.950406] 8139cp :00:03.0: eth0: Transmit timeout, status d 3b 15 80ff [ 149.961879] [ cut here ] [ 149.962245] WARNING: at kernel/softirq.c:159 _local_bh_enable_ip+0x44/0x8e() [ 149.962245] Hardware name: HVM domU [ 149.962245] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_state ip6_tables nf_conntrack 8139too 8139cp ppdev parport_pc mii parport i2c_piix4 i2c_core joydev [last unloaded: scsi_wait_scan] [ 149.962245] Pid: 0, comm: swapper Tainted: G W 3.1.0-5.fc16.x86_64 #1 [ 149.962245] Call Trace: [ 149.962245] IRQ [81057a56] warn_slowpath_common+0x83/0x9b [ 149.962245] [813ce599] ? skb_release_data+0xca/0xcf [ 149.962245] [81057a88] warn_slowpath_null+0x1a/0x1c [ 149.962245] [8105d462] _local_bh_enable_ip+0x44/0x8e [ 149.962245] [8105d4ba] local_bh_enable_ip+0xe/0x10 [ 149.962245] [814b5db4
Re: [Fedora-xen] [Xen-devel] Xen 4.1.2 PVHVM guest with Linux 3.1.0 network problem, empty MAC address (all zeroes)
On Mon, Oct 31, 2011 at 10:13:36PM +0200, Pasi Kärkkäinen wrote: Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn't have any vifs/taps connected to it anymore. Has anyone seen that behaviour? I bet that's also the reason why eth0 inside the PVHVM guest has a MAC address with only zeroes in it: 00:00:00:00:00:00. If I disable PVHVM with xen_platform_pci=0 in the domain cfgfile then network for the guest works OK using the qemu-dm emulated nic. PVHVM guest cfgfile: snip Some output from inside the PVHVM guest: # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) snip Full PVHVM guest kernel (Linux 3.1.0) dmesg attached to this email. Some parts of the guest dmesg here: $ egrep -i 'xen|vif' xen-4.1.2-f16pvhvm-linux-3.1.0-dmesg.txt snip dom0 kernel (Linux 3.1.0 aswell) messages: snip xm log doesn't have any errors. Any ideas how to fix this? Why do the vif/tap devices disappear from dom0? Well.. it was actually as simple as removing type=ioemu from the vif line. Working vif-example for Xen PVHVM Linux guest VM: vif = [ 'mac=00:16:5f:03:01:15, bridge=virbr0, model=e1000' ] So uhm.. when enabling PVHVM there's no need to modify the disk line, but you need to modify the vif-line.. is that like it should be ? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Testing (and karma) needed for F16 enhancement xen-4.1.1-8.fc16 enhancement update
On Thu, Oct 20, 2011 at 10:00:31PM +0300, Pasi Kärkkäinen wrote: Hello, Michael patched xen-4.1.1-8.fc16 to support Fedora 16 default GPT partition tables, with Xen PV domUs using pygrub, so everyone please test the the new F16 xen rpms from updates-testing, and leave feedback (positive karma) so the package can move out of updates-testing. Bugzilla entry: https://bugzilla.redhat.com/show_bug.cgi?id=745335 And to leave feedback / add karma: https://admin.fedoraproject.org/updates/xen-4.1.1-8.fc16 Ok so: xen-4.1.1-8.fc16 has been pushed to the Fedora 16 stable repository. Thanks, -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Testing (and karma) needed for F16 enhancement xen-4.1.1-8.fc16 enhancement update
Hello, Michael patched xen-4.1.1-8.fc16 to support Fedora 16 default GPT partition tables, with Xen PV domUs using pygrub, so everyone please test the the new F16 xen rpms from updates-testing, and leave feedback (positive karma) so the package can move out of updates-testing. Bugzilla entry: https://bugzilla.redhat.com/show_bug.cgi?id=745335 And to leave feedback / add karma: https://admin.fedoraproject.org/updates/xen-4.1.1-8.fc16 Thanks, -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Positive experience updating Dom0 from f14/2.6.32/4.0.2 to f15/2.6.40/4.1
On Mon, Aug 15, 2011 at 06:54:32PM -0400, Bill McGonigle wrote: Just some notes, in case others are planning similar upgrades. I was running 2.6.32 from M. Young's repo. My goal was to get up to 2.6.40 on Fedora 15 (mainline dom0!) with minimal downtime. I found that f15's version of Xen (4.1) wouldn't run, even after re-compiling on f14. So, that couldn't be staged ahead of time. As a retreat plan, I made sure to have rpm's for Xen 4.0.2 handy, but they wound up being unnecessary. Hmm.. I'm running xen-4.1.1-2.fc15 on f14.. recompiled, of course, and it works for me.. I knew there'd be some xend breakage during the upgrade, so I opened ssh sessions to each VM. I then started the yum upgrade, first with yum and rpm, then only the fedora and updates repos, then other repos. Some package upgrade problems needed to be solved (I have too much in dom0), but nothing worse than usual. Once all the upgrades were in place, I hand-edited grub.conf since the new kernel installed a non-Xen entry. We need to get the grubby patch in to handle the dom0 entries.. At this point, I should have checked to see that my initramfs was made properly (it wasn't, locally packaged zfs modules broke the scriptlet). I had to come back in with rescue mode to re-run dracut. Once all the updates were installed, I shut down each of the VM's using native 'shutdown -h now' inside the vm. xm shutdown was broken at this point. Usually when upgrading Xen I first shut down the VMs, then upgrade dom0, reboot, and restart VMs. Now, the only ugly part is that systemd wasn't yet running, but 'reboot' is replaced. So, to reboot the system, I had to do 'sync;sync;sync [reset button]'. I had filesystems mounted -o data=journal, so I was at least feeling good about consistency. Some people wouldn't tolerate this option, but it worked out OK for me. Heh :) With a working initramfs, the system came up just fine, the VM's started as they should, and everything seemed OK from the Xen perspective. All the domU's function, no domU updates required (Fedora 12/13/14, CentOS 5). Good. If I had noticed the initramfs problem properly, I would have gotten away with only about a 4 minute outage. Quite glad to be re-united, after many years in the Fedora/Xen exile community! Much kudos to Michael Young, Pasi, and all the others who have helped up through the dark times. Thanks! There's still more patches to be merged in for 3.x, so remember to read the kernel changelogs or http://wiki.xen.org/xenwiki/XenParavirtOps and upgrade later :) All the big changes are already in mainline Linux, and it seems to work pretty OK, so it's good to continue from here. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Grubby fix isn't enough for Fedora 16: Fedora 16 uses Grub2
On Tue, Aug 16, 2011 at 09:03:19PM +0300, Marko Ristola wrote: Hi Hello, I've experimented with a fresh Fedora 16, Thanks for testing! I need to install F16 myself aswell.. I've installed Fedora 16 from nightly CD. Fedora 16 uses Grub2, so grubby fix isn't enough for dom0. Grub2 has Xen Dom0 config script as /etc/grub.d/20_linux_xen on Fedora 16. The script searches initrd-* files from /boot. It should search initramfs-* files too. Thus Dom0 will not be able to boot. I've written a bug report about that, maybe it is against Rawhide now, with a patch to apply. bz url? Another problem on Fedora 16 seems to be that while yum installs a new upgraded kernel, Xen Dom0 rows will not get generated. I don't know why. If /etc/grub.d/20_linux_xen works okay, grub2 config can be easilly fixed afterwards by hand with grub2-mkconfig. I've learned to switch from Grub1 to Grub2 with BIOS boot (not EFI). One way is to move partitions down so that there is 1MB or more disk space outside of partitions, just at disk start. Switching to grub2 isn't easy. Better plan and prepare or start from an empty hard disk before switching to grub2: Fresh Fedora 16 install into an empty hard disk (without partitions) does it all for you (creates a BIOS boot partition, which is an alternative to 1MB outside partition space). -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 16 Xen Dom0 problem
On Fri, Aug 05, 2011 at 08:49:02PM +0300, Marko Ristola wrote: Hi. I think that I hit to the following bug on 3.0 kernel on current Fedora 16. I can't get over it to boot Dom0 under Xen. Regards, Marko Ristola Subject: Re: [Xen-devel] Re: xen 4.1.1 with current linus tree as dom0 [ 0.00] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.00] IP: [810074d4] xen_set_pte+0x24/0xe0 http://lists.xensource.com/archives/html/xen-devel/2011-08/msg00113.html I *think* this is a known problem, and there is already a fix available/sent to lkml. So I suggest you to try again when 3.1 rc1/rc2 is released. Also it's best to report issues like this to xen-de...@lists.xensource.com mailinglist (subscription needed). Thanks, -- Pasi Here is my console output: snip [0.00] Movable zone start PFN for each node [0.00] early_node_map[3] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0004 [0.00] 0: 0x0010 - 0x0017fff0 (XEN) mm.c:907:d0 Error getting mfn 1b78 (pfn ) from L1 entry 81b78465 for l1e_owner=0, pg_owner=0 (XEN) mm.c:4967:d0 ptwr_emulate: could not get_page_from_l1e() [0.00] BUG: unable to handle kernel NULL pointer dereference at (null) [0.00] IP: [8100643d] __xen_set_pte+0x51/0x5b [0.00] PGD 0 [0.00] Oops: 0003 [#1] SMP [0.00] CPU 0 [0.00] Modules linked in: [0.00] [0.00] Pid: 0, comm: swapper Not tainted 3.1.0-0.rc0.git19.1.fc17.x86_64 #1 FUJITSU SIEMENS A8NE-FM/A8NE-FM [0.00] RIP: e030:[8100643d] [8100643d] __xen_set_pte+0x51/0x5b [0.00] RSP: e02b:81a01da8 EFLAGS: 00010096 [0.00] RAX: RBX: 880001e37ff8 RCX: 829ab000 [0.00] RDX: 1001 RSI: 81b78465 RDI: 880001e37ff8 [0.00] RBP: 81a01dc8 R08: R09: 7ff0 [0.00] R10: 7ff0 R11: 7ff0 R12: 81b78465 [0.00] R13: 4000 R14: R15: [0.00] FS: () GS:81b79000() knlGS: [0.00] CS: e033 DS: ES: CR0: 80050033 [0.00] CR2: CR3: 01a04000 CR4: 0660 [0.00] DR0: DR1: DR2: [0.00] DR3: DR6: DR7: [0.00] Process swapper (pid: 0, threadinfo 81a0, task 81a0c020) [0.00] Stack: [0.00] 829ab000 829ab000 880001e37ff8 81b78465 [0.00] 81a01df8 81006562 7ff0 ff5ff000 [0.00] 81b78465 4000 81a01e08 81032db4 [0.00] Call Trace: [0.00] [81006562] xen_set_pte+0x75/0x95 [0.00] [81032db4] set_pte+0x10/0x12 [0.00] [810332dd] set_pte_vaddr_pud+0x3c/0x4b [0.00] [81033361] set_pte_vaddr+0x75/0x7a [0.00] [810367ef] __native_set_fixmap+0x27/0x2f [0.00] [81005119] xen_set_fixmap+0x8c/0xbb [0.00] [81d54324] map_vsyscall+0x50/0x55 [0.00] [81d53a72] setup_arch+0xa7e/0xb2f [0.00] [814e9583] ? printk+0x51/0x53 [0.00] [81d4e8a3] start_kernel+0xe1/0x3ea [0.00] [81d4e2c4] x86_64_start_reservations+0xaf/0xb3 [0.00] [81d50f0f] xen_start_kernel+0x57f/0x586 [0.00] Code: df e8 18 04 03 00 48 89 c7 e8 7c ee ff ff 48 8d 7d e0 48 89 45 e0 4c 89 65 e8 e8 fd f4 ff ff bf 01 00 00 00 e8 a4 f7 ff ff eb 03 4c 89 23 58 5a 5b 41 5c 5d c3 55 48 89 e5 41 57 41 56 41 55 41 [0.00] RIP [8100643d] __xen_set_pte+0x51/0x5b [0.00] RSP 81a01da8 [0.00] CR2: [0.00] ---[ end trace a7919e7f17c0a725 ]--- [0.00] Kernel panic - not syncing: Attempted to kill the idle task! --- snip --- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Xen dom0 / Fedora 16 Schedule Reminders - Feature Submission and Feature Freeze
On Tue, Jul 12, 2011 at 07:53:11PM +0200, Alexander Boström wrote: tis 2011-07-12 klockan 12:08 +0300 skrev Pasi Kärkkäinen: Feature submission deadline for F16 is today.. It's on http://fedoraproject.org/wiki/Category:FeatureAcceptedF16 so it doesn't need to be submitted, right? Hmm, so it seems. Thanks for pointing that out! -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Xen dom0 / Fedora 16 Schedule Reminders - Feature Submission and Feature Freeze
On Tue, Jul 12, 2011 at 01:56:16PM -0300, Itamar Reis Peixoto wrote: On Tue, Jul 12, 2011 at 8:04 AM, Pasi Kärkkäinen pa...@iki.fi wrote: still missing - http://fedoraproject.org/wiki/Features/XenPvopsDom0 https://bugzilla.redhat.com/show_bug.cgi?id=658387 https://bugzilla.redhat.com/show_bug.cgi?id=668063 How about other related things: - grub/grubby/kernel integration? still missing Ok. Anyone working on this? Did someone try if the patches on those bugzillas still apply ok? - libvirt/virt-manager support? seems to work Good. Did you try with xm/xend or with xl/libxl? (libvirt has driver for both..) Do we need to get something fixed in those? Has someone tried the F16/rawhide Xen related rpms yet? Thanks, -- Pasi where I should report about dom0 problems ? in my machine dom0 is crashing after 5 minutes of boot. I think xen-devel mailinglist is the correct place. Please post full serial console logs, including both the hypervisor output and dom0 linux kernel output. See: http://wiki.xen.org/xenwiki/XenParavirtOps http://wiki.xen.org/xenwiki/XenSerialConsole -- Pasi -- Itamar Reis Peixoto msn, google talk: ita...@ispbrasil.com.br +55 11 4063 5033 (FIXO SP) +55 34 9158 9329 (TIM) +55 34 8806 3989 (OI) +55 34 3221 8599 (FIXO MG) -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] linux 3.0 rawhide crashing after 5 minutes when running as dom0
On Tue, Jul 12, 2011 at 04:44:42PM -0300, Itamar Reis Peixoto wrote: my rawhide kernel is crashing atfer some time. https://bugzilla.redhat.com/show_bug.cgi?id=720801 I think you should report (and first subscribe) to xen-de...@lists.xensource.com mailinglist.. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] linux 3.0 rawhide crashing after 5 minutes when running as dom0
On Tue, Jul 12, 2011 at 11:13:29PM +0300, Pasi Kärkkäinen wrote: On Tue, Jul 12, 2011 at 04:44:42PM -0300, Itamar Reis Peixoto wrote: my rawhide kernel is crashing atfer some time. https://bugzilla.redhat.com/show_bug.cgi?id=720801 I think you should report (and first subscribe) to xen-de...@lists.xensource.com mailinglist.. Oh, in the bugzilla you have posted a JPG picture. Please post the full serial console logs as text.. that makes it much easier to debug the problem. http://wiki.xen.org/xenwiki/XenParavirtOps http://wiki.xen.org/xenwiki/XenSerialConsole -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] How to use xen-pciback
On Mon, May 09, 2011 at 01:48:03PM +0200, Robin Axelsson wrote: On 2011-05-09 08:45, Pasi Kärkkäinen wrote: On Fri, May 06, 2011 at 04:18:14PM +0200, Robin Axelsson wrote: On 2011-05-06 08:03, Pasi Kärkkäinen wrote: On Thu, May 05, 2011 at 07:48:36PM +0200, Robin Axelsson wrote: Hi, I have compiled Jeremy's kernel on Fedora 14 and it turned out that xen-pciback is compiled into the kernel as a module. So I made a xen-pciback.conf file in /etc/modprobe.d. The problem is that I have to get modprobe to load before the drivers to the PCI devices I want to hide are loaded. So my question is how do I locate the drivers and find the points in the boot scripts where I can put the modprobe so that it is loaded before them? I tried lsmod and modinfo but they don't give much information. I only managed to find the driver for the Intel EXPI9400PT adapter e1000e. I want to hide the graphics adapter (Radeon 5450), Two USB2.0 ports, the Intel adapter, the USB3.0 controller and the Audio device, their assignments on machine are as follows: pci__00_02_0 (GPU) pci__00_12_0 (USB 2.0 should give 2 ports) pci__00_14_2 (Audio device) pci__00_0a_0 (Intel Adapter) pci__00_09_0 (USB 3.0 Interface) but the question is where can I locate their drivers and how can I tap into the boot sequence so that the xen-pciback driver is loaded beforehand? The page http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module gives no information about this. It mentions something about install skge ... but it doesn't say where this line is to be put and how you figure out that skge is the driver to be disabled. You probably should add the modules to be loaded from initrd image. Are you using mkinitrd? If yes, there's an option to preload modules.. -- Pasi I issued the command mkinitrd -v -f --preload xen-pciback /boot/initramfs-2.6.32.39.img 2.6.32.39 and I noticed that the initramfs image file generated is considerably smaller than the initramfs imagefile generated by dracut. The dracut file is a bit over 80 MB whereas the new one is less than 8 MB. But the preload doesn't load the xen-pciback module. After the reboot when I list assignable PCI devices using xm, Xen returns nothing. If I issue 'modprobe xen-pciback' and then list the devices using xm I get one entry. What's wrong? Hmm.. Is it possible that the other xen-related required modules are not yet loaded at that point, so loading xen-pciback fails? You could always extract initramfs-2.6.32.39.img and read the 'init' script in it and see what it's trying to do.. -- Pasi Perhaps you know how to extract the initramfs? I'm unable to find the compression headers and I'm not sure what headers to look for. In the first step I tried to locate the gzip header: They're usually gzipped cpio archives. So something like this should work: mkdir temp cd temp zcat /boot/initramfs-version.img | cpio -i -d -- Pasi # grep -a -b --only-matching $'\x8B'$'\x08' \boot\initramfs-`uname -r`.img (offset1): (pattern) ... (offsetn): (pattern) # dd if=/boot/intramfs-`uname -r`.img bs=1 skip=(offset1) | gunzip myimagefile but I'm unable to get to the cpio file. I tried once again grepping for compression headers in myimagefile but I couldn't find anything. It appears not to be compressed with zx, bzip2 or gzip. I could not use cpio on the file directly either. Robin. I have set up the machine to init level 3 in the /etc/inittab (my install of F14 have no upstart targets). The xen-pciback module seems to be working. Something is wrong with the onboard sound chip. No drivers have ever successfully initiated it, neither in Windows nor Linux. So it is marked as an assignable device when looking it up with xm. Regards Robin. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen . -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen . -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] How to use xen-pciback
On Thu, May 05, 2011 at 07:48:36PM +0200, Robin Axelsson wrote: Hi, I have compiled Jeremy's kernel on Fedora 14 and it turned out that xen-pciback is compiled into the kernel as a module. So I made a xen-pciback.conf file in /etc/modprobe.d. The problem is that I have to get modprobe to load before the drivers to the PCI devices I want to hide are loaded. So my question is how do I locate the drivers and find the points in the boot scripts where I can put the modprobe so that it is loaded before them? I tried lsmod and modinfo but they don't give much information. I only managed to find the driver for the Intel EXPI9400PT adapter e1000e. I want to hide the graphics adapter (Radeon 5450), Two USB2.0 ports, the Intel adapter, the USB3.0 controller and the Audio device, their assignments on machine are as follows: pci__00_02_0 (GPU) pci__00_12_0 (USB 2.0 should give 2 ports) pci__00_14_2 (Audio device) pci__00_0a_0 (Intel Adapter) pci__00_09_0 (USB 3.0 Interface) but the question is where can I locate their drivers and how can I tap into the boot sequence so that the xen-pciback driver is loaded beforehand? The page http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module gives no information about this. It mentions something about install skge ... but it doesn't say where this line is to be put and how you figure out that skge is the driver to be disabled. You probably should add the modules to be loaded from initrd image. Are you using mkinitrd? If yes, there's an option to preload modules.. -- Pasi I have set up the machine to init level 3 in the /etc/inittab (my install of F14 have no upstart targets). The xen-pciback module seems to be working. Something is wrong with the onboard sound chip. No drivers have ever successfully initiated it, neither in Windows nor Linux. So it is marked as an assignable device when looking it up with xm. Regards Robin. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] How to compile Jeremy's dom0 pvops kernel (2.6.32.x) on Fedora 15
On Tue, May 03, 2011 at 02:06:24AM +0200, Robin Axelsson wrote: Hi, I'm trying to compile Jeremy's paravirt_ops kernel on Fedora 15 using the following tutorial: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial but in the compilation process I get error messages that some .c and .h files are missing. I couldn't locate the packages that would house these files for Fedora 15 so I wonder how to compile it for F15. I want to use Jeremy's kernel because I need dom0 pciback drivers for using VGAPassthrough and PCIpassthrough. Hello, Please paste the actual build errors.. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] How to compile Jeremy's dom0 pvops kernel (2.6.32.x) on Fedora 15
On Tue, May 03, 2011 at 11:48:47AM +0200, Robin Axelsson wrote: On 2011-05-03 08:22, Pasi Kärkkäinen wrote: On Tue, May 03, 2011 at 02:06:24AM +0200, Robin Axelsson wrote: Hi, I'm trying to compile Jeremy's paravirt_ops kernel on Fedora 15 using the following tutorial: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial but in the compilation process I get error messages that some .c and .h files are missing. I couldn't locate the packages that would house these files for Fedora 15 so I wonder how to compile it for F15. I want to use Jeremy's kernel because I need dom0 pciback drivers for using VGAPassthrough and PCIpassthrough. Hello, Please paste the actual build errors.. -- Pasi . During compilation I see a lot of warnings: They are in pretty much every .../.../xyz.h file, the warnings are about variables that are set but not used. Perhaps this is normal. Then when things start to go haywire it begins with a couple of LDs on drivers/video/fb.o .../built-in.o and vmlinux.o followed by the command MODPOST that gives a warning that it found 10 section mismatches. It suggested that I should make with 'CONFIG_DEBUG_SECTION_MISMATCH=y' option/argument added. Then the final straw that breaks it all is when line 28 in Documentation/video4linux/v4lgrab.c refers to linux/videodev.h that doesn't exist which terminates the compilation. The cause of this seems to be that (according to an ubuntu bug report) the V4L1 API was removed in one of the Linux 2.6.38 pre-releases since v4l support has been dropped since kernel 2.6.35, and the linux/videodev.h header doesn't exist. Perhaps it compiles mediastreamer2/src/msv4l.c if either V4L1 or V4L2 is detected, and that file unconditionally includes linux/videodev.h. Two suggestions: - Did you try my reference .config file? - Do you have enough free disk space to build the kernel? -- Pasi A more detailed version showing the last couple of lines follows: include/linux/irq.h: In function â€?alloc_desc_masksâ€?: include/linux/irq.h:441:8: warning: variable â€?gfpâ€? set but not used [-Wunused-but-set-variable] In file included from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/smp.h:13:0, from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/mmzone_64.h:12, from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/mmzone.h:4, from include/linux/mmzone.h:796, from include/linux/gfp.h:4, from include/linux/kmod.h:22, from include/linux/module.h:13, from drivers/video/vesafb.c:11: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h: In function â€?native_apic_msr_readâ€?: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h:144:11: warning: variable â€?highâ€? set but not used [-Wunused-but-set-variable] /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h: In function â€?x2apic_enabledâ€?: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h:184:11: warning: variable â€?msr2â€? set but not used [-Wunused-but-set-variable] In file included from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/smp.h:13:0, from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/mmzone_64.h:12, from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/mmzone.h:4, from include/linux/mmzone.h:796, from include/linux/gfp.h:4, from include/linux/kmod.h:22, from include/linux/module.h:13, from drivers/video/efifb.c:9: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h: In function â€?native_apic_msr_readâ€?: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h:144:11: warning: variable â€?highâ€? set but not used [-Wunused-but-set-variable] /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h: In function â€?x2apic_enabledâ€?: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h:184:11: warning: variable â€?msr2â€? set but not used [-Wunused-but-set-variable] LD drivers/video/fb.o LD drivers/video/built-in.o LD drivers/built-in.o LD vmlinux.o MODPOST vmlinux.o WARNING: modpost: Found 10 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o In file included from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/smp.h:13:0, from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/mmzone_64.h:12, from /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/mmzone.h:4, from include/linux/mmzone.h:796, from include/linux/gfp.h:4, from include/linux/kmod.h:22, from include/linux/module.h:13, from init/version.c:10: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h: In function â€?native_apic_msr_readâ€?: /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h:144:11: warning: variable â€?highâ€? set but not used [-Wunused-but-set-variable] /home/xen_repo/linux-2.6-xen/arch/x86/include/asm/apic.h: In function â€?x2apic_enabledâ€?: /home/xen_repo/linux-2.6-xen/arch/x86
Re: [Fedora-xen] How to compile Jeremy's dom0 pvops kernel (2.6.32.x) on Fedora 15
On Tue, May 03, 2011 at 02:54:36PM +0200, Robin Axelsson wrote: On 2011-05-03 14:41, Pasi Kärkkäinen wrote: On Tue, May 03, 2011 at 11:48:47AM +0200, Robin Axelsson wrote: On 2011-05-03 08:22, Pasi Kärkkäinen wrote: On Tue, May 03, 2011 at 02:06:24AM +0200, Robin Axelsson wrote: Hi, I'm trying to compile Jeremy's paravirt_ops kernel on Fedora 15 using the following tutorial: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial but in the compilation process I get error messages that some .c and .h files are missing. I couldn't locate the packages that would house these files for Fedora 15 so I wonder how to compile it for F15. I want to use Jeremy's kernel because I need dom0 pciback drivers for using VGAPassthrough and PCIpassthrough. Hello, Please paste the actual build errors.. -- Pasi . During compilation I see a lot of warnings: They are in pretty much every .../.../xyz.h file, the warnings are about variables that are set but not used. Perhaps this is normal. Then when things start to go haywire it begins with a couple of LDs on drivers/video/fb.o .../built-in.o and vmlinux.o followed by the command MODPOST that gives a warning that it found 10 section mismatches. It suggested that I should make with 'CONFIG_DEBUG_SECTION_MISMATCH=y' option/argument added. Then the final straw that breaks it all is when line 28 in Documentation/video4linux/v4lgrab.c refers to linux/videodev.h that doesn't exist which terminates the compilation. The cause of this seems to be that (according to an ubuntu bug report) the V4L1 API was removed in one of the Linux 2.6.38 pre-releases since v4l support has been dropped since kernel 2.6.35, and the linux/videodev.h header doesn't exist. Perhaps it compiles mediastreamer2/src/msv4l.c if either V4L1 or V4L2 is detected, and that file unconditionally includeslinux/videodev.h. Two suggestions: - Did you try my reference .config file? - Do you have enough free disk space to build the kernel? -- Pasi - If you by using reference config mean executing the following lines (which are stated in the tutorial): # wget -O .config http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.25-pvops-dom0-xen-stable-x86_64 # make oldconfig # make clean # make -j4 bzImage make -j4 modules the answer is yes. Ok. - Yes I have enough disk space for the kernel and I think it is quite evident from the error messages I supplied in my prior post that this is not the problem. I asked because one of the errors looked like running out of disk space.. unifdef: /home/xen_repo/linux-2.6-xen/usr/include/xen/privcmd.h.tmp: 79: Premature EOF (#if line 33 depth 1) unifdef: output may be truncated -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] running xen without libvirt, etc
On Fri, Mar 25, 2011 at 03:09:18PM -0700, Mike Wright wrote: Hi all, Very confused as to which list I should post: xen, fedora, fedora-xen. Apologies if this is the wrong one. Pointer to the most appropriate list is welcome. Current system is f14 with full updates, myoung's kernel 2.6.32.+, booted with xen 4.0.1. Hardware is AMD with svm, lotsa ram. After fighting with the all-in-one GUIs for virtmanager I gave up and tried to recycle my configs from a 2006 box running xen3 (which still purrs) and can't even get past scripts/network-bridge without a hang or no bridges. I'm not asking for help on creating a vm, just on getting dom0 to recognize even one single bridge, even the default one. My feeling is that if I can get that far I can take it from here. Does anybody have a working example of a current xend-config.sxp for a machine running xend with f14? You should set up the networking (bridges) using *distro* network scripts, that has been the recommended way for a long time. So use /etc/sysconfig/network-scripts/ifcfg-br* to create bridges. The new xl/libxl toolstack in Xen 4.1.0 actually requires you to use distro network scripts. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 4.1 released!
- Forwarded message from Keir Fraser keir@gmail.com - From: Keir Fraser keir@gmail.com To: xen-de...@lists.xensource.com xen-de...@lists.xensource.com, xen-us...@lists.xensource.com Cc: Date: Fri, 25 Mar 2011 15:11:53 + Subject: [Xen-devel] [ANNOUNCE] Xen 4.1 released! The Xen team is pleased to announce the release of Xen 4.1. The result of nearly 12 months of development, new features include: * A re-architected and improved XL toolstack replacing XM/XEND * Prototype credit2 scheduler designed for latency-sensitive workloads and very large systems. * CPU Pools for advanced partitioning. * Support for large systems (255 processors) * Support for x86 Advanced Vector eXtension (AVX). * New Memory Access API enabling integration of 3rd party security solutions into Xen virtualized environments. * Many IOMMU fixes (both Intel VT-d IOMMU and AMD IOMMU). * Many toolstack and buildsystem fixes for Linux and NetBSD hosts. * Thirdparty libs: libvirt driver for libxl has been merged to upstream libvirt. * HVM guest PXE boot enhancements, replacing gPXE with iPXE. * Even better stability through our new automated regression tests. Detailed release notes, including a more extensive feature list: http://wiki.xen.org/xenwiki/Xen4.1 To download tarballs: http://xen.org/products/xen_source.html Or the Mercurial source repository (tag 'RELEASE-4.1.0'): http://xenbits.xen.org/xen-unstable.hg And the announcement on the Xen blog: http://blog.xen.org/index.php/2011/03/25/xen-4-1-releases/ Thanks to the many people who have contributed to this release! Regards, The Xen Team ___ Xen-devel mailing list xen-de...@lists.xensource.com http://lists.xensource.com/xen-devel - End forwarded message - -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Testing Xen dom0 for Fedora 15
On Fri, Mar 18, 2011 at 03:34:20PM -0600, Tim Flink wrote: I was wondering about the progress towards dom0 support in F15. The feature page [1] hasn't been updated for a while, so I'm not clear on how close the feature is to completion. Specifically, I am looking to find out what kind of testing has been done or is being done for this new feature. As far as I know, the Fedora QA community is not very aware of xen dom0 support and it isn't a part of the test cases that we have been running. If dom0 support is likely to be complete in time for F15, we would certainly welcome assistance in writing test cases and/or helping out with the upcoming virtualization test day on 2011-04-14 [2]. Hello, Quick dom0 kernel status update: - upstream Linux 2.6.38 has core xen dom0 support, but no backend drivers. - upcoming Linux 2.6.39 will have xen-netback driver (already merged in). - xen-blkback is planned for 2.6.40. - xen-pciback (for pci passthru) is planned for 2.6.40. That's the afaik list. There are also git branches available with the not-yet-upstream drivers included in 2.6.38 / 2.6.39, so those branches are usable as dom0 kernel. If running *pure* upstream Linux 2.6.38 as Xen dom0 kernel then you can't launch domUs due to missing backend drivers. When Linux 2.6.39 is released and used as dom0 kernel you can actually run domUs, *IF* running with Xen 4.1 hypervisor/tools, as Xen 4.1 contains userspace blkback driver (kind of a failback when kernel based xen-blkback is not available). Based on the info/plans at the moment upcoming Linux 2.6.40 should have all the important backend drivers merged into the kernel. I assume Fedora 15 will ship with 2.6.38 kernel? There was some discussions earlier if we could add the various xen backend drivers as additional patches for F15 kernel.. what was the end result of that discussion? -- Pasi Thanks, Tim [1] http://fedoraproject.org/wiki/Features/XenPvopsDom0 [2] https://fedoraproject.org/wiki/QA/Fedora_15_test_days -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] virtinst: do I have virtualization or not?
On Wed, Mar 16, 2011 at 08:24:31PM -0400, Cole Robinson wrote: On 03/16/2011 04:32 PM, Mike Wright wrote: On 03/16/2011 12:53 PM, Cole Robinson wrote: On 03/16/2011 03:00 PM, Mike Wright wrote: Hi all, Using f14-x86_64 installed from the LiveCD with myoung's f12-xendom0. It boots both standalone and with xen. /sys/hypervisor is populated. /proc/cpuinfo reports CPU is AMD Phenom II X4 B60 Black Edition. Virtualization is [ENABLED] in the BIOS. Thanks for the reply, Cole. Could help to provide the full /proc/cpuinfo output, as well as 'virsh --connect xen:/// capabilities' as root http://pastebin.com/t6pUs03p Well, seems like libvirt is reporting that you can indeed install fullvirt guests, so despite that error message in virt-manager things should work fine. I'm trying to add a virtual machine using Virtual Machine Manager 0.8.5 but when I select *New* I receive the following: Warning: Host does not appear to support hardware virtualization. Install options may be limited. According to this link (s.b. one line) it does. http://www.cpu-world.com/CPUs/K10/AMD-Phenom%20II%20X2%20560%20-%20HDZ560WFK2DGM%20%28HDZ560WFGMBOX%29.html;. Now according to another webpage the AMD processor must have the flag svm to have virtualization. My CPU does NOT have that flag but it does have one called hypervisor. Hmm, not sure what the hypervisor flag is, but virtinst is looking for vmx or svm reported in libvirt capabilities Could be as simple as adding hypervisor to the list of acceptable flags, but I wouldn't put a paycheck on that guess ;) After some googling, I found this debian bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604160 Seems like hypervisor just means you are booted into xen, and doesn't say anything about whether fullvirt is supported. Does booting into a regular kernel show svm in cpuinfo? Anything interesting in 'xm dmesg'? When running under Xen you need to use xm info and check the caps if you can run HVM (hardware virtualized) or not. Dom0 Linux kernel won't see the cpu flags in /proc/cpuinfo since dom0 is a VM, and the hypervisor is hiding the flags from VMs. (at least until Xen Nested Hw Virt is merged, which should be soon). Other option is to read xm dmesg for supported features: http://wiki.xen.org/xenwiki/XenCommonProblems#head-39c253c76df6f0fa4fb7ff4769cc733284bac9cb -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Another 2.6.38-rc6 dom0 kernel
On Mon, Mar 14, 2011 at 05:31:38PM +0200, Marko Ristola wrote: 13.03.2011 21:15, W. Michael Petullo kirjoitti: Here is another kernel (2.6.38-0.rc6.git6.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2874240 The crash when a domU shuts down seems to be fixed. I just had a chance to test this, along with the xen-4.1.0-0.1.rc6.fc14.x86_64 Xen packages. Two notable things have been fixed by the Xen folks: xl now plays nicely with the vif-route script (see /etc/xen/xl.conf). xl is less picky about where the -c argument to create goes. Both of these issues were previously discussed on this list and the xen-devel list. I'm still having trouble with power management, as noted at: http://lists.fedoraproject.org/pipermail/xen/2011-January/005328.html My computer doesn't power down either. This has been seen all the time. Under Xen hypervisor: power down doesn't work. Without hypervisor power down works with the same kernel. Do you see the same behaviour with 2.6.32.x based dom0 kernel aswell? -- Pasi Regards, Marko Other than that, my first impression of 2.6.38-0.rc6.git6.1.xendom0.fc15 is good. I was able to load a PV OpenWrt guest using the QEMU-based network backend. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc4 dom0 kernel
On Sun, Feb 13, 2011 at 11:17:00AM -0600, W. Michael Petullo wrote: I just booted 2.6.38-0.rc4.git3.1.xendom0.fc15 on xen-4.1.0-0.1.rc4.fc14.x86_64. I end up with the xen_netback kernel module loaded: $ lsmod | grep net xen_netback24607 0 [permanent] I'm not sure if this is what you were refering to by indeed the hack stops xen-netback loading... The latest dom0 kernel and the latest xen rc should work unaltered. The hack I referred to was an edit to a file from the xen rc to get the previous dom0 kernel working. I've looked more into my trouble, and it seems that xl does not want to play nicely with the vif-route script. First, the udev subsystem executes vif-setup after Xen creates the vif device. For some reason, this script does not have $script defined and so it defaults to vif-bridge. Once I changed it to run vif-route things went further. I'm not entirely sure how $script is supposed to be set, but it worked fine with xm. Next, vif-route did not pick up $ip from my domain configuration's vif = [ 'ip=w.x.y.z' ]. When using xm, vif-route would find $ip set properly and would create a route based on its value. I think you should report these issues to xen-devel mailinglist! -- Pasi Networking between Dom0 and DomU works with a modified vif-setup script and a manually added route. Once I get it going, networking seems to be stable. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Final F12 2.6.32.x dom0 kernel and vanilla 2.6.37-rc4
On Thu, Feb 10, 2011 at 01:55:57AM -0500, Bill McGonigle wrote: Hi, folks, Has anybody had luck using phy: disks with this version? With *what* version? :) I'm trying to create a new OpenSolaris DomU (nexenta 3.0.4) with two phy: devices, and instead of the expected behavior I'm seeing two disks show up, one as 0GB and one as 64510.04GB. file: devices seem to work OK. Disks are declared like: 'phy:/dev/disk/by-id/scsi-SATA_ST31500341AS_9VS41HND,xvda,w', Did you try with /dev/sdX ? That shouldn't change the behaviour but you never know.. -- Pasi Thanks, -Bill -- Bill McGonigle, Owner BFC Computing, LLC http://bfccomputing.com/ Telephone: +1.603.448.4440 Email, IM, VOIP: b...@bfccomputing.com VCard: http://bfccomputing.com/vcard/bill.vcf Social networks: bill_mcgonigle/bill.mcgonigle -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] link to download dom0 kernel for fedora 14 (minimum 2.6.35)
On Mon, Feb 07, 2011 at 03:50:34PM -0800, balaji pattewar wrote: Hi , I am trying to install XEN on Fedora 14 with linux kernel 2.6.35 or above as dom0. Can some body give link for XEN 4.01 RPM for Fedora 14 with linux dom0 kernel 2.6.35 and above. I try to search on link given in email Kozi but I am not able to downlad it. I am able to download Xen 4.01 but not kernel. Xen 4.0.1 rpms are included out-of-the-box in Fedora 14, just install using yum. For dom0 kernel: http://repos.fedorapeople.org/repos/myoung/dom0-kernel/fedora-12/ That 2.6.32 based dom0 kernel is the best bet for now. If you want to go very experimental, you could try the 2.6.38-rcX based kernels posted to this list. Can some body also have some tutorial for installing XEN on Fedora 14 will be appreciated. This tutorial is about installing from sources and/or src.rpms, but maybe it helps: http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Sun, Jan 30, 2011 at 11:52:56PM +, M A Young wrote: On Sun, 30 Jan 2011, W. Michael Petullo wrote: I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. It is supposed to be a direct replacement for xm, the idea being for configuration files for xm to work for xl, though not necessarily the other way around. In practice, you can still find stuff that doesn't yet work. With the exception that xl doesn't support embedded python code in the cfgfiles. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, Jan 27, 2011 at 05:03:57PM -0600, W. Michael Petullo wrote: Now, the last issue remaining for me is the backend drivers. My understanding is that, in the absence of backends being accepted upstream, we can use QEMU-based drivers. This would be acceptable for our work. Has anyone been using these with Fedora 15? In theory the block driver should work in 4.1.0, though I am not sure about the net driver. In practise I have failed so far to get the block driver working so far. This post today http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html talks about what block driver configurations should work. I have written the following domain config (to try to force the QEMU block backend): kernel = '/tmp/openwrt-x86-xen_domu-vmlinuz' memory =32 # NOTE: Generated with qemu-img convert -f raw -O qcow2 input.img output.qcow2 disk = [ 'tap:qcow2:/tmp/openwrt-x86-xen_domu-rootfs-ext2.qcow2,xvda,r', ] vif = [ 'bridge=virbr0' ] name = '2.6.38-DomU-Test' root = '/dev/xvda1' on_crash = 'destroy' When I boot, I get: [...] NET: Registered protocol family 17 802.1Q VLAN Support v1.8 Ben Greear gree...@candelatech.com All bugs added by David S. Miller da...@redhat.com Using IPI No-Shortcut mode XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s... When I try to use: disk = [ 'file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r', ] I get: [No boot] Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 Just making sure.. you're running Xen 4.1 ? The userspace qemu blkback implementation is *only* in Xen 4.1 .. And it should get used automatically if dom0 kernel blkback is not available. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Dom0 xen support in Fedora 15?
On Thu, Jan 20, 2011 at 09:34:50PM -0500, Bill McGonigle wrote: On 11/07/2010 03:55 PM, M A Young wrote: If the plan to get key xen drivers into 2.6.38 succeeds With the caveat that I don't really know what I'm looking for, I didn't see these make 2.6.38-rc1 (plenty of other Xen work, though). I saw a proposed patch for netback hit xen-devel yesterday. So, did we miss Fedora 15? Yep, netback most probably won't be in 2.6.38. Upstreaming of the various dom0 bits needs to be done step-by-step, the previous everything at once clearly didn't work. netback could always be added as an out-of-tree patch, or even some dkms module/rpm ? -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.37 dom0 kernel
On Fri, Jan 07, 2011 at 11:21:44PM +0200, Marko Ristola wrote: Hi I tried M A Young's precompiled 2.6.37 XEN kernel (under xen-4.0.1-6.fc14.x86_64, grub.conf modified. I have a Radeon card. I booted with and without modesetting, without success. I booted successfully with Radeon driver without acceleration. I'm sending this email from Dom0 :) Speed is as expected. Hello, Are you aware that upstream Linux 2.6.37 doesn't have the xen (dom0) drm/ttm/kms fixes yet? They were just posted to dri-devel and to lkml just a couples of days ago for review.. Konrad has a git tree with the patches applied, iirc .. Also Jeremy's xen/stable-2.6.32.x git tree has (most) of the patches applied. Also you might want to discuss these issues on xen-devel.. and report success/failures :) Thanks! -- Pasi Here is the bug report: Plain Radeon without any xorg.conf modifications on Fedora 14: Initially there was a graphical modesetting based startup. I switched from graphical startup progress graphics into text mode during boot: I could see textual progress messages during bootup. When X tried to start, Radeon kernel driver caused a page fault, that it couldn't handle. Full kernel stack trace was visible on the screen, and it could be looked up with Shift + page up / page down. Unfortunately I don't have time to take a log via serial port this weekend. With nomodeset, booting up progressed (disk IO heard), but the screen was blank all the time. I initiated a reboot from the keyboard. With modesetting with the bug, keyboard didn't work. I initiated a reboot via reset button. Here is the xorg.conf's part as a workaround for Radeon driver problem, /etc/xorg.conf.d/00-radeon.conf for Fedora 14: Section Device Identifier UseRadeon Driver radeon Option NoAccel true Option DRI false EndSection Section Monitor Identifier MyMonitor Option DPMS true EndSection Section Screen Identifier MyScreen Device UseRadeon Monitor MyMonitor EndSection Regards, Marko Ristola -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.37 dom0 kernel
On Thu, Jan 06, 2011 at 05:20:37PM +0200, Pasi Kärkkäinen wrote: On Wed, Jan 05, 2011 at 11:18:59PM +, M A Young wrote: There is a 2.6.37 kernel to test (2.6.37-1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2703408 I have had mixed success with this as the kernel package doesn't boot, but the kernel-debug package does boot to runlevel 3 (albeit with the couple of minutes delay which I have been seeing in the 2.6.37-rc kernels). 2.6.37-1.xendom0.fc15 x86_64 boots as dom0 for me! I'm using the F14 xen-4.0.1-6 as the hypervisor. The only problem is the display goes all blank when dom0 kernel is booted - I need to check what's going on. (yeah, I have nomodeset specified). Forget that, it seems even kms modesetting works with dom0_mem=1024M! -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Final F12 2.6.32.x dom0 kernel and vanilla 2.6.37-rc4
On Mon, Jan 03, 2011 at 12:05:33AM -0600, W. Michael Petullo wrote: This kernel works as expected with one exception. The exception has been a nagging problem, but I have not reported it because 1) we are using a research OS in DomU and 2) we are not clear if the problem is in our code, Linux or Xen. But, here are the symptoms: Occasionally (this seems to correlate to network activity between Dom0 and DomU), the system becomes unresponsive. I am running the Michael Young kernel at runlevel 3 within Dom0 (very little memory used by applications). Our OS runs in DomU and is constrained to 128MB of memory. When the system is unresponsive, typing a character into a Dom0 console take 2-5 seconds to appear on the screen. Likewise, other activity is extremely slow. As I mentioned, we have not been able to isolate where the problem is. Running, for example, an OpenWrt Linux build in DomU does not have this problem. I have seen something similar, though I don't know where the fault lies either. That is somewhat good to hear. I have today solved this problem by running xm vcpu-set Domain-0 1. By default, Xen assigned Dom0 all of my cores (two). Reducing this to one solves the problem for me. I am working on a better write up that I'll send to fedora-xen and possibly the upstream Xen mailing list. I have not decided if this is a bug and am having some discussions locally that may help me formulate a better inquiry. Usually it's better to use dom0_max_vcpus=1 on the grub xen.gz line. So, is this a known issue. Is it typically best practice to limit Dom0 to one core? I've seen systems where this is not a problem (dom0_max_vcpus=n works fine, where n is the number of cores) and others where it is. Why would this be? Some people want to dedicate cores for vms, so then it makes sense to also limit and pin dom0 vcpus to specific cores. It all depends on the workload. See: http://wiki.xensource.com/xenwiki/XenBestPractices -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.32.x dom0 kernel
On Mon, Dec 13, 2010 at 11:30:35AM +1100, Virgil wrote: Found this in /var/log/messages as the last thing prior to death. Clocksource tsc unstable Did some Googling and found some people changed the dom0 clocksource. Added clocksource=jiffies to the kernel commandline. I believe jiffies is not a very good clocksource.. -- Pasi Will see if it does anything. V On Wed, 17 Nov 2010 12:00:01 pm Virgil wrote: Host crashed. Running HVM fc14-32. Skipping 86000 seconds. Skipping 86000 seconds. Skipping 86000 seconds. Skipping 86000 seconds. Skipping 86000 seconds. Skipping 86000 seconds. Skipping 86000 seconds. ... ... ... ... Kaboom Cheers V On Mon, 8 Nov 2010 07:43:36 am M A Young wrote: I have built another 2.6.32.x based kernel (2.6.32.25-172.xendom0.fc12) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2583536 and the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ . This updates the kernel from 2.6.32.25-rc1 to 2.6.32.25 (which may not actually change anything), and uses a later version of xen/stable-2.6.3.32.x which adds a couple of xen fixes. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Final F12 2.6.32.x dom0 kernel and vanilla 2.6.37-rc4
On Thu, Dec 02, 2010 at 09:17:41PM +, M A Young wrote: On Thu, 2 Dec 2010, W. Michael Petullo wrote: Moving forward and for the purposes of Fedora 15 development, can we get both patched 2.7.37/38 kernels that support DomU and raw upstream kernels? Or does xen/next-2.6.27 not have the requisite features yet anyway? xen/next-2.6.37 doesn't currently have kernel drivers for either block or network backends. Userspace block or network backends may be possible but I don't know how to get them to work, though it is supposed to be possible. Userspace qemu xen_blkback is included in current xen-unstable (4.1), afaik. -- Pasi This kernel works as expected with one exception. The exception has been a nagging problem, but I have not reported it because 1) we are using a research OS in DomU and 2) we are not clear if the problem is in our code, Linux or Xen. But, here are the symptoms: Occasionally (this seems to correlate to network activity between Dom0 and DomU), the system becomes unresponsive. I am running the Michael Young kernel at runlevel 3 within Dom0 (very little memory used by applications). Our OS runs in DomU and is constrained to 128MB of memory. When the system is unresponsive, typing a character into a Dom0 console take 2-5 seconds to appear on the screen. Likewise, other activity is extremely slow. As I mentioned, we have not been able to isolate where the problem is. Running, for example, an OpenWrt Linux build in DomU does not have this problem. I have seen something similar, though I don't know where the fault lies either. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen and dom0 kernel builds
On Sun, Oct 03, 2010 at 10:46:49AM -0700, Boris Derzhavets wrote: Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA? That would be good.. The most recent yum update installs xen-4.0.1-4.fc14 on F14 ( rawhide) I think rawhide is currently F15.. F14 has been branched already. But yeah, I re-checked, and I noticed xen-4.0.1-4.fc14.src.rpm in F14 updates-testing. So all fine. Thanks! -- Pasi Boris. --- On Sun, 10/3/10, Pasi Kärkkäinen pa...@iki.fi wrote: From: Pasi Kärkkäinen pa...@iki.fi Subject: Re: [Fedora-xen] xen and dom0 kernel builds To: M A Young m.a.yo...@durham.ac.uk Cc: xen@lists.fedoraproject.org Date: Sunday, October 3, 2010, 11:59 AM On Fri, Sep 24, 2010 at 11:02:00PM +0100, M A Young wrote: I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at [1]http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the repository [2]http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ It includes fixes for the recent x86_64 local root exploit. There are also some new builds of xen. The Fedora packages xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via [3]http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ fixes that solve a problem I was having with a keyboard and mouse and the patch that disables xsave which was causing problems with HVM (both these are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from the place it was in 3.4.x to where it is in 4.0.x for compatibility. Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA? That would be good.. It seems the current F14 tree still has xen-4.0.1-1.fc14.src.rpm. I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at [4]http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the fixes above. Note that he build system will delete those RPMs automatically after a week or so. Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd like to mirror it, some people might want to get it also now when it's removed from that koji page.. -- Pasi -- xen mailing list [5]...@lists.fedoraproject.org [6]https://admin.fedoraproject.org/mailman/listinfo/xen References Visible links 1. http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 2. http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ 3. http://koji.fedoraproject.org/koji/packageinfo?packageID=7 4. http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 5. file:///mc/compose?to=...@lists.fedoraproject.org 6. https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel
Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS Hopefully this is helpful to someone! :) -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Stable Xen Dom0 and DomU via Fedora 12
On Tue, Jul 27, 2010 at 01:55:22AM +0800, Zhiqiang Ma wrote: Hi all, Our group are using Fedora (We updated the system to Fedora 12 recently) in our research cluster and we virtualize the computing resources using Xen. I have do a lot test and we finally settle on a stable Xen solution for our cluster. The test shows it is quite stable and we are satisfy with the virtual machine's performance. We use Xen 4.0.0 and Xenified Linux kernel 2.6.32.13 to set up Dom0 since Fedora 12 no longer provides kernel form Dom0: http://pkill.info/b/2252/setting-up-stable-xen-dom0-with-fedora-xen-4-0-0-with-xenified-linux-kernel-2-6-32-13-in-fedora-12/ Fedora 12's kernel is already pv_ops enabled. We are happy to install Fedora 12 in the virtual machine without any special configuration. All the packages are from Fedora's repository: http://pkill.info/b/2256/setting-up-stable-xen-domu-with-fedora-unmodified-fedora-12-on-top-of-xenified-fedora-12-dom0-with-xen-4-0-0/ I know both the Xen and the kernel are not the most latest ones. But the current ones are enough for us. Please give your comments on this solution. Your suggestions will be highly appreciated. Hello, Nice and very clear tutorials! Thanks! -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Newbie Q's xen kernel + others?
On Wed, Jul 07, 2010 at 11:50:23AM +0100, Frank Murphy wrote: Hi Couldn't find some info via google. F13 x86_64 Fedora no longer seems to have a kernel-xen. If I try add xen via Virt-Manager, I get no xen kernel. http://fedoraproject.org/wiki/Features/XenPvopsDom0 I already have qemu installed, If I get xen up and running can it also use the already installed *.img files? As the host is x86_64, it will only guest x86_64, correct? Xen supports 32-on-64, so you can run 32bit guests on 64bit hypervisor. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen 3.4.3 SRPM / console problem
On Wed, Jun 23, 2010 at 11:11:58AM +1000, Virgil wrote: Hi Pasi, Had a hiccup overnite: The host became unresponsive in a weird way. The time stopped incrementing. Turns out the clock stopped ticking (which I put down to the interrupts being disconnected). Anyway I decided I'd reset the time using 'time -s 10:41:30'. Kaboom, or actually deathly silence. The machine fully stopped dead in its tracks. Just prior to this I connected to the console of one of the 64PV machines which was just running a ping from yesterday. Anyway, 60,000 or so lines of pings went to the console zipping up the screen. Then it was dead. I did a CTRL-C and eventually it returned to the prompt. So I looked at the other 64PV machine, which was also pining, and identical situation. So I reckon, there's some kind of buffer overflow going on when you're not xm console MACHINE connected. Once you pass 60,000 lines of text this buffer overflow causes the RTC to hangup somehow. Do you have xenconsoled running? I've noticed PV guests that print a lot to the console will stall if xenconsoled is not running.. xenconsoled needs to clear the guest console buffer.. -- Pasi I pressed the reset button, but this time the 2 64PV machines are not logged in. I'll just let it go and see if it keeps going. Cheers V On Tue, 22 Jun 2010 04:29:06 pm Pasi Kärkkäinen wrote: On Tue, Jun 22, 2010 at 12:03:53PM +1000, Virgil wrote: Hi Pasi, On Mon, 21 Jun 2010 08:57:55 pm Pasi Kärkkäinen wrote: On Mon, Jun 21, 2010 at 01:56:36PM +0300, Pasi Kärkkäinen wrote: On Mon, Jun 21, 2010 at 02:28:15PM +1000, Virgil wrote: Another quick update xen-4.0.1-0.1.rc3.fc13.src.rpm just compiled this under fc12. Identical results with this too (i.e. it's probably in the kernel). I have a (silly) idea for the serial console. The wiki page recommends using a phone camera to capture the screen Well my idea is to add an n-millisecond delay every time the output stream in Xen sees a \n. This would delay the screen updates enough for the camera to see them. The n should be configurable on the kernel boot command line. It's set to 0 right now. Yeah, we really need to get a log somehow to troubleshoot your problem. Serial console log would be the best: http://wiki.xensource.com/xenwiki/XenSerialConsole Btw are you running the latest kernel: http://koji.fedoraproject.org/koji/taskinfo?taskID=2254110 Or are you running custom/self compiled kernel? Everything is working with: xen-4.0.1-0.1.rc3 compiled from source on fc12 machine and 2.6.32.14-1.2.107.xendom0.fc12.x86_64 from the myoung repo. All fixed. Good to hear it works! We also now have a null modem cable to another old computer with a COM port. Turns out I was the only old man that could remember what a null modem cable is. The young guy said wtf? Also turns out I'm the only one who knows what minicom is and what 8N1 means :-) Hehe.. yeah I guess young people don't get to play with serial consoles nowadays, until they're doing networking stuff.. So I guess most SOL devices in servers go unused.. :) -- Pasi All VMs are now running concurrently. Very happy again. Thanks. V -- Pasi Cheers V On Mon, 21 Jun 2010 12:10:17 pm Virgil wrote: Just a quick update: Just tried xen-4.0.0-2. Recompile from source on fc12.x86_64. identical behaviour. Cheers V On Fri, 18 Jun 2010 03:17:19 pm Virgil wrote: On Sat, 29 May 2010 11:26:50 pm M A Young wrote: If anyone wants to test xen 3.4.3, I have put up a source RPM at http://myoung.fedorapeople.org/dom0/src/xen-3.4.3-0.91.fc13. src.r pm Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen Hi list, Host crashing on 64FC12 kernel -105 dom0 when 2 PV64 machines are run. I can run HV32WinXP and HV32FC12 and 1 PV64FC12 all at the same time. However, when any combination involves 2 PV64FC12 (kernel version doesn't matter) the host crashes. Running on the -97 dom0 everything works in all combos. Using Xen 3.4.3. Turning off the virt network cards in the PV64FC12 machines makes things go (obviously not much use though). Tried disabling IPV6, firewall stuff etc. etc. Sometimes it would fire up and go but whichever machine is started second gets really long ping times like it's not receiving unless it sends something (if that makes
Re: [Fedora-xen] dom0 kernel and xen hypervisor
On Tue, Jun 01, 2010 at 10:26:26PM +0100, M A Young wrote: I have built a new dom0 kernel (kernel-2.6.32.14-1.2.105.xendom0.fc12) which is available from http://koji.fedoraproject.org/koji/taskinfo?taskID=2217291 or the repository http://fedorapeople.org/~myoung/dom0/ kernel-2.6.32.14-1.2.105.xendom0.fc12 works OK for me, with Xen 4.0.0, on Fedora 13. -- Pasi There are now some xen 3.4.3 builds you can test this with available from koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7 . If there are no problems with them I will start the process to push them out to F-12 and F-13 proper in a few days time. Rawhide should get the new rpms anyway, though I plan to move rawhide on to the 4.0.x branch soon. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions
On Wed, May 19, 2010 at 06:00:10AM -0700, Boris Derzhavets wrote: With 2.6.32.13 RH's PV guests (F13,RHL6 Beta tested) do detect NAT interface and can smoothly installed via virt-manager ( virt-install). However, Ubuntu Lucid Official xenified installer is still failing with NAT and requires old style network bridging, OSOL 134 behaves same way. Ubuntu 10.04 PV guest works just fine for me with NAT. -- Pasi Boris. --- On Tue, 5/18/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Tuesday, May 18, 2010, 2:11 AM So, installed Xen 4.0 via MY's src.rpm on top F13 i had to set up manually br0 for PV Guests, HVM seems to be OK with NAT ( or br0 no matter) # chkconfig NetworkManager off # chkconfig network on Reboot VNC console doesn't get launched for virt-installs of PV guests , referencing br0. Virt-install should run in nographics mode with VNC setup at DomU for Fedoras,CentOS guests. I might did something wrong, but at the moment Xen 4.0 / Virt-managerVirt-install regression vs F12 is taken place. Boris. --- On Mon, 5/17/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Monday, May 17, 2010, 11:49 PM I had to disable Xen bridging and setup bridge manually to be able to work with PV guests . In other words all xen bridged networking has to be commented out on F13 and at the same time PV guest cannot obtain IP via virbr0 It doesn't happen on F12. --- On Mon, 5/17/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Monday, May 17, 2010, 1:44 PM What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13 Libvirt 0.7.7 and all related stuff (virsh,virt-manager,virt-install) seem to work fine at Xen 4.0 Dom0 ( pvops 2.6.31.13) on top of F13. Even HVM install now could be performed via virt-manager. Auto detecting Xen Hypervisor and several attempts suggesting KVM answered negative make strong impression. I thought it would ask me to install KVM every time at virt-manager start. [r...@fedorasrv ~]# virsh version Compiled against library: libvir 0.7.7 Using library: libvir 0.7.7 Using API: Xen 3.0.1 Running hypervisor: Xen 4.0.0 Boris. --- On Sun, 5/16/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Sunday, May 16, 2010, 12:35 AM * I use virsh define to create the VM configurations using virsh xml, and I assume that virsh/libvirtd won't work on a recent 2.6.32/33/3x kernel and Xen 4.0.0 * Although Pasi, Michael, Dale and others have been very generous with their information, testing and development, I am not completely clear on all the steps required to get a working F12/F13/ Xen 4.0.X dom0 with 2.6.32/33/3x kernel starting from a base F12/F13 system install. If someone can point out where to find different parts I would be grateful and would be willing to consolidate them into a single blob if that doesn't already exist. Responding both questions (for F12) :- http://www.linuxtoday.com/high_performance/2010041500635OSSV What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13 Boris. -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org [1]https://admin.fedoraproject.org/mailman/listinfo/xen -Inline Attachment Follows- -- xen mailing list
Re: [Fedora-xen] Xen version for Fedora 13
On Thu, Apr 08, 2010 at 12:33:21AM +0300, Pasi Kärkkäinen wrote: On Fri, Mar 26, 2010 at 02:35:00PM +0200, Pasi Kärkkäinen wrote: On Thu, Mar 25, 2010 at 01:20:49PM -0400, Bill Davidsen wrote: Pasi Kärkkäinen wrote: Hello, Should we update Xen version to 4.0.0 (-rc7) for F13? All the new pvops dom0 kernel trees require the new IOAPIC stuff from either Xen 3.4.3 or 4.0.0 anyway. xen-4.0.0-rc7 src.rpm from M A Young seems to work OK for me: http://fedorapeople.org/~myoung/dom0/src/xen-4.0.0-0.5.rc7.fc12.src.rpm If you don't update you are stuck with the problems in the old version. If you update now you have a path to a working version. Xen 4.0.0 is expected to get final soon, so we could then update the final release for F13. What do you guys think? Doesn't look like a hard choice here, the alternatives are patch 3.4.3 to make it work right, or not get it in the release. I doubt it will get added if it isn't there to start, and patching obsolete code is pretty much a no-go, as well. Fedora is cutting edge, time to move. Yeah, I agree. Xen 4.0.0-rc8 is the latest release now, and it's supposed to be the last rc.. Gerd: Would you like to update the Fedora xen rpm? Xen 4.0.0 has been released now.. so we definitely should update to it for F13. Michael's src.rpm is available here: http://fedorapeople.org/~myoung/dom0/src/xen-4.0.0-0.7.fc12.src.rpm -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen version for Fedora 13
On Fri, Mar 26, 2010 at 02:35:00PM +0200, Pasi Kärkkäinen wrote: On Thu, Mar 25, 2010 at 01:20:49PM -0400, Bill Davidsen wrote: Pasi Kärkkäinen wrote: Hello, Should we update Xen version to 4.0.0 (-rc7) for F13? All the new pvops dom0 kernel trees require the new IOAPIC stuff from either Xen 3.4.3 or 4.0.0 anyway. xen-4.0.0-rc7 src.rpm from M A Young seems to work OK for me: http://fedorapeople.org/~myoung/dom0/src/xen-4.0.0-0.5.rc7.fc12.src.rpm If you don't update you are stuck with the problems in the old version. If you update now you have a path to a working version. Xen 4.0.0 is expected to get final soon, so we could then update the final release for F13. What do you guys think? Doesn't look like a hard choice here, the alternatives are patch 3.4.3 to make it work right, or not get it in the release. I doubt it will get added if it isn't there to start, and patching obsolete code is pretty much a no-go, as well. Fedora is cutting edge, time to move. Yeah, I agree. Xen 4.0.0-rc8 is the latest release now, and it's supposed to be the last rc.. Gerd: Would you like to update the Fedora xen rpm? Xen 4.0.0 has been released now.. so we definitely should update to it for F13. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
