From tom.horsley at att.net Sun Mar 2 15:40:07 2008 From: tom.horsley at att.net (Tom Horsley) Date: Sun, 2 Mar 2008 10:40:07 -0500 Subject: [Fedora-xen] virbr0 comes from where? Message-ID: <20080302104007.3842f6c8@zooty> Actually I'm on centos, but I figure it probably does things similar to fedora. On centos I see a virbr0 bridge that gets created and used in clients where I pick virtual network. I've been trying to understand Xen networking, and since this virbr0 on centos is doing exactly what I tried unsuccessfully to do on a debian xen 3.2 system, I thought I'd look and see how it works. Easy to say, hard to do :-). I can't find any place that creates the virbr0 bridge. I don't see an ifcfg file to create it at boot time, and I just replaced the brctl command with a shell script to log all info about brctl calls, then invoke the original brctl, and no brctl command is ever issued to create virbr0! Where do it come from? From sputhenp at redhat.com Mon Mar 3 07:44:08 2008 From: sputhenp at redhat.com (Sadique Puthen) Date: Mon, 03 Mar 2008 13:14:08 +0530 Subject: [Fedora-xen] virbr0 comes from where? In-Reply-To: <20080302104007.3842f6c8@zooty> References: <20080302104007.3842f6c8@zooty> Message-ID: <47CBAC48.7030007@redhat.com> Tom Horsley wrote: > Actually I'm on centos, but I figure it probably does things > similar to fedora. On centos I see a virbr0 bridge that gets > created and used in clients where I pick virtual network. > > I've been trying to understand Xen networking, and since this > virbr0 on centos is doing exactly what I tried unsuccessfully > to do on a debian xen 3.2 system, I thought I'd look and > see how it works. > > Easy to say, hard to do :-). > > I can't find any place that creates the virbr0 bridge. I don't > see an ifcfg file to create it at boot time, and I just replaced > the brctl command with a shell script to log all info about > brctl calls, then invoke the original brctl, and no brctl command > is ever issued to create virbr0! > > Where do it come from? > This interface is brought up and configured by libvirt. So you probably need the libvirt source to check how it's created and configured. Configuration file for this can be found at /etc/libvirt/qemu/networks. --Sadique > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From rjones at redhat.com Tue Mar 4 11:49:48 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 4 Mar 2008 11:49:48 +0000 Subject: [Fedora-xen] VCL for xen? In-Reply-To: <47324ed80802260726m264451f3q68adaf45591ba200@mail.gmail.com> References: <47324ed80802260726m264451f3q68adaf45591ba200@mail.gmail.com> Message-ID: <20080304114948.GA5248@amd.home.annexia.org> On Tue, Feb 26, 2008 at 10:26:31AM -0500, yonas Abraham wrote: > Hi, > > I am looking for open source application that does similar to NC > states Virtual Computing Library (VCL) for xen management. I have > seen ovirt.org, but it seems to require hardware virtualization, which > I don't have. > > any pointers will be appreciated. virt-manager? http://virt-manager.et.redhat.com/ Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top From rjones at redhat.com Tue Mar 4 11:51:53 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 4 Mar 2008 11:51:53 +0000 Subject: [Fedora-xen] domU auto start order In-Reply-To: <1204078551.13088.3.camel@krs.systemsaligned.com> References: <1204078551.13088.3.camel@krs.systemsaligned.com> Message-ID: <20080304115153.GB5248@amd.home.annexia.org> On Tue, Feb 26, 2008 at 09:15:51PM -0500, Kanwar Ranbir Sandhu wrote: > Is it possible to auto start domU's listed in /etc/xen/auto in a > particular order? I imagine it is, but my reading comprehension or my > searching skills suck, because I can't find anything about this. Yes if you order the names of the start-up scripts alphabetically. However note that this probably doesn't do what you think you want it to do: There is no general way to say "don't start domain Y until domain X is up and running", because basically there is no good definition for "up and running". eg. Should it mean that the kernel is up, or it's reached the login prompt, or all services on X are listening ...? You can't easily test for these conditions, so just ordering the boots only has a minimal benefit. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top From rjones at redhat.com Tue Mar 4 11:52:43 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 4 Mar 2008 11:52:43 +0000 Subject: [Fedora-xen] no guest configuration file in /etc/xen In-Reply-To: <735874.54139.qm@web45706.mail.sp1.yahoo.com> References: <735874.54139.qm@web45706.mail.sp1.yahoo.com> Message-ID: <20080304115243.GC5248@amd.home.annexia.org> On Thu, Feb 28, 2008 at 10:00:29AM -0800, Akl Spec wrote: > Hi All, > > I am newbie to Xen. I installed xen-3.1.0-13.fc8 on fc8 and configured two fedora guest domains, one with virt-manager and the other with virt-installer. Both the virtual servers are up and i can boot them successfully, but both the installation didn't create the guest configuration file in /etc/xen directory(docs says configuration file will be created here). > > Can anybody please help me to find out those files?? Do: virsh dumpxml domainname > domainname.xml Edit the XML file then load it back by doing: virsh start domainname.xml Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v From berrange at redhat.com Tue Mar 4 15:17:52 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 4 Mar 2008 15:17:52 +0000 Subject: [Fedora-xen] virbr0 comes from where? In-Reply-To: <20080302104007.3842f6c8@zooty> References: <20080302104007.3842f6c8@zooty> Message-ID: <20080304151752.GD6713@redhat.com> On Sun, Mar 02, 2008 at 10:40:07AM -0500, Tom Horsley wrote: > Actually I'm on centos, but I figure it probably does things > similar to fedora. On centos I see a virbr0 bridge that gets > created and used in clients where I pick virtual network. > > I've been trying to understand Xen networking, and since this > virbr0 on centos is doing exactly what I tried unsuccessfully > to do on a debian xen 3.2 system, I thought I'd look and > see how it works. > > Easy to say, hard to do :-). > > I can't find any place that creates the virbr0 bridge. I don't > see an ifcfg file to create it at boot time, and I just replaced > the brctl command with a shell script to log all info about > brctl calls, then invoke the original brctl, and no brctl command > is ever issued to create virbr0! > > Where do it come from? It is the 'default' network shown by: virsh net-list There is no ifcfg file associatwe with it - it is managed directly by libvirt Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From fred at derf.nl Wed Mar 5 12:34:42 2008 From: fred at derf.nl (Friedrich Clausen) Date: Wed, 5 Mar 2008 13:34:42 +0100 Subject: [Fedora-xen] Fedora 8 - Guest can't find rootfs. Message-ID: Hi, Note: Full kernel output at end of email and Xen logs are at http://www.derf.nl/drop/xen-logs Details: OS - Fedora 8 Arch - x86_64 Kernel - 2.6.21.7-2.fc8xen Packages - xen-3.1.2-2.fc8, kernel-xen-2.6.21.7-2.fc8, xen-libs-3.1.2-2.fc8 Description: I am trying to boot a CentOS image downloaded from jailtime.org, specifically the image at: http://www.jailtime.org/download:centos64:v5.1 My configuration currently looks like this: kernel = "/boot/vmlinuz-2.6.21.7-2.fc8xen" ramdisk = "/boot/initrd-2.6.21.7-2.fc8xen.img" memory = 256 name = "centos.5-1.64" vif = [ '' ] disk = ['file:/var/lib/xen/images/xen/centos.5-1.64.img,sda1,w', 'file:/var/lib/xen/images/xen/centos.swap,sda2,w'] root = "/dev/sda1" extra = "ro enforcing=0" Selinux is off on the dom0 host, which is Fedora 8. The seemingly relevant bit of the log is : Loading xenblk.ko module register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2049 register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2049 register_blkdev: cannot get major 8 for sd vbd vbd-2050: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2050 register_blkdev: cannot get major 8 for sd vbd vbd-2050: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2050 XENBUS: Timeout connecting to device: device/vbd/2049 (state 6) XENBUS: Timeout connecting to device: device/vbd/2050 (state 6) 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! I have tried the following : * I have create a new initrd, making sure to include the Xen block devices but the guest is still not able to boot. * Loopback mounted to check for for the existence of /proc,/dev and /sys and those dirs are present. Any assistance will be much appreciated! Thanks, Fred. ------------------------------ Full log output below ------------------------------ Using config file "./centos.5-1.64.xen3.cfg". Started domain centos.5-1.64 Linux version 2.6.21.7-2.fc8xen ( mockbuild at 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.486 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.34 BogoMIPS (lpj=2329173) 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(1204719069.778: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 at 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.486 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.34 BogoMIPS (lpj=2329173) 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(1204719069.778: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/vbd/2050 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 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 scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.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 xenblk.ko module register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2049 register_blkdev: cannot get major 8 for sd vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2049 register_blkdev: cannot get major 8 for sd vbd vbd-2050: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2050 register_blkdev: cannot get major 8 for sd vbd vbd-2050: 19 xlvbd_add at /local/domain/0/backend/vbd/47/2050 XENBUS: Timeout connecting to device: device/vbd/2049 (state 6) XENBUS: Timeout connecting to device: device/vbd/2050 (state 6) 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 full log ---------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sa212+fcxen at cyconix.com Wed Mar 5 12:52:25 2008 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Wed, 05 Mar 2008 12:52:25 +0000 Subject: [Fedora-xen] Fedora 8 - Guest can't find rootfs. In-Reply-To: References: Message-ID: <47CE9789.1070403@cyconix.com> Have you seen these? http://lists.xensource.com/archives/html/xen-users/2008-03/msg00088.html http://lists.xensource.com/archives/html/xen-users/2008-02/msg01162.html http://lists.xensource.com/archives/html/xen-users/2008-03/msg00000.html Evan From fred at derf.nl Wed Mar 5 13:29:12 2008 From: fred at derf.nl (Friedrich Clausen) Date: Wed, 5 Mar 2008 14:29:12 +0100 Subject: [Fedora-xen] Fedora 8 - Guest can't find rootfs. In-Reply-To: <47CE9789.1070403@cyconix.com> References: <47CE9789.1070403@cyconix.com> Message-ID: Thanks for the references! My problem was that I was not pre-loading the xenblk module, the guest now boots. Thanks again. Fred. On 3/5/08, Evan Lavelle wrote: > > Have you seen these? > > http://lists.xensource.com/archives/html/xen-users/2008-03/msg00088.html > http://lists.xensource.com/archives/html/xen-users/2008-02/msg01162.html > http://lists.xensource.com/archives/html/xen-users/2008-03/msg00000.html > > Evan > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dustin.Henning at prd-inc.com Wed Mar 5 14:48:13 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 5 Mar 2008 09:48:13 -0500 Subject: [Fedora-xen] domU auto start order In-Reply-To: <20080304115153.GB5248@amd.home.annexia.org> References: <1204078551.13088.3.camel@krs.systemsaligned.com> <20080304115153.GB5248@amd.home.annexia.org> Message-ID: <002801c87ecf$f07e53c0$d17afb40$@Henning@prd-inc.com> I don't know if the virt-manager created domains are affected by this, but there is a setting in one of the xend configs that allows you to set how long to wait before starting each domain, this would allow you to at least have one domain close to (if not fully) loaded before the next starts. However, I don't know if this is the reason Kanwar wants to change the boot order anyway. Additionally, this setting extends the Dom0 boot by the number of domains multiplied by the length of the delay. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Richard W.M. Jones Sent: Tuesday, March 04, 2008 06:52 To: Kanwar Ranbir Sandhu Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] domU auto start order On Tue, Feb 26, 2008 at 09:15:51PM -0500, Kanwar Ranbir Sandhu wrote: > Is it possible to auto start domU's listed in /etc/xen/auto in a > particular order? I imagine it is, but my reading comprehension or my > searching skills suck, because I can't find anything about this. Yes if you order the names of the start-up scripts alphabetically. However note that this probably doesn't do what you think you want it to do: There is no general way to say "don't start domain Y until domain X is up and running", because basically there is no good definition for "up and running". eg. Should it mean that the kernel is up, or it's reached the login prompt, or all services on X are listening ...? You can't easily test for these conditions, so just ordering the boots only has a minimal benefit. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From Dustin.Henning at prd-inc.com Wed Mar 5 14:48:13 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 5 Mar 2008 09:48:13 -0500 Subject: [Fedora-xen] domU auto start order In-Reply-To: <20080304115153.GB5248@amd.home.annexia.org> References: <1204078551.13088.3.camel@krs.systemsaligned.com> <20080304115153.GB5248@amd.home.annexia.org> Message-ID: <002801c87ecf$f07e53c0$d17afb40$@Henning@prd-inc.com> I don't know if the virt-manager created domains are affected by this, but there is a setting in one of the xend configs that allows you to set how long to wait before starting each domain, this would allow you to at least have one domain close to (if not fully) loaded before the next starts. However, I don't know if this is the reason Kanwar wants to change the boot order anyway. Additionally, this setting extends the Dom0 boot by the number of domains multiplied by the length of the delay. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Richard W.M. Jones Sent: Tuesday, March 04, 2008 06:52 To: Kanwar Ranbir Sandhu Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] domU auto start order On Tue, Feb 26, 2008 at 09:15:51PM -0500, Kanwar Ranbir Sandhu wrote: > Is it possible to auto start domU's listed in /etc/xen/auto in a > particular order? I imagine it is, but my reading comprehension or my > searching skills suck, because I can't find anything about this. Yes if you order the names of the start-up scripts alphabetically. However note that this probably doesn't do what you think you want it to do: There is no general way to say "don't start domain Y until domain X is up and running", because basically there is no good definition for "up and running". eg. Should it mean that the kernel is up, or it's reached the login prompt, or all services on X are listening ...? You can't easily test for these conditions, so just ordering the boots only has a minimal benefit. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From lists at ralii.com Wed Mar 5 16:49:06 2008 From: lists at ralii.com (Robert Locke) Date: Wed, 05 Mar 2008 11:49:06 -0500 Subject: [Fedora-xen] Cannot start HVM DomU Message-ID: <1204735746.3707.34.camel@rlt60f8.laptop.redhat.com> 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 From christian.exner at cex-development.de Thu Mar 6 10:21:18 2008 From: christian.exner at cex-development.de (Christian Exner) Date: Thu, 06 Mar 2008 11:21:18 +0100 Subject: [Fedora-xen] After upgrade F7 to F8 vnc console no longer accessible {Scanned} Message-ID: <47CFC59E.5070801@cex-development.de> Hey list, after i upgraded my f7 xen host to f8 there is no way to access my vm's by vnc protocol (from Win workstation with UltraVNC Viewer). Something pops up and hide so quickly there is no chance to see what it is. virt-viewer also does not work. It seems that on f8 the "vnc-server" xen-vncfb has changed to qemu-dm. Can somebody tell me a location for good qemu-dm documentation? Is there a way to get debug output from qemu-dm? Any hint's are welcome. ThX a lot... Chris -- Diese Nachricht wurde auf Viren und andere gef?hrliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber. For all your IT requirements visit: http://www.transtec.co.uk From fred at derf.nl Thu Mar 6 10:25:04 2008 From: fred at derf.nl (Friedrich Clausen) Date: Thu, 6 Mar 2008 11:25:04 +0100 Subject: [Fedora-xen] Guest boots OK with ATA disk (hdX) but not SCSI (sdX). Message-ID: 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 at 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 at 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 -------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Thu Mar 6 15:29:17 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 06 Mar 2008 15:29:17 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen Message-ID: <1204817357.25995.21.camel@muff> Hi, Fedora's Xen hackers have been working hard towards switching our kernel-xen package from a forward-ported Xensource kernel tree to a state-of-the-art upstream, paravirt_ops based, kernel in Fedora 9 as described here: http://fedoraproject.org/wiki/Features/XenPvops http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html Some great progress has been made, and tomorrow's rawhide will have a kernel-xen update with: + A very recent 2.6.25-rc4 base + Xen paravirt_ops DomU from upstream + x86_64 Xen paravirt_ops DomU support + Paravirt framebuffer However, although the Dom0 paravirt_ops work is well advanced at this point, we still don't have backend drivers or x86_64 Dom0 working. With the feature freeze looming next week, we have make the difficult decision to focus the Fedora 9 efforts on DomU and postpone the inclusion of paravirt_ops Dom0 support. The alternative course of action was to keep shipping the 2.6.21.7 based kernel-xen in Fedora 9, but we have ruled this out as a supportable option. This kernel is almost a year old now and we cannot expect Fedora hackers to keep the distribution working on such an old kernel. Examples of the kind of issues we see cropping up are: 1) Broken installs due to old squashfs: https://bugzilla.redhat.com/431109 2) Broken SELinux due to old SELinux: https://bugzilla.redhat.com/436173 3) Broken networking due to old netlink: https://bugzilla.redhat.com/431179 We feel that making significant investment across the distribution to keep this old kernel working for the sake of Dom0 support would be wasting effort on a dead codebase. Work will continue apace on the Dom0 paravirt_ops effort for Fedora 10 and we hope to introduce the first build to rawhide soon after Fedora 9 been branched. This first build should include backend drivers and x86_64 support. If all goes well with the Dom0 support in Fedora 10 rawhide, we may well pull it into Fedora 9 as a post-GA update. So, in summary: 1) Try out the F9 rawhide/beta paravirt_ops kernel-xen in your DomUs 2) Keep your Dom0 on Fedora 8 for now 3) If you want to help out with Dom0 paravirt_ops testing, then be ready to jump onto Fedora 10 rawhide Thanks, Mark. From markmc at redhat.com Thu Mar 6 15:49:56 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 06 Mar 2008 15:49:56 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1204817357.25995.21.camel@muff> References: <1204817357.25995.21.camel@muff> Message-ID: <1204818596.25995.29.camel@muff> On Thu, 2008-03-06 at 15:29 +0000, Mark McLoughlin wrote: > Some great progress has been made, and tomorrow's rawhide will > have a kernel-xen update with: > > + A very recent 2.6.25-rc4 base > > + Xen paravirt_ops DomU from upstream > > + x86_64 Xen paravirt_ops DomU support I forgot to mention a minor detail :-) kernel-xen-2.6.25-0.0.rc4.fc9.x86_64 doesn't actually boot, but hopefully Eduardo will have that fixed up in the next short while ... It boots fine with the config Eduardo was using in testing, but blows up with the stock Fedora config. The i686 kernel seems to be in good shape, so please do give that a hammering. Cheers, Mark. From ametzger at silkspeed.com Thu Mar 6 16:51:34 2008 From: ametzger at silkspeed.com (Aaron Metzger) Date: Thu, 06 Mar 2008 11:51:34 -0500 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1204817357.25995.21.camel@muff> References: <1204817357.25995.21.camel@muff> Message-ID: <47D02116.6010603@silkspeed.com> Mark McLoughlin wrote: > > So, in summary: > > 1) Try out the F9 rawhide/beta paravirt_ops kernel-xen in your DomUs > > 2) Keep your Dom0 on Fedora 8 for now > > 3) If you want to help out with Dom0 paravirt_ops testing, then be > ready to jump onto Fedora 10 rawhide > Do you expect that the DomUs from the final Fedora 9 release will work smoothly with the Dom0 from RHEL/CentOS 5.1? From berrange at redhat.com Thu Mar 6 16:53:53 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 6 Mar 2008 16:53:53 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <47D02116.6010603@silkspeed.com> References: <1204817357.25995.21.camel@muff> <47D02116.6010603@silkspeed.com> Message-ID: <20080306165351.GD19897@redhat.com> On Thu, Mar 06, 2008 at 11:51:34AM -0500, Aaron Metzger wrote: > Mark McLoughlin wrote: > > > > > So, in summary: > > > > 1) Try out the F9 rawhide/beta paravirt_ops kernel-xen in your DomUs > > > > 2) Keep your Dom0 on Fedora 8 for now > > > > 3) If you want to help out with Dom0 paravirt_ops testing, then be > > ready to jump onto Fedora 10 rawhide > > > > Do you expect that the DomUs from the final Fedora 9 release will work > smoothly with the Dom0 from RHEL/CentOS 5.1? Yes, F9 DomU will fully support the Xen 3.x guest ABI, so should be compatible with any host running Xen 3.x releases including RHEL-5 and Fedora >= 5 Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From pasik at iki.fi Thu Mar 6 19:28:05 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 6 Mar 2008 21:28:05 +0200 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1204817357.25995.21.camel@muff> References: <1204817357.25995.21.camel@muff> Message-ID: <20080306192805.GG21162@edu.joroinen.fi> On Thu, Mar 06, 2008 at 03:29:17PM +0000, Mark McLoughlin wrote: > Hi, > Fedora's Xen hackers have been working hard towards switching > our kernel-xen package from a forward-ported Xensource kernel tree to a > state-of-the-art upstream, paravirt_ops based, kernel in Fedora 9 as > described here: > > http://fedoraproject.org/wiki/Features/XenPvops > http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html > > Some great progress has been made, and tomorrow's rawhide will > have a kernel-xen update with: > > + A very recent 2.6.25-rc4 base > > + Xen paravirt_ops DomU from upstream > > + x86_64 Xen paravirt_ops DomU support > > + Paravirt framebuffer > > However, although the Dom0 paravirt_ops work is well advanced at > this point, we still don't have backend drivers or x86_64 Dom0 working. > > With the feature freeze looming next week, we have make the > difficult decision to focus the Fedora 9 efforts on DomU and postpone > the inclusion of paravirt_ops Dom0 support. > First I'd like to thank you guys for doing this work. I think it's very important to get good Xen support working and integrated into upstream kernel. Was there some specific problem/bug about dom0 support (backend drivers and x86-64), or just not enough time? Thanks! -- Pasi From berrange at redhat.com Thu Mar 6 19:33:03 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 6 Mar 2008 19:33:03 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080306192805.GG21162@edu.joroinen.fi> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> Message-ID: <20080306193303.GE19897@redhat.com> On Thu, Mar 06, 2008 at 09:28:05PM +0200, Pasi K?rkk?inen wrote: > On Thu, Mar 06, 2008 at 03:29:17PM +0000, Mark McLoughlin wrote: > > Hi, > > Fedora's Xen hackers have been working hard towards switching > > our kernel-xen package from a forward-ported Xensource kernel tree to a > > state-of-the-art upstream, paravirt_ops based, kernel in Fedora 9 as > > described here: > > > > http://fedoraproject.org/wiki/Features/XenPvops > > http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html > > > > Some great progress has been made, and tomorrow's rawhide will > > have a kernel-xen update with: > > > > + A very recent 2.6.25-rc4 base > > > > + Xen paravirt_ops DomU from upstream > > > > + x86_64 Xen paravirt_ops DomU support > > > > + Paravirt framebuffer > > > > However, although the Dom0 paravirt_ops work is well advanced at > > this point, we still don't have backend drivers or x86_64 Dom0 working. > > > > With the feature freeze looming next week, we have make the > > difficult decision to focus the Fedora 9 efforts on DomU and postpone > > the inclusion of paravirt_ops Dom0 support. > > > > First I'd like to thank you guys for doing this work. I think it's very > important to get good Xen support working and integrated into upstream kernel. > > Was there some specific problem/bug about dom0 support (backend drivers and > x86-64), or just not enough time? Simply lack of time - stability of DomU is of most importance because we can't change the $INSTALL_TREE/images/xen/{vmlinux,initrd.img} once F9 is released. So we need to prioritize DomU support. Pushing out a new kernel to add Dom0 is trivial post-GA since it doesn't impact installer images. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From erenoglu at gmail.com Thu Mar 6 21:37:33 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Thu, 6 Mar 2008 22:37:33 +0100 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080306193303.GE19897@redhat.com> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> Message-ID: Then what would be the Dom0 kernel in Fedora 9? Emre On Thu, Mar 6, 2008 at 8:33 PM, Daniel P. Berrange wrote: > On Thu, Mar 06, 2008 at 09:28:05PM +0200, Pasi K?rkk?inen wrote: > > On Thu, Mar 06, 2008 at 03:29:17PM +0000, Mark McLoughlin wrote: > > > Hi, > > > Fedora's Xen hackers have been working hard towards switching > > > our kernel-xen package from a forward-ported Xensource kernel tree to > a > > > state-of-the-art upstream, paravirt_ops based, kernel in Fedora 9 as > > > described here: > > > > > > http://fedoraproject.org/wiki/Features/XenPvops > > > > http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html > > > > > > Some great progress has been made, and tomorrow's rawhide will > > > have a kernel-xen update with: > > > > > > + A very recent 2.6.25-rc4 base > > > > > > + Xen paravirt_ops DomU from upstream > > > > > > + x86_64 Xen paravirt_ops DomU support > > > > > > + Paravirt framebuffer > > > > > > However, although the Dom0 paravirt_ops work is well advanced > at > > > this point, we still don't have backend drivers or x86_64 Dom0 > working. > > > > > > With the feature freeze looming next week, we have make the > > > difficult decision to focus the Fedora 9 efforts on DomU and postpone > > > the inclusion of paravirt_ops Dom0 support. > > > > > > > First I'd like to thank you guys for doing this work. I think it's very > > important to get good Xen support working and integrated into upstream > kernel. > > > > Was there some specific problem/bug about dom0 support (backend drivers > and > > x86-64), or just not enough time? > > Simply lack of time - stability of DomU is of most importance because we > can't change the $INSTALL_TREE/images/xen/{vmlinux,initrd.img} once F9 > is released. So we need to prioritize DomU support. Pushing out a new > kernel to add Dom0 is trivial post-GA since it doesn't impact installer > images. > > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ -=| > |=- Projects: http://freshmeat.net/~danielpb/ -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 > -=| > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Emre Erenoglu erenoglu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Thu Mar 6 21:54:37 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 6 Mar 2008 21:54:37 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> Message-ID: <20080306215437.GH19897@redhat.com> On Thu, Mar 06, 2008 at 10:37:33PM +0100, Emre ERENOGLU wrote: > Then what would be the Dom0 kernel in Fedora 9? Nothing. There will *not* be any Dom0 kernel in Fedora 9 GA release. People who need Dom0 should stay on Fedora 8. We will work on Dom0 for Fedora 10, and if it is stable enough release it as an Fedora 9 update after GA. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From avi at qumranet.com Fri Mar 7 11:13:52 2008 From: avi at qumranet.com (Avi Kivity) Date: Fri, 07 Mar 2008 13:13:52 +0200 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080306215437.GH19897@redhat.com> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> <20080306215437.GH19897@redhat.com> Message-ID: <47D12370.10306@qumranet.com> Daniel P. Berrange wrote: > On Thu, Mar 06, 2008 at 10:37:33PM +0100, Emre ERENOGLU wrote: > >> Then what would be the Dom0 kernel in Fedora 9? >> > > Nothing. > > You can use xenner to run your Xen DomU, if your machine has hardware virtualization extensions, without a Dom0. -- Any sufficiently difficult bug is indistinguishable from a feature. From berrange at redhat.com Fri Mar 7 15:22:04 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 7 Mar 2008 15:22:04 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <47D12370.10306@qumranet.com> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> <20080306215437.GH19897@redhat.com> <47D12370.10306@qumranet.com> Message-ID: <20080307152204.GA18602@redhat.com> On Fri, Mar 07, 2008 at 01:13:52PM +0200, Avi Kivity wrote: > Daniel P. Berrange wrote: > >On Thu, Mar 06, 2008 at 10:37:33PM +0100, Emre ERENOGLU wrote: > > > >>Then what would be the Dom0 kernel in Fedora 9? > >> > > > >Nothing. > > You can use xenner to run your Xen DomU, if your machine has hardware > virtualization extensions, without a Dom0. In theory yes, but we're still working on getting Xenner integrated with the management tools & aren't confident of getting that completed for F9 GA either, so I wasn't going to mention Xenner yet. It also has a bug currently preventing it from receiving network traffic Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From markmc at redhat.com Fri Mar 7 16:40:04 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 07 Mar 2008 16:40:04 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1204817357.25995.21.camel@muff> References: <1204817357.25995.21.camel@muff> Message-ID: <1204908004.10864.25.camel@muff> Hey, So, just a status update on beta critical bugs with this kernel-xen: 1) x86_64 kernel won't boot https://bugzilla.redhat.com/436485 Eduardo is investigating 2) Anaconda will only do a text mode install at the moment https://bugzilla.redhat.com/434763 Jeremy seems to be on top of this 3) Intermittent boot failure due to disk probing race condition: https://bugzilla.redhat.com/436493 We've a good idea what the fix is, someone just need to backport it and pull it in. 3) Oops during yum update https://bugzilla.redhat.com/436453 We have a tracker bug here: https://bugzilla.redhat.com/showdependencytree.cgi?id=PvOpsTracker Please log any further bugs and add them to the tracker. Cheers, Mark. From Ian.Jackson at eu.citrix.com Fri Mar 7 16:58:38 2008 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Fri, 7 Mar 2008 16:58:38 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1204817357.25995.21.camel@muff> References: <1204817357.25995.21.camel@muff> Message-ID: <18385.29758.551654.984933@mariner.uk.xensource.com> Mark McLoughlin writes ("[Fedora-xen] Plans for paravirt_ops kernel-xen"): > + A very recent 2.6.25-rc4 base Is a public git tree of this kernel available somewhere ? Thanks, Ian. From markmc at redhat.com Fri Mar 7 17:09:47 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 07 Mar 2008 17:09:47 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <18385.29758.551654.984933@mariner.uk.xensource.com> References: <1204817357.25995.21.camel@muff> <18385.29758.551654.984933@mariner.uk.xensource.com> Message-ID: <1204909787.10864.37.camel@muff> On Fri, 2008-03-07 at 16:58 +0000, Ian Jackson wrote: > Mark McLoughlin writes ("[Fedora-xen] Plans for paravirt_ops kernel-xen"): > > + A very recent 2.6.25-rc4 base > > Is a public git tree of this kernel available somewhere ? Unfortunately not. I must move my tree moved to a public server. However, the biggest chunk is definitely Eduardo's x86_64 work which is here: http://git.et.redhat.com/?p=xen-pvops-64.git You can also see the patches that we're including here: http://cvs.fedora.redhat.com/viewcvs/rpms/kernel-xen-2.6/devel/ (All the linux-2.6-xen-00....patch patches) The quick summary is: - Eduardo's x86_64 patches (only applied on x86_64) - Marcus's latest pvfb patches - Frontend module auto-loading and compat aliases - Mark hvc0 as a preferred console - xenctrl module - vmlinuz target - Execshield revert Cheers, Mark. From markmc at redhat.com Fri Mar 7 17:40:44 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 07 Mar 2008 17:40:44 +0000 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1204909787.10864.37.camel@muff> References: <1204817357.25995.21.camel@muff> <18385.29758.551654.984933@mariner.uk.xensource.com> <1204909787.10864.37.camel@muff> Message-ID: <1204911644.10864.41.camel@muff> On Fri, 2008-03-07 at 17:09 +0000, Mark McLoughlin wrote: > On Fri, 2008-03-07 at 16:58 +0000, Ian Jackson wrote: > > Mark McLoughlin writes ("[Fedora-xen] Plans for paravirt_ops kernel-xen"): > > > + A very recent 2.6.25-rc4 base > > > > Is a public git tree of this kernel available somewhere ? > > Unfortunately not. I must move my tree moved to a public server. Okay, Dan sorted me out: http://git.et.redhat.com/?p=linux-2.6-fedora-pvops.git;a=summary Best thing to do is look at the tags where I rebase the patchset, merge commits etc.: http://git.et.redhat.com/?p=linux-2.6-fedora-pvops.git;a=shortlog;h=3a3aec06918f36a7e8d9deff1063a709a193b89f There are also "kernel-xen" tags which correspond to the source being built in the RPMs; that includes all the patches from the bare-metal kernel RPM. Cheers, Mark. From pasik at iki.fi Sun Mar 9 11:12:10 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 9 Mar 2008 13:12:10 +0200 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080306193303.GE19897@redhat.com> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> Message-ID: <20080309111210.GK21162@edu.joroinen.fi> On Thu, Mar 06, 2008 at 07:33:03PM +0000, Daniel P. Berrange wrote: > On Thu, Mar 06, 2008 at 09:28:05PM +0200, Pasi K?rkk?inen wrote: > > On Thu, Mar 06, 2008 at 03:29:17PM +0000, Mark McLoughlin wrote: > > > Hi, > > > Fedora's Xen hackers have been working hard towards switching > > > our kernel-xen package from a forward-ported Xensource kernel tree to a > > > state-of-the-art upstream, paravirt_ops based, kernel in Fedora 9 as > > > described here: > > > > > > http://fedoraproject.org/wiki/Features/XenPvops > > > http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html > > > > > > Some great progress has been made, and tomorrow's rawhide will > > > have a kernel-xen update with: > > > > > > + A very recent 2.6.25-rc4 base > > > > > > + Xen paravirt_ops DomU from upstream > > > > > > + x86_64 Xen paravirt_ops DomU support > > > > > > + Paravirt framebuffer > > > > > > However, although the Dom0 paravirt_ops work is well advanced at > > > this point, we still don't have backend drivers or x86_64 Dom0 working. > > > > > > With the feature freeze looming next week, we have make the > > > difficult decision to focus the Fedora 9 efforts on DomU and postpone > > > the inclusion of paravirt_ops Dom0 support. > > > > > > > First I'd like to thank you guys for doing this work. I think it's very > > important to get good Xen support working and integrated into upstream kernel. > > > > Was there some specific problem/bug about dom0 support (backend drivers and > > x86-64), or just not enough time? > > Simply lack of time - stability of DomU is of most importance because we > can't change the $INSTALL_TREE/images/xen/{vmlinux,initrd.img} once F9 > is released. So we need to prioritize DomU support. Pushing out a new > kernel to add Dom0 is trivial post-GA since it doesn't impact installer > images. > Yep. Thanks for the update! When is fedora 10 rawhide expected to open? Meaning when we can start testing kernel-xen with dom0 support :) -- Pasi From itamar at ispbrasil.com.br Sun Mar 9 11:36:39 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Sun, 09 Mar 2008 08:36:39 -0300 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080309111210.GK21162@edu.joroinen.fi> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> <20080309111210.GK21162@edu.joroinen.fi> Message-ID: <47D3CBC7.5080606@ispbrasil.com.br> I belive at the end of this year. > > Yep. Thanks for the update! > > When is fedora 10 rawhide expected to open? Meaning when we can start > testing kernel-xen with dom0 support :) > > -- Pasi > > From pasik at iki.fi Sun Mar 9 12:09:26 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 9 Mar 2008 14:09:26 +0200 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <47D3CBC7.5080606@ispbrasil.com.br> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> <20080309111210.GK21162@edu.joroinen.fi> <47D3CBC7.5080606@ispbrasil.com.br> Message-ID: <20080309120926.GM21162@edu.joroinen.fi> On Sun, Mar 09, 2008 at 08:36:39AM -0300, Itamar - IspBrasil wrote: > I belive at the end of this year. > Hmm.. I think it's sooner.. Mark wrote like this: "Work will continue on the Dom0 paravirt_ops effort for Fedora 10 and we hope to introduce the first build to rawhide soon after Fedora 9 been branched." I was just wondering when that actually is.. is it when F9 is released (29 April 2008) or sooner, perhaps after F9 beta freeze? -- Pasi > > > > >Yep. Thanks for the update! > > > >When is fedora 10 rawhide expected to open? Meaning when we can start > >testing kernel-xen with dom0 support :) > > > >-- Pasi > > > > > > From pasik at iki.fi Sun Mar 9 12:12:14 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 9 Mar 2008 14:12:14 +0200 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080309120926.GM21162@edu.joroinen.fi> References: <1204817357.25995.21.camel@muff> <20080306192805.GG21162@edu.joroinen.fi> <20080306193303.GE19897@redhat.com> <20080309111210.GK21162@edu.joroinen.fi> <47D3CBC7.5080606@ispbrasil.com.br> <20080309120926.GM21162@edu.joroinen.fi> Message-ID: <20080309121214.GN21162@edu.joroinen.fi> On Sun, Mar 09, 2008 at 02:09:26PM +0200, Pasi K?rkk?inen wrote: > On Sun, Mar 09, 2008 at 08:36:39AM -0300, Itamar - IspBrasil wrote: > > I belive at the end of this year. > > > > Hmm.. I think it's sooner.. > > Mark wrote like this: > > "Work will continue on the Dom0 paravirt_ops effort for Fedora 10 and we > hope to introduce the first build to rawhide soon after Fedora 9 been branched." > > I was just wondering when that actually is.. is it when F9 is released (29 > April 2008) or sooner, perhaps after F9 beta freeze? > Actually looking at this: http://fedoraproject.org/wiki/Releases/9/Schedule 8 April 2008 "Branch all packages for Fedora 9" So I guess that's the answer.. :) -- Pasi > > > > > > > > >Yep. Thanks for the update! > > > > > >When is fedora 10 rawhide expected to open? Meaning when we can start > > >testing kernel-xen with dom0 support :) > > > > > >-- Pasi > > > > > > > > > > > From Hua.Zhang at Sun.COM Sun Mar 9 06:16:13 2008 From: Hua.Zhang at Sun.COM (Henry Zhang) Date: Sun, 09 Mar 2008 14:16:13 +0800 Subject: [Fedora-xen] Re: A problem when creating HVM guest for Win 2003 server In-Reply-To: <47D0F94A.8070101@sun.com> References: <20080301170021.BCD81618CA2@hormel.redhat.com> <47CD54CE.3000702@sun.com> <47D0F94A.8070101@sun.com> Message-ID: <47D380AD.3050600@sun.com> Resending this mail to xen mailing list, hope someone can give any comment. Thanks, Henry Henry Zhang ??: > Hi there, > > When I tried to create a HVM guest for Win 2003 Server by using virt-manager, > I am failed, after the image download, and Win try to reboot, it stop > and complain that 'NTLDR is missing', I'd think it's a bug on Win2003? is > anyone see this problem, and know anything on this problem? > > I enclosed the screen shot for the problem, so you can see what's > happened.... > > Thanks, > Henry > > ------------------------------------------------------------------------ > -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot-1.png Type: image/png Size: 100436 bytes Desc: not available URL: From armbru at redhat.com Mon Mar 10 07:57:05 2008 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 10 Mar 2008 08:57:05 +0100 Subject: [Fedora-xen] After upgrade F7 to F8 vnc console no longer accessible {Scanned} In-Reply-To: <47CFC59E.5070801@cex-development.de> (Christian Exner's message of "Thu\, 06 Mar 2008 11\:21\:18 +0100") References: <47CFC59E.5070801@cex-development.de> Message-ID: <871w6j2er2.fsf@pike.pond.sub.org> Christian Exner writes: > Hey list, > > after i upgraded my f7 xen host to f8 there is no way to access my > vm's by vnc > protocol (from Win workstation with UltraVNC Viewer). Something pops up > and hide so quickly there is no chance to see what it is. > > virt-viewer also does not work. Have you filed a proper bug report for that? Steps to reproduce, actual results, expected results, ... [...] From jgiles at panix.com Tue Mar 11 17:52:53 2008 From: jgiles at panix.com (Jonathan Giles) Date: Tue, 11 Mar 2008 13:52:53 -0400 Subject: [Fedora-xen] 2.6.21.7-2.fc8xen kernel with X11 Message-ID: <3AD4FAE6-6AC0-40AE-A12C-450064173006@panix.com> After trying to resolve this problem on my own, perusing google etc. for 2 weeks, I could use some help figuring out why I can't start X11 when booting 2.6.21.7-2.fc8xen on my desktop. Booting 2.6.23.1-42.fc8 and running X11 works fine. I apologize if this is not the right place for this problem, and understand if you think it should be posted elsewhere. Just let me know and I will post it to the email list you think I should be posting to. logs etc. are truncated. I hope that's okay, I just didn't want to waste people's time. lspci out gives: 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35 Express DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) /var/log/Xorg.setup.log Build Date: 17 October 2007 Build ID: xorg-x11-server 1.3.0.0-33.fc8 (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) EE) intel(0): Internal Error: maxCacheLines < 0 in i830_allocate_2d_memory() (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 any help would be greatly appreciated. Thanks! jg From devesh.chandra at wipro.com Wed Mar 12 08:17:44 2008 From: devesh.chandra at wipro.com (devesh.chandra at wipro.com) Date: Wed, 12 Mar 2008 13:47:44 +0530 Subject: [Fedora-xen] Could not Monitor the VMs on Remote Machine Message-ID: <05B7784238A51247A0A9FB4B348CECAE026E189D@PNE-HJN-MBX01.wipro.com> Hi All, I have installed using Xen and XenMan 0.6 for Managing the Virtual Machines. I am able to monitor the VMs on the local host , but it fails for the remote machine. XenMan. Using netsat -tan , I monitored that managed system listens on 8006 , but XenMan by default connects at 8005 on system XenMan is used to manage other remote machine VMs I tested it also changing the the managing system Port from 8005 to 8006 Following log is generated in the XenMan side When Managed Server Port 8006 Client (Managing Xen Port) 8005 setting last_error [Error 0], [open_channel]Connect failed setting last_error [Error 0], [open_channel]Connect failed setting last_error [Error 0], [open_channel]Connect failed Traceback (most recent call last): File "src/xenman.py", line 2493, in wrapper funct(widget, *args, **cargs) File "src/xenman.py", line 2385, in start_all_domains domains = managed_node.get_dom_names() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 125, in get_dom_names return self.dom_list.iterkeys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 378, in iterkeys return self.dom_dict.keys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 311, in __getattr__ return self._init_dom_list() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 306, in _init_dom_list self.refresh() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 317, in refresh dom_list_info = self.node.node_proxy.xend.domains(1) File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 165, in __call__ ret = self.__send(self.__name, args) File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 122, in __request response = xmlrpclib.ServerProxy.__request(self, methodname, params) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 133, in request return Transport.request(self, host, '/RPC2', request_body, verbose) File "/usr/lib/python2.4/xmlrpclib.py", line 1129, in request self.send_content(h, request_body) File "/usr/lib/python2.4/xmlrpclib.py", line 1243, in send_content connection.endheaders() File "/usr/lib/python2.4/httplib.py", line 798, in endheaders self._send_output() File "/usr/lib/python2.4/httplib.py", line 679, in _send_output self.send(msg) File "/usr/lib/python2.4/httplib.py", line 646, in send self.connect() File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 84, in connect ("localhost",self.localport)) File "/root/XenMan_Installs/xenman-0.6/src/phelper.py", line 326, in open_channel raise CommunicationException(0, "[open_channel]" +str(ex)) CommunicationException: [Error 0], [open_channel]Connect fail The below fragment is generated when I changed the Xen port to 8006 on the managing system side. got expat error no element found: line 1, column 0 Traceback (most recent call last): File "src/xenman.py", line 2493, in wrapper funct(widget, *args, **cargs) File "src/xenman.py", line 2469, in connect_node names = managed_node.get_dom_names() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 125, in get_dom_names return self.dom_list.iterkeys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 378, in iterkeys return self.dom_dict.keys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 311, in __getattr__ return self._init_dom_list() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 306, in _init_dom_list self.refresh() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 317, in refresh dom_list_info = self.node.node_proxy.xend.domains(1) File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 165, in __call__ ret = self.__send(self.__name, args) File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 122, in __request response = xmlrpclib.ServerProxy.__request(self, methodname, params) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 133, in request return Transport.request(self, host, '/RPC2', request_body, verbose) File "/usr/lib/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.4/xmlrpclib.py", line 1284, in _parse_response p.close() File "/usr/lib/python2.4/xmlrpclib.py", line 530, in close self._parser.Parse("", 1) # end of data ExpatError: no element found: line 1, column 0 Valid, writable configuration found, using /etc/xenman.conf got expat error no element found: line 1, column 0 Traceback (most recent call last): File "src/xenman.py", line 584, in handle_timer_callback cls.notebook.showSummaryTab() File "src/xenman.py", line 835, in showSummaryTab self.summary_tab.refresh() File "src/xenman.py", line 1788, in refresh self._populate_pool_summary() File "src/xenman.py", line 1825, in _populate_pool_summary node_snapshot["TOTAL_VMs"] = len(m_node.get_dom_names())-1 File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 125, in get_dom_names return self.dom_list.iterkeys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 378, in iterkeys return self.dom_dict.keys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 311, in __getattr__ return self._init_dom_list() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 306, in _init_dom_list self.refresh() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 317, in refresh dom_list_info = self.node.node_proxy.xend.domains(1) File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 165, in __call__ ret = self.__send(self.__name, args) File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 122, in __request response = xmlrpclib.ServerProxy.__request(self, methodname, params) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 133, in request return Transport.request(self, host, '/RPC2', request_body, verbose) File "/usr/lib/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.4/xmlrpclib.py", line 1284, in _parse_response p.close() File "/usr/lib/python2.4/xmlrpclib.py", line 530, in close self._parser.Parse("", 1) # end of data ExpatError: no element found: line 1, column 0 Exception in callback...ignoring None got expat error no element found: line 1, column 0 Traceback (most recent call last): File "src/xenman.py", line 584, in handle_timer_callback cls.notebook.showSummaryTab() File "src/xenman.py", line 835, in showSummaryTab self.summary_tab.refresh() File "src/xenman.py", line 1788, in refresh self._populate_pool_summary() File "src/xenman.py", line 1825, in _populate_pool_summary node_snapshot["TOTAL_VMs"] = len(m_node.get_dom_names())-1 File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 125, in get_dom_names return self.dom_list.iterkeys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 378, in iterkeys return self.dom_dict.keys() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 311, in __getattr__ return self._init_dom_list() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 306, in _init_dom_list self.refresh() File "/root/XenMan_Installs/xenman-0.6/src/XenNode.py", line 317, in refresh dom_list_info = self.node.node_proxy.xend.domains(1) File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 165, in __call__ ret = self.__send(self.__name, args) File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 122, in __request response = xmlrpclib.ServerProxy.__request(self, methodname, params) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/root/XenMan_Installs/xenman-0.6/src/XenServerProxy.py", line 133, in request return Transport.request(self, host, '/RPC2', request_body, verbose) File "/usr/lib/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.4/xmlrpclib.py", line 1284, in _parse_response p.close() File "/usr/lib/python2.4/xmlrpclib.py", line 530, in close self._parser.Parse("", 1) # end of data ExpatError: no element found: line 1, column 0 Exception in callback...ignoring None -------------- next part -------------- An HTML attachment was scrubbed... URL: From keithm at paisd.com Thu Mar 13 19:45:17 2008 From: keithm at paisd.com (Keith Mitchell) Date: Thu, 13 Mar 2008 12:45:17 -0700 Subject: [Fedora-xen] Console Not Configured For Guest Message-ID: <7CB7AD89F6E23843B328C2C542D5AF5B020BEC4A@gates.paisd.com> Hello- I have a xen xen-3.1.2-2.fc8 vm created using Virtual Machine Manager 0.5.3-1 running on Fedora Core 8 Kernel 2.6.21.7-2.fc8xen. The xen vm is using qemu-dm x64 (hvm). Here is my problem: When I use the Virtual Machine Console to connect to the VM created with the VMM using the .sxp file as its base, the console is able to connect and everything runs fine. When I attempt to bring up the same VM, using a normal xen python config using the same parameters as the sxp file, I get the error from the VMM "Console Not Configured For Guest". I have another VM on the same machine that is paravirtualized and I do not have this problem. I would like to have all my VM's using a common config format for ease of editing, and I'd like to use the xen python format as it has the best documentation. Any suggestions as to what I might look at to try and solve the problem? NOTE: I have examined the qemu.log files, and the only error I can see thrown is "xs_read(): vncpasswd get error." However, that error comes up when the VM is able to connect as well. Keith Mitchell CTO Productivity Associates, Inc. keithm at gotopai.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Fri Mar 14 11:13:27 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 14 Mar 2008 11:13:27 +0000 Subject: [Fedora-xen] Console Not Configured For Guest In-Reply-To: <7CB7AD89F6E23843B328C2C542D5AF5B020BEC4A@gates.paisd.com> References: <7CB7AD89F6E23843B328C2C542D5AF5B020BEC4A@gates.paisd.com> Message-ID: <20080314111327.GA24744@amd.home.annexia.org> On Thu, Mar 13, 2008 at 12:45:17PM -0700, Keith Mitchell wrote: > When I attempt to bring up the same VM, using a normal xen python > config using the same parameters as the sxp file, I get the error from > the VMM "Console Not Configured For Guest". virt-viewer (in Fedora 8) should work. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top From rajaseelan at gmail.com Fri Mar 14 14:01:55 2008 From: rajaseelan at gmail.com (Rajaseelan Ganeswaran) Date: Fri, 14 Mar 2008 22:01:55 +0800 Subject: [Fedora-xen] Fedora (2.6.21.7-2.fc8xen) and Intel GM965 graphic card Message-ID: <2a0f467d0803140701q3ae6021bt7efdecb33e4e2720@mail.gmail.com> Hi all, Video doesn't work in this release of the kernel. I think I need to do the vbios hack for intel. Any suggestions? Here's some output that might help you diagnose:- lspci: 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8039 PCI-E Fast Ethernet Controller (rev 14) 07:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) 08:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 08:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 08:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12) 08:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 08:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) Xorg log: X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Fedora 8 Red Hat, Inc. Current Operating System: Linux atreides.dune 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 Build Date: 12 February 2008 Build ID: xorg-x11-server 1.3.0.0-42.fc8 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 12 23:19:07 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "" (**) | |-->Device "Videocard0" (WW) No monitor specified for screen "Screen0". Using a default monitor configuration. (**) |-->Input Device "Keyboard0" (**) |-->Input Device "Synaptics" (II) No default mouse found, adding one (**) |-->Input Device "" (WW) No FontPath specified. Using compiled-in default. (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins (==) RgbPath set to "/usr/share/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x820cce0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 103c,30cd rev 0c class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2a02 card 103c,30cd rev 0c class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,2a03 card 103c,30cd rev 0c class 03,80,00 hdr 80 (II) PCI: 00:1a:0: chip 8086,2834 card 103c,30cd rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 103c,30cd rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 103c,30cd rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 103c,30cd rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2843 card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:3: chip 8086,2845 card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 103c,30cd rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 103c,30cd rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 103c,30cd rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,2836 card 103c,30cd rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev f3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2815 card 103c,30cd rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2850 card 103c,30cd rev 03 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,2829 card 103c,30cd rev 03 class 01,06,01 hdr 00 (II) PCI: 00:1f:3: chip 8086,283e card 103c,30cd rev 03 class 0c,05,00 hdr 00 (II) PCI: 05:00:0: chip 11ab,4353 card 103c,30cd rev 14 class 02,00,00 hdr 00 (II) PCI: 07:00:0: chip 8086,4229 card 8086,1100 rev 61 class 02,80,00 hdr 00 (II) PCI: 08:09:0: chip 1180,0832 card 103c,30cd rev 05 class 0c,00,10 hdr 80 (II) PCI: 08:09:1: chip 1180,0822 card 103c,30cd rev 22 class 08,05,00 hdr 80 (II) PCI: 08:09:2: chip 1180,0592 card 103c,30cd rev 12 class 08,80,00 hdr 80 (II) PCI: 08:09:3: chip 1180,0852 card 103c,30cd rev 12 class 08,80,00 hdr 80 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,8), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:28:0), (0,2,3), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 2 I/O range: [0] -1 0 0x00002000 - 0x000020ff (0x100) IX[B] [1] -1 0 0x00002400 - 0x000024ff (0x100) IX[B] [2] -1 0 0x00002800 - 0x000028ff (0x100) IX[B] [3] -1 0 0x00002c00 - 0x00002cff (0x100) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xf2000000 - 0xf3ffffff (0x2000000) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xf0000000 - 0xf1ffffff (0x2000000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 5: bridge is at (0:28:1), (0,5,5), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 5 I/O range: [0] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [1] -1 0 0x00003400 - 0x000034ff (0x100) IX[B] [2] -1 0 0x00003800 - 0x000038ff (0x100) IX[B] [3] -1 0 0x00003c00 - 0x00003cff (0x100) IX[B] (II) Bus 5 non-prefetchable memory range: [0] -1 0 0xf4200000 - 0xf42fffff (0x100000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 6: bridge is at (0:28:2), (0,6,6), BCTRL: 0x0004 (VGA_EN is cleared) (II) PCI-to-PCI bridge: (II) Bus 7: bridge is at (0:28:3), (0,7,7), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 7 non-prefetchable memory range: [0] -1 0 0xf4300000 - 0xf43fffff (0x100000) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 8: bridge is at (0:30:0), (0,8,8), BCTRL: 0x0006 (VGA_EN is cleared) (II) Bus 8 non-prefetchable memory range: [0] -1 0 0xf4400000 - 0xf44fffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corporation Mobile Integrated Graphics Controller rev 12, Mem @ 0xf4000000/20, 0xd0000000/28, I/O @ 0x1800/3 (--) PCI: (0:2:1) Intel Corporation Mobile Integrated Graphics Controller rev 12, Mem @ 0xf4100000/20 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xf4401000 - 0xf44010ff (0x100) MX[B] [1] -1 0 0xf4400c00 - 0xf4400cff (0x100) MX[B] [2] -1 0 0xf4400800 - 0xf44008ff (0x100) MX[B] [3] -1 0 0xf4400000 - 0xf44007ff (0x800) MX[B] [4] -1 0 0xf4300000 - 0xf4301fff (0x2000) MX[B] [5] -1 0 0xf4200000 - 0xf4203fff (0x4000) MX[B] [6] -1 0 0xc2000000 - 0xc20000ff (0x100) MX[B] [7] -1 0 0xf4705000 - 0xf47057ff (0x800) MX[B] [8] -1 0 0xf4706000 - 0xf47063ff (0x400) MX[B] [9] -1 0 0xf4500000 - 0xf4503fff (0x4000) MX[B] [10] -1 0 0xf4705c00 - 0xf4705fff (0x400) MX[B] [11] -1 0 0xf4100000 - 0xf41fffff (0x100000) MX[B](B) [12] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [13] -1 0 0xf4000000 - 0xf40fffff (0x100000) MX[B](B) [14] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [15] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [16] -1 0 0x00001c00 - 0x00001c1f (0x20) IX[B] [17] -1 0 0x000018e8 - 0x000018eb (0x4) IX[B] [18] -1 0 0x000018f0 - 0x000018f7 (0x8) IX[B] [19] -1 0 0x000018ec - 0x000018ef (0x4) IX[B] [20] -1 0 0x000018f8 - 0x000018ff (0x8) IX[B] [21] -1 0 0x00001830 - 0x0000183f (0x10) IX[B] [22] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [23] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [26] -1 0 0x000018c0 - 0x000018df (0x20) IX[B] [27] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [28] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [31] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xf4401000 - 0xf44010ff (0x100) MX[B] [1] -1 0 0xf4400c00 - 0xf4400cff (0x100) MX[B] [2] -1 0 0xf4400800 - 0xf44008ff (0x100) MX[B] [3] -1 0 0xf4400000 - 0xf44007ff (0x800) MX[B] [4] -1 0 0xf4300000 - 0xf4301fff (0x2000) MX[B] [5] -1 0 0xf4200000 - 0xf4203fff (0x4000) MX[B] [6] -1 0 0xc2000000 - 0xc20000ff (0x100) MX[B] [7] -1 0 0xf4705000 - 0xf47057ff (0x800) MX[B] [8] -1 0 0xf4706000 - 0xf47063ff (0x400) MX[B] [9] -1 0 0xf4500000 - 0xf4503fff (0x4000) MX[B] [10] -1 0 0xf4705c00 - 0xf4705fff (0x400) MX[B] [11] -1 0 0xf4100000 - 0xf41fffff (0x100000) MX[B](B) [12] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [13] -1 0 0xf4000000 - 0xf40fffff (0x100000) MX[B](B) [14] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [15] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [16] -1 0 0x00001c00 - 0x00001c1f (0x20) IX[B] [17] -1 0 0x000018e8 - 0x000018eb (0x4) IX[B] [18] -1 0 0x000018f0 - 0x000018f7 (0x8) IX[B] [19] -1 0 0x000018ec - 0x000018ef (0x4) IX[B] [20] -1 0 0x000018f8 - 0x000018ff (0x8) IX[B] [21] -1 0 0x00001830 - 0x0000183f (0x10) IX[B] [22] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [23] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [26] -1 0 0x000018c0 - 0x000018df (0x20) IX[B] [27] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [28] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [31] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf4401000 - 0xf44010ff (0x100) MX[B] [5] -1 0 0xf4400c00 - 0xf4400cff (0x100) MX[B] [6] -1 0 0xf4400800 - 0xf44008ff (0x100) MX[B] [7] -1 0 0xf4400000 - 0xf44007ff (0x800) MX[B] [8] -1 0 0xf4300000 - 0xf4301fff (0x2000) MX[B] [9] -1 0 0xf4200000 - 0xf4203fff (0x4000) MX[B] [10] -1 0 0xc2000000 - 0xc20000ff (0x100) MX[B] [11] -1 0 0xf4705000 - 0xf47057ff (0x800) MX[B] [12] -1 0 0xf4706000 - 0xf47063ff (0x400) MX[B] [13] -1 0 0xf4500000 - 0xf4503fff (0x4000) MX[B] [14] -1 0 0xf4705c00 - 0xf4705fff (0x400) MX[B] [15] -1 0 0xf4100000 - 0xf41fffff (0x100000) MX[B](B) [16] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [17] -1 0 0xf4000000 - 0xf40fffff (0x100000) MX[B](B) [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [21] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [22] -1 0 0x00001c00 - 0x00001c1f (0x20) IX[B] [23] -1 0 0x000018e8 - 0x000018eb (0x4) IX[B] [24] -1 0 0x000018f0 - 0x000018f7 (0x8) IX[B] [25] -1 0 0x000018ec - 0x000018ef (0x4) IX[B] [26] -1 0 0x000018f8 - 0x000018ff (0x8) IX[B] [27] -1 0 0x00001830 - 0x0000183f (0x10) IX[B] [28] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [29] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [30] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [31] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [32] -1 0 0x000018c0 - 0x000018df (0x20) IX[B] [33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [34] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [35] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [36] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [37] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "freetype" (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 1.3.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font FreeType (II) LoadModule: "type1" (II) Loading /usr/lib/xorg/modules/fonts//libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Type1 (II) LoadModule: "record" (II) Loading /usr/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension RECORD (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading extension XFree86-DRI (II) LoadModule: "intel" (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.3.0, module version = 2.1.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.2 (II) LoadModule: "kbd" (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.2.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) LoadModule: "synaptics" (II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so (II) Module synaptics: vendor="X.Org Foundation" compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) LoadModule: "mouse" (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.2.3 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset 965GM found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf4401000 - 0xf44010ff (0x100) MX[B] [5] -1 0 0xf4400c00 - 0xf4400cff (0x100) MX[B] [6] -1 0 0xf4400800 - 0xf44008ff (0x100) MX[B] [7] -1 0 0xf4400000 - 0xf44007ff (0x800) MX[B] [8] -1 0 0xf4300000 - 0xf4301fff (0x2000) MX[B] [9] -1 0 0xf4200000 - 0xf4203fff (0x4000) MX[B] [10] -1 0 0xc2000000 - 0xc20000ff (0x100) MX[B] [11] -1 0 0xf4705000 - 0xf47057ff (0x800) MX[B] [12] -1 0 0xf4706000 - 0xf47063ff (0x400) MX[B] [13] -1 0 0xf4500000 - 0xf4503fff (0x4000) MX[B] [14] -1 0 0xf4705c00 - 0xf4705fff (0x400) MX[B] [15] -1 0 0xf4100000 - 0xf41fffff (0x100000) MX[B](B) [16] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [17] -1 0 0xf4000000 - 0xf40fffff (0x100000) MX[B](B) [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [21] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [22] -1 0 0x00001c00 - 0x00001c1f (0x20) IX[B] [23] -1 0 0x000018e8 - 0x000018eb (0x4) IX[B] [24] -1 0 0x000018f0 - 0x000018f7 (0x8) IX[B] [25] -1 0 0x000018ec - 0x000018ef (0x4) IX[B] [26] -1 0 0x000018f8 - 0x000018ff (0x8) IX[B] [27] -1 0 0x00001830 - 0x0000183f (0x10) IX[B] [28] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [29] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [30] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [31] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [32] -1 0 0x000018c0 - 0x000018df (0x20) IX[B] [33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [34] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [35] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [36] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [37] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf4401000 - 0xf44010ff (0x100) MX[B] [5] -1 0 0xf4400c00 - 0xf4400cff (0x100) MX[B] [6] -1 0 0xf4400800 - 0xf44008ff (0x100) MX[B] [7] -1 0 0xf4400000 - 0xf44007ff (0x800) MX[B] [8] -1 0 0xf4300000 - 0xf4301fff (0x2000) MX[B] [9] -1 0 0xf4200000 - 0xf4203fff (0x4000) MX[B] [10] -1 0 0xc2000000 - 0xc20000ff (0x100) MX[B] [11] -1 0 0xf4705000 - 0xf47057ff (0x800) MX[B] [12] -1 0 0xf4706000 - 0xf47063ff (0x400) MX[B] [13] -1 0 0xf4500000 - 0xf4503fff (0x4000) MX[B] [14] -1 0 0xf4705c00 - 0xf4705fff (0x400) MX[B] [15] -1 0 0xf4100000 - 0xf41fffff (0x100000) MX[B](B) [16] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [17] -1 0 0xf4000000 - 0xf40fffff (0x100000) MX[B](B) [18] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [19] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [20] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [23] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [24] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [25] -1 0 0x00001c00 - 0x00001c1f (0x20) IX[B] [26] -1 0 0x000018e8 - 0x000018eb (0x4) IX[B] [27] -1 0 0x000018f0 - 0x000018f7 (0x8) IX[B] [28] -1 0 0x000018ec - 0x000018ef (0x4) IX[B] [29] -1 0 0x000018f8 - 0x000018ff (0x8) IX[B] [30] -1 0 0x00001830 - 0x0000183f (0x10) IX[B] [31] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [32] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [33] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [34] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [35] -1 0 0x000018c0 - 0x000018df (0x20) IX[B] [36] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [37] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [38] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [39] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [40] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) [41] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [42] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Enabling PCI device (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/lib/xorg/modules//libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.0 ABI class: X.Org Video Driver, version 1.2 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/lib/xorg/modules//libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.3.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 1.2 (**) intel(0): Depth 24, (--) framebuffer bpp 32 (==) intel(0): RGB weight 888 (==) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM (--) intel(0): Chipset: "965GM" (--) intel(0): Linear framebuffer at 0xD0000000 (--) intel(0): IO registers at addr 0xF4000000 (II) intel(0): 2 display pipes available. (==) intel(0): Using XAA for acceleration (--) intel(0): Will try to allocate texture pool for old Mesa 3D driver. (II) intel(0): Will try to reserve 32768 kiB of AGP aperture space for the DRM memory manager. (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module already built-in (II) Loading sub module "i2c" (II) LoadModule: "i2c"(II) Module already built-in (II) intel(0): Output VGA has no monitor section (II) intel(0): I2C bus "CRTDDC_A" initialized. (II) intel(0): Output LVDS has no monitor section (II) intel(0): I2C bus "LVDSDDC_C" initialized. (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): EDID vendor "CMO", prod id 5157 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib/xorg/modules//libint10.so (II) intel(0): initializing int10 (EE) intel(0): V_BIOS address 0x80 out of range (EE) intel(0): Bad VBT signature (WW) intel(0): Couldn't detect panel mode. Disabling panel (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): I2C bus "LVDSDDC_C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70. (II) intel(0): No SDVO device found on SDVOB (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72. (II) intel(0): No SDVO device found on SDVOC (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. (II) intel(0): Output TV has no monitor section (II) intel(0): EDID for output VGA (II) intel(0): EDID for output TV (II) intel(0): Output VGA disconnected (II) intel(0): Output TV disconnected (EE) intel(0): No valid modes. (II) UnloadModule: "intel" (II) UnloadModule: "int10" (II) UnloadModule: "vgahw" (II) Unloading /usr/lib/xorg/modules//libvgahw.so (II) UnloadModule: "vbe" (II) Unloading /usr/lib/xorg/modules//libvbe.so (II) UnloadModule: "int10" (II) Unloading /usr/lib/xorg/modules//libint10.so (EE) Screen(s) found, but none have a usable configuration. -- #!/Raja From kvn at xakep.ru Sun Mar 16 14:46:39 2008 From: kvn at xakep.ru (=?KOI8-R?B?98zBxMnNydIg69XexdLR18XOy88=?=) Date: Sun, 16 Mar 2008 20:46:39 +0600 Subject: [Fedora-xen] Couldn't create xen domain Message-ID: <5a77d0410803160746g652b109fod5503ab7affd277f@mail.gmail.com> Couldn't create xen domain in Fedora 8. When I create new domain (full virtualization) and press create buttom, showing error message "Timeout while reading screen output" -------------- next part -------------- An HTML attachment was scrubbed... URL: From ask at develooper.com Thu Mar 20 02:36:56 2008 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Wed, 19 Mar 2008 19:36:56 -0700 Subject: Fwd: [Fedora-xen] Custom bridge script; upgrade from Fedora 6 to Fedora 8 References: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> Message-ID: Any ideas? Maybe my question could be rephrased as: How do I convert my /etc/xen configuration files to virsh XML files? - ask Begin forwarded message: > From: Ask Bj?rn Hansen > Date: February 10, 2008 1:24:10 AM PST > To: fedora-xen at redhat.com > Subject: [Fedora-xen] Custom bridge script; upgrade from Fedora 6 to > Fedora 8 > > 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/ > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- http://develooper.com/ - http://askask.com/ From orenault at redhat.com Thu Mar 20 07:44:57 2008 From: orenault at redhat.com (Olivier Renault) Date: Thu, 20 Mar 2008 08:44:57 +0100 Subject: Fwd: [Fedora-xen] Custom bridge script; upgrade from Fedora 6 to Fedora 8 In-Reply-To: References: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> Message-ID: <47E215F9.1080601@redhat.com> Ask Bj?rn Hansen wrote: > Any ideas? > > Maybe my question could be rephrased as: > > How do I convert my /etc/xen configuration files to virsh XML files? > > start the VM with xm, and when the guest is running, you can do virsh dumpxml Olivier From tom.horsley at att.net Thu Mar 20 13:13:45 2008 From: tom.horsley at att.net (Tom Horsley) Date: Thu, 20 Mar 2008 13:13:45 +0000 Subject: [Fedora-xen] usb tablet support? Message-ID: <032020081313.12930.47E26309000A2A050000328222230682329B0A02D29B9B0EBF970A049C9D0108D203019B@att.net> I'm having a heck of a time discovering if I can actually make the mouse behave via usb tablet support or not. I've added usb=1 and usbdevice='tablet' to my fedora 8 HVM config file, but the mouse seems to act exactly the same way (however the qemu tablet device does show up in the /proc input device description, so it is getting defined). I suspect I need to do something to explicitly fix the xorg.conf file to use the evdev driver (or whatever it is called) and absolute cursor positioning, but I am having a heck of a time find any example xorg.conf file to try. Is it actually supposed to be possible to make this work these days? Anyone have a working xorg.conf from a fedora 8 HVM that demonstrates correct mouse tracking in the vnc console? From berrange at redhat.com Thu Mar 20 13:18:33 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 20 Mar 2008 13:18:33 +0000 Subject: [Fedora-xen] usb tablet support? In-Reply-To: <032020081313.12930.47E26309000A2A050000328222230682329B0A02D29B9B0EBF970A049C9D0108D203019B@att.net> References: <032020081313.12930.47E26309000A2A050000328222230682329B0A02D29B9B0EBF970A049C9D0108D203019B@att.net> Message-ID: <20080320131833.GB16821@redhat.com> On Thu, Mar 20, 2008 at 01:13:45PM +0000, Tom Horsley wrote: > I'm having a heck of a time discovering if I can actually make the mouse > behave via usb tablet support or not. > > I've added usb=1 and usbdevice='tablet' to my fedora 8 HVM config file, > but the mouse seems to act exactly the same way (however the qemu tablet > device does show up in the /proc input device description, so it is getting > defined). > > I suspect I need to do something to explicitly fix the xorg.conf file to > use the evdev driver (or whatever it is called) and absolute cursor > positioning, but I am having a heck of a time find any example xorg.conf > file to try. > > Is it actually supposed to be possible to make this work these days? > Anyone have a working xorg.conf from a fedora 8 HVM that demonstrates > correct mouse tracking in the vnc console? Section "InputDevice" Name "Mouse0" Driver "evdev" Option "Name" "QEMU 0.8.2 QEMU USB Tablet" Option "Mode" "Absolute" EndSection And make sure Mouse0 is listed as your core pointer in the ServerLayout section. The 'Name' field there may need to be changed - I can't remember what name the F8 Xen QEMU exports. This example was from original F7. Look in the /proc/bus/input/devices file for actual name. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From kamdard71 at yahoo.com Fri Mar 21 02:31:06 2008 From: kamdard71 at yahoo.com (Dharmesh Kamdar) Date: Thu, 20 Mar 2008 19:31:06 -0700 (PDT) Subject: [Fedora-xen] newbie question to increase the size of "guest OS"... Message-ID: <454152.39687.qm@web90604.mail.mud.yahoo.com> 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 at hojo images]# [root at hojo images]# ls -ltr total 12398420 -rwxr-xr-x 1 root root 12884901888 2008-03-20 19:30 F8_XEN.img [root at 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 From deshantm at gmail.com Fri Mar 21 03:31:03 2008 From: deshantm at gmail.com (Todd Deshane) Date: Thu, 20 Mar 2008 23:31:03 -0400 Subject: [Fedora-xen] newbie question to increase the size of "guest OS"... In-Reply-To: <454152.39687.qm@web90604.mail.mud.yahoo.com> References: <454152.39687.qm@web90604.mail.mud.yahoo.com> Message-ID: <1e16a9ed0803202031q1ca81248o234dfd7d183fb41d@mail.gmail.com> On Thu, Mar 20, 2008 at 10:31 PM, Dharmesh Kamdar wrote: > 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 at hojo images]# > [root at hojo images]# ls -ltr > total 12398420 > -rwxr-xr-x 1 root root 12884901888 2008-03-20 19:30 > F8_XEN.img > [root at 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. > http://xen.markmail.org/search/?q=resize+disk > > Thanks, > kamdard. > > > > ____________________________________________________________________________________ > Looking for last minute shopping deals? > Find them fast with Yahoo! Search. > http://tools.search.yahoo.com/newsearch/category.php?category=shopping > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kamdard71 at yahoo.com Fri Mar 21 06:10:39 2008 From: kamdard71 at yahoo.com (Dharmesh Kamdar) Date: Thu, 20 Mar 2008 23:10:39 -0700 (PDT) Subject: [Fedora-xen] newbie question to increase the size of "guest OS"... In-Reply-To: <1e16a9ed0803202031q1ca81248o234dfd7d183fb41d@mail.gmail.com> Message-ID: <869113.8030.qm@web90612.mail.mud.yahoo.com> Hi, I tried the steps described in the link u sent me.. but at the end I am getting the following error: $>lvextend -L+3G /dev/VolGroup00/LogVol00 Extending logical volume LogVol00 to 10.03 GN device-mapper: reload ioctl failed: Invalid argument Failed to suspend LogVol00 My Fedora-8 guest is running following: kernel -->2.6.21-2950.fc8xen Device-Mapper--> device-mapper-multipath-0.4.7-11.fc7 device-mapper-libs-1.02.22-1.fc8 device-mapper-1.02.22-1.fc8 LVM-->lvm2-2.02.28-1.fc8 The last few lines of /var/log/messages (after attempting to "lvextend" the logical volume), as follows: +++++++++++++++++++++++++++++++++++++++++++++++++++ [root at localhost ~]# tail -f /var/log/messages Mar 20 22:49:12 localhost dhclient: bound to 192.168.122.199 -- renewal in 1373 seconds. Mar 20 22:52:04 localhost kernel: device-mapper: table: device 202:2 too small for target Mar 20 22:52:04 localhost kernel: device-mapper: table: 253:0: linear: dm-linear: Device lookup failed Mar 20 22:52:04 localhost kernel: device-mapper: ioctl: error adding target to table Mar 20 22:53:18 localhost kernel: device-mapper: table: device 202:2 too small for target Mar 20 22:53:18 localhost kernel: device-mapper: table: 253:0: linear: dm-linear: Device lookup failed Mar 20 22:53:18 localhost kernel: device-mapper: ioctl: error adding target to table Mar 20 23:07:52 localhost kernel: device-mapper: table: device 202:2 too small for target Mar 20 23:07:52 localhost kernel: device-mapper: table: 253:0: linear: dm-linear: Device lookup failed Mar 20 23:07:52 localhost kernel: device-mapper: ioctl: error adding target to table +++++++++++++++++++++++++++++++++++++++++++++++++++ Will appreciate any further feedback. Thanks, kamdard. I googled on "reload ioctl failed: Invalid argument",found a few hits describing this to be a possibly kernel or DM bug. --- Todd Deshane wrote: > On Thu, Mar 20, 2008 at 10:31 PM, Dharmesh Kamdar > > wrote: > > > 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 at hojo images]# > > [root at hojo images]# ls -ltr > > total 12398420 > > -rwxr-xr-x 1 root root 12884901888 2008-03-20 > 19:30 > > F8_XEN.img > > [root at 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. > > > > http://xen.markmail.org/search/?q=resize+disk > > > > > > Thanks, > > kamdard. > > > > > > > > > ____________________________________________________________________________________ > > Looking for last minute shopping deals? > > Find them fast with Yahoo! Search. > > > http://tools.search.yahoo.com/newsearch/category.php?category=shopping > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ From oditm at hotmail.com Sun Mar 23 14:51:03 2008 From: oditm at hotmail.com (Odi Mbeledogu) Date: Sun, 23 Mar 2008 14:51:03 +0000 Subject: [Fedora-xen] NO VIRTUALIZATION SUPPORT ON DELL POWEREDGE 840 Message-ID: what it is is that i recently purchased a Dell PowerEdge 840 after carefully selecting the specs i required, on its arrival i noticed that the BIOS does not support virtualization, as a result of this on successfully installing Xen vm on Open Suse 10.2 which creates the vm kernel and i try to start the vm i get the error message:'Cannot start the virtual machine'then it goes on to say :command: /usr/sbin/xm create /etc/xen/vm/vm1 return Error: (22, 'Invalid argument') Using config file "/etc/xen/vm/vm2". when i prompt for more details i get: 'Error: HVM guest support is unavailable: is VT/AMD-v supported by your CPU and enabled in your BIOS' i have had a word with dell support who confirmed that the that the BIOS does not support virtualization for now and that that option in the bios is defaultly set to disable and that the most recent release of my BIOS software doesn't list this in the menu for me to toggle that option, and that maybe a future release of the BIOS software will have accessibilty to this option. I was adviced by the Dell Engineer to come this site and seek for help on this site. does anyone know what i can do to get around this problem please. i was told by the Dell engineer to run a cat command on the cpuinfo file to see if the flag will reflect xt or vt, i did this and the i got the following: odi at PE840Srv:/proc> cat cpuinfoprocessor : 0vendor_id : GenuineIntelcpu family : 6model : 15model name : Intel(R) Xeon(R) CPU X3210 @ 2.13GHzstepping : 11cpu MHz : 2133.600cache size : 4096 KBphysical id : 0siblings : 4core id : 0cpu cores : 4fdiv_bug : nohlt_bug : nof00f_bug : nocoma_bug : nofpu : yesfpu_exception : yescpuid level : 10wp : yesflags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lmbogomips : 4269.91 i badly need to create virtual machines on this server, its got 750 GB HDD (mirroring support) and 8GB of RAM, i selected all this with virtualization in mind obviously. any assistance will be greatly appreciated. Odi _________________________________________________________________ Win 100?s of Virgin Experience days with BigSnapSearch.com http://www.bigsnapsearch.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From smiler at lanil.mine.nu Mon Mar 24 12:16:55 2008 From: smiler at lanil.mine.nu (Christian Axelsson) Date: Mon, 24 Mar 2008 13:16:55 +0100 Subject: [Fedora-xen] Guest shutdown problems Message-ID: <47E79BB7.50500@lanil.mine.nu> 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 at 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 at lanil.mine.nu -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xmlist_long.afterboot URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xmlist_long.aftershutdown URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xmlist_long.preboot URL: From oditm at hotmail.com Sat Mar 22 19:29:55 2008 From: oditm at hotmail.com (Odi) Date: Sat, 22 Mar 2008 12:29:55 -0700 (PDT) Subject: =?UTF-8?Q?[Fedora-xen]_no_Virtualization_su?= =?UTF-8?Q?pport_for_creating_VM's_on_PE840=E2=80=8F?= Message-ID: <16226392.post@talk.nabble.com> what it is is that i recently purchased a Dell PowerEdge 840 after carefully selecting the specs i required, on its arrival i noticed that the BIOS does not support virtualization, as a result of this on successfully installing Xen vm on Open Suse 10.2 which creates the vm kernel and i try to start the vm i get the error message: 'Cannot start the virtual machine' then it goes on to say : command: /usr/sbin/xm create /etc/xen/vm/vm1 return Error: (22, 'Invalid argument') Using config file "/etc/xen/vm/vm1". when i prompt for more details i get: 'Error: HVM guest support is unavailable: is VT/AMD-v supported by your CPU and enabled in your BIOS' i have had a word with dell support who confirmed that the that the BIOS does not support virtualization for now and that that option in the bios is defaultly set to disable and that the most recent release of my BIOS software doesn't list this in the menu for me to toggle that option, and that maybe a future release of the BIOS software will have accessibilty to this option. I was adviced by the Dell Engineer to come this site and seek for help on this site. does anyone know what i can do to get around this problem please. i was told by the Dell engineer to run a cat command on the cpuinfo file to see if the flag will reflect xt or vt, i did this and the i got the following: odi at PE840Srv:/proc> cat cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU X3210 @ 2.13GHz stepping : 11 cpu MHz : 2133.600 cache size : 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm bogomips : 4269.91 i badly need to create virtual machines on this server, its got 750 GB HDD (mirroring support) and 8GB of RAM, i selected all this with virtualization in mind obviously. any assistance will be greatly appreciated. Odi -- View this message in context: http://www.nabble.com/no-Virtualization-support-for-creating-VM%27s-on-PE840%E2%80%8F-tp16226392p16226392.html Sent from the Fedora Xen mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred at derf.nl Tue Mar 25 12:22:09 2008 From: fred at derf.nl (Friedrich Clausen) Date: Tue, 25 Mar 2008 13:22:09 +0100 Subject: [Fedora-xen] newbie question to increase the size of "guest OS"... In-Reply-To: <869113.8030.qm@web90612.mail.mud.yahoo.com> References: <1e16a9ed0803202031q1ca81248o234dfd7d183fb41d@mail.gmail.com> <869113.8030.qm@web90612.mail.mud.yahoo.com> Message-ID: If you are not using LVM you might be better off creating a brand new image > 7G and then copying the files from the existing image into the new image. The, once that is complete, simply boot into the new, larger image. I am not sure how to otherwise increase an image based installations storage space unless you are using LVM (which you said you are not). Cheers, Fred. On Fri, Mar 21, 2008 at 7:10 AM, Dharmesh Kamdar wrote: > Hi, > I tried the steps described in the link u sent me.. > but at the end I am getting the following error: > > $>lvextend -L+3G /dev/VolGroup00/LogVol00 > Extending logical volume LogVol00 to 10.03 GN > device-mapper: reload ioctl failed: Invalid argument > Failed to suspend LogVol00 > > My Fedora-8 guest is running following: > kernel -->2.6.21-2950.fc8xen > Device-Mapper--> device-mapper-multipath-0.4.7-11.fc7 > device-mapper-libs-1.02.22-1.fc8 > device-mapper-1.02.22-1.fc8 > > LVM-->lvm2-2.02.28-1.fc8 > > The last few lines of /var/log/messages (after > attempting to "lvextend" the logical volume), as > follows: > > +++++++++++++++++++++++++++++++++++++++++++++++++++ > [root at localhost ~]# tail -f /var/log/messages > Mar 20 22:49:12 localhost dhclient: bound to > 192.168.122.199 -- renewal in 1373 seconds. > Mar 20 22:52:04 localhost kernel: device-mapper: > table: device 202:2 too small for target > Mar 20 22:52:04 localhost kernel: device-mapper: > table: 253:0: linear: dm-linear: Device lookup failed > Mar 20 22:52:04 localhost kernel: device-mapper: > ioctl: error adding target to table > Mar 20 22:53:18 localhost kernel: device-mapper: > table: device 202:2 too small for target > Mar 20 22:53:18 localhost kernel: device-mapper: > table: 253:0: linear: dm-linear: Device lookup failed > Mar 20 22:53:18 localhost kernel: device-mapper: > ioctl: error adding target to table > Mar 20 23:07:52 localhost kernel: device-mapper: > table: device 202:2 too small for target > Mar 20 23:07:52 localhost kernel: device-mapper: > table: 253:0: linear: dm-linear: Device lookup failed > Mar 20 23:07:52 localhost kernel: device-mapper: > ioctl: error adding target to table > +++++++++++++++++++++++++++++++++++++++++++++++++++ > > Will appreciate any further feedback. > > Thanks, > kamdard. > > I googled on "reload ioctl failed: Invalid > argument",found a few hits describing this to be a > possibly kernel or DM bug. > > --- Todd Deshane wrote: > > > On Thu, Mar 20, 2008 at 10:31 PM, Dharmesh Kamdar > > > > wrote: > > > > > 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 at hojo images]# > > > [root at hojo images]# ls -ltr > > > total 12398420 > > > -rwxr-xr-x 1 root root 12884901888 2008-03-20 > > 19:30 > > > F8_XEN.img > > > [root at 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. > > > > > > > http://xen.markmail.org/search/?q=resize+disk > > > > > > > > > > Thanks, > > > kamdard. > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > Looking for last minute shopping deals? > > > Find them fast with Yahoo! Search. > > > > > > http://tools.search.yahoo.com/newsearch/category.php?category=shopping > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred at derf.nl Tue Mar 25 12:24:50 2008 From: fred at derf.nl (Friedrich Clausen) Date: Tue, 25 Mar 2008 13:24:50 +0100 Subject: Fwd: [Fedora-xen] Custom bridge script; upgrade from Fedora 6 to Fedora 8 In-Reply-To: <47E215F9.1080601@redhat.com> References: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> <47E215F9.1080601@redhat.com> Message-ID: Also, while I can't offer a complete solution, I have used "logger" (see man page) to debug network configuration scripts. Cheers, Fred. On Thu, Mar 20, 2008 at 8:44 AM, Olivier Renault wrote: > Ask Bj?rn Hansen wrote: > > Any ideas? > > > > Maybe my question could be rephrased as: > > > > How do I convert my /etc/xen configuration files to virsh XML files? > > > > > start the VM with xm, and when the guest is running, you can do > virsh dumpxml > > Olivier > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred at derf.nl Tue Mar 25 12:18:08 2008 From: fred at derf.nl (Friedrich Clausen) Date: Tue, 25 Mar 2008 13:18:08 +0100 Subject: =?WINDOWS-1256?Q?Re:_[Fedora-xen]_no_Virtualization_?= =?WINDOWS-1256?Q?support_for_creating_VM's_on_PE840=FE?= In-Reply-To: <16226392.post@talk.nabble.com> References: <16226392.post@talk.nabble.com> Message-ID: You CPU stats seems to indicate "vmx" which implies that the CPU us capable of running HVM hosts. So it is indeed a pity the BIOS does not let you enable it (for now). Which OS(s) do you want to run in virtual machines? If you want to run Linux guests then you don't need to use the hardware VM features - you can run them in a paravirtualised manner. This is how I run my Linux guests, I only use HVM for windows or OSs that have not been modified to run in a paravirtualised configuration. Hope this helps! Fred. On Sat, Mar 22, 2008 at 8:29 PM, Odi wrote: > what it is is that i recently purchased a Dell PowerEdge 840 after > carefully selecting the specs i required, on its arrival i noticed that the > BIOS does not support virtualization, as a result of this on successfully > installing Xen vm on Open Suse 10.2 which creates the vm kernel and i try > to start the vm i get the error message: 'Cannot start the virtual machine' > then it goes on to say : *command: /usr/sbin/xm create /etc/xen/vm/vm1 > return Error: (22, 'Invalid argument') Using config file "/etc/xen/vm/vm1". > * when i prompt for more details i get: *'Error: HVM guest support is > unavailable: is VT/AMD-v supported by your CPU and enabled in your BIOS'*i have had a word with dell support who confirmed that the that the BIOS > does not support virtualization for now and that that option in the bios is > defaultly set to disable and that the most recent release of my BIOS > software doesn't list this in the menu for me to toggle that option, and > that maybe a future release of the BIOS software will have accessibilty to > this option. I was adviced by the Dell Engineer to come this site and seek > for help on this site. does anyone know what i can do to get around this > problem please. i was told by the Dell engineer to run a cat command on the > cpuinfo file to see if the flag will reflect xt or vt, i did this and the i > got the following: *odi at PE840Srv:/proc> cat cpuinfo processor : 0 > vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) > Xeon(R) CPU X3210 @ 2.13GHz stepping : 11 cpu MHz : 2133.600 cache size : > 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 fdiv_bug : no > hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid > level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr > pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm > constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm bogomips : > 4269.91* i badly need to create virtual machines on this server, its got > 750 GB HDD (mirroring support) and 8GB of RAM, i selected all this with > virtualization in mind obviously. any assistance will be greatly > appreciated. Odi > ------------------------------ > View this message in context: no Virtualization support for creating VM's > on PE840? > Sent from the Fedora Xen mailing list archiveat > Nabble.com. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ukhanlists at hotmail.com Tue Mar 25 15:41:27 2008 From: ukhanlists at hotmail.com (Ubaidul Khan) Date: Tue, 25 Mar 2008 11:41:27 -0400 Subject: [Fedora-xen] RHEL5 - Xend will not start after software upgrade Message-ID: 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 at saleen xen]# /etc/init.d/xend start Starting xend: [ OK ] [root at 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 at 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_Refresh_realtime_042008 From berrange at redhat.com Tue Mar 25 15:45:15 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 25 Mar 2008 15:45:15 +0000 Subject: [Fedora-xen] RHEL5 - Xend will not start after software upgrade In-Reply-To: References: Message-ID: <20080325154515.GA12693@redhat.com> On Tue, Mar 25, 2008 at 11:41:27AM -0400, Ubaidul Khan wrote: > > 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 at saleen xen]# /etc/init.d/xend start > Starting xend: [ OK ] > > [root at 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 at 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') That means you have a mis-matched version of the kernel vs userspace. Make sure you have applied all RHEL-5.1 updates, and have rebooted into the new kernel. The new userspace won't work with old kernel & vica-verca. Regards, Daniel. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From jklein at saugus.k12.ca.us Tue Mar 25 17:52:12 2008 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Tue, 25 Mar 2008 10:52:12 -0700 (PDT) Subject: [Fedora-xen] Libvirt and xenstore - glitches on migrate In-Reply-To: <6591452.263061206467518251.JavaMail.root@do8> Message-ID: <21907977.263191206467532611.JavaMail.root@do8> 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.) -------------- next part -------------- An HTML attachment was scrubbed... URL: From smiler at lanil.mine.nu Tue Mar 25 18:09:19 2008 From: smiler at lanil.mine.nu (Christian Axelsson) Date: Tue, 25 Mar 2008 19:09:19 +0100 Subject: [Fedora-xen] Guest shutdown problems In-Reply-To: <47E79BB7.50500@lanil.mine.nu> References: <47E79BB7.50500@lanil.mine.nu> Message-ID: <47E93FCF.9070106@lanil.mine.nu> I have noticed that restarting xend fixes the states. Does that give anyone any ideas? Christian Axelsson wrote: > 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 at 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 at lanil.mine.nu > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From ukhanlists at hotmail.com Tue Mar 25 19:14:43 2008 From: ukhanlists at hotmail.com (Ubaidul Khan) Date: Tue, 25 Mar 2008 15:14:43 -0400 Subject: [Fedora-xen] RHEL5 - Xend will not start after software upgrade In-Reply-To: <20080325154515.GA12693@redhat.com> References: <20080325154515.GA12693@redhat.com> Message-ID: FYI, yum on my machine was configured with RHN repositories. Is yum supposed to handle these dependencies in way so people dont end up in the same situation I am in? ---------------------------------------- > Date: Tue, 25 Mar 2008 15:45:15 +0000 > From: berrange at redhat.com > To: ukhanlists at hotmail.com > CC: xen-users at lists.xensource.com; fedora-xen at redhat.com > Subject: Re: [Fedora-xen] RHEL5 - Xend will not start after software upgrade > > On Tue, Mar 25, 2008 at 11:41:27AM -0400, Ubaidul Khan wrote: >> >> 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 at saleen xen]# /etc/init.d/xend start >> Starting xend: [ OK ] >> >> [root at 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 at 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') > > That means you have a mis-matched version of the kernel vs userspace. > > Make sure you have applied all RHEL-5.1 updates, and have rebooted into > the new kernel. The new userspace won't work with old kernel & vica-verca. > > Regards, > Daniel. > -- > |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| > |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| > |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| _________________________________________________________________ Watch ?Cause Effect,? a show about real people making a real difference. Learn more. http://im.live.com/Messenger/IM/MTV/?source=text_watchcause From WCoole at aperiogroup.com Wed Mar 26 00:04:13 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Tue, 25 Mar 2008 17:04:13 -0700 Subject: [Fedora-xen] Newby Help Message-ID: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mnielsen at redhat.com Wed Mar 26 01:01:10 2008 From: mnielsen at redhat.com (Mark Nielsen) Date: Tue, 25 Mar 2008 21:01:10 -0400 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> Message-ID: <47E9A056.5090008@redhat.com> Hi Walter, sorry to hear you're having trouble. Walter Coole wrote: > > 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. > What type of system are you running this on? Is it 32 or 64 bit? What kernel are you running? (uname -a) > > I also tried xm, but haven?t figured out how to deal with the error: > > Cannot open root device "sda1" > um... what disk are you presenting to your guest? Installing from the http:// tree would indicate that you're installing a para-virt guest, but it's looking for sda1. Typically the disk inside the guest is known as xvda, which makes me wonder if you're presenting sda1 to the guest as its root. Is that the same root disk that your host is using? > > Virsh throws a different error: > > Domain not found: xenUnifiedDomainLookupByName > yeah, hate to say this, but the xen logs can be very confusing and hard to read until you get used to the various errors and what they *really* mean sometimes. > > 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. > Yep, it actually is relatively easy, but that is assuming all the requirements are met. Those are usually the hardest parts to figure out! Mark > Walter > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From WCoole at aperiogroup.com Wed Mar 26 01:24:39 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Tue, 25 Mar 2008 18:24:39 -0700 Subject: [Fedora-xen] Newby Help In-Reply-To: <47E9A056.5090008@redhat.com> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> Message-ID: <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> uname -a Linux cloudy 2.6.20-1.3002.fc6xen #1 SMP Mon Aug 13 14:21:21 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux FWIW, the file that Anaconda is complaining about is http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os//ima ges/stage2.img , which seems to be sitting there as advertised, although my link is pretty slow; could it be timing out over the transfer? If understand the flags: [wcoole at cloudy ~/Desktop]$ egrep "svm|vmx" /proc/cpuinfo [wcoole at cloudy ~/Desktop]$ I cannot run Fully-virtualized guests, which seems to imply that I have to run a para-virt guest. I was imagining that it would be simplest to use a file (on the host filesystem) as the filesystem for the guest, but I've probably mangled the configuration. I'm using this command to start it: sudo /usr/sbin/xm create -c football.cfg It seems likely that I haven't got the config set right; here's football.cfg: cat football.cfg kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen" memory = 256 name = "football" vif = [ '' ] dhcp = "dhcp" disk = ['file://xen/fedora/football.img,sda1,w', 'file://xen/fedora/football.swap,sda2,w'] root = "/dev/sda1 ro" I got the img, swap, and cfg files from the tarball at http://jailtime.org/download:fedora:fc6 , but copied and hacked them without really knowing what I was doing. I'm not fixated on any particular approach, just trying to do the easy thing to get started so I can fool myself into thinking I know what I'm doing. Thanks Walter -----Original Message----- From: Mark Nielsen [mailto:mnielsen at redhat.com] Sent: Tuesday, March 25, 2008 6:01 PM To: Walter Coole Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Newby Help Hi Walter, sorry to hear you're having trouble. Walter Coole wrote: > > 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. > What type of system are you running this on? Is it 32 or 64 bit? What kernel are you running? (uname -a) > > I also tried xm, but haven't figured out how to deal with the error: > > Cannot open root device "sda1" > um... what disk are you presenting to your guest? Installing from the http:// tree would indicate that you're installing a para-virt guest, but it's looking for sda1. Typically the disk inside the guest is known as xvda, which makes me wonder if you're presenting sda1 to the guest as its root. Is that the same root disk that your host is using? > > Virsh throws a different error: > > Domain not found: xenUnifiedDomainLookupByName > yeah, hate to say this, but the xen logs can be very confusing and hard to read until you get used to the various errors and what they *really* mean sometimes. > > 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. > Yep, it actually is relatively easy, but that is assuming all the requirements are met. Those are usually the hardest parts to figure out! Mark > Walter > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From mnielsen at redhat.com Wed Mar 26 01:37:30 2008 From: mnielsen at redhat.com (Mark Nielsen) Date: Tue, 25 Mar 2008 21:37:30 -0400 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> Message-ID: <47E9A8DA.90204@redhat.com> Walter Coole wrote: > uname -a > Linux cloudy 2.6.20-1.3002.fc6xen #1 SMP Mon Aug 13 14:21:21 EDT 2007 > x86_64 x86_64 x86_64 GNU/Linux > > ok, so it's 64 on 64, just making sure. I've seen similar random crash during install errors when people try to run 32 on 64 PV (not supported and buggy) > FWIW, the file that Anaconda is complaining about is > http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os//ima > ges/stage2.img , which seems to be sitting there as advertised, although > my link is pretty slow; could it be timing out over the transfer? > > hm, I've seen the same thing many times, failing to get stage2. The typical problem is networking. dom0 gets the initial images to set the install up, then somewhere around the time stage2 gets picked up, networking is set up inside the guest to download the packages. I strongly suspect some networking issue with the bridge not correctly configured. Unfortunately that's going to be a little harder to troubleshoot... maybe someone can chime in that's an expert on troubleshooting bridges. One easy way to fix this might be to download the FC6 ISOs and create your own install repo on the local network, or even the same machine if possible. > If understand the flags: > > [wcoole at cloudy ~/Desktop]$ egrep "svm|vmx" /proc/cpuinfo > [wcoole at cloudy ~/Desktop]$ > > I cannot run Fully-virtualized guests, which seems to imply that I have > to run a para-virt guest. > > correct > I was imagining that it would be simplest to use a file (on the host > filesystem) as the filesystem for the guest, but I've probably mangled > the configuration. I'm using this command to start it: > > sudo /usr/sbin/xm create -c football.cfg > > It seems likely that I haven't got the config set right; here's > football.cfg: > > cat football.cfg > kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen" > memory = 256 > name = "football" > vif = [ '' ] > dhcp = "dhcp" > disk = ['file://xen/fedora/football.img,sda1,w', > 'file://xen/fedora/football.swap,sda2,w'] > root = "/dev/sda1 ro" > > I use LVMs for my guest root and other disks.. again hopefully someone else can chime in to verify if that's correct. One thing I do notice here is that the vif is blank. That could be an issue related to the problem above? > I got the img, swap, and cfg files from the tarball at > http://jailtime.org/download:fedora:fc6 , but copied and hacked them > without really knowing what I was doing. I'm not fixated on any > particular approach, just trying to do the easy thing to get started so > I can fool myself into thinking I know what I'm doing. > > Mark > Thanks > Walter > > > -----Original Message----- > From: Mark Nielsen [mailto:mnielsen at redhat.com] > Sent: Tuesday, March 25, 2008 6:01 PM > To: Walter Coole > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Newby Help > > Hi Walter, sorry to hear you're having trouble. > > Walter Coole wrote: > >> 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. >> >> > What type of system are you running this on? Is it 32 or 64 bit? What > kernel are you running? (uname -a) > >> I also tried xm, but haven't figured out how to deal with the error: >> >> Cannot open root device "sda1" >> >> > um... what disk are you presenting to your guest? Installing from the > http:// tree would indicate that you're installing a para-virt guest, > but it's looking for sda1. Typically the disk inside the guest is known > as xvda, which makes me wonder if you're presenting sda1 to the guest as > > its root. Is that the same root disk that your host is using? > >> Virsh throws a different error: >> >> Domain not found: xenUnifiedDomainLookupByName >> >> > yeah, hate to say this, but the xen logs can be very confusing and hard > to read until you get used to the various errors and what they *really* > mean sometimes. > >> 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. >> >> > Yep, it actually is relatively easy, but that is assuming all the > requirements are met. Those are usually the hardest parts to figure out! > > Mark > > >> Walter >> >> >> > ------------------------------------------------------------------------ > >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> From clalance at redhat.com Wed Mar 26 12:28:35 2008 From: clalance at redhat.com (Chris Lalancette) Date: Wed, 26 Mar 2008 08:28:35 -0400 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> Message-ID: <47EA4173.8050609@redhat.com> Walter Coole wrote: > cat football.cfg > kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen" > memory = 256 > name = "football" > vif = [ '' ] > dhcp = "dhcp" > disk = ['file://xen/fedora/football.img,sda1,w', > 'file://xen/fedora/football.swap,sda2,w'] This is wrong. For paravirtualized guests, you want to use xvda1 and xvda2. Also, you want to use tap:aio, otherwise you will corrupt your guest disks if the dom0 crashes. So your disk line really wants to look like: disk = ['tap:aio:/xen/fedora/football.img,xvda1,w','tap:aio:/xen/fedora/football.swap,xvda2,w'] It might be easier, though, just to use virt-install and/or virt-manager to install your guests; they take care of these details for you. Chris Lalancette From WCoole at aperiogroup.com Wed Mar 26 20:13:28 2008 From: WCoole at aperiogroup.com (Walter Coole) Date: Wed, 26 Mar 2008 13:13:28 -0700 Subject: [Fedora-xen] Newby Help In-Reply-To: <47EA4173.8050609@redhat.com> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> Message-ID: <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> Agreed, it might be easier to use virt-manager, if Anaconda didn't complain about not getting http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os//ima ges/stage2.img . Is http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/ the best URL for a Fedora install tree? I tried your xvda suggestion, but got an error: VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option I changed the root clause to: root = "/dev/xvda1 ro" , which changed the error to: VFS: Cannot open root device "xvda1" or unknown-block(0,0) Please append a correct "root=" boot option I'm unclear whether the problem is in creating the virtual disk or in being able to mount it after it's been created. On the virt-manager front I tried copying the install disks I have onto a local directory, but got the error: Unable to complete install: 'Invalid install location: Mounting location /install/fc6/ failed'. Apparently, the local path for Create Wizard needs to be a device that it can mount, because it gets farther if I use /dev/cdrom. Pulling directly from the CD fails with the error: Unable to complete install: 'virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (22, 'Invalid argument')")' , but I'm unclear on which argument is invalid. Thanks for your help so far! Walter -----Original Message----- From: Chris Lalancette [mailto:clalance at redhat.com] Sent: Wednesday, March 26, 2008 5:29 AM To: Walter Coole Cc: mnielsen at redhat.com; fedora-xen at redhat.com Subject: Re: [Fedora-xen] Newby Help Walter Coole wrote: > cat football.cfg > kernel = "/boot/vmlinuz-2.6.20-1.3002.fc6xen" > memory = 256 > name = "football" > vif = [ '' ] > dhcp = "dhcp" > disk = ['file://xen/fedora/football.img,sda1,w', > 'file://xen/fedora/football.swap,sda2,w'] This is wrong. For paravirtualized guests, you want to use xvda1 and xvda2. Also, you want to use tap:aio, otherwise you will corrupt your guest disks if the dom0 crashes. So your disk line really wants to look like: disk = ['tap:aio:/xen/fedora/football.img,xvda1,w','tap:aio:/xen/fedora/footbal l.swap,xvda2,w'] It might be easier, though, just to use virt-install and/or virt-manager to install your guests; they take care of these details for you. Chris Lalancette From fred at derf.nl Thu Mar 27 12:23:19 2008 From: fred at derf.nl (Friedrich Clausen) Date: Thu, 27 Mar 2008 13:23:19 +0100 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> Message-ID: Hello, I can offer some input from my own experiences regarding mounting root. On Wed, Mar 26, 2008 at 9:13 PM, Walter Coole wrote: > Please append a correct "root=" boot option > > I changed the root clause to: > > root = "/dev/xvda1 ro" > > , which changed the error to: > > VFS: Cannot open root device "xvda1" or unknown-block(0,0) > Please append a correct "root=" boot option > > I'm unclear whether the problem is in creating the virtual disk or in > being able to mount it after it's been created. > I found that the default initrd did not contain the xenblk driver and so it could not access the root filesystem. See here: http://lists.xensource.com/archives/html/xen-users/2008-03/msg00000.html You might even want to use the --preload option of mkinitrd. My exact mkinitrd was: # mkinitrd -v --preload=sd_mod --preload=xenblk --with=xennet --with=xenblktap\ --with=xenbus_be /tmp/test `uname -r` Then I copied /tmp/test to /boot/initrd-2.6.21.7-2.fc8xen.img. This worked for me - YMMV. Cheers, Fred. -------------- next part -------------- An HTML attachment was scrubbed... URL: From armbru at redhat.com Thu Mar 27 12:47:01 2008 From: armbru at redhat.com (Markus Armbruster) Date: Thu, 27 Mar 2008 13:47:01 +0100 Subject: [Fedora-xen] Newby Help In-Reply-To: <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> (Walter Coole's message of "Wed\, 26 Mar 2008 13\:13\:28 -0700") References: <4292CEA5F4927248979C701CA83500BB83D9DF@SERVER.aperiogroup.local> <47E9A056.5090008@redhat.com> <4292CEA5F4927248979C701CA83500BB83D9EF@SERVER.aperiogroup.local> <47EA4173.8050609@redhat.com> <4292CEA5F4927248979C701CA83500BB83DA4B@SERVER.aperiogroup.local> Message-ID: <87ej9wpc56.fsf@pike.pond.sub.org> You need to tell us *exactly* how you run virt-install, and what error you get back. From rick at debix.com Thu Mar 27 18:01:18 2008 From: rick at debix.com (Mixer) Date: Thu, 27 Mar 2008 11:01:18 -0700 (PDT) Subject: [Fedora-xen] Guest shutdown problems In-Reply-To: <47E79BB7.50500@lanil.mine.nu> References: <47E79BB7.50500@lanil.mine.nu> Message-ID: <16329496.post@talk.nabble.com> I'm seeing the same thing regardless of shutdown state. I've tried downloading the latest mercurial virtinst--devel distribution and running it. hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel cd virtinst--devel ./virt-clone -o svn -n vpnroute -f /var/lib/xen/images/vpnroute.img ERROR: virDomainGetXMLDesc() failed failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain 1732681615 xm list svn Name ID Mem VCPUs State Time(s) svn 24 1024 1 ------ 18.3 Host and guest are both Fedora 8 Anyone know of a fix or workaround? Is this now a known issue? :) If I can help troubleshoot this in any way please let me know. I really need this to work. Rick Christian Axelsson wrote: > > 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 at 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 at 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) > ) > ) > ) > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- View this message in context: http://www.nabble.com/Guest-shutdown-problems-tp16250249p16329496.html Sent from the Fedora Xen mailing list archive at Nabble.com. From franz.vonhahn at yahoo.de Sat Mar 29 10:41:18 2008 From: franz.vonhahn at yahoo.de (Franz Von Hahn) Date: Sat, 29 Mar 2008 11:41:18 +0100 (CET) Subject: [Fedora-xen] How to add a PCI-Card to a DomU? Message-ID: <843099.75585.qm@web28216.mail.ukl.yahoo.com> 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 From swethu_bandaru at yahoo.com Mon Mar 31 06:50:25 2008 From: swethu_bandaru at yahoo.com (swethu bandaru) Date: Sun, 30 Mar 2008 23:50:25 -0700 (PDT) Subject: [Fedora-xen] Problem with XEN Message-ID: <882854.53356.qm@web36202.mail.mud.yahoo.com> 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From armbru at redhat.com Mon Mar 31 09:23:08 2008 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 31 Mar 2008 11:23:08 +0200 Subject: [Fedora-xen] Problem with XEN In-Reply-To: <882854.53356.qm@web36202.mail.mud.yahoo.com> (swethu bandaru's message of "Sun\, 30 Mar 2008 23\:50\:25 -0700 \(PDT\)") References: <882854.53356.qm@web36202.mail.mud.yahoo.com> Message-ID: <87tzin8cxv.fsf@pike.pond.sub.org> swethu bandaru writes: > 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 This is an unusual location. Is SELinux enabled? Does /var/lib/xen/images/xenbox.img work? [...]