<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.redhat.fedora.xen">
    <title>gmane.linux.redhat.fedora.xen</title>
    <link>http://blog.gmane.org/gmane.linux.redhat.fedora.xen</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5780"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5779"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5778"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5777"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5776"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5775"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5774"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5773"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5772"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5771"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5770"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5769"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5768"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5767"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5766"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5765"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5764"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5763"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5762"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5760"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5780">
    <title>Re: [Fedora-xen] Boot errors, https://bugzilla.redhat.com/show_bug.cgi?id=804347</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5780</link>
    <description>&lt;pre&gt;
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.

&lt;/pre&gt;</description>
    <dc:creator>Pasi Kärkkäinen</dc:creator>
    <dc:date>2012-05-17T07:36:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5779">
    <title>Re: [Fedora-xen] [xen-maint] Change xen package owner away fromxen-maint?</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5779</link>
    <description>&lt;pre&gt;
Resolved now, pkgdb lists myoung as the owner.

Thanks,
Cole

--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Cole Robinson</dc:creator>
    <dc:date>2012-05-15T19:58:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5778">
    <title>Re: [Fedora-xen] Change xen package owner away from xen-maint?</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5778</link>
    <description>&lt;pre&gt;
Great, I filed an infrastructure ticket:

https://fedorahosted.org/fedora-infrastructure/ticket/3291

- Cole
--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Cole Robinson</dc:creator>
    <dc:date>2012-05-15T18:25:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5777">
    <title>Re: [Fedora-xen] Change xen package owner away from xen-maint?</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5777</link>
    <description>&lt;pre&gt;

Yes, it sounds good to me.

 Michael Young
--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>M A Young</dc:creator>
    <dc:date>2012-05-15T17:57:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5776">
    <title>Re: [Fedora-xen] [xen-maint] Change xen package owner awayfromxen-maint?</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5776</link>
    <description>&lt;pre&gt;+1.  I thought Michael was already the (un?)official xen maintainer in Fedora!  ;-)


--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Don Dutile</dc:creator>
    <dc:date>2012-05-15T15:27:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5775">
    <title>Re: [Fedora-xen] Change xen package owner away from xen-maint?</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5775</link>
    <description>&lt;pre&gt;
That sounds sensible to me


Daniel
&lt;/pre&gt;</description>
    <dc:creator>Daniel P. Berrange</dc:creator>
    <dc:date>2012-05-15T15:26:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5774">
    <title>[Fedora-xen] Change xen package owner away from xen-maint?</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5774</link>
    <description>&lt;pre&gt;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 &amp;lt; at &amp;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 &amp;lt; at &amp;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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Cole Robinson</dc:creator>
    <dc:date>2012-05-15T15:24:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5773">
    <title>Re: [Fedora-xen] Boot errors,https://bugzilla.redhat.com/show_bug.cgi?id=804347</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5773</link>
    <description>&lt;pre&gt;
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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Marko Ristola</dc:creator>
    <dc:date>2012-05-14T17:11:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5772">
    <title>Re: [Fedora-xen] Can't text install DomU</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5772</link>
    <description>&lt;pre&gt;
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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Lars Bjørndal</dc:creator>
    <dc:date>2012-05-14T08:55:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5771">
    <title>Re: [Fedora-xen] Can't text install DomU</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5771</link>
    <description>&lt;pre&gt;

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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>M A Young</dc:creator>
    <dc:date>2012-05-14T07:27:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5770">
    <title>[Fedora-xen] Can't text install DomU</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5770</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;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&amp;lt; at &amp;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 pages of unused memory
