<?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://comments.gmane.org/gmane.linux.redhat.fedora.xen/5774"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5770"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5764"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5750"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5746"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5745"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5744"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5725"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5724"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5723"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5718"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5717"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5712"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5709"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5708"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5706"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5705"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5704"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5695"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5684"/>
      </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://comments.gmane.org/gmane.linux.redhat.fedora.xen/5774">
    <title>[Fedora-xen] Change xen package owner away from xen-maint?</title>
    <link>http://comments.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://comments.gmane.org/gmane.linux.redhat.fedora.xen/5770">
    <title>[Fedora-xen] Can't text install DomU</title>
    <link>http://comments.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://comments.gmane.org/gmane.linux.redhat.fedora.xen/5764">
    <title>[Fedora-xen] 4.1.3-rc1 available to test</title>
    <link>http://comments.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://comments.gmane.org/gmane.linux.redhat.fedora.xen/5750">
    <title>[Fedora-xen] Xen Fedora Virtualization Test Day Planning</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5750</link>
    <description>&lt;pre&gt;Hi All,

I've put together some resources for the Xen testing effort.

http://openetherpad.org/xen-fedora-testing

Please let me know if you are planning to help with this effort and I
will continue to coordinate.

Thanks,
Todd

&lt;/pre&gt;</description>
    <dc:creator>Todd Deshane</dc:creator>
    <dc:date>2012-04-10T16:32:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5746">
    <title>[Fedora-xen] Error message after virt-install</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5746</link>
    <description>&lt;pre&gt;I'm not able to install a guest OS. I give the following command on
my Fedora 16 machine, running i686:

'virt-install --connect xen:/// --os-type linux \
-l
http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/i386/os
\
--ram 512 --disk /var/lib/libvirt/images/f16.img,size=4  --name F16 \
--graphic none  --paravirt --virt-type=xen \
-x "serial console=tty0 console=ttyS0,115200"'

I get the following output:

'Starting install...
Retrieving file .treeinfo...                             | 1.8 kB
00:00 ...
Retrieving file vmlinuz-PAE...                           | 7.9 MB
00:03 ...
Retrieving file initrd-PAE.img...                        | 257 MB
01:47 ...
Creating domain...                                       |    0 B
00:04
Connected to domain F16
Escape character is ^]
error: Unable to open stream for '(null)': Bad address

Domain installation still in progress. You can reconnect to
the console to complete the installation process.'

I'm not able to reconnect. How can I solve this problem?

Thanks and 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-04-07T12:01:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5745">
    <title>[Fedora-xen] Dom0 and colord</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5745</link>
    <description>&lt;pre&gt;I'm testing Xen dom0 on a Fedora 16 i686 box. I notice a process called
/usr/libexec/colord, that leads to high cpu load, resulting in a
spinning cpu fan. The process also runs when Xen is not running, but then
the TIME reported by 'ps ax' is 0:00.

As I'm blind and don't use any X or GUI, I think I don't need the colord
process, so I did 'killall -9 /usr/libexec/colord'. However, this
doesn't work from a script, like /etc/rc.d/rc.local, and I need to do it
manually after every reboot.

Where is colord started, and how can I get rid of the process?

Thanks and 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-04-07T11:42:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5744">
    <title>[Fedora-xen] Calling all Fedora Xen users, testers, and developers</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5744</link>
    <description>&lt;pre&gt;The Fedora community is holding a virtualization test day [1] next
week (Thursday) and it would be great if we could help them on the Xen
side of things

Let me know if you are interested in helping out and I'll coordinated
the Xen efforts.

Thanks,
Todd

[1] http://fedoraproject.org/wiki/Test_Day:2012-04-12_Virtualization_Test_Day

&lt;/pre&gt;</description>
    <dc:creator>Todd Deshane</dc:creator>
    <dc:date>2012-04-06T17:16:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5725">
    <title>[Fedora-xen] Boot errors</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5725</link>
    <description>&lt;pre&gt;I installed Fedora 16 and then ran:

sudo yum install xen

Xen installed without errors and I rebooted. In the Grub2 list I selected
Xen 4.1.2 and then selected the option:

Fedora Linux, with Xen 4.1.2 and Linux 3.3.0-4.fc16.x86_64

The boot process starts (i notice that loading ramdisk is very short) and
then shortly thereafter the boot fails and the system reboots without any
error.

