xen January 2011

xen@lists.fedoraproject.org

10 participants
15 discussions

execute commands from dom0 into domU
by silviu d 06 Jun '15

06 Jun '15

Hello, I was wondering if there is a way to execute commands from dom0 into domU without loging into domU with ssh. thanks

3 2

2.6.32.x dom0 kernel
by M A Young 28 Apr '11

28 Apr '11

I have built another 2.6.32.x based kernel (2.6.32.25-172.xendom0.fc12) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2583536 and the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ . This updates the kernel from 2.6.32.25-rc1 to 2.6.32.25 (which may not actually change anything), and uses a later version of xen/stable-2.6.3.32.x which adds a couple of xen fixes. Michael Young

5 18

Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
by Boris Derzhavets 31 Jan '11

31 Jan '11

Attempt to create F14 DomU : name="VF14" memory=2048 disk = ['file:/tmp/disk1.img,xvda,w' ] vif = [ 'bridge=br0' ] # vfb = [ 'type=vnc,vncunused=1'] 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 3311 [ 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(a)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.086 MHz processor. [ 0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 5666.17 BogoMIPS (lpj=2833086) [ 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.001643] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.001999] Mount-cache hash table entries: 256 [ 0.002144] Initializing cgroup subsys ns [ 0.002155] Initializing cgroup subsys cpuacct [ 0.002163] Initializing cgroup subsys memory [ 0.002185] Initializing cgroup subsys devices [ 0.002192] Initializing cgroup subsys freezer [ 0.002198] Initializing cgroup subsys net_cls [ 0.002204] Initializing cgroup subsys blkio [ 0.002264] CPU: Unsupported number of siblings 4 [ 0.002272] Performance Events: unsupported p6 CPU model 23 no PMU driver, software events only. [ 0.002336] 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.003345] installing Xen timer for CPU 1 [ 0.003379] SMP alternatives: switching to SMP code [ 0.000999] CPU: Unsupported number of siblings 4 [ 0.004107] Brought up 2 CPUs [ 0.004210] devtmpfs: initialized [ 0.009241] atomic64 test passed for x86-64 platform with CX8 and with SSE [ 0.009262] Grant table initialized [ 0.028254] Time: 165:165:165 Date: 165/165/65 [ 0.028299] NET: Registered protocol family 16 [ 0.029088] PCI: Fatal: No config space access function found [ 0.030649] bio: create slab <bio-0> at 0 [ 0.030649] ACPI: Interpreter disabled. [ 0.031025] xen_balloon: Initialising balloon driver. [ 0.031058] vgaarb: loaded [ 0.031180] SCSI subsystem initialized [ 0.031303] usbcore: registered new interface driver usbfs [ 0.031303] usbcore: registered new interface driver hub [ 0.031313] usbcore: registered new device driver usb [ 0.032084] PCI: System does not support PCI [ 0.032091] PCI: System does not support PCI [ 0.032245] NetLabel: Initializing [ 0.032245] NetLabel: domain hash size = 128 [ 0.032245] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.032245] NetLabel: unlabeled traffic allowed by default [ 0.032245] Switching to clocksource xen [ 0.046227] pnp: PnP ACPI: disabled [ 0.048124] NET: Registered protocol family 2 [ 0.048286] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.049499] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 0.050962] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.051317] TCP: Hash tables configured (established 262144 bind 65536) [ 0.051325] TCP reno registered [ 0.051341] UDP hash table entries: 1024 (order: 3, 32768 bytes) [ 0.051367] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) [ 0.051464] NET: Registered protocol family 1 [ 0.051544] Trying to unpack rootfs image as initramfs... [ 0.130231] Freeing initrd memory: 59764k freed [ 0.151159] platform rtc_cmos: registered platform RTC device (no PNP device found) [ 0.151588] audit: initializing netlink socket (disabled) [ 0.151611] type=2000 audit(1296486517.664:1): initialized [ 0.160610] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.162444] VFS: Disk quotas dquot_6.5.2 [ 0.162497] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.163020] msgmni has been set to 3993 [ 0.163870] alg: No test for stdrng (krng) [ 0.163953] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.163970] io scheduler noop registered [ 0.163976] io scheduler deadline registered [ 0.164032] io scheduler cfq registered (default) [ 0.164188] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.164224] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.164231] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.164247] pci-stub: invalid id string "" [ 0.164855] Non-volatile memory driver v1.3 [ 0.164863] Linux agpgart interface v0.103 [ 0.164914] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.166386] brd: module loaded [ 0.167028] loop: module loaded [ 0.167169] Fixed MDIO Bus: probed [ 0.167227] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.167250] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.167270] uhci_hcd: USB Universal Host Controller Interface driver [ 0.167321] PNP: No PS/2 controller found. Probing ports directly. [ 0.168056] mice: PS/2 mouse device common for all mice [ 0.168394] rtc_cmos: probe of rtc_cmos failed with error -16 [ 0.168475] device-mapper: uevent: version 1.0.3 [ 0.168635] device-mapper: ioctl: 4.19.1-ioctl (2010-10-12) initialised: dm-devel(a)redhat.com [ 0.168788] cpuidle: using governor ladder [ 0.168795] cpuidle: using governor menu [ 0.169094] usbcore: registered new interface driver hiddev [ 0.169115] usbcore: registered new interface driver usbhid [ 0.169122] usbhid: USB HID core driver [ 0.169145] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 0.169290] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 0.169304] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 0.169312] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 0.169376] ip_tables: (C) 2000-2006 Netfilter Core Team [ 0.169395] TCP cubic registered [ 0.169401] Initializing XFRM netlink socket [ 0.169411] NET: Registered protocol family 17 [ 0.169536] registered taskstats version 1 [ 0.169557] XENBUS: Device with no driver: device/vbd/51712 [ 0.169563] XENBUS: Device with no driver: device/vif/0 [ 0.169578] Magic number: 1:252:3141 [ 0.169597] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 0.169614] Initalizing network drop monitor service [ 0.169776] Freeing unused kernel memory: 944k freed [ 0.170033] Write protecting the kernel read-only data: 10240k [ 0.174701] Freeing unused kernel memory: 1576k freed [ 0.175744] 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... Boris. --- On Mon, 1/31/11, W. Michael Petullo <mike(a)flyn.org> wrote: From: W. Michael Petullo <mike(a)flyn.org> Subject: Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2 To: xen(a)lists.fedoraproject.org Date: Monday, January 31, 2011, 8:40 AM >>>> I have finally got a domU to boot in this sort of situation, having >>>> found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub >>>> as a bootloader. Note that you may have to use xl rather than xm >>>> because they are deprecating xm and xm may not have support for qemu >>>> block backends. >>> Does anyone know where I can find documentatin on domain configuration >>> for xl? There does not seem to be a man page and a review of the Xen Wiki >>> did not find authoritative documentation. I am trying to figure out how >>> to write an xl configuration, i.e., rewrite xmexample1 to work with xl. >> It is supposed to be a direct replacement for xm, the idea being for >> configuration files for xm to work for xl, though not necessarily the >> other way around. In practice, you can still find stuff that doesn't yet >> work. > With the exception that xl doesn't support embedded python code > in the cfgfiles. I am able to boot a DomU kernel using xl with xen-4.1.0-0.1.rc2.fc14.x86_64 and kernel-2.6.38-0.rc2.git3.2.xendom0.fc15.x86_64. Both block and network devices work. -- Mike :wq -- xen mailing list xen(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen

