Boris Derzhavets
2011-Feb-02 19:03 UTC
[Xen-devel] Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
> Just making sure.. you''re running Xen 4.1 ? > The userspace qemu blkback implementation is *only* in Xen 4.1 .. > And it should get used automatically if dom0 kernel blkback is not available.Attempt of DomU install env above :- # xl create -c f14.install Parsing config file f14.install Daemon running with PID 3411 [ 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-rc2 (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.096 MHz processor. [ 0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 5666.19 BogoMIPS (lpj=2833096) [ 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.001567] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.001898] Mount-cache hash table entries: 256 [ 0.002028] Initializing cgroup subsys ns [ 0.002043] Initializing cgroup subsys cpuacct [ 0.002052] Initializing cgroup subsys memory [ 0.002074] Initializing cgroup subsys devices [ 0.002081] Initializing cgroup subsys freezer [ 0.002088] Initializing cgroup subsys net_cls [ 0.002094] Initializing cgroup subsys blkio [ 0.002157] CPU: Unsupported number of siblings 4 [ 0.002168] Performance Events: unsupported p6 CPU model 23 no PMU driver, software events only. [ 0.002221] SMP alternatives: switching to UP code [ 0.002999] ftrace: converting mcount calls to 0f 1f 44 00 00 [ 0.002999] ftrace: allocating 23839 entries in 94 pages [ 0.003348] installing Xen timer for CPU 1 [ 0.003388] SMP alternatives: switching to SMP code [ 0.000999] CPU: Unsupported number of siblings 4 [ 0.005106] Brought up 2 CPUs [ 0.005207] devtmpfs: initialized [ 0.010172] atomic64 test passed for x86-64 platform with CX8 and with SSE [ 0.010194] Grant table initialized [ 0.029174] Time: 165:165:165 Date: 165/165/65 [ 0.029222] NET: Registered protocol family 16 [ 0.030089] PCI: Fatal: No config space access function found [ 0.031659] bio: create slab <bio-0> at 0 [ 0.032065] ACPI: Interpreter disabled. [ 0.032092] xen_balloon: Initialising balloon driver. [ 0.032092] vgaarb: loaded [ 0.032182] SCSI subsystem initialized [ 0.032301] usbcore: registered new interface driver usbfs [ 0.032301] usbcore: registered new interface driver hub [ 0.033031] usbcore: registered new device driver usb [ 0.033066] PCI: System does not support PCI [ 0.033067] PCI: System does not support PCI [ 0.033195] NetLabel: Initializing [ 0.033202] NetLabel: domain hash size = 128 [ 0.033207] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.033226] NetLabel: unlabeled traffic allowed by default [ 0.033297] Switching to clocksource xen [ 0.047271] pnp: PnP ACPI: disabled [ 0.049170] NET: Registered protocol family 2 [ 0.049343] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.050611] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 0.052075] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.052444] TCP: Hash tables configured (established 262144 bind 65536) [ 0.052452] TCP reno registered [ 0.052469] UDP hash table entries: 1024 (order: 3, 32768 bytes) [ 0.052500] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [ 0.052597] NET: Registered protocol family 1 [ 0.052677] Trying to unpack rootfs image as initramfs... [ 0.131750] Freeing initrd memory: 59764k freed [ 0.153181] platform rtc_cmos: registered platform RTC device (no PNP device found) [ 0.153659] audit: initializing netlink socket (disabled) [ 0.153686] type=2000 audit(1296672845.495:1): initialized [ 0.162680] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.164420] VFS: Disk quotas dquot_6.5.2 [ 0.164471] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.164972] msgmni has been set to 3993 [ 0.165582] alg: No test for stdrng (krng) [ 0.165656] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.165668] io scheduler noop registered [ 0.165673] io scheduler deadline registered [ 0.165714] io scheduler cfq registered (default) [ 0.165866] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.165901] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.165908] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.165925] pci-stub: invalid id string "" [ 0.166481] Non-volatile memory driver v1.3 [ 0.166495] Linux agpgart interface v0.103 [ 0.166545] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.167961] brd: module loaded [ 0.168604] loop: module loaded [ 0.168732] Fixed MDIO Bus: probed [ 0.168789] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver [ 0.168813] ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver [ 0.168832] uhci_hcd: USB Universal Host Controller Interface driver [ 0.168884] PNP: No PS/2 controller found. Probing ports directly. [ 0.169056] mice: PS/2 mouse device common for all mice [ 0.169894] rtc_cmos: probe of rtc_cmos failed with error -16 [ 0.169972] device-mapper: uevent: version 1.0.3 [ 0.170095] device-mapper: ioctl: 4.19.1-ioctl (2010-10-12) initialised: dm-devel@redhat.com [ 0.170221] cpuidle: using governor ladder [ 0.170231] cpuidle: using governor menu [ 0.170489] usbcore: registered new interface driver hiddev [ 0.170509] usbcore: registered new interface driver usbhid [ 0.170515] usbhid: USB HID core driver [ 0.170537] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 0.170664] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 0.170678] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 0.170686] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 0.170750] ip_tables: (C) 2000-2006 Netfilter Core Team [ 0.170770] TCP cubic registered [ 0.170775] Initializing XFRM netlink socket [ 0.170787] NET: Registered protocol family 17 [ 0.170915] registered taskstats version 1 [ 0.170936] XENBUS: Device with no driver: device/vbd/51712 [ 0.170942] XENBUS: Device with no driver: device/vif/0 [ 0.170957] Magic number: 1:252:3141 [ 0.170978] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 0.170995] Initalizing network drop monitor service [ 0.171173] Freeing unused kernel memory: 944k freed [ 0.171470] Write protecting the kernel read-only data: 10240k [ 0.176107] Freeing unused kernel memory: 1576k freed [ 0.177188] 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 ┌────────────────────────────┤ Retrieving ├────────────────────────────┐ │ │ │ Retrieving /install.img... │ │ │ │ 100% │ Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... │ kernel: 1% ┘ Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.186082] Call Trace:t Feb 2 21:54:47 ... kernel:[ 423.185529] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.186111] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc c cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.186139] Stack:kvm at Feb 2 21:54:47 ... <F12> next screen kernel:[ 423.186061] Stack: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.186139] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.186139] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.191177] Stack: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.191198] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.191228] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc c cc 51 41 53 b8 1d 00 00 00 0f 25 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.218990] Stack:kvm at Feb 2 21:54:47 ... kernel:[ 423.192039] Stack: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.219010] Call Trace:t Feb 2 21:54:47 ... kernel:[ 423.192060] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.219059] Code: cc 51 41 53 b8 10 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 11 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc c cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.221189] Stack: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.221210] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.221240] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc c 51 41 53 b8 1d 00 00 00 0f 65 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.323933] Call Trace:t Feb 2 21:54:47 ... kernel:[ 423.231207] Stack: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.323966] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc kernel:[ 423.324563] Stack:0 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc c cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.324563] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.324563] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.328363] Stack: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.328384] Call Trace: Message from syslogd@fedora14kvm at Feb 2 21:54:47 ... kernel:[ 423.328415] Code: cc 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc c 51 41 53 b8 1d 00 00 00 0f 85 <41> 5b 59 c3 cc cc cc cc cc cc cc cc Boris. --- On Sat, 1/29/11, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2 To: "W. Michael Petullo" <mike@flyn.org> Cc: xen@lists.fedoraproject.org Date: Saturday, January 29, 2011, 9:08 AM On Thu, Jan 27, 2011 at 05:03:57PM -0600, W. Michael Petullo wrote:> >> Now, the last issue remaining for me is the backend drivers. My > >> understanding is that, in the absence of backends being accepted > >> upstream, we can use QEMU-based drivers. This would be acceptable for > >> our work. Has anyone been using these with Fedora 15? > > > In theory the block driver should work in 4.1.0, though I am not > > sure about the net driver. In practise I have failed so far to get > > the block driver working so far. This post today > > http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html > > talks about what block driver configurations should work. > > I have written the following domain config (to try to force the QEMU > block backend): > > kernel = ''/tmp/openwrt-x86-xen_domu-vmlinuz'' > memory = 32 > # NOTE: Generated with qemu-img convert -f raw -O qcow2 input.img output.qcow2 > disk = [ ''tap:qcow2:/tmp/openwrt-x86-xen_domu-rootfs-ext2.qcow2,xvda,r'', ] > vif = [ ''bridge=virbr0'' ] > name = ''2.6.38-DomU-Test'' > root = ''/dev/xvda1'' > on_crash = ''destroy'' > > When I boot, I get: > > [...] > NET: Registered protocol family 17 > 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> > All bugs added by David S. Miller <davem@redhat.com> > Using IPI No-Shortcut mode > XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s... > > When I try to use: > > disk = [ ''file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r'', ] > > I get: > > [No boot] > Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 >Just making sure.. you''re running Xen 4.1 ? The userspace qemu blkback implementation is *only* in Xen 4.1 .. And it should get used automatically if dom0 kernel blkback is not available. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-Feb-03 11:41 UTC
Re: [Xen-devel] Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Wed, 2 Feb 2011, Boris Derzhavets wrote:> > Just making sure.. you''re running Xen 4.1 ? > > The userspace qemu blkback implementation is *only* in Xen 4.1 .. > > And it should get used automatically if dom0 kernel blkback is not available. > > Attempt of DomU install env above :- > > # xl create -c f14.install > Parsing config file f14.install > Daemon running with PID 3411Are you trying to use 2.6.38 as dom0 or domU? If this test is a dom0 2.6.38 test then you should know that upstream 2.6.38 doesn''t have a network backend yet. IanC is working on it and he has already sent a some patches to the lkml a little while ago. If you want to give it a try, checkout Konrad''s devel/next-2.6.38. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2011-Feb-03 16:08 UTC
Re: [Xen-devel] Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
> If you want to give it a try, checkout Konrad''s > devel/next-2.6.38.Full git path, please. Boris. --- On Thu, 2/3/11, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote: From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> Date: Thursday, February 3, 2011, 6:41 AM On Wed, 2 Feb 2011, Boris Derzhavets wrote:> > Just making sure.. you''re running Xen 4.1 ? > > The userspace qemu blkback implementation is *only* in Xen 4.1 .. > > And it should get used automatically if dom0 kernel blkback is not available. > > Attempt of DomU install env above :- > > # xl create -c f14.install > Parsing config file f14.install > Daemon running with PID 3411Are you trying to use 2.6.38 as dom0 or domU? If this test is a dom0 2.6.38 test then you should know that upstream 2.6.38 doesn''t have a network backend yet. IanC is working on it and he has already sent a some patches to the lkml a little while ago. If you want to give it a try, checkout Konrad''s devel/next-2.6.38. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-Feb-03 16:13 UTC
Re: [Xen-devel] Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, 3 Feb 2011, Boris Derzhavets wrote:> > If you want to give it a try, checkout Konrad''s > > devel/next-2.6.38. > > Full git path, please.Sure, sorry: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/next-2.6.38. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Maybe Matching Threads
- Bug#422819: kernel BUG at drivers/xen/core/evtchn.c
- OCFS2 + CMAN/PCMK Kernel Error
- ocfs2 1.6 2.6.38-2-amd64 kernel panic when unmount
- Wine 1.2 + Kernel 2.6.34.2 + nVidia 256.44 + WoW = Crash!
- Bug#469811: xen-hypervisor-3.0.3-1-i386-pae: kernel BUG at drivers/xen/core/evtchn.c:481