I tried checking the boot log but I'm not sure I'm looking at the right
log.

The only problem I see in the boot is

Started SYSV: sandbox, xguest and other apps that want to use pam_names$
Failed to start Xenstored - daemon managing xenstore file system
--
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>Chris Jones</dc:creator>
    <dc:date>2012-03-24T21:07:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5724">
    <title>[Fedora-xen] mdadm fails to start raid in pv fc16 DomU on old host</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5724</link>
    <description>&lt;pre&gt;I'm having a problem with mdraid running in a DomU. The issue is that mdraid 
declares one leg of the raid to have failed (when there's actually nothing 
wrong).

DomU is fc16 - 3.2.2-1.fc16.x86_64
Dom0 is fc14 - 2.6.32.26-174.2.xendom0.fc12.x86_64

The same DomU running on Dom0 fc16 - 3.2.7-1.fc16.x86_64 runs perfectly.

This appears to be a known issue, however the resolution (which seems to be to 
disable barriers on the fly) doesn't seem to work in this case.

My question is: Is it possible to pass a parameter to the blkfront driver to 
ask it not to enable barrier during initialization? or is there another work 
around?

[    1.033058] blkfront: xvda: barrier: enabled
[    1.099153]  xvda: xvda1 xvda2
[    1.102871] blkfront: xvdb: barrier: enabled
[    1.130876]  xvdb: xvdb1 xvdb2
[    1.292692] md: bind&amp;lt;xvdb1&amp;gt;
[    1.413416] md: bind&amp;lt;xvda1&amp;gt;
[    1.419411] md: raid1 personality registered for level 1
[    1.419836] bio: create slab &amp;lt;bio-1&amp;gt; at 1
[    1.419953] md/raid1:md127: active with 2 out of 2 mirrors
[    1.419992] md127: detected capacity change from 0 to 7516180480
[    1.424562]  md127: unknown partition table
[    1.547284] EXT4-fs (md127): barriers disabled
[    1.553107] EXT4-fs (md127): mounted filesystem with ordered data mode. 
Opts: (null)
[    1.669483] dracut: Checking ext4: /dev/disk/by-label/rootfs
[    1.669592] dracut: issuing e2fsck -a  /dev/disk/by-label/rootfs
[    1.690595] blkfront: barrier: empty write xvdb op failed
[    1.690611] blkfront: xvdb: barrier or flush: disabled
[    1.690628] end_request: I/O error, dev xvdb, sector 14682096
[    1.690638] end_request: I/O error, dev xvdb, sector 14682096
[    1.690646] md: super_written gets error=-5, uptodate=0
[    1.690655] md/raid1:md127: Disk failure on xvdb1, disabling device.
[    1.690657] md/raid1:md127: Operation continuing on 1 devices.
[    1.690677] blkfront: barrier: empty write xvda op failed
[    1.690684] blkfront: xvda: barrier or flush: disabled
[    1.690696] end_request: I/O error, dev xvda, sector 14682096
[    1.690705] end_request: I/O error, dev xvda, sector 14682096
[    1.690713] md: super_written gets error=-5, uptodate=0
[    1.692991] RAID1 conf printout:
[    1.692997]  --- wd:1 rd:2
[    1.693002]  disk 0, wo:0, o:1, dev:xvda1
[    1.693006]  disk 1, wo:1, o:0, dev:xvdb1
[    1.693010] RAID1 conf printout:
[    1.693013]  --- wd:1 rd:2
[    1.693016]  disk 0, wo:0, o:1, dev:xvda1
[    1.702896] dracut: rootfs: clean, 25635/454272 files, 293967/1835005 blocks
[    1.703682] dracut: Remounting /dev/disk/by-label/rootfs with -o ro
[    1.773347] EXT4-fs (md127): barriers disabled
[    1.774552] EXT4-fs (md127): mounted filesystem with ordered data mode. 
Opts: (null)
[    1.797159] dracut: Mounted root filesystem /dev/md127
[    1.937620] dracut: Switching root

--
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>Virgil</dc:creator>
    <dc:date>2012-03-19T02:35:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5723">
    <title>[Fedora-xen] DomU nat router fails when DomUs on same host</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5723</link>
    <description>&lt;pre&gt;Hi List,

I have a strange issue someone, hopefully, can advise me on.