1 0

2.6.38-rc dom0 kernel
by M A Young 31 Jan '11

31 Jan '11

I have a new dom0 kernel available for testing (2.6.38-0.rc2.git3.1.xendom0.fc15) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2742521 This is based on the xen/next-2.6.38 branch with a few extra memory fixes, including one which fixes a problem I had causing a crash during boot. xen/next-2.6.38 adds net and pci backends. Michael Young

6 14

2.6.38-0.rc2.git3.2.xendom0.fc15 and power management
by W. Michael Petullo 29 Jan '11

29 Jan '11

As reported earlier, I have been using 2.6.38-0.rc2.git3.2.xendom0.fc15 with good results. One thing I have come across is that power management does not seem to work. For example, "pm-suspend" does not suspend my system. Instead, the system merely becomes unresponsive. On the other hand, 2.6.32.26-174.2.xendom0 suspends fine. 2.6.38-0.rc2.git3.2.xendom0.fc15 also does not power down my system when I run shutdown. The last things that is printed to the console is: Halting system... [7962.081194] Power down. - The system "halts" but does not power down. -- Mike :wq

2 2

Dom0 xen support in Fedora 15?
by M A Young 21 Jan '11

21 Jan '11

I am trying to work out whether it is practical to propose Dom0 xen support as a feature for Fedora 15. The kernel situation is that Domain 0 has been accepted upstream for 2.6.37. Assuming a 3 month kernel release cycle, F15 will most likely ship with a 2.6.37.x kernel, with 2.6.38 coming out either after the F15 release or just before but too late to be included. If the plan to get key xen drivers into 2.6.38 succeeds, then F15 may be become usable as a Domain 0 system at some point during its lifetime as the kernel package in a Fedora version typically has one major update. If the kernel team accept backported patches then it might just be possible to ship F15 with usable Domain 0 support but the timescale for that would be very tight. The other thing we would need to consider is what needs to be done to make xen friendly enough to be usable by an ordinary user. The page https://fedoraproject.org/wiki/Features/XenPvopsDom0 contains plans from when dom0 xen support was expected to make a quick return to Fedora, but they are a couple of years old now so probably need updating. I think as a minimum we would need a way to add a dom0 enabled grub entry for a kernel, rather than requiring the user to hand edit the grub file. We should also make sure that xen works with the other Fedora virtualisation tools. What do others think about this? For example is it achievable as a feature, is it too early and better to wait for F16, and what else should we aim to do to make xen usable in Fedora? Michael Young

