xen November 2008

xen@lists.fedoraproject.org

18 participants
13 discussions

Guest shutdown problems
by Christian Axelsson 02 Apr '09

02 Apr '09

Hello I have a problem shutting down xen guests. Using xm shutdown guests get shut down but gets stuck in state '---s-d' or sometimes '------'. When trying to clone a domain when in this state (my original purpose of the whole operation) I'll get the error: [root@hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f /var/lib/xen/images/new_img.img ERROR: virDomainGetXMLDesc() failed failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain -490299505 The same errors occurs when for example trying to attach to the console using virsh. I have tried to use 'xm destroy' to kill the guest the hard way but it has no effect - the state remains unchanged. I have also tried this on a few different guest installations with the same result. A thing worth noting is that the output from 'xm list --long' differs, I've attached the out put pre boot, after boot and after shutdown. Note how all the devices in the guests are missing after shutdown. Both the hosts and the guests are fedora 8 installations. Regards, Christian Axelsson smiler(a)lanil.mine.nu [?1034h(domain (domid 0) (on_crash restart) (uuid 00000000-0000-0000-0000-000000000000) (bootloader_args ) (vcpus 2) (name Domain-0) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 16777215) (memory 1491) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (cpu_time 1644.84369405) (online_vcpus 2) (image (linux (kernel ))) (status 2) (state r-----) ) (domain (domid 2) (on_crash restart) (uuid a7638797-e237-3891-5e64-390f828238ca) (bootloader_args ) (vcpus 1) (name minimal) (on_poweroff destroy) (on_reboot restart) (bootloader /usr/bin/pygrub) (maxmem 512) (memory 512) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1206360333.14) (cpu_time 9.753408915) (online_vcpus 1) (image (linux (kernel ) (notes (FEATURES 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel' ) (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 18446744071562067968) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071564189696) (LOADER generic) (SUSPEND_CANCEL 1) (ENTRY 18446744071564165120) (XEN_VERSION xen-3.0) ) ) ) (status 2) (state -b----) (store_mfn 196619) (console_mfn 196618) (device (vif (bridge xenbr0) (mac 00:16:3e:3f:93:b8) (script vif-bridge) (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) (backend 0) ) ) (device (vbd (uname file:/var/lib/xen/images/minimal.img) (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) (mode w) (dev xvda:disk) (backend 0) (bootable 1) ) ) (device (console (protocol vt100) (location 2) (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) ) ) ) [?1034h(domain (domid 0) (on_crash restart) (uuid 00000000-0000-0000-0000-000000000000) (bootloader_args ) (vcpus 2) (name Domain-0) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 16777215) (memory 1491) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (cpu_time 1648.92600832) (online_vcpus 2) (image (linux (kernel ))) (status 2) (state r-----) ) (domain (domid 2) (on_crash restart) (uuid a7638797-e237-3891-5e64-390f828238ca) (bootloader_args ) (vcpus 1) (name minimal) (on_poweroff destroy) (on_reboot restart) (bootloader /usr/bin/pygrub) (maxmem 512) (memory 512) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1206360333.14) (cpu_time 13.048743365) (online_vcpus 1) (image (linux (kernel ) (notes (FEATURES 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel' ) (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 18446744071562067968) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071564189696) (LOADER generic) (SUSPEND_CANCEL 1) (ENTRY 18446744071564165120) (XEN_VERSION xen-3.0) ) ) ) (status 0) (state ---s-d) (store_mfn 196619) (console_mfn 196618) ) [?1034h(domain (domid 0) (on_crash restart) (uuid 00000000-0000-0000-0000-000000000000) (bootloader_args ) (vcpus 2) (name Domain-0) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 16777215) (memory 1491) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (cpu_time 1635.21430615) (online_vcpus 2) (image (linux (kernel ))) (status 2) (state r-----) ) (domain (on_crash restart) (uuid a7638797-e237-3891-5e64-390f828238ca) (bootloader_args ) (vcpus 1) (name minimal) (on_poweroff destroy) (on_reboot restart) (bootloader /usr/bin/pygrub) (maxmem 512) (memory 512) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1206309092.82) (cpu_time 0.0) (image (linux (kernel ) (notes (FEATURES 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel' ) (VIRT_BASE 18446744071562067968) (GUEST_VERSION 2.6) (PADDR_OFFSET 18446744071562067968) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071564189696) (LOADER generic) (SUSPEND_CANCEL 1) (ENTRY 18446744071564165120) (XEN_VERSION xen-3.0) ) ) ) (status 0) (device (vif (bridge xenbr0) (mac 00:16:3e:3f:93:b8) (backend 0) (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) (script vif-bridge) ) ) (device (vbd (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) (bootable 1) (driver paravirtualised) (dev xvda:disk) (uname file:/var/lib/xen/images/minimal.img) (mode w) (backend 0) ) ) (device (console (protocol vt100) (location 2) (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) ) ) )

3 3

Should kernel 2.6.27.5-41.fc9 boot as xen guest?
by M A Young 28 Jan '09

28 Jan '09

I was trying to get a NVIDIA video driver working with the Fedora 9 kernel 2.6.27.5-41.fc9 (on x86_64) and it refused because it decided it was a xen kernel, so I thought I would check this claim out. My attempts to boot a xen guest with that kernel failed, though it got past the boot loader stage, and I know Fedora 9 has kernel-xen packages, but I was wondering whether this kernel would be expected to work or not. Michael Young

2 2

Updating out-of-date Fedora XenPvopsDom0 wiki page
by Pasi Kärkkäinen 22 Jan '09

22 Jan '09

Hi! http://fedoraproject.org/wiki/Features/XenPvopsDom0 Could someone with wiki access update that page.. it contains a lot of out-of-date information. That page is also referenced in F10 release notes.. Things like: - "Work on getting Dom0 support in the upstream kernel has pretty much stalled for the last number of months so this feature is postponed until work upstream restarts." - "Last updated: 2008-07-30" - "x86_64 Dom0 No active work yet...." And many more things are out-of-date, because they're based on earlier work by Redhat/Fedora people.. Upstream (Xensource) is actively working on pv_ops dom0 now, and it's getting close to being included upstream. latest pv_ops dom0 patches: http://xenbits.xen.org/paravirt_ops/patches.hg/ Xen wiki pv_ops status page: http://wiki.xensource.com/xenwiki/XenParavirtOps -- Pasi

3 13

Turning off virt-manager dhcp and dns
by Stephen Johnston 14 Jan '09

14 Jan '09

Hi I have virt-manager with a static ip'ed windows server 2003 and a win xp client so I can play with active directory etc for work. All under Fedora 10 beta. Can someone tell me if I can turn off the dhcp and dns in the virt-manager framework (vibr0) as it is handing out an ip to my client before the virtual windows server does. I believe this is confusing the issue when I try to join the client to my virtual windows domain. I only wish the virt-manager to nat vibr0 to my physical nic so i can provide the other config items from within my virtual network. Thank you. Stephen -- Stephen Johnston 8 Lime Grove Tel. +44 (0)1506 437766 Craigshill Mob. 07786 733 150 Livingston West Lothian EH54 5FB

9 9

rawhide domU on RHEL5.2 dom0?
by Jon Stanley 16 Dec '08

16 Dec '08

I can't seem to make a rawhide domU work on a RHEL5.2 dom0, because virt-install doesn't think that there's a valid tree. Looking at it, there is indeed no images/xen in the tree, are we using the standard kernel for DomU's now, or is F10 not going to be supported as a domU? This is on x86_64.

5 8

Re: Compiling Xen-3.0.-testing.hg from source on FC5[general protection fault 000[1]]
by ADITYA KRISHNAN 29 Nov '08

29 Nov '08

Hi, > > > I am working on x86_64 amd opetron cluster which runs fc5. I wanted to > install the older version of Xen i.e xen 3.0-testing.hg for academic > purposes. I wanted to compile the xen kernel with debug info. Hence I tried > to compile it from source. It compiled successfully and I made corresponding > entries to the grub.conf file. Is there any rpm package for xen with debug > info available on fc5 for x86_64 ? > Please let me know. For now directly compiling from the source gives the > following error: > > root (hd0,0) > Filesystem type is ext2fs, partition type 0x83 > kernel /xen-3.0.2-3.gz console=com2,vga com2=19200,8n1 sync_console > [Multiboot-elf, <0x100000:0xed530:0x39ad0>, shtab=0x227078, > entry=0x100000] [0H0000] [06;00 __ __ _____ ___ ____ > _____ > . > . . (XEN) 3... 2... 1... > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input > to Xen). > kernel direct mapping tables up to f087e000 @ ea2000-ea2000 > Bootdata ok (command line is ro root=LABEL=/ console=ttyS1,19200n8 3 > selinux=0) > Linux version 2.6.16.13-xen (root@opt13) (gcc version 4.1.0 20060304 (Red > Hat 4.1.0-3)) #1 SMP Thu Nov 20 21:45:06 EST 2008 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) > ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) > ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0]) > IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23 > ACPI: IOAPIC (id[0x05] address[0xfebff000] gsi_base[24]) > IOAPIC[1]: apic_id 5, version 17, address 0xfebff000, GSI 24-27 > ACPI: IOAPIC (id[0x06] address[0xfebfe000] gsi_base[28]) > IOAPIC[2]: apic_id 6, version 17, address 0xfebfe000, GSI 28-31 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > Setting APIC routing to xen > Using ACPI (MADT) for SMP configuration information > Allocating PCI resources starting at fc400000 (gap: fc000000:3780000) > Built 1 zonelists > Kernel command line: ro root=LABEL=/ console=ttyS1,19200n8 3 selinux=0 > Initializing CPU#0 > PID hash table entries: 4096 (order: 12, 131072 bytes) > Xen reported: 1793.340 MHz processor. > Console: colour VGA+ 80x25 > Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) > Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) > Software IO TLB enabled: > Aperture: 64 megabytes > Kernel range: 0xffff8800058d1000 - 0xffff8800098d1000 > PCI-DMA: Using software bounce buffering for IO (SWIOTLB) > Memory: 3783548k/3940856k available (2415k kernel code, 148460k reserved, > 904k data, 164k init) > Calibrating delay using timer specific routine.. 3588.10 BogoMIPS > (lpj=17940514) > Security Framework v1.0.0 initialized > Capability LSM initialized > Mount-cache hash table entries: 256 > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 1024K (64 bytes/line) > Initializing CPU#1 > Initializing CPU#2 > Brought up 4 CPUs > Initializing CPU#3 > migration_cost=309 > checking if image is initramfs... it is > Freeing initrd memory: 2177k freed > DMI 2.3 present. > Grant table initialized > NET: Registered protocol family 16 > ACPI: bus type pci registered > PCI: Using configuration type 1 > ACPI: Subsystem revision 20060127 > ACPI: Interpreter enabled > ACPI: Using IOAPIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (0000:00) > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) > xen_mem: Initialising balloon driver. > SCSI subsystem initialized > usbcore: registered new driver usbfs > usbcore: registered new driver hub > PCI: Using ACPI for IRQ routing > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a > report > PCI: Bridge: 0000:00:06.0 > IO window: 9000-bfff > MEM window: fc900000-feafffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:0a.0 > IO window: disabled. > MEM window: fc800000-fc8fffff > PREFETCH window: ff500000-ff5fffff > PCI: Bridge: 0000:00:0b.0 > IO window: disabled. > MEM window: disabled. > PREFETCH window: disabled. > IA-32 Microcode Update Driver: v1.14-xen <tigran(a)veritas.com> > IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > io scheduler noop registered > io scheduler anticipatory registered (default) > io scheduler deadline registered > io scheduler cfq registered > PCI: MSI quirk detected. pci_msi_quirk set. > PCI: MSI quirk detected. pci_msi_quirk set. > Real Time Clock Driver v1.12ac > serio: i8042 AUX port at 0x60,0x64 irq 12 > serio: i8042 KBD port at 0x60,0x64 irq 1 > isa bounce pool size: 16 pages > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize > Xen virtual console successfully installed as ttyS0 > Event-channel device installed. > blkif_init: reqs=64, pages=704, mmap_vstart=0xffff8800ef800000 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > AMD8111: IDE controller at PCI slot 0000:00:07.1 > AMD8111: chipset revision 3 > AMD8111: not 100% native mode: will probe irqs later > AMD8111: 0000:00:07.1 (rev 03) UDMA133 controller > ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio > ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio > hdc: SR244W, ATAPI CD/DVD-ROM drive > ide1 at 0x170-0x177,0x376 on irq 15 > hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) > Uniform CD-ROM driver Revision: 3.20 > ide-floppy driver 0.99.newide > usbmon: debugfs is not available > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > mice: PS/2 mouse device common for all mice > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > NET: Registered protocol family 2 > IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) > TCP established hash table entries: 262144 (order: 10, 4194304 bytes) > TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > TCP: Hash tables configured (established 262144 bind 65536) > TCP reno registered > Initializing IPsec netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > Red Hat nash version 5.0.32 startinginput: AT Translated Set 2 keyboard as > /class/input/input0 > > Mounting proc filesystem > Mounting sysfs filesystem > Creating /dev > Creating initial device nodes > Setting up hotplug. > Creating block device nodes. > Loading sata_sil.ko module > GSI 16 sharing vector 0x98 and IRQ 16 > ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 19 (level, low) -> IRQ 16 > ata1: SATA max UDMA/100 cmd 0xFFFFC20000004C80 ctl 0xFFFFC20000004C8A bmdma > 0xFFFFC20000004C00 irq 16 > ata2: SATA max UDMA/100 cmd 0xFFFFC20000004CC0 ctl 0xFFFFC20000004CCA bmdma > 0xFFFFC20000004C08 irq 16 > ata3: SATA max UDMA/100 cmd 0xFFFFC20000004E80 ctl 0xFFFFC20000004E8A bmdma > 0xFFFFC20000004E00 irq 16 > ata4: SATA max UDMA/100 cmd 0xFFFFC20000004EC0 ctl 0xFFFFC20000004ECA bmdma > 0xFFFFC20000004E08 irq 16 > ata1: SATA link up 1.5 Gbps (SStatus 113) > ata1: dev 0 ATA-7, max UDMA/133, 156301488 sectors: LBA48 > ata1: dev 0 configured for UDMA/100 > scsi0 : sata_sil > ata2: SATA link down (SStatus 0) > scsi1 : sata_sil > ata3: SATA link down (SStatus 0) > scsi2 : sata_sil > ata4: SATA link down (SStatus 0) > scsi3 : sata_sil > Vendor: ATA Model: WDC WD800JD-22LS Rev: 06.0 > Type: Direct-Access ANSI SCSI revision: 05 > SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > sda: sda1 sda2 sda3 sda4 < sda5 sda6 > > sd 0:0:0:0: Attached scsi disk sda > Loading jbd.ko module > Loading ext3.ko module > Creating root device. > Mounting root filesystem. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > INIT: version 2.86 booting > Welcome to Fedora Core > Press 'I' to enter interactive startup. > Setting clock (localtime): Thu Nov 27 22:38:38 EST 2008 [ OK ] > Starting udev: general protection fault: 0000 [1] SMP > CPU 1 > Modules linked in: tg3 i2c_core ext3 jbd sata_sil > Pid: 457, comm: modprobe Not tainted 2.6.16.13-xen #1 > RIP: e030:[<ffffffff801c4332>] <ffffffff801c4332>{create_dir+34} > RSP: e02b:ffff8800ef3cfc28 EFLAGS: 00010296 > RAX: ffffffff88039010 RBX: ffff8800efd12400 RCX: ffff8800ef3cfc60 > RDX: ffff8800efd12400 RSI: 90666690666666c3 RDI: ffff8800efd123f8 > RBP: ffff8800efd123f8 R08: 00000000fffffffe R09: ffff8800eff2b889 > R10: ffff8800efd12000 R11: 0000000000000000 R12: 0000000000000000 > R13: ffff8800efd123e8 R14: ffffffff88039010 R15: ffffffff804049e0 > FS: 00002b49a3774210(0000) GS:ffffffff804a9080(0000) > knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 > Process modprobe (pid: 457, threadinfo ffff8800ef3ce000, task > ffff8800efcc09b0) > Stack: ffff8800efd123f8 ffff8800efd123e8 0000000000000000 ffff8800efd123e8 > ffffffff88039010 ffffffff801c4b28 ffffffff88039010 0000000000000000 > ffff8800efd123f8 ffffffff801f52ea > Call Trace: <ffffffff88039010>{:tg3:tg3_disable_ints+0} > <ffffffff801c4b28>{sysfs_create_dir+88} > <ffffffff88039010>{:tg3:tg3_disable_ints+0} > <ffffffff801f52ea>{kobject_add+234} > <ffffffff88039000>{:tg3:tg3_write32+0} > <ffffffff80251cf9>{class_device_add+185} > <ffffffff802f72d1>{netdev_register_sysfs+81} > <ffffffff802ed2d2>{netdev_run_todo+242} > <ffffffff802ec634>{register_netdev+100} > <ffffffff88044b07>{:tg3:tg3_init_one+3175} > <ffffffff801297f3>{__wake_up+67} > <ffffffff80204269>{pci_device_probe+89} > <ffffffff80250d75>{driver_probe_device+101} > <ffffffff80250e50>{__driver_attach+0} > <ffffffff80250eb0>{__driver_attach+96} > <ffffffff80250e50>{__driver_attach+0} > <ffffffff80250619>{bus_for_each_dev+73} > <ffffffff802501f8>{bus_add_driver+136} > <ffffffff802044d0>{__pci_register_driver+128} > <ffffffff8014fdd2>{sys_init_module+258} > <ffffffff8010b2fe>{system_call+134} > <ffffffff8010b278>{system_call+0} > > Code: 48 8b 7e 10 49 89 cc 49 89 f6 48 81 c7 c0 00 00 00 e8 88 33 > RIP <ffffffff801c4332>{create_dir+34} RSP <ffff8800ef3cfc28> > udevd-event[456]: run_program: '/sbin/modprobe' abnormal exit > eepro100.c:v1.09j-t 9/29/99 Donald Becker > http://www.scyld.com/network/eepro100.html > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin < > saw(a)saw.sw.com.sg> and others > sd 0:0:0:0: Attached scsi generic sg0 type 0 > Unable to handle kernel paging request at ffffffff8807c000 RIP: > > Please let me know if I have apply any FC5 related patches to the xen > source. > Please help. > > Thanks, > > Aditya > Graduate student > princeofporsche(a)gmail.com > > >

1 0

Fedora 10 Release and Virtualization News
by Dale Bewley 26 Nov '08

26 Nov '08

Sorry for the annoying cross post. The next Fedora Weekly News[1] will be published Monday, one day before the release of Fedora 10. I would like dedicate a special section of the Virtualization Beat[2] to touting the advances and new features in F10. As with the release notes[3], I am seeking your input. (A little late, I know.) I'm interested not only in the new virtualization features and breakthroughs found in the F10 release, but also any updates that might be right around the corner in f10-updates. Perhaps you have some special insight into the upstream progress of pv_ops, or maybe you know about a almost complete implementation of a libvirt API feature into virt-manager or... I'm sorry if this is a little scattershot. For sometime, I've considered trying to present questions in interview style to each of these lists, but I just haven't gotten that together. The publication deadline is Sunday night, but I'll be able to use anything in the next edition of FWN. Please contribute, even if you read this on Monday. [1] http://fedoraproject.org/wiki/FWN [2] http://fedoraproject.org/wiki/FWN/Beats/Virtualization [3] http://fedoraproject.org/wiki/Docs/Beats/Virtualization -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3

7 13

[Xen-devel] Linux 2.6.27 temporary tree on xenbits
by Pasi Kärkkäinen 21 Nov '08

21 Nov '08

----- Forwarded message from Keir Fraser <keir.fraser(a)eu.citrix.com> ----- From: Keir Fraser <keir.fraser(a)eu.citrix.com> To: "xen-devel(a)lists.xensource.com" <xen-devel(a)lists.xensource.com> Cc: "Dugger, Donald D" <donald.d.dugger(a)intel.com> Date: Fri, 21 Nov 2008 13:02:26 +0000 Subject: [Xen-devel] Linux 2.6.27 temporary tree on xenbits As a stop-gap measure until full dom0 support is ready in pv_ops, I've placed a Linux 2.6.27 tree at http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg Actually this is a Novell-patched 2.6.27 kernel -- see 00-README in the repo for more details. The intention is to give a single source tree to develop and test against for those developers who need a more modern 2.6 kernel for advanced platform work such as power management. Regular test and maintenance will continue to focus on 2.6.18, with a grand switchover when pv_ops in kernel.org is considered sufficiently ready. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message -----

1 0

New to Xen - Need Help Please!
by HostBigger Admin 17 Nov '08

17 Nov '08

Hello All: I am new to Xen and have been having some problems getting it running. I had posted on the xen-users list but they recommended that I direct my questions to this list. So I apologize if this is misdirected. I am just trying to find a solution to the issue I am having. I have read and followed several tutorials and tried different fixes for this issue but have had no luck. Here is my server setup first: Dual Core - Dual Processor Xeon 5120 2GB RAM Virtualization support in bios is enabled CentOS 5.2 No direct console access, only remote access via SSH2 I have used the tutorial located at http://www.howtoforge.com/centos_5.0_xen Everything works up until I run virt-install to create the domU. I run virt-install with the -nographics switch and get the following No console available for domain Domain installation still in progress. You can reconnect to the console to complete the installation process. I then tried to connect to the console using Xm console 5 And I get: xenconsole: Could not read tty from store: No such file or directory I looked at the qemu log in /var/log/xen And this is what I see domid: 5 qemu: the number of cpus is 1 *** image /local/domain/0/backend/vbd/5/768 format raw driver 0x80e7940 *** image /local/domain/0/backend/vbd/5/5632 format raw driver 0x80e7940 Watching /local/domain/5/logdirty/next-active Could not initialize SDL - exiting I am however unable to find any information on this error. So basically I am in need of help in getting a domU started and running. Can someone please give me some advice, point me in the right direction etc? Thanks in advance Jason

2 1

[PATCH 00 of 38] xen: add more Xen dom0 support
by Pasi Kärkkäinen 13 Nov '08

13 Nov '08

----- Forwarded message from Jeremy Fitzhardinge <jeremy(a)goop.org> ----- From: Jeremy Fitzhardinge <jeremy(a)goop.org> To: Ingo Molnar <mingo(a)elte.hu> Cc: linux-kernel(a)vger.kernel.org, Xen-devel <xen-devel(a)lists.xensource.com>, the arch/x86 maintainers <x86(a)kernel.org>, Ian Campbell <ian.campbell(a)citrix.com> Date: Thu, 13 Nov 2008 11:09:58 -0800 Subject: [PATCH 00 of 38] xen: add more Xen dom0 support Hi Ingo, Here's the chunk of patches to add Xen Dom0 support (it's probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain's pseudo-physical addresses and real machine addresses (for ioremap and setting up DMA) - routing hardware interrupts into the domain ioremap is relatively easy to deal with. An earlier patch introduced the _PAGE_IOMAP pte flag, which we use to distinguish between a regular pseudo-physical mapping and a real machine mapping. Everything falls out pretty cleanly. A consequence is that the various pieces of table-parsing code - DMI, ACPI, MP, etc - work out of the box. Similarly, the series adds hooks into swiotlb so that architectures can allocate the swiotlb memory appropriately; on the x86/xen side, Xen hooks these allocation functions to make special hypercalls to guarantee that the allocated memory is contiguous in machine memory. Interrupts are a very different affair. The descriptions in each patch describe how it all fits together in detail, but the overview is: 1. Xen owns the local APICs; the dom0 kernel controls the IO APICs 2. Hardware interrupts are delivered on event channels like everything else 3. To set this up, we intercept at pcibios_enable_irq: - given a dev+pin, we use ACPI to get a gsi - hook acpi_register_gsi to call xen_register_gsi, which - allocates an irq (generally not 1:1 with the gsi) - asks Xen for a vector and event channel for the irq - program the IO APIC to deliver the hardware interrupt to the allocated vector The upshot is that the device driver gets an irq, and when the hardware raises an interrupt, it gets delivered on that irq. We maintain our own irq allocation space, since the hardware-bound event channel irqs are intermixed with all the other normal Xen event channel irqs (inter-domain, timers, IPIs, etc). For compatibility the irqs 0-15 are reserved for legacy device interrupts, but the rest of the range is dynamically allocated. Initialization also requires care. The dom0 kernel parses the ACPI tables as usual, in order to discover the local and IO APICs, and all the rest of the ACPI-provided data the kernel requires. However, because the kernel doesn't own the local APICs and can't directly map the IO APICs, we must be sure to avoid actually touching the hardware when running under Xen. TODO: work out how to fit MSI into all this. So, in summary, this series contains: - dom0 console support - dom0 xenbus support - CPU features and IO access for a privleged domain - mtrrs - making ioremap work on machine addresses - swiotlb allocation hooks - interrupts - introduce PV io_apic operations - add Xen-specific IRQ allocator - switch to using all-Xen event delivery - add pirq Xen interrupt type - table parsing and setup - intercept driver interrupt registration All this code will compile away to nothing when CONFIG_XEN_DOM0 is not enabled. If it is enabled, it will only have an effect if booted as a dom0 kernel; normal native execution and domU execution should be unaffected. Thanks, J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ----- End forwarded message -----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen November 2008