xen April 2008

xen@lists.stg.fedoraproject.org

32 participants
31 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

Xen 3.x FC6 paravirt no issues, trying to create guest with full virt, problem
by Tory M Blue 29 Apr '08

29 Apr '08

If I do a install using -p things work great, no issues, have 8+ virtuals created around using para and even on my fully virtual enabled server, I can create a guest without issue using paravirtual. If i do the same install but use the config switch -v (full virtualization) the install dumps me back saying i can reconnect but I can't. Attempted creation: [root@devxen xen]# /usr/bin/virt-install --debug -n trub -r 1000 -m 00:16:3e:41:71:d1 --nographics --os-type=linux --os-variant=fedora6 -l /virtual.img -f /dev/mapper/dev-trub --noapic --noacpi --arch=i686 Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. y Tue, 29 Apr 2008 14:25:34 DEBUG Path is block file: Assuming Block disk type. Starting install... libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Tue, 29 Apr 2008 14:25:35 DEBUG Creating guest from '<domain type='xen'> <name>trub</name> <currentMemory>1024000</currentMemory> <memory>1024000</memory> <uuid>dd0a4cef-ce10-b268-fa3f-5e44e4ac346c</uuid> <os> <type arch='i686'>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev='cdrom'/> </os> <features> <apic/><acpi/><pae/> </features> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <vcpu>1</vcpu> <devices> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> <console device='pty'/> <disk type='block' device='disk'> <source dev='/dev/mapper/dev-trub'/> <target dev='hda'/> </disk> <disk type='file' device='cdrom'> <source file='/virtual.img'/> <target dev='hdc'/> <readonly/> </disk> <interface type='bridge'> <source bridge='xenbr0'/> <mac address='00:16:3e:41:71:d1'/> </interface> </devices> </domain> ' Creating domain... 0 B 00:01 Tue, 29 Apr 2008 14:25:36 DEBUG Created guest, looking to see if it is running Tue, 29 Apr 2008 14:25:36 DEBUG Launching console callback Tue, 29 Apr 2008 14:25:36 DEBUG Saving XML boot config '<domain type='xen'> <name>trub</name> <currentMemory>1024000</currentMemory> <memory>1024000</memory> <uuid>dd0a4cef-ce10-b268-fa3f-5e44e4ac346c</uuid> <os> <type arch='i686'>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <features> <apic/><acpi/><pae/> </features> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <vcpu>1</vcpu> <devices> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> <console device='pty'/> <disk type='block' device='disk'> <source dev='/dev/mapper/dev-trub'/> <target dev='hda'/> </disk> <disk type='file' device='cdrom'> <source file=''/> <target dev='hdc'/> <readonly/> </disk> <interface type='bridge'> <source bridge='xenbr0'/> <mac address='00:16:3e:41:71:d1'/> </interface> </devices> </domain> ' Domain installation still in progress. You can reconnect to the console to complete the installation process. [root@devxen xen]# virsh connect trub libvir: error : could not connect to trub error: Failed to connect to the hypervisor [root@devxen xen]# virsh list Id Name State ---------------------------------- 0 Domain-0 running 4 trub no state I can't connect or console or anything and I'm only using console access, ssh, serial, no graphical stuff at all. I must be missing something, just strange. don't see anything in logs, and my remote install is showing that it's getting to installing some boel binaries and nothing else. What's so different about paravirt and fullvirt? Thanks Tory

1 0

[Fwd: Number 9, number 9. Fedora 9 Preview has been cleared for takeoff!]
by Mark McLoughlin 24 Apr '08

24 Apr '08

Hey, There doesn't appear to be any install trees yet for the F9 Preview release, but please do try and run F9 rawhide in your Xen DomU (both i686 and x86_64) and help us flush out any remaining issues in the lead up to the final release. The current blocker list looks like: https://bugzilla.redhat.com/showdependencytree.cgi?id=434756&hide_resolved=1 Cheers, Mark.

3 5

Unable to use multiple CPUs inside an HVM
by David Levinger 23 Apr '08

23 Apr '08

Hey Guys, I have a fully virtualized XP guest that is set to have 2 VCPUs and in the guest I see 2 CPUs but when it is under heavy load it only utilizes 1 of the physical cores. Both xm and virsh show that the guest only has 1 CPU, but my config file and the guest show it should have 2. What am I missing? How can I get this guest to have access to both cores? Thanks! David

4 5

xen booting problem
by swethu bandaru 23 Apr '08

23 Apr '08

While booting XEN I amgetting an eror saying Kernel panic - not syncing:attempted to kill init! I am not getting what is the problem I am using FC6 OS Can any one please suggest me Thank you --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

2 1

Serial console as well as serial access for apps
by bcrawfo2 22 Apr '08

22 Apr '08

I have 2.6.18-53.1.14.el5xen on a box with an on-board serial port I want to use for console access to my dom0. I also have a 4 port serial card I want to use on the dom0 as well. I can configure one or the other...access to the console, or access to the 4 port serials. I can't figure out how to do both. When I get console to work, dmesg | grep ttyS only shows it binding to the virtual console...no others. I do use domUs, but don't have a direct need for serials there. I could, if I had to...move the serial apps over to a domU, but that would be un-ideal. Any help would be appreciated. Thanks Scott -- View this message in context: http://www.nabble.com/Serial-console-as-well-as-serial-access-for-apps-tp16… Sent from the Fedora Xen mailing list archive at Nabble.com.

2 1

Upgrading a Xen guest
by John Swartzentruber 21 Apr '08

21 Apr '08

I hope I am using correct terminology for this question. I'm a home user who is using Xen in a small way, but want to ramp up my usage over time. I have a Fedora 7 host server. On this computer, I installed two Fedora 8 virtual servers using virt-install. What I can't find the answer to, is how to upgrade these virtual computers from Fedora 8 to Fedora 9 when Fedora 9 is released. On my physical server, I normally create an installation DVD, then boot from that. Anaconda then takes care of appropriately upgrading the system and generally does a very good job of it. So how will I do the equivalent for a virtual computer? I don't know how to virtually put the virtual DVD in the virtual DVD drive and reboot the virtual computer. I know I've read of ways to upgrade using Yum, which I assume would work, but I'd prefer to upgrade using Anaconda because that seems like a much safer approach. Because my two current virtual computers are not used for much yet, I could start from scratch, but in the future that isn't going to be the way I will want to handle the upgrades. Thanks for your help. I've read the FedoraProject.org wiki docs, but if there are references I missed, please feel free to point me to them.

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen April 2008