[    0.000000] Set 0 page(s) to 1-1 mapping.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 0000000020000000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] last_pfn = 0x20000 max_arch_pfn = 0x1000000
[    0.000000] init_memory_mapping: 0000000000000000-0000000020000000
[    0.000000] RAMDISK: 00eca000 - 08f57000
[    0.000000] 0MB HIGHMEM available.
[    0.000000] 512MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 20000000
[    0.000000]   low ram: 0 - 20000000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -&amp;gt; 0x00001000
[    0.000000]   Normal   0x00001000 -&amp;gt; 0x00020000
[    0.000000]   HighMem  empty
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -&amp;gt; 0x000000a0
[    0.000000]     0: 0x00000100 -&amp;gt; 0x00020000
[    0.000000] Using APIC driver default
[    0.000000] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org
[    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
[    0.000000] APIC: disable apic facility
[    0.000000] APIC: switched to apic NOOP
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 4.1.2 (preserve-AD)
[    0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1
[    0.000000] PERCPU: Embedded 13 pages/cpu &amp;lt; at &amp;gt;dfbee000 s32000 r0 d21248 u53248
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129936
[    0.000000] Kernel command line: method=http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/i386/os
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] allocated 2096896 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Initializing HighMem for node 0 (00000000:00000000)
[    0.000000] Memory: 375456k/524288k available (4278k kernel code, 148384k reserved, 2724k data, 612k init, 0k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xf5295000 - 0xf57ff000   (5544 kB)
[    0.000000]     pkmap   : 0xf4e00000 - 0xf5000000   (2048 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xf4dfe000   ( 325 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]       .init : 0xc0ad7000 - 0xc0b70000   ( 612 kB)
[    0.000000]       .data : 0xc082d816 - 0xc0ad6840   (2724 kB)
[    0.000000]       .text : 0xc0400000 - 0xc082d816   (4278 kB)
[    0.000000] SLUB: Genslabs=15, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] NR_IRQS:1280
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [hvc0] enabled
[    0.000000] installing Xen timer for CPU 0
[    0.000000] Detected 3000.144 MHz processor.
[    0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 6000.28 BogoMIPS (lpj=3000144)
[    0.001045] pid_max: default: 32768 minimum: 301
[    0.001373] Security Framework initialized
[    0.001514] SELinux:  Initializing.
[    0.001868] Mount-cache hash table entries: 512
[    0.002761] Initializing cgroup subsys cpuacct
[    0.002961] Initializing cgroup subsys memory
[    0.002999] Initializing cgroup subsys devices
[    0.002999] Initializing cgroup subsys freezer
[    0.002999] Initializing cgroup subsys net_cls
[    0.002999] Initializing cgroup subsys blkio
[    0.003034] Initializing cgroup subsys perf_event
[    0.003333] CPU: Physical Processor ID: 0
[    0.003460] CPU: Processor Core ID: 0
[    0.003829] SMP alternatives: switching to UP code
[    0.005311] Freeing SMP alternatives: 12k freed
[    0.005517] ftrace: allocating 24660 entries in 49 pages
[    0.007181] Performance Events: unsupported Netburst CPU model 4 no PMU driver, software events only.
[    0.008787] NMI watchdog disabled (cpu0): hardware events not enabled
[    0.008894] Brought up 1 CPUs
[    0.009721] devtmpfs: initialized
[    0.012825] atomic64 test passed for i586+ platform with CX8 and with SSE
[    0.012916] Grant table initialized
[    0.031893] RTC time: 165:165:165, date: 165/165/65
[    0.032094] NET: Registered protocol family 16
[    0.034997] PCI: setting up Xen PCI frontend stub
[    0.038731] bio: create slab &amp;lt;bio-0&amp;gt; at 0
[    0.039179] ACPI: Interpreter disabled.
[    0.040964] xen/balloon: Initialising balloon driver.
[    0.040991] last_pfn = 0x20000 max_arch_pfn = 0x1000000
[    0.050377] xen-balloon: Initialising balloon driver.
[    0.051831] vgaarb: loaded
[    0.052121] SCSI subsystem initialized
[    0.052457] usbcore: registered new interface driver usbfs
[    0.052516] usbcore: registered new interface driver hub
[    0.052708] usbcore: registered new device driver usb
[    0.052995] PCI: System does not support PCI
[    0.052995] PCI: System does not support PCI
[    0.053035] NetLabel: Initializing
[    0.053057] NetLabel:  domain hash size = 128
[    0.053077] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.053121] NetLabel:  unlabeled traffic allowed by default
[    0.053152] Switching to clocksource xen
[    0.053995] Switched to NOHz mode on CPU #0
[    0.076539] pnp: PnP ACPI: disabled
[    0.084678] NET: Registered protocol family 2
[    0.085081] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.086163] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[    0.086893] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
[    0.087070] TCP: Hash tables configured (established 16384 bind 16384)
[    0.087070] TCP reno registered
[    0.087070] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.087070] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.087070] NET: Registered protocol family 1
[    0.088629] Unpacking initramfs...
[    1.385540] Freeing initrd memory: 131636k freed
[    1.482913] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    1.483446] apm: BIOS not found.
[    1.483754] Intel AES-NI instructions are not detected.
[    1.484230] audit: initializing netlink socket (disabled)
[    1.484276] type=2000 audit(1336972488.808:1): initialized
[    1.517251] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    1.521353] VFS: Disk quotas dquot_6.5.2
[    1.521587] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.523240] msgmni has been set to 990
[    1.524571] alg: No test for stdrng (krng)
[    1.524609] NET: Registered protocol family 38
[    1.524751] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    1.524888] io scheduler noop registered
[    1.524906] io scheduler deadline registered
[    1.524954] io scheduler cfq registered (default)
[    1.525152] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    1.525238] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    1.525260] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    1.525530] isapnp: Scanning for PnP cards...
[    1.885464] isapnp: No Plug &amp;amp; Play device found
[    1.886695] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.888191] Non-volatile memory driver v1.3
[    1.888218] Linux agpgart interface v0.103
[    1.891628] loop: module loaded
[    1.891987] Fixed MDIO Bus: probed
[    1.892240] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.892308] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.892365] uhci_hcd: USB Universal Host Controller Interface driver
[    1.892540] usbcore: registered new interface driver usbserial
[    1.892586] USB Serial support registered for generic
[    1.892643] usbcore: registered new interface driver usbserial_generic
[    1.892668] usbserial: USB Serial Driver core
[    1.892766] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    1.893837] mousedev: PS/2 mouse device common for all mice
[    1.934410] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    1.934570] rtc_cmos: probe of rtc_cmos failed with error -38
[    1.934849] device-mapper: uevent: version 1.0.3
[    1.935180] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: dm-devel&amp;lt; at &amp;gt;redhat.com
[    1.935427] EFI Variables Facility v0.08 2004-May-17
[    1.935895] usbcore: registered new interface driver usbhid
[    1.935919] usbhid: USB HID core driver
[    1.936148] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.936209] TCP cubic registered
[    1.936229] Initializing XFRM netlink socket
[    1.936623] NET: Registered protocol family 10
[    1.937123] Mobile IPv6
[    1.937140] NET: Registered protocol family 17
[    1.937186] Registering the dns_resolver key type
[    1.937250] Using IPI No-Shortcut mode
[    1.937542] registered taskstats version 1
[    1.937567] IMA: No TPM chip found, activating TPM-bypass!
[    1.937680] XENBUS: Device with no driver: device/vbd/51712
[    1.937699] XENBUS: Device with no driver: device/vif/0
[    1.937716] XENBUS: Device with no driver: device/console/0
[    1.937765]   Magic number: 1:252:3141
[    1.937809] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.937876] Initializing network drop monitor service
[    1.938729] Freeing unused kernel memory: 612k freed
[    1.942723] Write protecting the kernel text: 4280k
[    1.944461] Write protecting the kernel read-only data: 2064k
[    1.944487] NX-protecting the kernel data: 3912k
[    2.088215] dracut: dracut-013-18.fc16
[    2.109377] dracut: root was live:/squashfs.img, liveroot is now live:/squashfs.img
[    2.144554] udevd[65]: starting version 173
[    2.455170] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    2.667001] EXT4-fs (dm-0): warning: checktime reached, running e2fsck is recommended
[    2.669876] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[    2.688729] dracut: Mounted root filesystem /dev/mapper/live-rw
[    2.788224] dracut: Switching root
[    3.588479] type=1403 audit(1336972490.912:2): policy loaded auid=4294967295 ses=4294967295
[    3.604555] systemd[1]: Successfully loaded SELinux policy in 311ms 966us.
[    3.753016] systemd[1]: Successfully loaded SELinux database in 147ms 59us, size on heap is 362K.
[    4.066382] systemd[1]: Relabelled /dev and /run in 290ms 464us.
[    4.079236] systemd[1]: systemd 36 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)