20 45

Network-route and vif-route scripts broken?
by W. Michael Petullo 20 Jan '11

20 Jan '11

This is something I raised on the upstream xen-devel mailing list. I have not yet received any response, so I though I'd try to ask here: I am using Xen with the included network-route and vif-route scripts. My system runs Fedora 14 with Michael Young's Dom0 kernel. When xend starts and network-route executes, I see the following error: /etc/xen/scripts/network-route: line 28: /proc/sys/net/ipv4/conf/eth/proxy_arp: No such file or directory It seems that the problem is that the vifnum shell variable is not set. Later, when I start an unprivileged domain, I see: physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. Are these messages expected? I have submitted a report to the Red Hat Bugzilla system: https://bugzilla.redhat.com/show_bug.cgi?id=669747 The report includes two patches that fix this issue for me. -- Mike :wq

3 3

xen 4.1.0-rc1 build
by M A Young 15 Jan '11

15 Jan '11

Here is another release candidate to test, at http://koji.fedoraproject.org/koji/taskinfo?taskID=2722322 This is my first successful 4.1 build, and I haven't been particularly careful about the choices required to get it to build, so there are likely to be rough edges. Michael Young

2 1

xen 4.0.2-rc1 build
by M A Young 15 Jan '11

15 Jan '11

If anyone wants to test the first release candidate of xen 4.0.2 I have done a test build for Fedora 14 at http://koji.fedoraproject.org/koji/taskinfo?taskID=2713704 Michael Young

3 4

2.6.37 dom0 kernel
by Marko Ristola 12 Jan '11

12 Jan '11

Hi I tried M A Young's precompiled 2.6.37 XEN kernel (under xen-4.0.1-6.fc14.x86_64, grub.conf modified. I have a Radeon card. I booted with and without modesetting, without success. I booted successfully with Radeon driver without acceleration. I'm sending this email from Dom0 :) Speed is as expected. Here is the bug report: Plain Radeon without any xorg.conf modifications on Fedora 14: Initially there was a graphical modesetting based startup. I switched from graphical startup progress graphics into text mode during boot: I could see textual progress messages during bootup. When X tried to start, Radeon kernel driver caused a page fault, that it couldn't handle. Full kernel stack trace was visible on the screen, and it could be looked up with Shift + page up / page down. Unfortunately I don't have time to take a log via serial port this weekend. With nomodeset, booting up progressed (disk IO heard), but the screen was blank all the time. I initiated a reboot from the keyboard. With modesetting with the bug, keyboard didn't work. I initiated a reboot via reset button. Here is the xorg.conf's part as a workaround for Radeon driver problem, /etc/xorg.conf.d/00-radeon.conf for Fedora 14: Section "Device" Identifier "UseRadeon" Driver "radeon" Option "NoAccel" "true" Option "DRI" "false" EndSection Section "Monitor" Identifier "MyMonitor" Option "DPMS" "true" EndSection Section "Screen" Identifier "MyScreen" Device "UseRadeon" Monitor "MyMonitor" EndSection Regards, Marko Ristola

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen January 2011