xen March 2008

xen@lists.fedoraproject.org

37 participants
26 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

Cannot start HVM DomU
by Robert Locke 04 Jul '08

04 Jul '08

This has newly started, so I am presuming that it is perhaps related to some recently updated package on F8 in say the last week or so. I have a WindowsXP DomU that when I try to start from virt-manager gives the following error: Error starting domain: virDomainCreate() failed POST operation failed: (xend.err 'int argument required') Details shows: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 472, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 379, in startup self.vm.create() File "/usr/lib/python2.5/site-packages/libvirt.py", line 240, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: virDomainCreate() failed POST operation failed: (xend.err 'int argument required') I have no idea what other information to supply or where to particularly find it since this has generally "just worked" for the occasional running of a Windows instance that I have needed for the last several months. Thanks for any help, --Rob

2 2

Custom bridge script; upgrade from Fedora 6 to Fedora 8
by Ask Bjørn Hansen 07 May '08

07 May '08

Hi, Since upgrading from Fedora 6 to Fedora 8 my custom bridge script stopped working. I need to have both eth0 and eth1 bridged into each XM. My xen machines are just defined in old-style /etc/xen/foo configuration files, like vif = [ 'mac=00:16:3e:42:08:1d, bridge=xenbr0', 'mac=00:16:3e: 42:08:1e, bridge=xenbr1' ] I've changed that to vif = [ 'mac=00:16:3e:42:08:1d, bridge=eth0', 'mac=00:16:3e:42:08:1e, bridge=eth1' ] but when I do a "xm create foo" I still end up with the new interfaces on the wrong bridge! # brctl show bridge name bridge id STP enabled interfaces eth0 8000.0030488c8a26 no peth0 eth1 8000.0030488c8a27 no peth1 xenbr0 8000.feffffffffff no vif1.0 xenbr1 8000.feffffffffff no vif1.1 If I manually move the vifX.X interfaces to the eth0/eth1 bridges then everything works. This is my custom bridge script: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" netdev=eth1 bridge=eth1 "$dir/network-bridge" "$@" netdev=eth0 bridge=eth0 Any ideas? - ask -- http://develooper.com/ - http://askask.com/

3 5

Guest boots OK with ATA disk (hdX) but not SCSI (sdX).
by Friedrich Clausen 06 May '08

06 May '08