Welcome to [0;34mFedora release 16 (Verne)[0m!

[    4.093558] systemd[1]: No hostname configured.
[    4.096337] systemd[1]: Initializing machine ID from random generator.
[    4.250819] systemd[1]: Failed to fully start up daemon: No such file or directory
[    4.251155] systemd[1]: Cannot add dependency job for unit fedora-storage-init.service, ignoring: Unit fedora-storage-init.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-storage-init.service' for details.
[    4.251288] systemd[1]: Cannot add dependency job for unit fedora-wait-storage.service, ignoring: Unit fedora-wait-storage.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-wait-storage.service' for details.
[    4.251405] systemd[1]: Cannot add dependency job for unit systemd-remount-api-vfs.service, ignoring: Unit systemd-remount-api-vfs.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-remount-api-vfs.service' for details.
[    4.251516] systemd[1]: Cannot add dependency job for unit fedora-readonly.service, ignoring: Unit fedora-readonly.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-readonly.service' for details.
[    4.251647] systemd[1]: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
[    4.251979] systemd[1]: Cannot add dependency job for unit rpcbind.socket, ignoring: Unit rpcbind.socket failed to load: No such file or directory. See system logs and 'systemctl status rpcbind.socket' for details.
[    4.252139] systemd[1]: Cannot add dependency job for unit dm-event.socket, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
[    4.252242] systemd[1]: Cannot add dependency job for unit avahi-daemon.socket, ignoring: Unit avahi-daemon.socket failed to load: No such file or directory. See system logs and 'systemctl status avahi-daemon.socket' for details.
[    4.252432] systemd[1]: Cannot add dependency job for unit ip6tables.service, ignoring: Unit ip6tables.service failed to load: No such file or directory. See system logs and 'systemctl status ip6tables.service' for details.
[    4.253495] systemd[1]: Cannot add dependency job for unit iptables.service, ignoring: Unit iptables.service failed to load: No such file or directory. See system logs and 'systemctl status iptables.service' for details.
Starting Collect Read-Ahead Data...
Started Replay Read-Ahead Data.
Started Lock Directory.
Starting Initialize storage subsystems (RAID, LVM, etc.)...
Starting Software RAID Monitor Takeover...
Starting Security File System...
Starting Debug File System...
Starting Huge Pages File System...
Starting POSIX Message Queue File System...
Starting udev Coldplug all Devices...
Starting udev Kernel Device Manager...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Starting Runtime Directory...
Started Collect Read-Ahead Data.
[    4.812765] systemd[1]: fedora-storage-init-late.service: main process exited, code=exited, status=203
Starting Initialize storage subsystems (RAID, LVM, etc.) [1;31mfailed[0m, see 'systemctl status fedora-storage-init-late.service' for details.
[    4.815369] systemd[1]: Unit fedora-storage-init-late.service entered failed state.
Started Software RAID Monitor Takeover.
Started Security File System.
Started Debug File System.
Started Huge Pages File System.
Started POSIX Message Queue File System.
Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Started Load legacy module configuration.
Starting File System Check on Root Device...
Started Load Kernel Modules.
Started Configuration File System.
Started FUSE Control File System.
Starting Setup Virtual Console...
Started Set Up Additional Binary Formats.
Starting Apply Kernel Variables...
Starting STDOUT Syslog Bridge...
Started STDOUT Syslog Bridge.
Started Runtime Directory.
[    5.140020] systemd-fsck[194]: Root directory is writable, skipping check.
Started File System Check on Root Device.
Starting Remount Root FS...
[    5.197725] systemd-vconsole-setup[195]: /bin/loadkeys failed with error code 1.
[    5.198839] systemd-vconsole-setup[195]: /bin/setfont failed with error code 1.
Started Setup Virtual Console.
Started Apply Kernel Variables.
[    5.257727] mount[201]: warning: can't open /etc/fstab: No such file or directory
[    5.294187] EXT4-fs (dm-0): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered
Started Remount Root FS.
Started udev Kernel Device Manager.
[    5.598173] udevd[188]: starting version 173
Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
[    6.113732] lvm[192]: No volume groups found
Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Started Reconfigure the system on administrator request.
Started Relabel all filesystems, if necessary.
Started Mark the need to relabel after reboot.
Starting Load Random Seed...
Starting Recreate Volatile Files and Directories...
Started Load Random Seed.
[    6.616135] systemd-tmpfiles[229]: Successfully loaded SELinux database in 367ms 792us, size on heap is 363K.
[    6.821216] Initialising Xen virtual ethernet driver.
[    6.903454] blkfront: xvda: flush diskcache: enabled
[    6.909609]  xvda: unknown partition table
Started Recreate Volatile Files and Directories.
Started udev Wait for Complete Device Initialization.
Started anaconda performance monitor.
Starting System Logging Service...
Starting Shell on tty2...
Started Shell on tty2.
Starting Shell on hvc1...
[    8.831724] udevd[208]: setfilecon /dev/vcs2 failed: No such file or directory
Started Shell on hvc1.
Starting Anaconda version 16.25.
--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Lars Bjørndal</dc:creator>
    <dc:date>2012-05-14T06:11:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5769">
    <title>Re: [Fedora-xen] Boot errors,https://bugzilla.redhat.com/show_bug.cgi?id=804347</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5769</link>
    <description>&lt;pre&gt;
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 &amp;lt; 16, made it work with Fedora 16
without Dom0. As Dom0 it doesn't work).

Regards,
Marko

On 05/10/2012 06:42 PM, Konrad Rzeszutek Wilk wrote:

--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Marko Ristola</dc:creator>
    <dc:date>2012-05-13T17:42:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5768">
    <title>Re: [Fedora-xen] Cannot boot into Xen hypervisor in FC17 beta</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5768</link>
    <description>&lt;pre&gt;
https://bugzilla.redhat.com/show_bug.cgi?id=801650



--
xen mailing list
xen&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Konrad Rzeszutek Wilk</dc:creator>
    <dc:date>2012-05-10T16:22:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5767">
    <title>Re: [Fedora-xen] Boot errors, https://bugzilla.redhat.com/show_bug.cgi?id=804347</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5767</link>
    <description>&lt;pre&gt;
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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Konrad Rzeszutek Wilk</dc:creator>
    <dc:date>2012-05-10T15:42:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5766">
    <title>Re: [Fedora-xen] DomU nat router fails when DomUs on same host</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5766</link>
    <description>&lt;pre&gt;
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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Konrad Rzeszutek Wilk</dc:creator>
    <dc:date>2012-05-10T15:36:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5765">
    <title>[Fedora-xen] Cannot boot into Xen hypervisor in FC17 beta</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5765</link>
    <description>&lt;pre&gt;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.





&lt;/pre&gt;</description>
    <dc:creator>Peter Teoh</dc:creator>
    <dc:date>2012-05-10T14:59:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5764">
    <title>[Fedora-xen] 4.1.3-rc1 available to test</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5764</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>M A Young</dc:creator>
    <dc:date>2012-05-09T19:08:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5763">
    <title>Re: [Fedora-xen] Dom0 and colord</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5763</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Lars Bjørndal</dc:creator>
    <dc:date>2012-05-05T20:43:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5762">
    <title>Re: [Fedora-xen] Error message after virt-install</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5762</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Lars Bjørndal</dc:creator>
    <dc:date>2012-05-05T19:53:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5760">
    <title>Re: [Fedora-xen] Reminder: Fedora 17 virt test day going on rightnow!</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5760</link>
    <description>&lt;pre&gt;

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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>Gordon McLellan</dc:creator>
    <dc:date>2012-05-04T17:11:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5759">
    <title>Re: [Fedora-xen] Reminder: Fedora 17 virt test day going on right now!</title>
    <link>http://permalink.gmane.org/gmane.linux.redhat.fedora.xen/5759</link>
    <description>&lt;pre&gt;

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&amp;lt; at &amp;gt;lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen&lt;/pre&gt;</description>
    <dc:creator>M A Young</dc:creator>
    <dc:date>2012-05-04T14:05:43</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.redhat.fedora.xen">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.redhat.fedora.xen</link>
  </textinput>
</rdf:RDF>

