http://permalink.gmane.org/gmane.linux.redhat.fedora.xen hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5780 <pre> That's good to hear. Xen 4.1.3 fixes many bugs, and obviously those fixes include something you were hitting :) Yeah, the "default" version currently is Xen 4.1.2. </pre> Pasi Kärkkäinen 2012-05-17T07:36:03 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5779 <pre> Resolved now, pkgdb lists myoung as the owner. Thanks, Cole -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Cole Robinson 2012-05-15T19:58:50 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5778 <pre> Great, I filed an infrastructure ticket: https://fedorahosted.org/fedora-infrastructure/ticket/3291 - Cole -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Cole Robinson 2012-05-15T18:25:20 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5777 <pre> Yes, it sounds good to me. Michael Young -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> M A Young 2012-05-15T17:57:28 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5776 <pre>+1. I thought Michael was already the (un?)official xen maintainer in Fedora! ;-) -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Don Dutile 2012-05-15T15:27:30 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5775 <pre> That sounds sensible to me Daniel </pre> Daniel P. Berrange 2012-05-15T15:26:18 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5774 <pre>Hey folks. Right now the package owner for xen in fedora is the xen-maint alias account. Originally this was an alias that was mapped to various &lt; at &gt;redhat folks who were doing xen development, and was used for both fedora and internal RHEL stuff. Nowadays it's not really used in upstream/fedora land and fedora-virt-maint is a better suited alias. Additionally &lt; at &gt;redhat isn't doing much xen work these days so we should just have a single package owner which reflects reality. So I propose we drop xen-maint as the package owner, and Michael can 'officially' take on package ownership. If that sounds fine I'll file a ticket with fedora infrastructure to make the change (required AFAIK for alias account changes). Michael, does that sound good to you? Thanks, Cole -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Cole Robinson 2012-05-15T15:24:52 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5773 <pre> 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. 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. Regards, Marko On 05/13/2012 08:42 PM, Marko Ristola wrote: ... ... ... -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Marko Ristola 2012-05-14T17:11:24 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5772 <pre> Thank you. I gave these options by appending -x "serial text console=hvc0" on the command line. Now, I get some text output, but something is wrong. I'm using a braile display and BRLTTY to access the screen content. When Anaconda prompts me to configure TCP/IP, for instance, I can't see any text, like "IP address", "DHCP" etc. The heading is displayed, and also the OK button if I tab to it. I further tried to add "nomodeset nofb console=force-text" as extra options, but I have the same result. I need a clean 80x25 text display. Any ideas? Lars -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Lars Bjørndal 2012-05-14T08:55:55 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5771 <pre> I am not particularly familiar with installing through libvirt, but I suggest you try giving anaconda the options serial text console=hvc0 Michael Young-- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> M A Young 2012-05-14T07:27:25 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5770 <pre>My approach is to install a DomU on top of a Fedora 16, 32 bit machine. I don't have any X running, so I need a real text install. Anaconda starts, but nothing happens after that. Below is the output. Hope someone can help. -------------------- [root&lt; at &gt;fox ~]# virt-install -l http://download.fedoraproject.org/pub/fedora/linux /releases/16/Fedora/i386/os --ram 512 --disk /var/lib/libvirt/images/f16.img,siz e=4 -n f16 --graphic none Starting install... Retrieving file .treeinfo... Retrieving file vmlinuz- Retrieving file initrd-PA Creating domain... Connected to domain f16 Escape character is ^] [ 0.000000] Reserving virtual address space above 0xf5800000 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.1.0-7.fc16.i686.PAE (mockbuild&lt; at &gt;x86-11.phx2.fedoraproject.org) (gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) ) #1 SMP Tue Nov 1 20:53:45 UTC 2011 [ 0.000000] ACPI in unprivileged domain disabled [ 0.000000] released 0 pa</pre> Lars Bjørndal 2012-05-14T06:11:37 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5769 <pre> Thanks for taking time for this. I have swithced on the Dom0 server into latest Fedora 17 RC this weekend. I had severe problems with non-Xen i386 non-PCIE rack server with NFS etc: IBM xSeries 306. It halted with latest Fedora 16 kernel about two minutes after successful boot. Before these problems, NFS server could livelock, if for example compiling or copying Kernel over NFS. 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. I haven't got the kernel message log yet. So the SELinux problem isn't now at the topmost on my list. (With another non-PCIE AMD motherboard disabling MSI interrupts and making motherboard use only interrupts &lt; 16, made it work with Fedora 16 without Dom0. As Dom0 it doesn't work). Regar</pre> Marko Ristola 2012-05-13T17:42:59 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5768 <pre> https://bugzilla.redhat.com/show_bug.cgi?id=801650 -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Konrad Rzeszutek Wilk 2012-05-10T16:22:46 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5767 <pre> I thought it was xen_disk_t? There are some slides by Walsh about what your need for LVM and Xen - see if Google comes up with anything. -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Konrad Rzeszutek Wilk 2012-05-10T15:42:01 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5766 <pre> How big is the packet. There is a bug we found in netback where a specific length of a packet causes netback to stall. Patches will be visible soon once we have run through all the regression tests. -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Konrad Rzeszutek Wilk 2012-05-10T15:36:21 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5765 <pre>I just install all the Xen-related updates (via yum) into FC17 Beta and reboot into Xen hypervisor...bug reported here: https://bugzilla.redhat.com/show_bug.cgi?id=820495 Please diagnose the problem. More info needed please let me know. thanks. </pre> Peter Teoh 2012-05-10T14:59:12 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5764 <pre>I have built 4.1.3-rc1 for F17 and it is temporarily available for testing at http://koji.fedoraproject.org/koji/taskinfo?taskID=4063767 . Michael Young -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> M A Young 2012-05-09T19:08:35 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5763 <pre>Hello M A Young writes: The package is required by foomatic, not cups. However, 'systemctl disable cups.service' and reboot, helped. Then the colord proscess isn't running. Starting cups with 'systemctl start cups.service' results in the process running again, and it's not stopped by 'systemctl stop cups.service'. Regards, Lars -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Lars Bjørndal 2012-05-05T20:43:13 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5762 <pre>Hello Konrad Rzeszutek Wilk writes: Thank you. I tried that, but got exactly the same error message. Do I miss some other parameters to virt-install? Regards, Lars -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Lars Bjørndal 2012-05-05T19:53:27 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5760 <pre> Thank you for the tips everyone! I will retest the FC17 beta as soon as find another hard drive... having some fun with VT-d right now. I've been trying vt-d on every new machine I've built or come across at work, and finally arrived on a home machine that does it, without having to run a "server" grade mobo and cpu (pretty close though). Specs: Core i7-3820 Sandy Bridge-E cpu 4 core, 8 thread Asus Sabertooth x79 main board 32gb ddr3-1600 ram Radeon HD7970 graphics adapter I'll post up my vt-d success story in a separate thread, but I was grinning ear to ear when it first started working. Gordon -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Gordon McLellan 2012-05-04T17:11:06 http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5759 <pre> If you are capturing logging with a photo, it can be helpful to add a boot_delay parameter eg. boot_delay=100 to the kernel line, particularly if the interesting lines scroll off the top of the screen before you can capture them. It does slow the boot down considerably though so you may need to adjust the parameter to get the balance right between it being slow enough to capture without taking ages to get to the crash. Michael Young -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> M A Young 2012-05-04T14:05:43 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.redhat.fedora.xen