I have two external connections into a host: em1 is behind a firewall machine 
which is connected to an internet backbone link, while em2 is an adsl all-u-
can-eat deal with a cheap router.

Both are bridged. So there's pem1 and pem2 which are connected to the em1 and 
em2 bridges respectively.

There is a domU router which nats (and is connected to both bridges).

Some domU servers (a variety of fc6 to fc16 32 and 64) default route to the 
domU router and go out the all-u-can-eat link.

The issue is, I recent upgraded the host from Fedora8 to Fedora16, and now the 
domU machines that once happily used the all-u-can-eat link, no longer can.

However, in an act of desperation, I moved one of the domUs to a backup 
machine. Nothing else changed. Bingo. That domU works. All resources are still 
on the original machine (i.e. the DB servers, the router, etc. etc.).

It seems that the router does't seem to nat domUs on the same host. You move 
the domU off with comms going via em1 to another host and it works.

Iptraf tracing seems to indicate that the TCP connection is setup. The first 
packet goes off and is acked. Then everything stops and eventually the tcp 
connection closes on the router, but the domU and the remote computer think 
the link is still up (at least that's what I think is happening). The domU's 
send queue ends up with lots of data in it according to 'netstat -ant'

Only nat'd tcp connections are effected. Connections to machines on the same 
bridge work fine.

Does this sound familiar to anyone?

Thanks in advance
Virgil
--
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>Virgil</dc:creator>
    <dc:date>2012-03-13T06:16:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5718">
    <title>[Fedora-xen] Rebélate by self-management, first project of free software by which we bet all / Rebélate por la autogestión, primer proyecto de software libre por el que apostamos todas</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5718</link>
    <description>&lt;pre&gt;Inglés :

Many already we have contributed to the first project of free software
dedicated to self-management in this campaign of collective financing,
it collaborates and it spreads!/


Beginning campaign collective financing

http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion?lang=en


Login to enter with user of social networks and for would register in Goteo :

http://www.goteo.org/user/login?lang=en


Rebelaos! Publication by self-management A massive publication that
floods the public transport, the work centers, the parks, the
consumption centers, by means of distribution of 500,000 gratuitous
units, acting simultaneously in all sides and nowhere.

We announce the main tool of a vestibule Web for the management of
self-sustaining resources by means of Drupal, in addition in the
publication there will be an article dedicated to free software,
hardware, It is being prepared in inglès,  the machinery You can see
more details in the index of the
publication    https://n-1.cc/pg/file/read/1151902/indexresumen-de-los-contenidos-pdf

 . A computer system that allows us to share resources in all the
scopes of our life so that we do not have to generate means different
for each subject nor for each territory.

A point of contact digitalis to generate projects of life outside
Capitalism and to margin of the State.


A tool to spread and to impel the social transformation through the
resources that will set out in their contents around self-management,
the autoorganización, the disobedience and the collective action.

In which the capitalist system goes to the collapse, in a while
immersed in a deep systemic crisis (ecological, political and
economic, but mainly of values), where individual and collective of
people they are being lacking of his fundamental rights, is necessary
to develop a horizontal collective process where all the human beings
we pruned to interact in equality of conditions and freedom.


To interact means to relate to us (as much human as economically), to
communicate to us, to cover our basic needs, to generate and to
protect communal properties, to know and to provide collective
solutions us problematic that our lives interfere. We want abrir a
breach within normality in the monotonous life state-capitalist, a day
anyone, that finally will not be any day.


By means of this publication we try:

- To drive a horizontal collective process where all and all we pruned
to interact in equality of conditions and freedom.

 - To create communications network between the people it jeopardize
with the change and arranged to act.


 - To find collective solutions to problematic that our lives interfere


- To facilitate the access to resources that make possible self-management.

- To participate in the construction of networks of mutual support,
generated horizontals, asamblearias and from the base.


 - To publish all this information in an attractive format stops to
facilitate the access to all the society.



There are 15 days remaining for the upcoming March 15, the day that
will come Rebelaos!, Magazine for the selfmanagement

Today, we issue the cover of Rebelaos! (Castilian version) that can be
displayed on the following link:
https://n-1.cc/pg/file/read/1200503/portada-15-de-marzo-rebelaos
The contents of the store owners to us by 15 March. Do you? Do you
keep on 15 March?

In addition, we have over 200 distribution nodes, distributed
throughout the Spanish state. Check the map:
https://afinidadrebelde.crowdmap.com/

On the other hand, the funding campaign continues to move and still
have 12 days to collect the remaining 6,000 euros. We can all make a
bit for all the grains of sand become a great beach on March 15. You
can access the co-financing campaign:
http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion

Rebel Affinity group
www.rebelaos.net


-------------------------------------------------------------------------------
Castellano:

Muchos ya hemos aportado al primer proyecto de software libre dedicado
a la la financiación colectiva, colabora y diffunde !!!!!

Inicio campaña financiación colectiva goteo.org

www.goteo.org/project/rebelaos-publicacion-por-la-autogestion


Link para registrarse en Goteo y acceder a redes sociales para
colaborar en la difusín

http://www.goteo.org/user/login

¡Rebelaos! Publicación por la autogestión

Una publicación masiva que inunde el transporte público, los centros
de trabajo, los parques, los centros de consumo, mediante la
distribución de 500.000 ejemplares gratuitos, actuando simultáneamente
en todos lados y en ninguna parte.


Anunciamos la herramienta principal de un  portal web para la gestión
de recursos autogestionados mediante Drupal, además en  la publicación
habrá un artículo dedicado al software libre, el hardware, la
maquinaria... Puedes ver más detalles en el índice de la publicación
https://n-1.cc/pg/file/read/1151902/indexresumen-de-los-contenidos-pdf

Un sistema infórmatico que nos permita compartir recursos en todos los
ámbitos de nuestra vida de forma que no tengamos que generar un medio
distinto para cada tema ni para cada territorio. Un punto de encuentro
digital para generar proyectos de vida fuera del capitalismo y al
margen del Estado.


Una herramienta para difundir e impulsar la transformación social a
través de los recursos que se propondrán en sus contenidos en torno a
la autogestión, la autoorganización, la desobediencia y la acción
colectiva.

En un momento en que el sistema capitalista se dirige al colapso,
inmerso en una profunda crisis sistémica (ecológica, política y
económica, pero principalmente de valores), donde individuos y
colectivos de personas están siendo desprovistos de sus derechos
fundamentales, es necesario desarrollar un proceso colectivo
horizontal donde todos los seres humanos podamos interactuar en
igualdad de condiciones y en libertad.

Interactuar significa relacionarnos (tanto humana como
económicamente), comunicarnos, cubrir nuestras necesidades básicas,
generar y proteger bienes comunes, conocernos y dar soluciones
colectivas a problemáticas que interfieren nuestras vidas. Queremos
abrir una brecha dentro de la normalidad en la monótona vida
estatal-capitalista, un día cualquiera, que finalmente no será
cualquier día.

Mediante esta publicación pretendemos:

- Impulsar un proceso colectivo horizontal donde todos y todas podamos
interactuar en igualdad de condiciones y en libertad.

- Crear red de comunicaciones entre las personas comprometidas con el
cambio y dispuestas a actuar.

- Encontrar soluciones colectivas a problemáticas que interfieren
nuestras vidas.

- Facilitar el acceso a recursos que posibiliten la autogestión.

- Participar en la construcción de redes de apoyo mutuo, horizontales,
asamblearias y generadas desde la base.

- Publicar toda esta información en un formato atractivo para
facilitar el acceso a toda la sociedad.

Son 15 los días que restan para el próximo 15 de marzo, día en el que
verá la luz ¡Rebelaos!, publicación por la autogestión.

Hoy, hacemos pública la portada de ¡Rebelaos! (versión en castellano)
que podéis visualizar en el siguiente enlace:
https://n-1.cc/pg/file/read/1200503/portada-15-de-marzo-rebelaos
El contenido de los titulares nos los guardamos para el 15 de marzo.
¿Y tú? ¿Te guardas el 15 de marzo?

Además, ya hemos superado los 200 nodos de distribución, repartidos
por todo el estado español. Ver el mapa:
https://afinidadrebelde.crowdmap.com/

Por otro lado, la campaña de financiación continúa avanzando y todavía
quedan 12 días para reunir los 6.000 euros que restan. Todas podemos
aportar un poco para que todos los granitos de arena se conviertan en
una gran playa el 15 de marzo. Podéis acceder a la campaña de
cofinanciación en:
http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion

Colectivo Afinidad Rebelde
www.rebelaos.net
--
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>Orquidea Salt mas</dc:creator>
    <dc:date>2012-03-02T15:00:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5717">
    <title>[Fedora-xen] F17 Kernel Badness</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5717</link>
    <description>&lt;pre&gt;Hi,

My Fedora 17 3.3-rc4.git1 kernel boots on bare metal, but it dies very
early on in the boot process when loading on top of Xen. It's got
CONFIG_XEN_DOM0=y and all the other CONFIG_XEN* options are either "y"
or "m". Linux panics with

init[1] trap invalid opcode ip:7f99a072ff15 sp:7fffbf2a5088 error :0
in libc-2.15.so[7f99a05f8000+1ac000]
init used greatest stack depth: 2392 bytes left
Kernel panic - not syncing: Attempted to kill init!

The kernel itself seems able to execute on top of Xen because I see a
very normal-looking Xen init, then the screen blanks, then Linux
initializes and starts executing early boot, stuff like the USB stack
and SATA starts to come up, and then it tries to run the init process
in userspace and it all comes crashing down.

This is on Sandy Bridge hardware with all the CPU optional instruction
sets enabled.

Any ideas?

Thanks,

Sean
--
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>Sean McNamara</dc:creator>
    <dc:date>2012-03-01T04:04:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5712">
    <title>[Fedora-xen] blocked domain</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5712</link>
    <description>&lt;pre&gt;Hi,

I tried to install a fedora onto my xen domain with virt-manager. At
the third attempt I reached some success:

# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  3005     1     r-----   6236.5
MobileOtp                                       1024     1                 0.0
MobileOtp2                                      1024     1                 0.0
MobileOtp3                                   3   800     1     -b----    338.4

But, when trying to issue

# xm console MobileOtp3

the terminal becomes stuck and only killing the xenconsole process frees it.

The installation itself did not run, how can I step ahead?

- Gergely
--
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>Gergely Buday</dc:creator>
    <dc:date>2012-02-07T12:46:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5709">
    <title>[Fedora-xen] virt-manager / install fedora image</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5709</link>
    <description>&lt;pre&gt;Hi,

I would like to install a fedora as a subdomain operating system on my
fedora box. virt-manager throws the following error:

libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Error creating domain: Disk image does not exist:
/home/gergoe/Downloads/Fedora-16-x86_64-Live-Security.iso')

I wonder as /home/gergoe/Downloads/Fedora-16-x86_64-Live-Security.iso
exists. What can be the problem?

- Gergely
--
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>Gergely Buday</dc:creator>
    <dc:date>2012-02-06T15:46:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5708">
    <title>[Fedora-xen] Fedora 16 [3.1.0-7.fc16.i686] and Xen [4.1.2] problem</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5708</link>
    <description>&lt;pre&gt;Hi All,

I have installed Fedora 16.

[root&amp;lt; at &amp;gt;RSJ boot]# uname -a
Linux RSJ 3.1.0-7.fc16.i686 #1 SMP Tue Nov 1 21:00:16 UTC 2011 i686 i686
i386 GNU/Linux
[root&amp;lt; at &amp;gt;RSJ boot]#

Then:
1. yum intsall xen

xen got install successfully but it could not update grub entry with xen.

2. [root&amp;lt; at &amp;gt;RSJ boot]# xl info
libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running?
failed to stat /var/run/xenstored.pid: No such file or directory
cannot init xl context
[root&amp;lt; at &amp;gt;RSJ boot]#

3. Then i manually updated the grub [entry = /etc/grub.d/20_linux_xen], now
grub.conf:
----------------/etc/grub2/grub.conf--------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="${saved_entry}"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora Linux, with Linux 3.1.0-7.fc16.i686' --class fedora
--class gnu-linux --class gnu --class os {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set=root
a61dbabc-0d61-41cd-a2c9-3857ae9ee060
        echo    'Loading Linux 3.1.0-7.fc16.i686 ...'
        linux   /vmlinuz-3.1.0-7.fc16.i686 root=/dev/mapper/vg_rsj-lv_root
ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_rsj/lv_root  KEYTABLE=us quiet
SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_rsj/lv_swap
LANG=en_US.UTF-8
        echo    'Loading initial ramdisk ...'
        initrd  /initramfs-3.1.0-7.fc16.i686.img
}
menuentry 'Fedora Linux, with Linux 3.1.0-7.fc16.i686 (recovery mode)'
--class fedora --class gnu-linux --class gnu --class os {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set=root
a61dbabc-0d61-41cd-a2c9-3857ae9ee060
        echo    'Loading Linux 3.1.0-7.fc16.i686 ...'
        linux   /vmlinuz-3.1.0-7.fc16.i686 root=/dev/mapper/vg_rsj-lv_root
ro single rd.md=0 rd.dm=0 rd.lvm.lv=vg_rsj/lv_root  KEYTABLE=us quiet
SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_rsj/lv_swap
LANG=en_US.UTF-8
        echo    'Loading initial ramdisk ...'
        initrd  /initramfs-3.1.0-7.fc16.i686.img
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
menuentry 'Fedora Linux, with Xen 4.1.2 and Linux 3.1.0-7.fc16.i686'
--class fedora --class gnu-linux --class gnu --class os {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set=root
a61dbabc-0d61-41cd-a2c9-3857ae9ee060
        echo    'Loading Xen 4.1.2 ...'
        multiboot /xen-4.1.2.gz placeholder
        echo    'Loading Linux 3.1.0-7.fc16.i686 ...'
        module  /vmlinuz-3.1.0-7.fc16.i686 placeholder
root=/dev/mapper/vg_rsj-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_rsj/lv_root
KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0
rd.lvm.lv=vg_rsj/lv_swap
LANG=en_US.UTF-8
        echo    'Loading initial ramdisk ...'
        module  /initramfs-3.1.0-7.fc16.i686.img
}
menuentry 'Fedora Linux, with Linux 3.1.0-7.fc16.i686 (recovery mode)'
--class fedora --class gnu-linux --class gnu --class os {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos6)'
        search --no-floppy --fs-uuid --set=root
a61dbabc-0d61-41cd-a2c9-3857ae9ee060
        echo    'Loading Linux 3.1.0-7.fc16.i686 ...'
        linux   /vmlinuz-3.1.0-7.fc16.i686 root=/dev/mapper/vg_rsj-lv_root
ro single rd.md=0 rd.dm=0 rd.lvm.lv=vg_rsj/lv_root  KEYTABLE=us quiet
SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 rd.lvm.lv=vg_rsj/lv_swap
LANG=en_US.UTF-8
        echo    'Loading initial ramdisk ...'
        initrd  /initramfs-3.1.0-7.fc16.i686.img
}
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows NT/2000/XP (loader) (on /dev/sda1)" --class windows
--class os {
        insmod part_msdos
        insmod ntfs
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set=root 9C78AAFE78AAD5F4
        drivemap -s (hd0) ${root}
        chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type
the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/90_persistent ###
### END /etc/grub.d/90_persistent ###

--------------------------------------------------------------------------

After reboot and booting with XEN kernel, it show:
elf_xen_note_check: ERROR: Will only load images built for the generic
loader or Linux images
******************************************
Panic on CPU0
Could not set up DOM0 guest OS
*** ***************************************

Is linux kernel  3.1.0-7.fc16.i686 comes with XEN kernel modules compiled ?
What is going wrong, any pointers ?


Regards,
Raj
--
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>Rajeshwar Singh Janwar</dc:creator>
    <dc:date>2012-02-05T03:16:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5706">
    <title>[Fedora-xen] Failed to bring up network interface</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5706</link>
    <description>&lt;pre&gt;I have a problem with network interfaces after installing Xen. Network
interface has network address but can't to bring up.

 

[root&amp;lt; at &amp;gt;dom0 ~]# uname -r 
3.2.2-1.fc16.i686.PAE

 

[root&amp;lt; at &amp;gt;dom0 ~]# yum list | grep xen-hyper

xen-hypervisor.i686                      4.1.2-2.fc16

 

With default kernel system works perfectly. But after booting with xen
kernel 

 

# dmesg | grep eth 
[   15.860121] e100 0000:00:04.0: eth0: addr 0xfeafe000, irq 9, MAC addr
00:e0:81:21:53:96 
[   15.884513] e100 0000:00:05.0: eth1: addr 0xfeafd000, irq 5, MAC addr
00:e0:81:21:53:97 
[   18.506585] udevd[458]: renamed network interface eth1 to em2 
[   18.568406] udevd[457]: renamed network interface eth0 to em1 

# lsmod | grep e100 
e100                   36014  0. 
mii                    13311  1 e100 

 

# lspci | grep Ethernet

00:04.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
100 (rev 08)

00:05.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
100 (rev 08)

# ifup em1 
RTNETLINK answers: Function not implemented 
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Failed to bring up em1.


# ifconfig em1 192.168.129.1 
SIOCSIFFLAGS: Function not implemented

 

I don't understand that happens. A difference between loadings only in irq.
20,21 for default kernel and 5,9 for xen kernel. But 5 and 9 irq is not used
anywhere more.

 

--
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>Sergey A. Pechiony</dc:creator>
    <dc:date>2012-02-03T11:59:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5705">
    <title>[Fedora-xen] Failed to bring up network interface</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5705</link>
    <description>&lt;pre&gt;I have a problem with network interfaces after installing Xen.

 

[root&amp;lt; at &amp;gt;dom0 ~]# uname -r 
3.2.2-1.fc16.i686.PAE

 

[root&amp;lt; at &amp;gt;dom0 ~]# yum list | grep xen-hyper

xen-hypervisor.i686                      4.1.2-2.fc16
&amp;lt; at &amp;gt;updates

 

With default kernel system works perfectly. But after booting with xen
kernel 

 

# dmesg | grep eth 
[   15.860121] e100 0000:00:04.0: eth0: addr 0xfeafe000, irq 9, MAC addr
00:e0:81:21:53:96 
[   15.884513] e100 0000:00:05.0: eth1: addr 0xfeafd000, irq 5, MAC addr
00:e0:81:21:53:97 
[   18.506585] udevd[458]: renamed network interface eth1 to em2 
[   18.568406] udevd[457]: renamed network interface eth0 to em1 

# lsmod | grep e100 
e100                   36014  0. 
mii                    13311  1 e100 

 

# lspci | grep Ethernet

00:04.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
100 (rev 08)

00:05.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
100 (rev 08)

# /etc/init.d/network status 
Configured devices: 
lo em1 em2 
Currently active devices: 
lo 

# ifup em1 
RTNETLINK answers: Function not implemented 
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Failed to bring up em1.


# ifconfig em1 
em1       Link encap:Ethernet  HWaddr 00:E0:81:21:53:97.. 
           inet addr:192.168.129.16  Bcast:192.168.131.255
Mask:255.255.252.0 
          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) 

# ifconfig em1 192.168.129.1 
SIOCSIFFLAGS: Function not implemented

 

Network interface has network address but can't to bring up.

I don't understand that happens. A difference between loadings only in irq.
20,21 for default kernel and 5,9 for xen kernel. But 5 and 9 irq is not used
anywhere more.

--
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>Sergey A. Pechiony</dc:creator>
    <dc:date>2012-02-03T10:43:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5704">
    <title>[Fedora-xen] (no subject)</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5704</link>
    <description>&lt;pre&gt;

D.Srinivas--
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>srinivas d</dc:creator>
    <dc:date>2012-02-02T04:21:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5695">
    <title>[Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5695</link>
    <description>&lt;pre&gt;Hi All,

I just update one of my Fedora 14 domU to Fedora 16 and everything when ok
in the update process. But once I did the first domU reboot than I got the

Error: Boot loader didn't return any data!

while virt-manager reports:

Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err "Boot loader didn't return any
data!")

details reports:

raceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 589, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
    self._backend.create()
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err "Boot loader didn't return any data!")

My thought is that since Fedora 16 comes with grub2, my current xen setup doesn't support it.

I also did a backport of xen4.2.1 from F16, recompiling it from src.rpm but anything was really working.

Does anyone can suggest something to solve this problem.

Thanks in advance.
Roberto Fichera.
--
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>Roberto Fichera</dc:creator>
    <dc:date>2012-01-24T19:24:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5684">
    <title>[Fedora-xen] beginner question</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5684</link>
    <description>&lt;pre&gt;Hi there,

I have installed xen through yum. How can I start it? I started xend
via its init.d script but still xm info says that it cannot connect
xend. What should I do then?

- Gergely
--
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>Gergely Buday</dc:creator>
    <dc:date>2012-01-11T15:51:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5672">
    <title>[Fedora-xen] xen "broke" my system</title>
    <link>http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5672</link>
    <description>&lt;pre&gt;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) --
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>Carlos Felipe Santacruz</dc:creator>
    <dc:date>2011-12-06T15:14:57</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>

