I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
You may need one or both of the following hacks
Edit /etc/init.d/xenstored replacing the line XENSTORED_PID="/var/run/xenstore.pid" with XENSTORED_PID="/var/run/xenstored.pid" (I didn't notice they had changed the name of this file until after I tested the xen packages)
Edit /etc/sysconfig/modules/xen.modules to remove xen-netback from the list of modules in the for loop then add modprobe xen-netback netback_kthread=1 to the end of the file. The xen-netback module in xen/next-2.6.38 when I built the kernel still needed some work and setting this value makes it less likely to throw up backtraces if you try to use it.
Michael Young
On Wed, Feb 2, 2011 at 8:43 PM, M A Young m.a.young@durham.ac.uk wrote:
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
You may need one or both of the following hacks
why the kernel is fc15 and xen is fc14 ?
------------
Itamar Reis Peixoto msn, google talk: itamar@ispbrasil.com.br +55 11 4063 5033 (FIXO SP) +55 34 9158 9329 (TIM) +55 34 8806 3989 (OI) +55 34 3221 8599 (FIXO MG)
On Wed, 2 Feb 2011, Itamar Reis Peixoto wrote:
On Wed, Feb 2, 2011 at 8:43 PM, M A Young m.a.young@durham.ac.uk wrote:
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
You may need one or both of the following hacks
why the kernel is fc15 and xen is fc14 ?
You are right, it isn't very consistent. The kernel is fc15 because it is actually a xenified version of current fc15 kernel, though it should work on other Fedora versions, and I use it on fc14 without any obvious additional problems. The xen package is fc14 because I am guessing that most people are still using fc14 and haven't switched to rawhide yet. I haven't tried the fc14 xen packages on rawhide, but I am not aware of any big differences that would cause them to break.
Michael Young
why the kernel is fc15 and xen is fc14 ?
You are right, it isn't very consistent. The kernel is fc15 because it is actually a xenified version of current fc15 kernel, though it should work on other Fedora versions, and I use it on fc14 without any obvious additional problems. The xen package is fc14 because I am guessing that most people are still using fc14 and haven't switched to rawhide yet. I haven't tried the fc14 xen packages on rawhide, but I am not aware of any big differences that would cause them to break.
Michael Young
it doesn`t install well in my fc15 box.
I have tried to rebuild it and fails.
are you able to build it for fc15 for me ?
On Wed, 2 Feb 2011, Itamar Reis Peixoto wrote:
it doesn`t install well in my fc15 box.
I have tried to rebuild it and fails.
are you able to build it for fc15 for me ?
I had no problems rebuilding it for F15. The result is at http://koji.fedoraproject.org/koji/taskinfo?taskID=2760578
Michael Young
On Wed, Feb 02, 2011 at 10:43:18PM +0000, M A Young wrote:
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
Here is some feedback.
Seems fixed:
Red Hat bug #669484, Xen's network-route and vif-route scripts broken
Rsync crash (sent a photograph of kernel panic, but didn't see it get to the list)
Still broken:
Xen bug #1733, vif-route does not support IPv6
Power management and halt, http://lists.fedoraproject.org/pipermail/xen/2011-January/005328.html
On 02/02/2011 05:43 PM, M A Young wrote:
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
You may need one or both of the following hacks
Edit /etc/init.d/xenstored replacing the line XENSTORED_PID="/var/run/xenstore.pid" with XENSTORED_PID="/var/run/xenstored.pid" (I didn't notice they had changed the name of this file until after I tested the xen packages)
Edit /etc/sysconfig/modules/xen.modules to remove xen-netback from the list of modules in the for loop then add modprobe xen-netback netback_kthread=1 to the end of the file. The xen-netback module in xen/next-2.6.38 when I built the kernel still needed some work and setting this value makes it less likely to throw up backtraces if you try to use it.
Michael Young
First blush (no domUs yet) - dom0 boots with >2GB RAM - dom0 boots with encrypted root partition. - CPU frequency scaling /doesn't/ work (Intel Core2Duo P9400) - There seems to be a UI lag somewhere. Windows and key-presses seem to occasionally "stall" (<1 sec at worst). Not serious, and possibly my imagination.
All in all, this is the first 2.6.37+ dom0 that even booted using the xen hypervisor. That makes it, for me, a huge improvement. :D I'll try provisioning a couple domUs for further testing.
Thanks for the hard work, it really is appreciated!
On 02/02/2011 11:02 PM, Digimer wrote:
First blush (no domUs yet)
- dom0 boots with >2GB RAM
- dom0 boots with encrypted root partition.
- CPU frequency scaling /doesn't/ work (Intel Core2Duo P9400)
- There seems to be a UI lag somewhere. Windows and key-presses seem to
occasionally "stall" (<1 sec at worst). Not serious, and possibly my imagination.
All in all, this is the first 2.6.37+ dom0 that even booted using the xen hypervisor. That makes it, for me, a huge improvement. :D I'll try provisioning a couple domUs for further testing.
Thanks for the hard work, it really is appreciated!
Another note; When I tried to sleep the machine, it hung. Screen went dark and the power button pulsed. I had to hard-reset the machine. :)
On 02/03/2011 08:28 AM, Digimer wrote:
On 02/02/2011 11:02 PM, Digimer wrote:
First blush (no domUs yet)
- dom0 boots with >2GB RAM
- dom0 boots with encrypted root partition.
- CPU frequency scaling /doesn't/ work (Intel Core2Duo P9400)
- There seems to be a UI lag somewhere. Windows and key-presses seem to
occasionally "stall" (<1 sec at worst). Not serious, and possibly my imagination.
All in all, this is the first 2.6.37+ dom0 that even booted using the xen hypervisor. That makes it, for me, a huge improvement. :D I'll try provisioning a couple domUs for further testing.
Thanks for the hard work, it really is appreciated!
Another note; When I tried to sleep the machine, it hung. Screen went dark and the power button pulsed. I had to hard-reset the machine. :)
Yet another; Normal power-off hung as well. Had to cold-boot the laptop. In case it matters, it's a Thinkpad T400s.
note: taken under the plain kernel, not while booting via xen.
lspci: http://pastebin.com/D5QJpb2b dmidecode: http://pastebin.com/mRMhragn cpuinfo: http://pastebin.com/P1hS8AYa uname: Linux lework.alteeve.com 2.6.38-0.rc3.git0.1.xendom0.fc15.x86_64 #1 SMP Tue Feb 1 23:35:33 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
On Thu, 3 Feb 2011, Digimer wrote:
On 02/03/2011 08:28 AM, Digimer wrote:
On 02/02/2011 11:02 PM, Digimer wrote: Another note; When I tried to sleep the machine, it hung. Screen went dark and the power button pulsed. I had to hard-reset the machine. :)
Yet another; Normal power-off hung as well. Had to cold-boot the laptop. In case it matters, it's a Thinkpad T400s.
note: taken under the plain kernel, not while booting via xen.
lspci: http://pastebin.com/D5QJpb2b dmidecode: http://pastebin.com/mRMhragn cpuinfo: http://pastebin.com/P1hS8AYa uname: Linux lework.alteeve.com 2.6.38-0.rc3.git0.1.xendom0.fc15.x86_64 #1 SMP Tue Feb 1 23:35:33 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Try with kernel-2.6.38-0.rc3.git0.1.fc15 at http://koji.fedoraproject.org/koji/buildinfo?buildID=216558 (the latest regular rawhide kernel, though a later was is currently being built). If that shows the same behaviour you can probably file a bug somewhere (eg. http://bugzilla.redhat.com/ ) because it will be a Fedora or mainline kernel issue.
Michael Young
On 02/03/2011 10:04 AM, M A Young wrote:
On Thu, 3 Feb 2011, Digimer wrote:
On 02/03/2011 08:28 AM, Digimer wrote:
On 02/02/2011 11:02 PM, Digimer wrote: Another note; When I tried to sleep the machine, it hung. Screen went dark and the power button pulsed. I had to hard-reset the machine. :)
Yet another; Normal power-off hung as well. Had to cold-boot the laptop. In case it matters, it's a Thinkpad T400s.
note: taken under the plain kernel, not while booting via xen.
lspci: http://pastebin.com/D5QJpb2b dmidecode: http://pastebin.com/mRMhragn cpuinfo: http://pastebin.com/P1hS8AYa uname: Linux lework.alteeve.com 2.6.38-0.rc3.git0.1.xendom0.fc15.x86_64 #1 SMP Tue Feb 1 23:35:33 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Try with kernel-2.6.38-0.rc3.git0.1.fc15 at http://koji.fedoraproject.org/koji/buildinfo?buildID=216558 (the latest regular rawhide kernel, though a later was is currently being built). If that shows the same behaviour you can probably file a bug somewhere (eg. http://bugzilla.redhat.com/ ) because it will be a Fedora or mainline kernel issue.
Michael Young
Will do, and will report.
On 02/03/2011 10:10 AM, Digimer wrote:
Try with kernel-2.6.38-0.rc3.git0.1.fc15 at http://koji.fedoraproject.org/koji/buildinfo?buildID=216558 (the latest regular rawhide kernel, though a later was is currently being built). If that shows the same behaviour you can probably file a bug somewhere (eg. http://bugzilla.redhat.com/ ) because it will be a Fedora or mainline kernel issue.
Michael Young
Will do, and will report.
Booted the stock kernel above, and it slept and powered off cleanly, no jitters and cpu frequency scaling worked. Same with your xen'ified kernel when /not/ running through kernel=xen.gz.
On 02/03/2011 10:04 AM, M A Young wrote:
On Thu, 3 Feb 2011, Digimer wrote:
On 02/03/2011 08:28 AM, Digimer wrote:
On 02/02/2011 11:02 PM, Digimer wrote: Another note; When I tried to sleep the machine, it hung. Screen went dark and the power button pulsed. I had to hard-reset the machine. :)
Yet another; Normal power-off hung as well. Had to cold-boot the laptop. In case it matters, it's a Thinkpad T400s.
note: taken under the plain kernel, not while booting via xen.
lspci: http://pastebin.com/D5QJpb2b dmidecode: http://pastebin.com/mRMhragn cpuinfo: http://pastebin.com/P1hS8AYa uname: Linux lework.alteeve.com 2.6.38-0.rc3.git0.1.xendom0.fc15.x86_64 #1 SMP Tue Feb 1 23:35:33 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Try with kernel-2.6.38-0.rc3.git0.1.fc15 at http://koji.fedoraproject.org/koji/buildinfo?buildID=216558 (the latest regular rawhide kernel, though a later was is currently being built). If that shows the same behaviour you can probably file a bug somewhere (eg. http://bugzilla.redhat.com/ ) because it will be a Fedora or mainline kernel issue.
Michael Young
I should mention; running the same kernel without the Xen microkernel works fine. I can suspend, power off and I don't experience the jitters. I'll still install this though, to be certain.
Yes, it works now. But qemu upstream blkback performance is unacceptable slow during F14 PV DomU install :-
name="VF14" memory=2048 disk = ['file:/usr/tmp/disk.img,xvda,w',] vif = [ 'bridge=br0' ] kernel = "/home/boris/fedora/vmlinuz" ramdisk = "/home/boris/fedora/initrd.img" vcpus=2 on_reboot = 'restart' on_crash = 'restart' # xl create -c f14.install Parsing config file f14.install Daemon running with PID 3589 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.35.6-45.fc14.x86_64 (mockbuild@x86-02.phx2.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Mon Oct 18 23:57:44 UTC 2010 [ 0.000000] Command line: [ 0.000000] ACPI in unprivileged domain disabled [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable) [ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 0000000080000000 (usable) [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI not present or invalid. [ 0.000000] No AGP bridge found [ 0.000000] last_pfn = 0x80000 max_arch_pfn = 0x400000000 [ 0.000000] init_memory_mapping: 0000000000000000-0000000080000000 [ 0.000000] RAMDISK: 01e63000 - 058c0000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000080000000 [ 0.000000] Initmem setup node 0 0000000000000000-0000000080000000 [ 0.000000] NODE_DATA [0000000001e42880 - 0000000001e5687f] [ 0.000000] bootmap [0000000005cf6000 - 0000000005d05fff] pages 10 [ 0.000000] (9/32 early reservations) ==> bootmem [0000000000 - 0080000000] [ 0.000000] #0 [0005cc3000 - 0005cf6000] XEN PAGETABLES ==> [0005cc3000 - 0005cf6000] [ 0.000000] #1 [0001000000 - 0001e42878] TEXT DATA BSS ==> [0001000000 - 0001e42878] [ 0.000000] #2 [0001e63000 - 00058c0000] RAMDISK ==> [0001e63000 - 00058c0000] [ 0.000000] #3 [00058c0000 - 0005cc3000] XEN START INFO ==> [00058c0000 - 0005cc3000] [ 0.000000] #4 [0000001000 - 0000003000] TRAMPOLINE ==> [0000001000 - 0000003000] [ 0.000000] #5 [0000003000 - 0000007000] ACPI WAKEUP ==> [0000003000 - 0000007000] [ 0.000000] #6 [0000100000 - 00004cd000] PGTABLE ==> [0000100000 - 00004cd000] [ 0.000000] #7 [0001e42880 - 0001e56880] NODE_DATA ==> [0001e42880 - 0001e56880] [ 0.000000] #8 [0005cf6000 - 0005d06000] BOOTMAP ==> [0005cf6000 - 0005d06000] [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000001 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal empty [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[2] active PFN ranges [ 0.000000] 0: 0x00000001 -> 0x000000a0 [ 0.000000] 0: 0x00000100 -> 0x00080000 [ 0.000000] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs [ 0.000000] No local APIC present [ 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 80000000 (gap: 80000000:80000000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.1.0-rc3-pre (preserve-AD) [ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:2 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff880005d3c000 s90496 r8192 d24192 u122880 [ 0.000000] pcpu-alloc: s90496 r8192 d24192 u122880 alloc=30*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Xen: using vcpu_info placement [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 516044 [ 0.000000] Policy zone: DMA32 [ 0.000000] Kernel command line: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Checking aperture... [ 0.000000] No AGP bridge found [ 0.000000] Memory: 1984848k/2097152k available (4548k kernel code, 388k absent, 111916k reserved, 7261k data, 944k init) [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. [ 0.000000] RCU-based detection of stalled CPUs is disabled. [ 0.000000] Verbose stalled-CPUs detection is disabled. [ 0.000000] NR_IRQS:16640 nr_irqs:288 [ 0.000000] Console: colour dummy device 80x25 [ 0.000000] console [tty0] enabled [ 0.000000] console [hvc0] enabled [ 0.000000] allocated 20971520 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] installing Xen timer for CPU 0 [ 0.000000] Detected 2833.038 MHz processor. [ 0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 5666.07 BogoMIPS (lpj=2833038) [ 0.000999] pid_max: default: 32768 minimum: 301 [ 0.000999] Security Framework initialized [ 0.000999] SELinux: Initializing. [ 0.000999] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.001629] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.001999] Mount-cache hash table entries: 256 [ 0.002130] Initializing cgroup subsys ns [ 0.002146] Initializing cgroup subsys cpuacct [ 0.002154] Initializing cgroup subsys memory [ 0.002176] Initializing cgroup subsys devices [ 0.002183] Initializing cgroup subsys freezer [ 0.002190] Initializing cgroup subsys net_cls [ 0.002196] Initializing cgroup subsys blkio [ 0.002259] CPU: Unsupported number of siblings 4 [ 0.002270] Performance Events: unsupported p6 CPU model 23 no PMU driver, software events only. [ 0.002322] SMP alternatives: switching to UP code [ 0.003999] ftrace: converting mcount calls to 0f 1f 44 00 00 [ 0.003999] ftrace: allocating 23839 entries in 94 pages [ 0.004359] installing Xen timer for CPU 1 [ 0.004410] SMP alternatives: switching to SMP code [ 0.000999] CPU: Unsupported number of siblings 4 [ 0.005138] Brought up 2 CPUs [ 0.005294] devtmpfs: initialized [ 0.010269] atomic64 test passed for x86-64 platform with CX8 and with SSE [ 0.010293] Grant table initialized [ 0.029274] Time: 165:165:165 Date: 165/165/65 [ 0.029320] NET: Registered protocol family 16 [ 0.030085] PCI: Fatal: No config space access function found [ 0.031569] bio: create slab <bio-0> at 0 [ 0.032055] ACPI: Interpreter disabled. [ 0.032079] xen_balloon: Initialising balloon driver. [ 0.033116] vgaarb: loaded [ 0.033255] SCSI subsystem initialized [ 0.033295] usbcore: registered new interface driver usbfs [ 0.033295] usbcore: registered new interface driver hub [ 0.033295] usbcore: registered new device driver usb [ 0.033295] PCI: System does not support PCI [ 0.033295] PCI: System does not support PCI [ 0.033295] NetLabel: Initializing [ 0.033295] NetLabel: domain hash size = 128 [ 0.033295] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.033295] NetLabel: unlabeled traffic allowed by default [ 0.033295] Switching to clocksource xen [ 0.047306] pnp: PnP ACPI: disabled [ 0.049218] NET: Registered protocol family 2 [ 0.049381] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.050516] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 0.051974] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.052327] TCP: Hash tables configured (established 262144 bind 65536) [ 0.052341] TCP reno registered [ 0.052357] UDP hash table entries: 1024 (order: 3, 32768 bytes) [ 0.052384] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [ 0.052485] NET: Registered protocol family 1 [ 0.052576] Trying to unpack rootfs image as initramfs... [ 0.131692] Freeing initrd memory: 59764k freed [ 0.152319] platform rtc_cmos: registered platform RTC device (no PNP device found) [ 0.152797] audit: initializing netlink socket (disabled) [ 0.152830] type=2000 audit(1296761357.631:1): initialized [ 0.161815] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.163569] VFS: Disk quotas dquot_6.5.2 [ 0.163623] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.164137] msgmni has been set to 3993 [ 0.164711] alg: No test for stdrng (krng) [ 0.164778] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.164789] io scheduler noop registered [ 0.164794] io scheduler deadline registered [ 0.164835] io scheduler cfq registered (default) [ 0.164990] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.165024] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.165031] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.165047] pci-stub: invalid id string "" [ 0.165575] Non-volatile memory driver v1.3 [ 0.165588] Linux agpgart interface v0.103 [ 0.165641] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.167071] brd: module loaded [ 0.167711] loop: module loaded [ 0.167838] Fixed MDIO Bus: probed [ 0.167896] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.167920] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.167939] uhci_hcd: USB Universal Host Controller Interface driver [ 0.167991] PNP: No PS/2 controller found. Probing ports directly. [ 0.168888] mice: PS/2 mouse device common for all mice [ 0.169024] rtc_cmos: probe of rtc_cmos failed with error -16 [ 0.169105] device-mapper: uevent: version 1.0.3 [ 0.169239] device-mapper: ioctl: 4.19.1-ioctl (2010-10-12) initialised: dm-devel@redhat.com [ 0.169370] cpuidle: using governor ladder [ 0.169377] cpuidle: using governor menu [ 0.169621] usbcore: registered new interface driver hiddev [ 0.169642] usbcore: registered new interface driver usbhid [ 0.169648] usbhid: USB HID core driver [ 0.169669] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 0.169789] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 0.169803] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 0.169812] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 0.169876] ip_tables: (C) 2000-2006 Netfilter Core Team [ 0.169895] TCP cubic registered [ 0.169900] Initializing XFRM netlink socket [ 0.169911] NET: Registered protocol family 17 [ 0.170037] registered taskstats version 1 [ 0.170057] XENBUS: Device with no driver: device/vbd/51712 [ 0.170064] XENBUS: Device with no driver: device/vif/0 [ 0.170079] Magic number: 1:252:3141 [ 0.170100] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 0.170118] Initalizing network drop monitor service [ 0.170278] Freeing unused kernel memory: 944k freed [ 0.170608] Write protecting the kernel read-only data: 10240k [ 0.175431] Freeing unused kernel memory: 1576k freed [ 0.176545] Freeing unused kernel memory: 1836k freed [9;0][8] Greetings. anaconda installer init version 14.22 starting mounting /proc filesystem... done
(process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed creating /dev filesystem... done starting udev...done mounting /dev/pts (unix98 pty) filesystem... done mounting /sys filesystem... done
(process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed anaconda installer init version 14.22 using /dev/hvc0 as console trying to remount root filesystem read write... done mounting /tmp as tmpfs... done
(process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed running install... running /sbin/loader detecting hardware... waiting for hardware to initialize... detecting hardware... waiting for hardware to initialize...
Welcome to Fedora for x86_64
Running anaconda 14.22, the Fedora system installer - please wait.
┌─────────────┤ VNC Configuration ├──────────────┐ │ │ │ A password will prevent unauthorized listeners │ │ connecting and monitoring your installation │ │ progress. Please enter a password to be used │ │ for the installation │ │ │ │ Password: ________________ │ │ Password (confirm): ________________ │ │ │ │ │ │ ┌────┐ ┌─────────────┐ ┌──────┐ │ │ │ OK │ │ No password │ │ Back │ │ │ └────┘ └─────────────┘ └──────┘ │ │ │ │ │ └────────────────────────────────────────────────┘
19:30:25 Starting VNC... 19:30:36 The VNC server is now running. 19:30:36
WARNING!!! VNC server running with NO PASSWORD! You can use the vncpassword=<password> boot option if you would like to secure the server.
19:30:36 Please manually connect your vnc client to 192.168.0.104:1 to begin the install. 19:30:37 Starting graphical installation.
Boris.
--- On Wed, 2/2/11, M A Young m.a.young@durham.ac.uk wrote:
From: M A Young m.a.young@durham.ac.uk Subject: [Fedora-xen] rc3 kernel and xen To: xen@lists.fedoraproject.org Date: Wednesday, February 2, 2011, 5:43 PM
I have builds of a new dom0 kernel (2.6.38-0.rc3.git0.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2755802 and xen (4.1.0-0.1.rc3.fc14) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2753907
You may need one or both of the following hacks
Edit /etc/init.d/xenstored replacing the line XENSTORED_PID="/var/run/xenstore.pid" with XENSTORED_PID="/var/run/xenstored.pid" (I didn't notice they had changed the name of this file until after I tested the xen packages)
Edit /etc/sysconfig/modules/xen.modules to remove xen-netback from the list of modules in the for loop then add modprobe xen-netback netback_kthread=1 to the end of the file. The xen-netback module in xen/next-2.6.38 when I built the kernel still needed some work and setting this value makes it less likely to throw up backtraces if you try to use it.
Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
On Thu, 3 Feb 2011, Boris Derzhavets wrote:
Yes, it works now. But qemu upstream blkback performance is unacceptable slow during F14 PV DomU install :-
Yes, unfortunately is true; the problem is the pthread based aio implementation in qemu-xen (I guess with "upstream qemu" you mean the qemu that comes with xen-unstable). To have decent performances we need the new qemu (what we usually refer as "upstream qemu" around here), but it is not ready yet. Our target for this is the xen 4.2 release.