Hi All, (please feel free to refer me to the official Xen list if need be) I am still using the same dom0 as outlined in : https://www.redhat.com/archives/fedora-xen/2008-March/msg00006.html I can successfully boot a domU using /dev/hda1 as rootfs but when I boot using a scsi device it is unable to find its rootfs. I created an initrd, preloading the sd_mod, in the hopes that that will fix it. The initrd was created like so: # mkinitrd -v --preload=sd_mod --preload=xenblk --with=xennet --with=xenblktap --with=xenbus_be /tmp/test `uname -r` # cp /tmp/test /boot/initrd-2.6.21.7-2.fc8xen.img And the config of the guest is: kernel = "/boot/vmlinuz-2.6.21.7-2.fc8xen" ramdisk = "/boot/initrd-2.6.21.7-2.fc8xen.img" extra = "ro enforcing=0" root = "/dev/sda1" memory = 256 name = "centos.5-1.64" vif = [ '' ] disk = ['phy:VolGroup00/LogVol00,sda1,w'] But is fails to boot, here are some possibly relevant messages with the complete output at the end of this email : Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading xenblk.ko module register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049 register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049 XENBUS: Timeout connecting to device: device/vbd/2049 (state 6) [ lines removed ] unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Booting has failed. Kernel panic - not syncing: Attempted to kill init! I am glad I can successfully boot a guest but I would still like to get to the bottom of this problem. Thanks! Fred. -------------------------- Complete output -------------------------- Using config file "./centos.conf.sda". Started domain centos.5-1.64 Linux version 2.6.21.7-2.fc8xen (mockbuild(a)xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:34:28 EST 2008 Command line: root=/dev/sda1 ro enforcing=0 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) end_pfn_map = 67584 Zone PFN ranges: DMA 0 -> 67584 DMA32 67584 -> 67584 Normal 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 No mptable found. PERCPU: Allocating 26496 bytes of per cpu data Built 1 zonelists. Total pages: 63160 Kernel command line: root=/dev/sda1 ro enforcing=0 Initializing CPU#0 PID hash table entries: 1024 (order: 10, 8192 bytes) Xen reported: 2327.484 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Software IO TLB disabled Memory: 243620k/270336k available (2265k kernel code, 18172k reserved, 1351k data, 200k init) Calibrating delay using timer specific routine.. 4658.18 BogoMIPS (lpj=2329090) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 SMP alternatives: switching to UP code Freeing SMP alternatives: 28k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 2, 16384 bytes) TCP established hash table entries: 8192 (order: 5, 196608 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 8336k freed audit: initializing netlink socket (disabled) audit(1204798687.726:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.102 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Linux version 2.6.21.7-2.fc8xen (mockbuild(a)xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:34:28 EST 2008 Command line: root=/dev/sda1 ro enforcing=0 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) end_pfn_map = 67584 Zone PFN ranges: DMA 0 -> 67584 DMA32 67584 -> 67584 Normal 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 No mptable found. PERCPU: Allocating 26496 bytes of per cpu data Built 1 zonelists. Total pages: 63160 Kernel command line: root=/dev/sda1 ro enforcing=0 Initializing CPU#0 PID hash table entries: 1024 (order: 10, 8192 bytes) Xen reported: 2327.484 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Software IO TLB disabled Memory: 243620k/270336k available (2265k kernel code, 18172k reserved, 1351k data, 200k init) Calibrating delay using timer specific routine.. 4658.18 BogoMIPS (lpj=2329090) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 SMP alternatives: switching to UP code Freeing SMP alternatives: 28k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 2, 16384 bytes) TCP established hash table entries: 8192 (order: 5, 196608 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 8336k freed audit: initializing netlink socket (disabled) audit(1204798687.726:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.102 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Freeing unused kernel memory: 200k freed Write protecting the kernel read-only data: 981k Red Hat nash version 6.0.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading xenblk.ko module register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049 register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049 XENBUS: Timeout connecting to device: device/vbd/2049 (state 6) Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading mbcache.ko module Loading jbd.ko module Loading ext3.ko module Loading libata.ko module Loading ahci.ko module Waiting for driver initialization. Loading ata_generic.ko module Loading usb-storage.ko module Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. Waiting for driver initialization. stabilized: stat /proc/bus/usb/devices: No such file or directory Loading xennet.ko module netfront: Initialising virtual ethernet driver. netfront: device eth0 has copying receive path. Loading xenbus_be.ko module Loading xenblktap.ko module Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Booting has failed. Kernel panic - not syncing: Attempted to kill init! -------------------------- End Complete output --------------------------

2 1

Newby Help
by Walter Coole 08 Apr '08

08 Apr '08

I'm having trouble getting Xen up on Fedora 6. Following the instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 , I've got xend running, but haven't gotten a viable image running. I tried (per the above) virt-manager. I guessed that http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ was a suitable install tree, but when the installer (Anaconda, I guess) gets to some point (it varies with each attempt) it stalls, sometimes complaining about not getting a file. I also tried xm, but haven't figured out how to deal with the error: Cannot open root device "sda1" Virsh throws a different error: Domain not found: xenUnifiedDomainLookupByName I'm befuddled by having tried several different sources, each of which said "it's soooo easy", but failing to provide sufficient information to get me past these issues, so I'd be grateful if someone could point me to instructions geared to the meanest understanding. Walter

7 15

Problem with XEN
by swethu bandaru 01 Apr '08

01 Apr '08

Respected Sir, When we are trying to install a guest os by using xen in fedora6 I am using virt-install command and i have specified the following What is the name of the VM ?guest1 How much RAM should be allocated in MB ? 200 What would you like to use as the diskpath ? /home/xenbox.img What is the install location ?nfs:192.168.5.47:/home/fc6 In /home/fc6 folder we have the fc6 installation docs. when i used xm list command we have found the guest os guest1 and its permission as -b----- when we have given xm create -c guest1 then we got the errors UNABLE TO READ FILE SYSTEM BOOTLOADER DIDN.T RETURN ANY DATA please help me with this problem Thank you! --------------------------------- Like movies? Here's a limited-time offer: Blockbuster Total Access for one month at no cost.

4 3

How to add a PCI-Card to a DomU?
by Franz Von Hahn 29 Mar '08

29 Mar '08

Hello list! I know that there is some documentation about how to add a PCI-Card to a DomU using pciback and co. My problem is, that I'm really stuck and don't know where to start. Normally I create my DomUs with virt-install, following the instructions and later I get a .sxp-Configfile and an Imagefile. Works perfecty. But how in the world do I now add the PCI-Card to that config.sxp? Do I have to reinstall the DomU to do that? I'm using Fedora 8 with the latest updates. Thanks in advance, yours Franz v. Hahn E-Mails jetzt auf Ihrem Handy. www.yahoo.de/go

1 0

RHEL5 - Xend will not start after software upgrade
by Ubaidul Khan 25 Mar '08

25 Mar '08

Hello, Recently I ran yum update on a RHEL5 x86_64 machine and as part of the update, the following packages were installed: Updated: xen-libs-3.0.3-41.el5.x86_64 Updated: xen-libs-3.0.3-41.el5.i386 Installed: kernel-xen-2.6.18-53.1.14.el5.x86_64 Updated: xen-3.0.3-41.el5.x86_64 After the update, I rebooted the machine. Now, I cannot get xend to start: [root@saleen xen]# /etc/init.d/xend start Starting xend: [ OK ] [root@saleen xen]# ps -ef | grep xend root 4080 1 0 11:27 ? 00:00:00 python /usr/sbin/xend start root 4081 4080 0 11:27 ? 00:00:00 python /usr/sbin/xend start root 4264 3109 0 11:45 pts/1 00:00:00 grep xend [root@saleen log]# tail -f /var/log/xen/xend.log self.obj = klassobj() File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 39, in __init__ self.xd = XendDomain.instance() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 655, in instance inst.init() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 76, in init self._add_domain( File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 139, in xen_domains domlist = xc.domain_getinfo() Error: (13, 'Permission denied') I googled around, but I can't find anything useful. Some people mentioned they rolled back to the previous version of the kernel-xen, xend, xen-libs. I would like to find the reasons behind the problem before rolling back. Any assistance is greatly appreciated. Thanks _________________________________________________________________ In a rush? Get real-time answers with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refres…

2 2

Libvirt and xenstore - glitches on migrate
by Jim Klein 25 Mar '08

25 Mar '08

Nothing major, but when migrating with the current Red Hat xen bits and libvirt on F8 and RHEL, libvirt and virt-manager have all sorts of trouble (though the migrate works fine.) Example below is two laptops, the first with and NFS share of /var/lib/xen/images and the second attached to that share. On a migrate, source console kicks out out of memory errors on xenstore, and virt-manager status for the machine being migrated oscillates between "Running" and "Shutoff." No errors on the target machine. Console errors are listed below: xm migrate -l rhel4 turion64 libvir: error : invalid argument in __virGetDomain libvir: Xen Store error : out of memory libvir: error : invalid argument in __virGetDomain libvir: Xen Store error : out of memory libvir: error : invalid argument in __virGetDomain libvir: Xen Store error : out of memory libvir: error : invalid argument in __virGetDomain libvir: Xen Store error : out of memory libvir: error : invalid argument in __virGetDomain libvir: Xen Store error : out of memory libvir: Xen Daemon error : internal error domain information incomplete, missing name Nothing abnormal in xend.log or xend-debug.log, and the migrate works fine, just general ugliness in the interface (which is a bummer if you are doing a demo in front of an audience.)

1 0

newbie question to increase the size of "guest OS"...
by Dharmesh Kamdar 25 Mar '08

25 Mar '08

Hi, I've installed Fedora 8 as a guest OS on Fedora-7+XEN. The host info: $> uname -a Linux hojo 2.6.21-7.fc7xen #1 SMP Tue Feb 12 12:32:24 EST 2008 i686 athlon i386 GNU/Linux CPU: mobile AMD Athlon(tm) XP-M 1400+ RAM: 1GB ARCHITECTURE: x86 (32 bit) While creating the guest, I specified the storage as /var/lib/xen/images/f8_xen.img (of about 7 GB). Unfortunately the guest OS is running out of storage space and I want to add more storage to it (file system based, no LVM or partition etc). I did manage to increase the size of the image file via "dd" with dd as follows: dd if=/dev/zero of=/var/lib/xen/images/F8_XEN.img bs=2M seek=4096 conv=notrunc count=2048 2048+0 records in 2048+0 records out 4294967296 bytes (4.3 GB) copied, 124.617 s, 34.5 MB/s [root@hojo images]# [root@hojo images]# ls -ltr total 12398420 -rwxr-xr-x 1 root root 12884901888 2008-03-20 19:30 F8_XEN.img [root@hojo images]# Now, I want to add some more storage space to the guest OS. So how do I do it ? Will appreciate if someone can provide some pointers. Thanks, kamdard. ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen March 2008