From fedora.lists at burns.me.uk Thu May 1 12:29:03 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Thu, 1 May 2008 13:29:03 +0100 Subject: [Fedora-xen] Weird xen network problem after upgrade Message-ID: Host machine was running F7 no problems, upgraded via yum to F8, no problems with deps, all went smoothly, installed latest fedora-updates versions of everything. Rebooted host, but found I had lost contact with it over the LAN, even though the machine is on a datacentre this not a disaster because I have remote serial port access to this machine, so I PXE booted into rescue mode from an F8 repo I have locally, modified grub.conf to set xen and linux to use serial console and got logged in as root OK Networking showed the eth0 had been renamed to peth0, the eth0 bridge created, peth0 enslaved to eth0 (virbr0 and vnet0 bridges also created but I don't actually use those) The problem is the IP address that ifcfg-eth0 assigns statically to [p]eth0 ends up assigned assigned to NIC eth1 instead of bridge eth0 (won't work as that NIC is connected to a different VLAN intended for iSCSI access). As soon as I remove the correct IP address from the wrong NIC with ip addr del x.x.x.x/24 dev eth1 ip link set down eth1 the same IP address somehow gets re-incarnated on the eth0 bridge! So I manually remove all addresses and shutdown all interfaces, and restart networking ip addr del x.x.x.x/24 dev eth0 ip link set down eth0 brctl delif eth0 peth0, brctl delbr eth0, virsh net-destroy virbr0 virsh net-destroy vnet0 ip link set name eth0 dev peth0 (to rename peth0 back to eth0) service network start this correctly brings up only eth0 and assigns correct IP address and routes at this point "network-bridge status" seems confused about NICs, it seems to see two copies of eth0 and not to see eth1 # /etc/xen/scripts/network-bridge status ============================================================ 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:04:23:d3:3c:10 brd ff:ff:ff:ff:ff:ff inet 172.20.1.2/24 brd 172.20.1.255 scope global eth0 inet6 fe80::204:23ff:fed3:3c10/64 scope link valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:04:23:d3:3c:10 brd ff:ff:ff:ff:ff:ff inet 172.20.1.2/24 brd 172.20.1.255 scope global eth0 inet6 fe80::204:23ff:fed3:3c10/64 scope link valid_lft forever preferred_lft forever bridge name bridge id STP enabled interfaces 172.20.1.0/24 dev eth0 proto kernel scope link src 172.20.1.2 169.254.0.0/16 dev eth0 scope link default via 172.20.1.1 dev eth0 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.20.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 172.20.1.1 0.0.0.0 UG 0 0 0 eth0 ============================================================ Then I then run "network-bridge start" the script properly renames eth0 to peth0, re-creates the eth0 bridge, enslaves peth0 to eth0 and moves the IP address, MAC address, routes over to eth0, everything is working properly. Yet following a reboot it goes wrong again just like before. Any ideas what is confusing network-bridge on reboot, when it works if manually run after networking has been shutdown? From fedora.lists at burns.me.uk Mon May 5 19:20:46 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Mon, 5 May 2008 20:20:46 +0100 Subject: [Fedora-xen] Re: Weird xen network problem after upgrade In-Reply-To: References: Message-ID: 2008/5/1 Andy Burns : > The problem is the IP address that ifcfg-eth0 assigns statically to > [p]eth0 ends up assigned assigned to NIC eth1 instead of bridge eth0 Just in case anyone else encounters this, it was NetworkManager that was managing to break the network setup after libvirtd/xend had set it up properly, presumably this daemon got enabled by default for F8 when it was disabled by default for F7? From ask at develooper.com Thu May 8 02:16:44 2008 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Wed, 7 May 2008 19:16:44 -0700 Subject: [Fedora-xen] Custom bridge script - how to setup two bridges? In-Reply-To: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> References: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> Message-ID: <3337E8F6-BFD6-45AE-9E60-6CE049B877C3@develooper.com> Hi everyone, The "best" custom network-bridge script I have come up with was: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" netdev=eth1 bridge=eth1 "$dir/network-bridge" "$@" netdev=eth0 bridge=eth0 I'd prefer however to have the bridges called xenbr0 and xenbr1 -- but when I try that I end up with half a bridge made and a "tmpbridge" device. Any ideas? I'm (still) on Fedora 8. - ask From ask at develooper.com Thu May 8 02:19:32 2008 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Wed, 7 May 2008 19:19:32 -0700 Subject: [Fedora-xen] Custom bridge script - how to setup two bridges? In-Reply-To: <3337E8F6-BFD6-45AE-9E60-6CE049B877C3@develooper.com> References: <88C215E0-9119-4438-AA4E-20A429857ED2@develooper.com> <3337E8F6-BFD6-45AE-9E60-6CE049B877C3@develooper.com> Message-ID: <5E8347DE-627B-4012-8503-34F88EB85A16@develooper.com> On May 7, 2008, at 19:16, Ask Bj?rn Hansen wrote: [ whoops - hit send too soon ] Hi everyone, The "best" custom network-bridge script I have come up with was: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" netdev=eth1 bridge=eth1 "$dir/network-bridge" "$@" netdev=eth0 bridge=eth0 I'd prefer however to have the bridges called xenbr0 and xenbr1 -- but when I try that I end up with half a bridge made and a "tmpbridge" device. For example with this script: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1 "$dir/network-bridge" "$@" vifnum=0 bridge=xenbr0 netdev=eth0 I end up with this: [root at app1 ~]# /etc/xen/scripts/solfo-network-bridge start Nothing to flush. Waiting for peth1 to negotiate link...SIOCGIFFLAGS: No such device Error for wireless request "Set Encode" (8B2A) : SET failed on device eth1 ; No such device. SIOCGIFFLAGS: No such device Failed to bring up eth1. Error: either "local" is duplicate, or "secondary" is a garbage. [root at app1 ~]# brctl show bridge name bridge id STP enabled interfaces tmpbridge 8000.000000000000 no xenbr1 8000.0030488a53ef no peth1 Any ideas? I'm (still) on Fedora 8. - ask -- http://www.askbjoernhansen.com/ From gayasan_2004 at yahoo.co.in Tue May 6 08:21:05 2008 From: gayasan_2004 at yahoo.co.in (san48) Date: Tue, 6 May 2008 01:21:05 -0700 (PDT) Subject: [Fedora-xen] Guest boots OK with ATA disk (hdX) but not SCSI (sdX). In-Reply-To: References: Message-ID: <17078127.post@talk.nabble.com> even i hav the same problem can i kn the solution. I use sata hard drives (sdx). Regards san Fred Clausen-2 wrote: > > 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 > -------------------------- > > -- > 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-boots-OK-with-ATA-disk-%28hdX%29-but-not-SCSI-%28sdX%29.-tp15870405p17078127.html Sent from the Fedora Xen mailing list archive at Nabble.com. From pasik at iki.fi Tue May 13 07:04:55 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 13 May 2008 10:04:55 +0300 Subject: [Fedora-xen] Fedora kernel-xen pv_ops plans after F9 release (F10 rawhide) Message-ID: <20080513070455.GT20425@edu.joroinen.fi> Hello list! Fedora 9 will be released shortly, so I thought I'll ask about the kernel-xen pv_ops plans and status.. would be nice to get some short progress report. Are these wiki pages up to date? http://fedoraproject.org/wiki/Features/XenPvops http://fedoraproject.org/wiki/Features/XenPvopsDom0 Waiting for dom0 capable kernel-xen to test :) -- Pasi From markmc at redhat.com Tue May 13 07:41:51 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Tue, 13 May 2008 08:41:51 +0100 Subject: [Fedora-xen] Fedora kernel-xen pv_ops plans after F9 release (F10 rawhide) In-Reply-To: <20080513070455.GT20425@edu.joroinen.fi> References: <20080513070455.GT20425@edu.joroinen.fi> Message-ID: <1210664511.3553.1.camel@muff> Hi, On Tue, 2008-05-13 at 10:04 +0300, Pasi K?rkk?inen wrote: > Hello list! > > Fedora 9 will be released shortly, so I thought I'll ask about the > kernel-xen pv_ops plans and status.. would be nice to get some short progress > report. > > Are these wiki pages up to date? > > http://fedoraproject.org/wiki/Features/XenPvops > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > Waiting for dom0 capable kernel-xen to test :) :-) Yep, the pages are up to date. We haven't made any further progress with the Dom0 work - the focus so far has remained on fixing bugs for the F-9 kernel-xen, particularly on x86_64. Cheers, Mark. From pasik at iki.fi Tue May 13 09:27:46 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 13 May 2008 12:27:46 +0300 Subject: [Fedora-xen] Fedora kernel-xen pv_ops plans after F9 release (F10 rawhide) In-Reply-To: <1210664511.3553.1.camel@muff> References: <20080513070455.GT20425@edu.joroinen.fi> <1210664511.3553.1.camel@muff> Message-ID: <20080513092746.GU20425@edu.joroinen.fi> On Tue, May 13, 2008 at 08:41:51AM +0100, Mark McLoughlin wrote: > Hi, > > On Tue, 2008-05-13 at 10:04 +0300, Pasi K?rkk?inen wrote: > > Hello list! > > > > Fedora 9 will be released shortly, so I thought I'll ask about the > > kernel-xen pv_ops plans and status.. would be nice to get some short progress > > report. > > > > Are these wiki pages up to date? > > > > http://fedoraproject.org/wiki/Features/XenPvops > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > > > Waiting for dom0 capable kernel-xen to test :) > > :-) > > Yep, the pages are up to date. We haven't made any further progress with > the Dom0 work - the focus so far has remained on fixing bugs for the F-9 > kernel-xen, particularly on x86_64. > Ok. Thanks for the update! -- Pasi From daniel.spies at fuceekay.com Tue May 13 10:46:56 2008 From: daniel.spies at fuceekay.com (Irrlicht) Date: Tue, 13 May 2008 03:46:56 -0700 (PDT) Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen Message-ID: <17205184.post@talk.nabble.com> Hi there! It's May now, and today is the day for Fedora 9 to be released. So any news on F10 dom0 support? Is this already implemented in the meantime? I don't want to nag anyone, don't get me wrong, please... I am using Kubuntu 8.04 ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a try, but it turns out that there's no dom0 support... So I would like to give F10/rawhide a try, and maybe get things working again... :) Thanks, Daniel Pasi K?rkk?inen wrote: > > 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 >> > > >> > > >> > >> > >> > > -- > 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/Plans-for-paravirt_ops-kernel-xen-tp15876181p17205184.html Sent from the Fedora Xen mailing list archive at Nabble.com. From markmc at redhat.com Tue May 13 11:17:46 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Tue, 13 May 2008 12:17:46 +0100 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <17205184.post@talk.nabble.com> References: <17205184.post@talk.nabble.com> Message-ID: <1210677466.25117.1.camel@muff> On Tue, 2008-05-13 at 03:46 -0700, Irrlicht wrote: > Hi there! > > It's May now, and today is the day for Fedora 9 to be released. So any news > on F10 dom0 support? Is this already implemented in the meantime? I don't > want to nag anyone, don't get me wrong, please... >From earlier this morning: http://www.redhat.com/archives/fedora-xen/2008-May/msg00006.html > I am using Kubuntu 8.04 > ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a > try, but it turns out that there's no dom0 support... So I would like to > give F10/rawhide a try, and maybe get things working again... :) Our advice for now would be to either use Fedora 8 for Xen Dom0 or try using KVM in Fedora 9. Cheers, Mark. From itamar at ispbrasil.com.br Tue May 13 11:25:53 2008 From: itamar at ispbrasil.com.br (Itamar - IspBrasil) Date: Tue, 13 May 2008 08:25:53 -0300 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1210677466.25117.1.camel@muff> References: <17205184.post@talk.nabble.com> <1210677466.25117.1.camel@muff> Message-ID: <48297AC1.7010300@ispbrasil.com.br> there are the xenner in fc9 anyone tried ? Mark McLoughlin wrote: > On Tue, 2008-05-13 at 03:46 -0700, Irrlicht wrote: > >> Hi there! >> >> It's May now, and today is the day for Fedora 9 to be released. So any news >> on F10 dom0 support? Is this already implemented in the meantime? I don't >> want to nag anyone, don't get me wrong, please... >> > > > From earlier this morning: > > http://www.redhat.com/archives/fedora-xen/2008-May/msg00006.html > > >> I am using Kubuntu 8.04 >> ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a >> try, but it turns out that there's no dom0 support... So I would like to >> give F10/rawhide a try, and maybe get things working again... :) >> > > Our advice for now would be to either use Fedora 8 for Xen Dom0 or try > using KVM in Fedora 9. > > Cheers, > Mark. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > From markmc at redhat.com Tue May 13 11:29:19 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Tue, 13 May 2008 12:29:19 +0100 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <48297AC1.7010300@ispbrasil.com.br> References: <17205184.post@talk.nabble.com> <1210677466.25117.1.camel@muff> <48297AC1.7010300@ispbrasil.com.br> Message-ID: <1210678159.25117.3.camel@muff> On Tue, 2008-05-13 at 08:25 -0300, Itamar - IspBrasil wrote: > there are the xenner in fc9 Yes, I forgot that third option - you can use xenner with F9 to run Xen paravirt guests. > anyone tried ? > > > Mark McLoughlin wrote: > > On Tue, 2008-05-13 at 03:46 -0700, Irrlicht wrote: > > > >> Hi there! > >> > >> It's May now, and today is the day for Fedora 9 to be released. So any news > >> on F10 dom0 support? Is this already implemented in the meantime? I don't > >> want to nag anyone, don't get me wrong, please... > >> > > > > > From earlier this morning: > > > > http://www.redhat.com/archives/fedora-xen/2008-May/msg00006.html > > > > > >> I am using Kubuntu 8.04 > >> ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a > >> try, but it turns out that there's no dom0 support... So I would like to > >> give F10/rawhide a try, and maybe get things working again... :) > >> > > > > Our advice for now would be to either use Fedora 8 for Xen Dom0 or try > > using KVM in Fedora 9. > > > > Cheers, > > Mark. > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > From berrange at redhat.com Tue May 13 11:58:45 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 13 May 2008 12:58:45 +0100 Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <1210678159.25117.3.camel@muff> References: <17205184.post@talk.nabble.com> <1210677466.25117.1.camel@muff> <48297AC1.7010300@ispbrasil.com.br> <1210678159.25117.3.camel@muff> Message-ID: <20080513115845.GE15625@redhat.com> On Tue, May 13, 2008 at 12:29:19PM +0100, Mark McLoughlin wrote: > On Tue, 2008-05-13 at 08:25 -0300, Itamar - IspBrasil wrote: > > there are the xenner in fc9 > > Yes, I forgot that third option - you can use xenner with F9 to run Xen > paravirt guests. Xenner is still very new & raw in F9 - I'm in process of finishing off libvirt integration. Come F10 xenner will be 100% supported in Fedora and we'll likely push out updates to F9 at some point too. If you have Xenner installed and are using virt-manager with the 'QEMU' driver it will automatically detect Xenner and give you the option of choosing paravirt in the new VM wizard. 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 rjones at redhat.com Tue May 13 16:42:38 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 13 May 2008 17:42:38 +0100 Subject: [Fedora-xen] [ANNOUNCE] virt-df 2.1.0 - a 'df' tool for virtual guests Message-ID: <20080513164238.GA10564@amd.home.annexia.org> I'm pleased to announce the most recent release of virt-df (2.1.0). Virt-df is 'df' for virtual guests. Run the program on the host / dom0 to display disk space used and available on all partitions on all guests. You don't need to run any sort of program/agent within the guest. Home page: http://et.redhat.com/~rjones/virt-df/ Source/binaries: http://et.redhat.com/~rjones/virt-df/files/ Developer repository: http://hg.et.redhat.com/virt/applications/virt-df--devel This version supports most common filesystems and partitioning schemes, including: - Linux ext2/3 - DOS FAT32 - Windows NTFS - Linux LVM2 (volume groups and logical volumes) - Primary and extended disk partitions - Linux swap - Linux suspend partition You can run it in your host / dom0 to display guest filesystems: # virt-df -c qemu:///system -h Filesystem Size Used Available Type rhel51x32kvm:hda1 96.8 MiB 14.6 MiB 82.2 MiB Linux ext2/3 rhel51x32kvm:VolGroup00/LogVol00 6.4 GiB 3.6 GiB 2.8 GiB Linux ext2/3 rhel51x32kvm:VolGroup00/LogVol01 992.0 MiB Linux swap You can also run it on general disk images, or disk devices: # virt-df -t /dev/sda Filesystem 1K-blocks Used Available Type /dev/sda:hda1 25599996 11309448 14290552 Windows NTFS /dev/sda:hda2 992016 93772 898244 Linux ext2/3 /dev/sda:F9VG/F9Root 23316072 7818164 15497908 Linux ext2/3 /dev/sda:F9VG/F9Swap 1015808 Linux swap /dev/sda:RHEL51VG/RHEL51Root 22382184 7796640 14585544 Linux ext2/3 /dev/sda:RHEL51VG/RHEL51Swap 2031616 Linux swap /dev/sda:VolGroup/FAT32Test 916736 4 914676 DOS/Windows You can write the output to a CSV file (use --csv option) in order to import the data easily into spreadsheets and databases. Included also is an experimental command line tool called 'diskzip' which intelligently compresses disk images by leaving out the bits which aren't actually used in the filesystems / partitions / volume groups contained within. 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 schneecrash+xen at gmail.com Tue May 13 23:08:38 2008 From: schneecrash+xen at gmail.com (snowcrash+xen@gmail.com) Date: Tue, 13 May 2008 16:08:38 -0700 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? Message-ID: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> i've F8 as Dom0. for F8 DomU, pci-passthru devices are visible via lspci *in* DomU. for a new install of F9 DomU, lcpci is (empty). there was discussion that PCI-PassThrough might not make it into F9, http://lists.xensource.com/archives/html/xen-devel/2007-12/msg00454.html "> F9 may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no > PCI device passthrough, or CPU hotplug)" but release notes, http://fedoraproject.org/wiki/Features/XenPvops#head-e15c9305e8d715da9d904a1a99e658409cf12929 make no mention one way or other. *is* pci-passthru known/supposed to work in F9 DomU? if so, then i've got a different issue ... From berrange at redhat.com Tue May 13 23:21:31 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 14 May 2008 00:21:31 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> Message-ID: <20080513232131.GB8844@redhat.com> On Tue, May 13, 2008 at 04:08:38PM -0700, snowcrash+xen at gmail.com wrote: > i've F8 as Dom0. > > for F8 DomU, pci-passthru devices are visible via lspci *in* DomU. > > for a new install of F9 DomU, lcpci is (empty). > > there was discussion that PCI-PassThrough might not make it into F9, > > http://lists.xensource.com/archives/html/xen-devel/2007-12/msg00454.html > "> F9 may well end up lacking features compared to Xen in Fedora 8 & > earlier (eg no > > PCI device passthrough, or CPU hotplug)" > > but release notes, > > http://fedoraproject.org/wiki/Features/XenPvops#head-e15c9305e8d715da9d904a1a99e658409cf12929 > > make no mention one way or other. > > *is* pci-passthru known/supposed to work in F9 DomU? No. Only block, network and framebuffer devices were implemented in the F9 DomU kernel. Regards, 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 schneecrash+xen at gmail.com Tue May 13 23:31:30 2008 From: schneecrash+xen at gmail.com (snowcrash+xen@gmail.com) Date: Tue, 13 May 2008 16:31:30 -0700 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080513232131.GB8844@redhat.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> Message-ID: <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> > > *is* pci-passthru known/supposed to work in F9 DomU? > > No. Only block, network and framebuffer devices were implemented in > the F9 DomU kernel. argh. not what i was hoping to hear :-/ but, good to know (should it be added to the 'release notes', above?), i've been spinning my wheels here. any rough sense for a 'when' it'll be back? soon-to-F10, i'd guess, but *any* add'l guidance would be helpful ... without it, back to F8 for a couple of DomUs. thanks! From berrange at redhat.com Tue May 13 23:40:41 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 14 May 2008 00:40:41 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> Message-ID: <20080513234041.GC8844@redhat.com> On Tue, May 13, 2008 at 04:31:30PM -0700, snowcrash+xen at gmail.com wrote: > > > *is* pci-passthru known/supposed to work in F9 DomU? > > > > No. Only block, network and framebuffer devices were implemented in > > the F9 DomU kernel. > > argh. not what i was hoping to hear :-/ but, good to know (should it > be added to the 'release notes', above?), i've been spinning my wheels > here. > > any rough sense for a 'when' it'll be back? soon-to-F10, i'd guess, > but *any* add'l guidance would be helpful ... This isn't what you'll want to hear but... To be perfectly honest, it is not really a high priority. Our priorities are getting the DomU stuff merged upstream & working reliably and continuing the Dom0 work, since those impact every single user of Xen. Unfortunately PCI pasthrough is quite a niche userbase, so its hard to justify work on it in the short term given limited resources. If someone has skills & time to volunteer to work on the PCI passthrough stuff..... 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 schneecrash+xen at gmail.com Tue May 13 23:55:04 2008 From: schneecrash+xen at gmail.com (snowcrash+xen@gmail.com) Date: Tue, 13 May 2008 16:55:04 -0700 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080513234041.GC8844@redhat.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> Message-ID: <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> > This isn't what you'll want to hear but... > > To be perfectly honest, it is not really a high priority. Our priorities > are getting the DomU stuff merged upstream & working reliably and continuing > the Dom0 work, since those impact every single user of Xen. Unfortunately > PCI pasthrough is quite a niche userbase, so its hard to justify work on it > in the short term given limited resources. If someone has skills & time to > volunteer to work on the PCI passthrough stuff..... ouch! a large %age of the boxes we deploy have a firewall/DomU & and a NAS/Domu, each with dedicated, pass'd-thru NICs. without passthru, performance is lousy. so, iiuc "not really a high priority", i guess -- short of 'growing' someone with the skills -- we're hosed. the unfortunate irony is we *moved* to Fedora because the passthru support in RHEL was flaky, and Fedora was touted as "the right way to get it". regressing a working feature that differentiates the distro would not have been my first choice ... majority, or otherwise. thanks for the straight-up ! now to figure out *which* supported distro CAN fit my needs. sigh. From berrange at redhat.com Wed May 14 01:16:35 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 14 May 2008 02:16:35 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> Message-ID: <20080514011635.GA22943@redhat.com> On Tue, May 13, 2008 at 04:55:04PM -0700, snowcrash+xen at gmail.com wrote: > > This isn't what you'll want to hear but... > > > > To be perfectly honest, it is not really a high priority. Our priorities > > are getting the DomU stuff merged upstream & working reliably and continuing > > the Dom0 work, since those impact every single user of Xen. Unfortunately > > PCI pasthrough is quite a niche userbase, so its hard to justify work on it > > in the short term given limited resources. If someone has skills & time to > > volunteer to work on the PCI passthrough stuff..... > > ouch! a large %age of the boxes we deploy have a firewall/DomU & and > a NAS/Domu, each with dedicated, pass'd-thru NICs. without passthru, > performance is lousy. > > so, iiuc "not really a high priority", i guess -- short of 'growing' > someone with the skills -- we're hosed. > > the unfortunate irony is we *moved* to Fedora because the passthru > support in RHEL was flaky, and Fedora was touted as "the right way to > get it". regressing a working feature that differentiates the distro > would not have been my first choice ... majority, or otherwise. PCI passthrough *is* supported in RHEL-5 Xen kernels. There was a bug in the RHEL-5.1 Dom0 userspace, but that is fixed in 5.2. AFAIK, any RHEL-5.x guest supports PCI passthrough. 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 rjones at redhat.com Wed May 14 13:54:00 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 14 May 2008 14:54:00 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> Message-ID: <20080514135400.GA18846@amd.home.annexia.org> On Tue, May 13, 2008 at 04:55:04PM -0700, snowcrash+xen at gmail.com wrote: > ouch! a large %age of the boxes we deploy have a firewall/DomU & and > a NAS/Domu, each with dedicated, pass'd-thru NICs. without passthru, > performance is lousy. You're aware that PCI passthrough is insecure? Someone who gets root access to a guest can reprogram the NICs (trivially) to read or write any area of memory in any guest or the dom0. This might be pertinent information if you were expecting your firewall to provide isolation. 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 schneecrash+xen at gmail.com Wed May 14 15:23:32 2008 From: schneecrash+xen at gmail.com (snowcrash+xen@gmail.com) Date: Wed, 14 May 2008 08:23:32 -0700 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080514135400.GA18846@amd.home.annexia.org> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> Message-ID: <70f41ba20805140823r6288cf8kf39cda3dda3ee450@mail.gmail.com> hi, > You're aware that PCI passthrough is insecure? Someone who gets root > access to a guest can reprogram the NICs (trivially) to read or write > any area of memory in any guest or the dom0. This might be pertinent > information if you were expecting your firewall to provide isolation. nope. 1st i'm hearing of it ... not that i haven't looked :-/ sigh. hrm. so, although this is "just" a RH/Fedora forum, but xen focussed, let me then ask ... i *want* a distro with -- X86_64/SMP (AMD multicore) support -- Xen 3.2.x builds & runs both in Dom0 & DomU -- capable of deploying a FW in DomU that does not suffer NIC-performance degradation -- or (apparently) security holes -- stable core that'll keep us 'supported' (e.g., *not* the Fedaora scenario i'm now facing; feature-incomplete until, perhaps, F10+, @ which point F8 -- which we're "stuck" on is unsupported) -- app repos (rpm, srpm, other ...) that are safe/available/reliable for full releases (one example, Bind 9.4.2, which seems to be tough to find for RHEL/Centos 5.1) *can* i (yet) "have it all"? iiuc, "no" .... From rjones at redhat.com Wed May 14 15:48:39 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 14 May 2008 16:48:39 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805140823r6288cf8kf39cda3dda3ee450@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <70f41ba20805140823r6288cf8kf39cda3dda3ee450@mail.gmail.com> Message-ID: <20080514154839.GB13833@amd.home.annexia.org> On Wed, May 14, 2008 at 08:23:32AM -0700, snowcrash+xen at gmail.com wrote: > NIC-performance degradation -- or (apparently) security holes Well, the security thing is a hardware limitation. You'll have to wait for next-gen hardware to support VT-d (I think all of motherboard, processor and PCI cards, though I may be wrong about this). There is some experimental support for VT-d in the latest Xen, but not in RHEL 5. 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 parsley at linuxjedi.org Wed May 14 18:29:29 2008 From: parsley at linuxjedi.org (David Parsley) Date: Wed, 14 May 2008 14:29:29 -0400 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080514135400.GA18846@amd.home.annexia.org> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> Message-ID: <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> On Wed, May 14, 2008 at 9:54 AM, Richard W.M. Jones wrote: > On Tue, May 13, 2008 at 04:55:04PM -0700, snowcrash+xen at gmail.com wrote: > > ouch! a large %age of the boxes we deploy have a firewall/DomU & and > > a NAS/Domu, each with dedicated, pass'd-thru NICs. without passthru, > > performance is lousy. > > You're aware that PCI passthrough is insecure? Someone who gets root > access to a guest can reprogram the NICs (trivially) to read or write > any area of memory in any guest or the dom0. This might be pertinent > information if you were expecting your firewall to provide isolation. I figured that a domU having direct hardware access would open security holes; however, the VM I built is for monitoring our Internet connection, and I couldn't figure a way to sniff that traffic without direct hardware access. It's a tightly secured VM with only pinhole access to it in any case. If there's a better way to configure a VM for traffic sniffing, I'd be interested in hearing... Regards, David -- David L. Parsley Manager of Network Services, Bridgewater College "If I have seen further, it is by standing on ye shoulders of giants" - Isaac Newton From schneecrash+xen at gmail.com Wed May 14 18:48:33 2008 From: schneecrash+xen at gmail.com (snowcrash+xen@gmail.com) Date: Wed, 14 May 2008 11:48:33 -0700 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> Message-ID: <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> > If there's a better way to configure a VM > for traffic sniffing, I'd be interested in hearing... as would i. :-/ my understanding (?) is that passthru to PV domu need to be eliminated to avoid the aforementioned security hole. that leaves passthru to HVM -- which requires AMD-V (or intel VT-d ...) extension support. and, i _think_ that means xen ver >= 3.2.0 is required. fedora9's not an option. fedora8's "not going to support it" policy, though understandable on the march to paravirt_ops, leaves little to lean on in terms of community support ... best option i'm finding so far is Centos51, with a rpmrebuild of xen 320 from src rpm, http://bits.xensource.com/oss-xen/release/3.2.0/centos-5.1/xen-3.2.0-0xs.centos5.src.rpm (if there's a 3.2.1 src rpm available, i haven't found it yet ...) in the process of trying it myself ... From berrange at redhat.com Wed May 14 18:53:59 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 14 May 2008 19:53:59 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> Message-ID: <20080514185359.GO15783@redhat.com> On Wed, May 14, 2008 at 11:48:33AM -0700, snowcrash+xen at gmail.com wrote: > > If there's a better way to configure a VM > > for traffic sniffing, I'd be interested in hearing... > > as would i. :-/ > > my understanding (?) is that passthru to PV domu need to be eliminated > to avoid the aforementioned security hole. > > that leaves passthru to HVM -- which requires AMD-V (or intel VT-d > ...) extension support. and, i _think_ that means xen ver >= 3.2.0 is > required. > > fedora9's not an option. fedora8's "not going to support it" policy, > though understandable on the march to paravirt_ops, leaves little to > lean on in terms of community support ... Sadly that's life with Xen. Upstream Xen has basically stopped all kernel development leaving 'official' Xen kernels stuck on 2.6.28 which is essentially useless for any modern distro. We had the choice between trying to finish off the paravirt_ops port, or dropping Xen entirely :-( 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 schneecrash+xen at gmail.com Wed May 14 18:58:21 2008 From: schneecrash+xen at gmail.com (snowcrash+xen@gmail.com) Date: Wed, 14 May 2008 11:58:21 -0700 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080514185359.GO15783@redhat.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> Message-ID: <70f41ba20805141158j3c0c6cd8yd52d18bca269cb50@mail.gmail.com> > Sadly that's life with Xen. Upstream Xen has basically stopped all kernel > development leaving 'official' Xen kernels stuck on 2.6.28 which is > essentially useless for any modern distro. We had the choice between trying > to finish off the paravirt_ops port, or dropping Xen entirely :-( not criticising the choice (well, much anyway ;-) ) ... rather, just hunting for options that work -- if even for the short(ish) term p.s. 2.6.28 a typo? that's 2.6.18, no? From berrange at redhat.com Wed May 14 18:59:59 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 14 May 2008 19:59:59 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <70f41ba20805141158j3c0c6cd8yd52d18bca269cb50@mail.gmail.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <70f41ba20805141158j3c0c6cd8yd52d18bca269cb50@mail.gmail.com> Message-ID: <20080514185959.GQ15783@redhat.com> On Wed, May 14, 2008 at 11:58:21AM -0700, snowcrash+xen at gmail.com wrote: > > Sadly that's life with Xen. Upstream Xen has basically stopped all kernel > > development leaving 'official' Xen kernels stuck on 2.6.28 which is > > essentially useless for any modern distro. We had the choice between trying > > to finish off the paravirt_ops port, or dropping Xen entirely :-( > > not criticising the choice (well, much anyway ;-) ) ... > > rather, just hunting for options that work -- if even for the short(ish) term > > p.s. 2.6.28 a typo? that's 2.6.18, no? Yes, 2.6.18 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 gastonkeller at gmail.com Thu May 15 02:05:48 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Wed, 14 May 2008 22:05:48 -0400 Subject: [Fedora-xen] Paravirtualization with Fedora 7 in Pentium IV Message-ID: Hello, everybody. I'm planning to play with Xen (version 3.1.2) in a machine with a Pentium IV and 2 GB of memory. Fedora 7 is the installed OS (kernel 2.6.21-7.fc7xen), so I guess I'm going to use Fedora 7 for guests as well (can I use Fedora 8 for guests?). I'm considering using a second disk of 140 GB with LVM, in order to change the disk space allocated to the guests in case I need to. My next consideration is how to deal with the installation tree. I think that downloading the files from a repository each time I want to create a new guest would be kind of silly, so I'm considering the suggestion in the Fedora7VirtQuickStart [0] of downloading it once and making it available from the host OS through NFS... or maybe through HTTP using a web server (this last option is just a sudden thought without much evaluation of its value =P ). Any suggestion or comment? I mean. I might be doing something stupid due to my lack of experience. :) Thanks, Gaston PS: I'm trying to give all the info possible, not that is actually needed. [0] http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart#head-546553e2f5a1e21d0ac1b65e0f641c3dc3e36cf4 -- La ?nica verdad es la realidad. From berrange at redhat.com Thu May 15 13:54:53 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 15 May 2008 14:54:53 +0100 Subject: [Fedora-xen] Re: [libvirt] [ANNOUNCE] virt-df 2.1.0 - a 'df' tool for virtual guests In-Reply-To: <20080513164238.GA10564@amd.home.annexia.org> References: <20080513164238.GA10564@amd.home.annexia.org> Message-ID: <20080515135453.GG5983@redhat.com> On Tue, May 13, 2008 at 05:42:38PM +0100, Richard W.M. Jones wrote: > I'm pleased to announce the most recent release of virt-df (2.1.0). > > Virt-df is 'df' for virtual guests. Run the program on the host / dom0 > to display disk space used and available on all partitions on all > guests. You don't need to run any sort of program/agent within the > guest. > > Home page: http://et.redhat.com/~rjones/virt-df/ > Source/binaries: http://et.redhat.com/~rjones/virt-df/files/ > Developer repository: > http://hg.et.redhat.com/virt/applications/virt-df--devel > > This version supports most common filesystems and partitioning > schemes, including: > - Linux ext2/3 > - DOS FAT32 > - Windows NTFS > - Linux LVM2 (volume groups and logical volumes) > - Primary and extended disk partitions > - Linux swap > - Linux suspend partition I'm assuming this only works for raw file & block devices ? Are you planning to support the funky QCow / VMDK formats too ? The other thing that could be annoying is that Fedora 9 support for encrypting all volumes - might need to prompt for a decryption key for that. > Included also is an experimental command line tool called 'diskzip' > which intelligently compresses disk images by leaving out the bits > which aren't actually used in the filesystems / partitions / volume > groups contained within. That's pretty neat. Which file systems does that work for ? VMWare have a funky guest tool which tries to let you get to a similar point. It works by basically openning a file inside the guest VM and filling it with zeros until the entire disk is full. THeir backend can then detect and discard all the sectors with zeros. Understanding the filesystem metdata is a much nicer way todo this :-) 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 rjones at redhat.com Thu May 15 18:53:55 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 15 May 2008 19:53:55 +0100 Subject: [Fedora-xen] Re: [libvirt] [ANNOUNCE] virt-df 2.1.0 - a 'df' tool for virtual guests In-Reply-To: <20080515135453.GG5983@redhat.com> References: <20080513164238.GA10564@amd.home.annexia.org> <20080515135453.GG5983@redhat.com> Message-ID: <20080515185355.GA32617@amd.home.annexia.org> On Thu, May 15, 2008 at 02:54:53PM +0100, Daniel P. Berrange wrote: > > This version supports most common filesystems and partitioning > > schemes, including: > > - Linux ext2/3 > > - DOS FAT32 > > - Windows NTFS > > - Linux LVM2 (volume groups and logical volumes) > > - Primary and extended disk partitions > > - Linux swap > > - Linux suspend partition > > I'm assuming this only works for raw file & block devices ? Are you planning > to support the funky QCow / VMDK formats too ? Yes, interesting point. Since I always use flat files or straight partitions for my guests I admit I hadn't given this much thought :-) However support for these formats is just a matter of decoding enough of the structure to enable the same mappings to be made in the 'virt-df' library, same as for LVM2 or indeed MBR partitions now. I'll take a look at it. IIRC there are several different undocumented variations on the QCow format? > The other thing that could be annoying is that Fedora 9 support for > encrypting all volumes - might need to prompt for a decryption key > for that. Yes -- any encrypted volumes aren't going to work at the moment, and couldn't work unless there was a way to access the passphrase. > > Included also is an experimental command line tool called 'diskzip' > > which intelligently compresses disk images by leaving out the bits > > which aren't actually used in the filesystems / partitions / volume > > groups contained within. > > That's pretty neat. Which file systems does that work for ? VMWare have > a funky guest tool which tries to let you get to a similar point. It works > by basically openning a file inside the guest VM and filling it with zeros > until the entire disk is full. THeir backend can then detect and discard > all the sectors with zeros. Understanding the filesystem metdata is a much > nicer way todo this :-) It works with most of the formats supported by virt-df. For MBR & LVM once you've parsed the partition tables / LVM metadata, then the information you need just falls out naturally. For NTFS & DOS FAT (you won't believe it but ...) you need to find the allocation bitmaps/tables in both cases in order to calculate blocks used/free for df anyway. For ext2 it's a little bit more tricky because one needs to additionally parse the group block free bitmaps [this bit doesn't work at the moment, but is in principle very simple to add]. 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 Thu May 15 19:02:22 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 15 May 2008 20:02:22 +0100 Subject: [Fedora-xen] Paravirtualization with Fedora 7 in Pentium IV In-Reply-To: References: Message-ID: <20080515190222.GA32654@amd.home.annexia.org> On Wed, May 14, 2008 at 10:05:48PM -0400, Gast?n Keller wrote: > Hello, everybody. I'm planning to play with Xen (version 3.1.2) in a > machine with a Pentium IV and 2 GB of memory. Fedora 7 is the > installed OS (kernel 2.6.21-7.fc7xen), so I guess I'm going to use > Fedora 7 for guests as well (can I use Fedora 8 for guests?). You can certainly mix different guests on different hosts. In fact, the ability to run different versions of the operating system is very useful for testing and development of software. > I'm considering using a second disk of 140 GB with LVM, in order to > change the disk space allocated to the guests in case I need to. Yes, LVM is a very good match with virtualization. It's also much faster to use LVM, instead of (eg.) file-backed guests. Give each guest a generous amount of disk space -- usually at least 8 GB for a simple guest install. > My next consideration is how to deal with the installation tree. I > think that downloading the files from a repository each time I want to > create a new guest would be kind of silly, so I'm considering the > suggestion in the Fedora7VirtQuickStart [0] of downloading it once and > making it available from the host OS through NFS... or maybe through > HTTP using a web server (this last option is just a sudden thought > without much evaluation of its value =P ). I'm using exactly this scheme -- with HTTP (ie. Apache) as it happens, just because it was easier to set up. For Fedora you can mirror everything in the /os/ directory, for example http://www.mirrorservice.org/sites/download.fedora.redhat.com/pub/fedora/linux/releases/9/Fedora/i386/os/ > Any suggestion or comment? I mean. I might be doing something stupid > due to my lack of experience. :) 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 lists at ralii.com Thu May 15 19:58:19 2008 From: lists at ralii.com (Robert Locke) Date: Thu, 15 May 2008 15:58:19 -0400 Subject: [Fedora-xen] Question on Windows HVM Domain Message-ID: <1210881499.3627.23.camel@rlt60f8.laptop.redhat.com> Bit of a n00b question.... I am currently running F8-Dom0 with an HVM-based Windows XP DomU. I tend to run it from virt-manager the occasional times I use it. Given that F9-Dom0 support is still a work-in-progress, I started reading about KVM existing in the "regular" kernel. Since the Dom0 is my main "work" platform, I am considering upgrading to F9, but, losing Xen. The question becomes, can I run the existing Windows XP instance under virt-manager via KVM? BTW, the disk for Windows XP is an LV, and I would prefer to continue NAT'ing it to the outside, if that matters.... Some of the doc's on fedoraproject.org started identifying parity between KVM and Qemu (which I thought is what is used for HVM).... Am I totally insane, or on to a potential solution that lets me move my Dom0 to F9? Thanks for any pointers/help, --Rob From acathrow at redhat.com Thu May 15 20:06:08 2008 From: acathrow at redhat.com (Andrew Cathrow) Date: Thu, 15 May 2008 16:06:08 -0400 Subject: [Fedora-xen] Question on Windows HVM Domain In-Reply-To: <1210881499.3627.23.camel@rlt60f8.laptop.redhat.com> References: <1210881499.3627.23.camel@rlt60f8.laptop.redhat.com> Message-ID: <1210881968.8918.75.camel@aic-thinkpad-f9.cathrow.org> On Thu, 2008-05-15 at 15:58 -0400, Robert Locke wrote: > Bit of a n00b question.... > > I am currently running F8-Dom0 with an HVM-based Windows XP DomU. I > tend to run it from virt-manager the occasional times I use it. > > Given that F9-Dom0 support is still a work-in-progress, I started > reading about KVM existing in the "regular" kernel. > > Since the Dom0 is my main "work" platform, I am considering upgrading to > F9, but, losing Xen. > > The question becomes, can I run the existing Windows XP instance under > virt-manager via KVM? BTW, the disk for Windows XP is an LV, and I > would prefer to continue NAT'ing it to the outside, if that matters.... Yes. Windows will probably ask you to reactivate, since it sees a significant change in the underlying hardware. > > Some of the doc's on fedoraproject.org started identifying parity > between KVM and Qemu (which I thought is what is used for HVM).... > > Am I totally insane, or on to a potential solution that lets me move my > Dom0 to F9? > > Thanks for any pointers/help, > > --Rob > > > -- > 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 berrange at redhat.com Fri May 16 00:38:24 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 16 May 2008 01:38:24 +0100 Subject: [Fedora-xen] Re: [libvirt] [ANNOUNCE] virt-df 2.1.0 - a 'df' tool for virtual guests In-Reply-To: <20080515185355.GA32617@amd.home.annexia.org> References: <20080513164238.GA10564@amd.home.annexia.org> <20080515135453.GG5983@redhat.com> <20080515185355.GA32617@amd.home.annexia.org> Message-ID: <20080516003824.GB28467@redhat.com> On Thu, May 15, 2008 at 07:53:55PM +0100, Richard W.M. Jones wrote: > On Thu, May 15, 2008 at 02:54:53PM +0100, Daniel P. Berrange wrote: > > > This version supports most common filesystems and partitioning > > > schemes, including: > > > - Linux ext2/3 > > > - DOS FAT32 > > > - Windows NTFS > > > - Linux LVM2 (volume groups and logical volumes) > > > - Primary and extended disk partitions > > > - Linux swap > > > - Linux suspend partition > > > > I'm assuming this only works for raw file & block devices ? Are you planning > > to support the funky QCow / VMDK formats too ? > > Yes, interesting point. Since I always use flat files or straight > partitions for my guests I admit I hadn't given this much thought :-) > However support for these formats is just a matter of decoding enough > of the structure to enable the same mappings to be made in the > 'virt-df' library, same as for LVM2 or indeed MBR partitions now. > > I'll take a look at it. IIRC there are several different undocumented > variations on the QCow format? There's version 1, and version 2. And then the incompatible version 2 inflicted by Xen :-( > > The other thing that could be annoying is that Fedora 9 support for > > encrypting all volumes - might need to prompt for a decryption key > > for that. > > Yes -- any encrypted volumes aren't going to work at the moment, and > couldn't work unless there was a way to access the passphrase. The passphrase is in the user's brain. THe OS prompts for it at boot time, so virt-df would need todo similar if it wanted to support decryption. Perhaps its just not a important use case. In the ISP model, guest admins won't trust the host admin so you won't have the keys anyway. If the guest admin does trust the host admin, would they really be using encryption in the guest ? 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 rjones at redhat.com Fri May 16 07:42:13 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 16 May 2008 08:42:13 +0100 Subject: [Fedora-xen] Question on Windows HVM Domain In-Reply-To: <1210881499.3627.23.camel@rlt60f8.laptop.redhat.com> References: <1210881499.3627.23.camel@rlt60f8.laptop.redhat.com> Message-ID: <20080516074213.GA3077@amd.home.annexia.org> On Thu, May 15, 2008 at 03:58:19PM -0400, Robert Locke wrote: > The question becomes, can I run the existing Windows XP instance under > virt-manager via KVM? BTW, the disk for Windows XP is an LV, and I > would prefer to continue NAT'ing it to the outside, if that matters.... Yes and no. It will probably work, but in my experience it was quite sensitive to the exact version of KVM & whether features such as ACPI were enabled or disabled. Maybe XP is better -- I was using W2K8. Note that KVM requires hardware virtualization support in your CPU and (for Intel) BIOS. 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 daniel.spies at fuceekay.com Tue May 13 10:08:46 2008 From: daniel.spies at fuceekay.com (Irrlicht) Date: Tue, 13 May 2008 03:08:46 -0700 (PDT) Subject: [Fedora-xen] Plans for paravirt_ops kernel-xen In-Reply-To: <20080309121214.GN21162@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> <20080309121214.GN21162@edu.joroinen.fi> Message-ID: <17205184.post@talk.nabble.com> Hi there! It's May now, and today is the day for Fedora 9 to be released. So any news on F10 dom0 support? Is this already implemented in the meantime? I don't want to nag anyone, don't get me wrong, please... I am using Kubuntu 8.04 ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a try, but it turns out that there's no dom0 support... So I would like to give F10/rawhide a try, and maybe get things working again... :) Thanks, Daniel Pasi K?rkk?inen wrote: > > 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 >> > > >> > > >> > >> > >> > > -- > 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/Plans-for-paravirt_ops-kernel-xen-tp15876181p17205184.html Sent from the Fedora Xen mailing list archive at Nabble.com. From daniel.spies at fuceekay.com Fri May 16 12:10:53 2008 From: daniel.spies at fuceekay.com (Daniel Spies) Date: Fri, 16 May 2008 14:10:53 +0200 Subject: [Fedora-xen] Plans for =?UTF-8?Q?paravirt=5Fops=20kernel-xen?= In-Reply-To: <17205184.post@talk.nabble.com> References: <1204817357.25995.21.camel@muff> Message-ID: <20080516121053.601994CF4516@ms001.fuceekay.com> <20080306192805.GG21162 at edu.joroinen.fi> <20080306193303.GE19897 at redhat.com> <20080309111210.GK21162 at edu.joroinen.fi> <47D3CBC7.5080606 at ispbrasil.com.br> <20080309120926.GM21162 at edu.joroinen.fi> <20080309121214.GN21162 at edu.joroinen.fi> <17205184.post at talk.nabble.com> Message-ID: X-Sender: daniel.spies at fuceekay.com Received: from 62.159.37.130 [62.159.37.130] with HTTP/1.1 (POST); Fri, 16 May 2008 14:10:53 +0200 User-Agent: RoundCube Webmail/0.1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit wtf? This message can be ignored. It's old and already answered... Thanks, Daniel On Tue, 13 May 2008 03:08:46 -0700 (PDT), Irrlicht wrote: > > Hi there! > > It's May now, and today is the day for Fedora 9 to be released. So any > news > on F10 dom0 support? Is this already implemented in the meantime? I don't > want to nag anyone, don't get me wrong, please... I am using Kubuntu 8.04 > ATM, and am facing loads of troubles with Xen. Now I wanted to give F9 a > try, but it turns out that there's no dom0 support... So I would like to > give F10/rawhide a try, and maybe get things working again... :) > > Thanks, > Daniel > > > Pasi K??rkk??inen wrote: >> >> 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 >>> > > >>> > > >>> > >>> > >>> >> >> -- >> 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/Plans-for-paravirt_ops-kernel-xen-tp15876181p17205184.html > Sent from the Fedora Xen mailing list archive at Nabble.com. > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From mathieu.kretchner at sophia.inria.fr Fri May 16 12:55:13 2008 From: mathieu.kretchner at sophia.inria.fr (Mathieu Kretchner) Date: Fri, 16 May 2008 14:55:13 +0200 Subject: [Fedora-xen] backup domU Message-ID: <482D8431.5000608@sophia.inria.fr> Hello all, I'm sure it's a frequent question asked a lot of time, But is it possible to backup domU without stopping it ? Else could you please give me some url talking about the subject ? (it's difficult to find something in the list archives) -------------- next part -------------- A non-text attachment was scrubbed... Name: mathieu_kretchner.vcf Type: text/x-vcard Size: 258 bytes Desc: not available URL: From greg.hellings at harcourt.com Fri May 16 16:10:39 2008 From: greg.hellings at harcourt.com (Greg Hellings) Date: Fri, 16 May 2008 09:10:39 -0700 Subject: [Fedora-xen] Problem adding new domu Message-ID: I'm trying to create a paravirtual domu on a system that I've already got an hvm domu on using Virt-Manager. I am choosing Shared physical device on the network page, and 'peth0 (Bridge eth0)' is the only selectable option for Device. I choose this, and then I get the following error: Unable to complete install: 'virDomainCreatelinux() failed POST operation failed: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working. What am I doing wrong? -- Greg From deepc2005 at hotmail.com Fri May 16 22:42:42 2008 From: deepc2005 at hotmail.com (Maximilian Freisinger) Date: Fri, 16 May 2008 18:42:42 -0400 Subject: [Fedora-xen] Update of dom0 posible? Message-ID: Hello, as there is no dom0 support in FC9, i am about to use FC8 as dom0 with FC9 as domU. My question now is: If there should be an update for dom0 support in FC9, will it be possible to install a FC9 dom0 system and move all domUs to that system, on the same machine? My idea was to setup a functional dom0 and move all configs to that system, but as FC8 is xen 3.1.2 and anything else would at least be 3.2.x it would be interesting to know if a port is possible. dc _________________________________________________________________ Give to a good cause with every e-mail. Join the i?m Initiative from Microsoft. http://im.live.com/Messenger/IM/Join/Default.aspx?souce=EML_WL_ GoodCause -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Fri May 16 22:51:12 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 16 May 2008 23:51:12 +0100 Subject: [Fedora-xen] backup domU In-Reply-To: <482D8431.5000608@sophia.inria.fr> References: <482D8431.5000608@sophia.inria.fr> Message-ID: <20080516225112.GA8523@amd.home.annexia.org> On Fri, May 16, 2008 at 02:55:13PM +0200, Mathieu Kretchner wrote: > I'm sure it's a frequent question asked a lot of time, But is it possible > to backup domU without stopping it ? No. But some things like checkpointing are possible.. What exactly do you want to do? 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 mathieu.kretchner at sophia.inria.fr Mon May 19 06:54:36 2008 From: mathieu.kretchner at sophia.inria.fr (Mathieu Kretchner) Date: Mon, 19 May 2008 08:54:36 +0200 Subject: [Fedora-xen] backup domU In-Reply-To: <20080516225112.GA8523@amd.home.annexia.org> References: <482D8431.5000608@sophia.inria.fr> <20080516225112.GA8523@amd.home.annexia.org> Message-ID: <4831242C.6090701@sophia.inria.fr> I would like a backup system tool like vmware offer. In other words how to have a maximum availability with my domU fully backuped ? Thanks for your help ... Richard W.M. Jones a ?crit : > On Fri, May 16, 2008 at 02:55:13PM +0200, Mathieu Kretchner wrote: >> I'm sure it's a frequent question asked a lot of time, But is it possible >> to backup domU without stopping it ? > > No. But some things like checkpointing are possible.. What exactly > do you want to do? > > Rich. > -------------- next part -------------- A non-text attachment was scrubbed... Name: mathieu_kretchner.vcf Type: text/x-vcard Size: 258 bytes Desc: not available URL: From rjones at redhat.com Mon May 19 06:57:15 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 19 May 2008 07:57:15 +0100 Subject: [Fedora-xen] backup domU In-Reply-To: <4831242C.6090701@sophia.inria.fr> References: <482D8431.5000608@sophia.inria.fr> <20080516225112.GA8523@amd.home.annexia.org> <4831242C.6090701@sophia.inria.fr> Message-ID: <20080519065715.GA14573@amd.home.annexia.org> On Mon, May 19, 2008 at 08:54:36AM +0200, Mathieu Kretchner wrote: > I would like a backup system tool like vmware offer. In other words how to > have a maximum availability with my domU fully backuped ? Just choose your favourite back up program and run it inside the guest. Treat the guest as you would any other machine. It's not possible to do the backups entirely from the dom0. 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 aclark at commsolv.com Fri May 16 13:34:20 2008 From: aclark at commsolv.com (Aaron Clark) Date: Fri, 16 May 2008 09:34:20 -0400 Subject: [Fedora-xen] backup domU In-Reply-To: <482D8431.5000608@sophia.inria.fr> References: <482D8431.5000608@sophia.inria.fr> Message-ID: <482D8D5C.5060407@commsolv.com> Mathieu Kretchner wrote: > Hello all, > > I'm sure it's a frequent question asked a lot of time, But is it > possible to backup domU without stopping it ? > Else could you please give me some url talking about the subject ? If you're using LVM then I believe you should be able to snapshot the domU LV and then backup via the snapshot without stopping the domU. Aaron From mathieu.kretchner at sophia.inria.fr Mon May 19 08:27:41 2008 From: mathieu.kretchner at sophia.inria.fr (Mathieu Kretchner) Date: Mon, 19 May 2008 10:27:41 +0200 Subject: [Fedora-xen] backup domU In-Reply-To: <20080519065715.GA14573@amd.home.annexia.org> References: <482D8431.5000608@sophia.inria.fr> <20080516225112.GA8523@amd.home.annexia.org> <4831242C.6090701@sophia.inria.fr> <20080519065715.GA14573@amd.home.annexia.org> Message-ID: <483139FD.4030200@sophia.inria.fr> Ok thanks for your advice. Richard W.M. Jones a ?crit : > On Mon, May 19, 2008 at 08:54:36AM +0200, Mathieu Kretchner wrote: >> I would like a backup system tool like vmware offer. In other words how to >> have a maximum availability with my domU fully backuped ? > > Just choose your favourite back up program and run it inside the > guest. Treat the guest as you would any other machine. It's not > possible to do the backups entirely from the dom0. > > Rich. > -------------- next part -------------- A non-text attachment was scrubbed... Name: mathieu_kretchner.vcf Type: text/x-vcard Size: 258 bytes Desc: not available URL: From mathieu.kretchner at sophia.inria.fr Mon May 19 08:29:17 2008 From: mathieu.kretchner at sophia.inria.fr (Mathieu Kretchner) Date: Mon, 19 May 2008 10:29:17 +0200 Subject: [Fedora-xen] backup domU In-Reply-To: <482D8D5C.5060407@commsolv.com> References: <482D8431.5000608@sophia.inria.fr> <482D8D5C.5060407@commsolv.com> Message-ID: <48313A5D.9030209@sophia.inria.fr> Are you speaking about LVM in the FS of the DomU or in the FS of Dom0 ? Aaron Clark a ?crit : > Mathieu Kretchner wrote: >> Hello all, >> >> I'm sure it's a frequent question asked a lot of time, But is it >> possible to backup domU without stopping it ? >> Else could you please give me some url talking about the subject ? > > If you're using LVM then I believe you should be able to snapshot the > domU LV and then backup via the snapshot without stopping the domU. > > Aaron > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- A non-text attachment was scrubbed... Name: mathieu_kretchner.vcf Type: text/x-vcard Size: 258 bytes Desc: not available URL: From aclark at commsolv.com Mon May 19 12:58:30 2008 From: aclark at commsolv.com (Aaron Clark) Date: Mon, 19 May 2008 08:58:30 -0400 Subject: [Fedora-xen] backup domU In-Reply-To: <48313A5D.9030209@sophia.inria.fr> References: <482D8431.5000608@sophia.inria.fr> <482D8D5C.5060407@commsolv.com> <48313A5D.9030209@sophia.inria.fr> Message-ID: <48317976.9070307@commsolv.com> Mathieu Kretchner wrote: > Are you speaking about LVM in the FS of the DomU or in the FS of Dom0 ? I meant using LVM on the Dom0 and then using an LV as the backing filesystem of the DomU. Aaron P.S. Please don't top-post, it's hard to follow. > Aaron Clark a ?crit : >> Mathieu Kretchner wrote: >>> Hello all, >>> >>> I'm sure it's a frequent question asked a lot of time, But is it >>> possible to backup domU without stopping it ? >>> Else could you please give me some url talking about the subject ? >> >> If you're using LVM then I believe you should be able to snapshot the >> domU LV and then backup via the snapshot without stopping the domU. >> >> Aaron >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen > From mathieu.kretchner at sophia.inria.fr Mon May 19 14:30:12 2008 From: mathieu.kretchner at sophia.inria.fr (Mathieu Kretchner) Date: Mon, 19 May 2008 16:30:12 +0200 Subject: [Fedora-xen] backup domU In-Reply-To: <48317976.9070307@commsolv.com> References: <482D8431.5000608@sophia.inria.fr> <482D8D5C.5060407@commsolv.com> <48313A5D.9030209@sophia.inria.fr> <48317976.9070307@commsolv.com> Message-ID: <48318EF4.3030801@sophia.inria.fr> Aaron Clark a ?crit : > Mathieu Kretchner wrote: >> Are you speaking about LVM in the FS of the DomU or in the FS of Dom0 ? > > I meant using LVM on the Dom0 and then using an LV as the backing > filesystem of the DomU. > > Aaron > > P.S. Please don't top-post, it's hard to follow. > >> Aaron Clark a ?crit : >>> Mathieu Kretchner wrote: >>>> Hello all, >>>> >>>> I'm sure it's a frequent question asked a lot of time, But is it >>>> possible to backup domU without stopping it ? >>>> Else could you please give me some url talking about the subject ? >>> >>> If you're using LVM then I believe you should be able to snapshot the >>> domU LV and then backup via the snapshot without stopping the domU. >>> >>> Aaron >>> >>> -- >>> Fedora-xen mailing list >>> Fedora-xen at redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-xen >> > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Ok thank you and sorry for top-posting ! Do you have good how to about backup a LV ? and creating a domU in an LV ? Thanks -------------- next part -------------- A non-text attachment was scrubbed... Name: mathieu_kretchner.vcf Type: text/x-vcard Size: 258 bytes Desc: not available URL: From ametzger at silkspeed.com Mon May 19 15:03:15 2008 From: ametzger at silkspeed.com (Aaron Metzger) Date: Mon, 19 May 2008 11:03:15 -0400 Subject: [Fedora-xen] backup domU In-Reply-To: <48318EF4.3030801@sophia.inria.fr> References: <482D8431.5000608@sophia.inria.fr> <482D8D5C.5060407@commsolv.com> <48313A5D.9030209@sophia.inria.fr> <48317976.9070307@commsolv.com> <48318EF4.3030801@sophia.inria.fr> Message-ID: <483196B3.1030804@silkspeed.com> Mathieu Kretchner wrote: > Do you have good how to about backup a LV ? and creating a domU in an LV ? > Google for "LVM2 snapshot" or look at the "snapshot" option on the man page for "lvcreate" to answer the first half of your question. Here is a snippet of the cron script that I run twice a day to backup all of my guests while they are running. > /usr/sbin/lvcreate --extents 100%FREE --snapshot --name vmsnapshots /dev/vms/vms > /bin/mount /dev/vms/vmsnapshots /vmsnapshots > DAY="`date +%A-%H%M`" > /usr/bin/time --format "%E" /bin/tar --sparse -zcvf /mnt/ssbackup01/vms-$DAY.tar.gz /var/lib/xend/domains /vmsnapshots > /bin/umount /vmsnapshots > /usr/sbin/lvremove --force /dev/vms/vmsnapshots I am also interested in seeing a detailed howto for the "creating a domU in an LV" part of your question. I currently do live backups of all of my virtual machines using LVM2 snapshots but I had to put my virtual machine images in files instead of partitions to accomplish this. I never successfully created a virtual machine in an a logical volume partition. Some people say that I am sacrificing performance by putting my virtual machines in files. If that is true, then I'd love to see a detailed example of creating an arbitrary Xen guest image in a a logical volume. -- Good luck, Aaron Metzger From Dustin.Henning at prd-inc.com Mon May 19 15:14:20 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Mon, 19 May 2008 11:14:20 -0400 Subject: [Fedora-xen] backup domU - DomU in LV, FYI In-Reply-To: <483196B3.1030804@silkspeed.com> References: <482D8431.5000608@sophia.inria.fr> <482D8D5C.5060407@commsolv.com> <48313A5D.9030209@sophia.inria.fr> <48317976.9070307@commsolv.com> <48318EF4.3030801@sophia.inria.fr> <483196B3.1030804@silkspeed.com> Message-ID: <003001c8b9c3$0326b9d0$09742d70$@Henning@prd-inc.com> I have created PVMs in LVM partitions in the past. I assume that HVMs would be similar. I believe I was using CentOS 4 at the time, and I had to use the complete /dev path instead of the shortcut you get used to with most distros (including CentOS). Also, I was using standard XenSource rpm-installed manually-configured xen in runlevel 3, so I don't know if you can do that through the Fedora tools or even with the Fedora Xen. However, you might give it a shot. Unfortunately, I am not currently messing with LVM, so I can't give you any kind of detail on this (such as an example complete /dev path vs shortcut). Dustin From rjones at redhat.com Mon May 19 15:29:29 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 19 May 2008 16:29:29 +0100 Subject: [Fedora-xen] Dump guest memory in Xen? Message-ID: <20080519152929.GA19826@amd.home.annexia.org> I might be missing something obvious but ... QEMU has a nice 'memsave' command which lets you save/dump parts of guest memory to a file. Is there a similar feature in Xen? (Note I don't want to dump all memory to a core file, just snoop on small sections of memory). 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 markmc at redhat.com Mon May 19 15:42:20 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 19 May 2008 16:42:20 +0100 Subject: [Fedora-xen] Dump guest memory in Xen? In-Reply-To: <20080519152929.GA19826@amd.home.annexia.org> References: <20080519152929.GA19826@amd.home.annexia.org> Message-ID: <1211211740.3368.7.camel@muff> On Mon, 2008-05-19 at 16:29 +0100, Richard W.M. Jones wrote: > I might be missing something obvious but ... > > QEMU has a nice 'memsave' command which lets you save/dump parts of > guest memory to a file. Is there a similar feature in Xen? > > (Note I don't want to dump all memory to a core file, just snoop on > small sections of memory). Don't know of a tool to do that, but you can map the guest's memory using the xc_map_foreign_*() API. Take a look at xen/tools/xentrace/xenctx.c to see how it pokes around in guest memory when dumping a stack trace. Cheers, Mark. From armbru at redhat.com Mon May 19 16:05:27 2008 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 19 May 2008 18:05:27 +0200 Subject: [Fedora-xen] Update of dom0 posible? In-Reply-To: (Maximilian Freisinger's message of "Fri\, 16 May 2008 18\:42\:42 -0400") References: Message-ID: <87hccus2ig.fsf@pike.pond.sub.org> Maximilian Freisinger writes: > Hello, > as there is no dom0 support in FC9, i am about to use FC8 as dom0 with FC9 as domU. > My question now is: > If there should be an update for dom0 support in FC9, will it be possible to install a FC9 dom0 system and move all domUs to that system, on the same machine? > My idea was to setup a functional dom0 and move all configs to that system, but as FC8 is xen 3.1.2 and anything else would at least be 3.2.x it would be interesting to know if a port is possible. > > dc The domU interface is supposed to be stable, so you should be able to do that. From Dustin.Henning at prd-inc.com Tue May 20 15:15:39 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 20 May 2008 11:15:39 -0400 Subject: [Fedora-xen] HVM DomU on F9? Message-ID: <000a01c8ba8c$5cc63320$16529960$@Henning@prd-inc.com> I am currently running F7 with HVMs. I am considering trying out F8 or F9 to see if I can get them to work as well. I know F9 doesn't have a Dom0, at least not yet. I also understand that DomUs are supposed to work on it. However, I don't believe I have seen any discussion as to how that is done and/or whether or not HVM DomUs are supported in that environment. I am assuming that since the decision that F9 wouldn't include Dom0 support was relatively recent that I probably don't need to search the list archives. Can anyone tell me whether or not HVM DomUs work in F9 and whether or not there is any additional performance degradation vs running them in a Dom0? I actually prefer to run HVM DomUs in a regular kernel if possible because I have always had mouse problems in Dom0 of F7, but not in the base kernel. I understand that KVM is an option, but since Xen now supports Windows with ACPI (without the degradation that was once common in Xen and is still common in KVM because of a certain ACPI register apparently regularly polled by Windows [I would love to know what register, as I could then try to find a way to prevent Windows from doing that and KVM might perform as well as Xen]), I feel that KVM would be a big step backwards. Additionally, there are apparently more paravirtual drivers available for Windows (though they are not readily available in binary form and stable, more on that in my next message), though using std-vga in KVM is nice (with standard VESA 2.0, a generic Windows driver already exists outside of the project). Finally, assuming that HVM DomUs can be run in F9, do the old services and xm commands still exist, or will I have to learn to use virsh and make xml configs? Thanks, Dustin From Dustin.Henning at prd-inc.com Tue May 20 15:54:13 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 20 May 2008 11:54:13 -0400 Subject: [Fedora-xen] Paravirtual Windows Driver Binaries? Message-ID: <000e01c8ba91$c036a4d0$40a3ee70$@Henning@prd-inc.com> Apparently a James Harper in Australia has been working on PV drivers for Windows on GPL Xen for some time. I don't know if this link will work for others, but it looks like it should (though probably not permanently): http://markmail.org/search/?q=WindowsXenPV-0.8.9.zip#query:WindowsXenPV-0.8. 9.zip+page:1+mid:gmf4kraasqdxxamm+state:facets I downloaded his latest work, WindowsXenPV-0.8.9.zip, but apparently compilation is required. I know Windows drivers and programs don't have to be different (on account of Windows) the way they do on Linux (because of the many different distros), so I am not sure why compilation is required unless it is somehow related to the version of Xen running on the host system potentially offering up paravirtualization in a different way. I am not sure on this because the directions are slightly vague and if I read them properly, source code for the version of Xen in question is not mentioned. Anyway, I am curious as to whether or not anyone can point me toward a these drivers in an already compiled state. I don't know if they would be included in any certain repository of which I am unaware or whether it is more likely that they simply don't exist (yet). As I am running F7, I am also curious as to whether or not Fedora's custom Xen kernels would even support the PV capabilities on HVMs. I say on HVMs because it is my understanding that the Windows machine decides which drivers to load (and which devices to detect) based on a boot switch in the VM OS and I haven't seen anything indicating a separate Xen setup for full PV. I ask because I would love to download binary drivers and have a go at this, but actually building it all is a bit more complicated and time consuming for me (especially if I'm re-inventing the wheel), as I've never compiled anything in Windows and don't have any of the necessary software readily available (free to download, but I don't have any seriously high speed access). I also don't know whether it is possible that the Fedora team (or any third party) would have any interest in compiling these drivers or making them available even if someone else did the work since they are for Windows and would certainly require manual installation after download/(yum) "install". It would be possible (though far from automated) to mount the VM partition and copy the directory tree to it, so downloading them directly to the Dom0 doesn't seem like a problem to me, but downloading them on the DomU would work as well if they were available some other way. I would love to find out that the version of Xen doesn't matter for PV drivers (beyond being above 3.0 or whatever), that the Fedora version is standard in regards to PV, that a compiled version is available because of that, and that one can download it from URL X as such, but I am rarely so lucky. As an interesting aside, apparently the KVM project includes a PV driver for Windows networking, but this (not necessarily production ready) Xen GPLPV driver package includes not only networking, but also block devices and a service to enable the xm shutdown and xm restart commands. Anyway, I welcome all input. Thanks, Dustin -------------- next part -------------- An HTML attachment was scrubbed... URL: From avi at qumranet.com Tue May 20 15:54:55 2008 From: avi at qumranet.com (Avi Kivity) Date: Tue, 20 May 2008 18:54:55 +0300 Subject: [Fedora-xen] HVM DomU on F9? In-Reply-To: <000a01c8ba8c$5cc63320$16529960$@Henning@prd-inc.com> References: <000a01c8ba8c$5cc63320$16529960$@Henning@prd-inc.com> Message-ID: <4832F44F.5050308@qumranet.com> Dustin Henning wrote: > I actually prefer to run HVM DomUs in a regular kernel if possible > because I have always had mouse problems in Dom0 of F7, but not in the base > kernel. I understand that KVM is an option, but since Xen now supports > Windows with ACPI (without the degradation that was once common in Xen and > is still common in KVM because of a certain ACPI register apparently > regularly polled by Windows [I would love to know what register, as I could > It's called that Task Priority Register, or TPR. > then try to find a way to prevent Windows from doing that and KVM might > perform as well as Xen]), I feel that KVM would be a big step backwards. > For uniprocessor guests, kvm supports TPR optimization (since December 2007). It's disabled on SMP guests due to stability issues, unfortunately. > Additionally, there are apparently more paravirtual drivers available for > Windows (though they are not readily available in binary form and stable, > more on that in my next message), though using std-vga in KVM is nice (with > standard VESA 2.0, a generic Windows driver already exists outside of the > project). A paravirtualized network driver is freely available for kvm. It is still not fully stable under heavy loads, though. We expect to fix this soon. -- error compiling committee.c: too many arguments to function From Dustin.Henning at prd-inc.com Tue May 20 16:01:40 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 20 May 2008 12:01:40 -0400 Subject: [Fedora-xen] HVM DomU on F9? In-Reply-To: <4832F44F.5050308@qumranet.com> References: <000a01c8ba8c$5cc63320$16529960$@Henning@prd-inc.com> <4832F44F.5050308@qumranet.com> Message-ID: <001901c8ba92$cae6e420$60b4ac60$@Henning@prd-inc.com> Great information, and straight from the source! Can you tell me on which version of KVM support for TPR was implemented? I assume I am not up to said version, but I want to confirm, because when I start my Windows guests (currently all uniprocessor) in KVM, csrss.exe uses all available processor constantly until I follow the KVM Windows ACPI workaround directions. I have updated since December, but I am running Fedora 7 rpms, so I may have to move up a version or two to get that support. Thanks, Dustin -----Original Message----- From: Avi Kivity [mailto:avi at qumranet.com] Sent: Tuesday, May 20, 2008 11:55 To: Dustin.Henning at prd-inc.com Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] HVM DomU on F9? Dustin Henning wrote: > I actually prefer to run HVM DomUs in a regular kernel if possible > because I have always had mouse problems in Dom0 of F7, but not in the base > kernel. I understand that KVM is an option, but since Xen now supports > Windows with ACPI (without the degradation that was once common in Xen and > is still common in KVM because of a certain ACPI register apparently > regularly polled by Windows [I would love to know what register, as I could > It's called that Task Priority Register, or TPR. > then try to find a way to prevent Windows from doing that and KVM might > perform as well as Xen]), I feel that KVM would be a big step backwards. > For uniprocessor guests, kvm supports TPR optimization (since December 2007). It's disabled on SMP guests due to stability issues, unfortunately. > Additionally, there are apparently more paravirtual drivers available for > Windows (though they are not readily available in binary form and stable, > more on that in my next message), though using std-vga in KVM is nice (with > standard VESA 2.0, a generic Windows driver already exists outside of the > project). A paravirtualized network driver is freely available for kvm. It is still not fully stable under heavy loads, though. We expect to fix this soon. -- error compiling committee.c: too many arguments to function From avi at qumranet.com Tue May 20 16:07:46 2008 From: avi at qumranet.com (Avi Kivity) Date: Tue, 20 May 2008 19:07:46 +0300 Subject: [Fedora-xen] HVM DomU on F9? In-Reply-To: <001901c8ba92$cae6e420$60b4ac60$@Henning@prd-inc.com> References: <000a01c8ba8c$5cc63320$16529960$@Henning@prd-inc.com> <4832F44F.5050308@qumranet.com> <001901c8ba92$cae6e420$60b4ac60$@Henning@prd-inc.com> Message-ID: <4832F752.7070300@qumranet.com> Dustin Henning wrote: > Great information, and straight from the source! Can you tell me on > which version of KVM support for TPR was implemented? kvm-58 (see http://kvm.qumranet.com/kvmwiki/ChangeLog). F7's rpms were stuck on kvm-36 IIRC. -- error compiling committee.c: too many arguments to function From erenoglu at gmail.com Tue May 20 16:36:41 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Tue, 20 May 2008 18:36:41 +0200 Subject: [Fedora-xen] Paravirtual Windows Driver Binaries? In-Reply-To: <-4118396398988483182@unknownmsgid> References: <-4118396398988483182@unknownmsgid> Message-ID: Hi Dustin, Please follow the mailing list for xen-users as there's a 0.9.0 version of the drivers. The binary releases never need compilation. I guess you are missing a point here. The only possibility that you would need to compile is if you download the daily source code from the mercurial repository, but then even it's a trivial task as you just say "bld" in the root directory of the driver source code, after installing the latest WDK. Emre On Tue, May 20, 2008 at 5:54 PM, Dustin Henning wrote: > Apparently a James Harper in Australia has been working > on PV drivers for Windows on GPL Xen for some time. I don't know if this > link will work for others, but it looks like it should (though probably not > permanently): > > > http://markmail.org/search/?q=WindowsXenPV-0.8.9.zip#query:WindowsXenPV-0.8.9.zip+page:1+mid:gmf4kraasqdxxamm+state:facets > > I downloaded his latest work, WindowsXenPV-0.8.9.zip, but > apparently compilation is required. I know Windows drivers and programs > don't have to be different (on account of Windows) the way they do on Linux > (because of the many different distros), so I am not sure why compilation is > required unless it is somehow related to the version of Xen running on the > host system potentially offering up paravirtualization in a different way. > I am not sure on this because the directions are slightly vague and if I > read them properly, source code for the version of Xen in question is not > mentioned. Anyway, I am curious as to whether or not anyone can point me > toward a these drivers in an already compiled state. I don't know if they > would be included in any certain repository of which I am unaware or whether > it is more likely that they simply don't exist (yet). As I am running F7, I > am also curious as to whether or not Fedora's custom Xen kernels would even > support the PV capabilities on HVMs. I say on HVMs because it is my > understanding that the Windows machine decides which drivers to load (and > which devices to detect) based on a boot switch in the VM OS and I haven't > seen anything indicating a separate Xen setup for full PV. > > I ask because I would love to download binary drivers and > have a go at this, but actually building it all is a bit more complicated > and time consuming for me (especially if I'm re-inventing the wheel), as > I've never compiled anything in Windows and don't have any of the necessary > software readily available (free to download, but I don't have any seriously > high speed access). I also don't know whether it is possible that the > Fedora team (or any third party) would have any interest in compiling these > drivers or making them available even if someone else did the work since > they are for Windows and would certainly require manual installation after > download/(yum) "install". It would be possible (though far from automated) > to mount the VM partition and copy the directory tree to it, so downloading > them directly to the Dom0 doesn't seem like a problem to me, but downloading > them on the DomU would work as well if they were available some other way. > I would love to find out that the version of Xen doesn't matter for PV > drivers (beyond being above 3.0 or whatever), that the Fedora version is > standard in regards to PV, that a compiled version is available because of > that, and that one can download it from URL X as such, but I am rarely so > lucky. > > As an interesting aside, apparently the KVM project > includes a PV driver for Windows networking, but this (not necessarily > production ready) Xen GPLPV driver package includes not only networking, but > also block devices and a service to enable the xm shutdown and xm restart > commands. Anyway, I welcome all input. Thanks, > > Dustin > > -- > 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 erenoglu at gmail.com Tue May 20 16:38:09 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Tue, 20 May 2008 18:38:09 +0200 Subject: [Fedora-xen] HVM DomU on F9? In-Reply-To: <4832F752.7070300@qumranet.com> References: <4832F44F.5050308@qumranet.com> <4832F752.7070300@qumranet.com> Message-ID: Hi Dustin, I guest you to use F8 and Xen. Emre On Tue, May 20, 2008 at 6:07 PM, Avi Kivity wrote: > Dustin Henning wrote: > >> Great information, and straight from the source! Can you tell me >> on >> which version of KVM support for TPR was implemented? >> > > kvm-58 (see http://kvm.qumranet.com/kvmwiki/ChangeLog). F7's rpms were > stuck on kvm-36 IIRC. > > > > -- > error compiling committee.c: too many arguments to function > > -- > 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 erenoglu at gmail.com Tue May 20 16:38:35 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Tue, 20 May 2008 18:38:35 +0200 Subject: [Fedora-xen] HVM DomU on F9? In-Reply-To: References: <4832F44F.5050308@qumranet.com> <4832F752.7070300@qumranet.com> Message-ID: Forgot to say, F8 also has good KVM support, so you can try that also... Emre On Tue, May 20, 2008 at 6:38 PM, Emre ERENOGLU wrote: > Hi Dustin, I guest you to use F8 and Xen. > > Emre > > > On Tue, May 20, 2008 at 6:07 PM, Avi Kivity wrote: > >> Dustin Henning wrote: >> >>> Great information, and straight from the source! Can you tell me >>> on >>> which version of KVM support for TPR was implemented? >>> >> >> kvm-58 (see http://kvm.qumranet.com/kvmwiki/ChangeLog). F7's rpms were >> stuck on kvm-36 IIRC. >> >> >> >> -- >> error compiling committee.c: too many arguments to function >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> > > > > -- > Emre Erenoglu > erenoglu at gmail.com -- Emre Erenoglu erenoglu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dustin.Henning at prd-inc.com Wed May 21 15:48:34 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 21 May 2008 11:48:34 -0400 Subject: [Fedora-xen] Paravirtual Windows Driver Binaries? In-Reply-To: References: <-4118396398988483182@unknownmsgid> Message-ID: <002401c8bb5a$20f4bd20$62de3760$@Henning@prd-inc.com> You?re right. I was confused. The Install.txt in the 0.89 version tells how to lay out the file structure, but the structure isn?t like that for the binary version, because the install.bat moves files around, so the EXE and DLL I was missing were actually just in another location. The 0.90 version is apparently WDM instead of WDF, and the install documents are now supposed to be in the XenWiki, but apparently aren't completed yet. I am going to see what I can figure out. Thanks, Dustin From: Emre ERENOGLU [mailto:erenoglu at gmail.com] Sent: Tuesday, May 20, 2008 12:37 To: Dustin.Henning at prd-inc.com Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Paravirtual Windows Driver Binaries? Hi Dustin, Please follow the mailing list for xen-users as there's a 0.9.0 version of the drivers. The binary releases never need compilation. I guess you are missing a point here. The only possibility that you would need to compile is if you download the daily source code from the mercurial repository, but then even it's a trivial task as you just say "bld" in the root directory of the driver source code, after installing the latest WDK. Emre On Tue, May 20, 2008 at 5:54 PM, Dustin Henning wrote: ??????????????? Apparently a James Harper in Australia has been working on PV drivers for Windows on GPL Xen for some time.? I don't know if this link will work for others, but it looks like it should (though probably not permanently): http://markmail.org/search/?q=WindowsXenPV-0.8.9.zip#query:WindowsXenPV-0.8. 9.zip+page:1+mid:gmf4kraasqdxxamm+state:facets ??????????????? I downloaded his latest work, WindowsXenPV-0.8.9.zip, but apparently compilation is required.? I know Windows drivers and programs don't have to be different (on account of Windows) the way they do on Linux (because of the many different distros), so I am not sure why compilation is required unless it is somehow related to the version of Xen running on the host system potentially offering up paravirtualization in a different way.? I am not sure on this because the directions are slightly vague and if I read them properly, source code for the version of Xen in question is not mentioned.? Anyway, I am curious as to whether or not anyone can point me toward a these drivers in an already compiled state.? I don't know if they would be included in any certain repository of which I am unaware or whether it is more likely that they simply don't exist (yet).? As I am running F7, I am also curious as to whether or not Fedora's custom Xen kernels would even support the PV capabilities on HVMs.? I say on HVMs because it is my understanding that the Windows machine decides which drivers to load (and which devices to detect) based on a boot switch in the VM OS and I haven't seen anything indicating a separate Xen setup for full PV. ??????????????? I ask because I would love to download binary drivers and have a go at this, but actually building it all is a bit more complicated and time consuming for me (especially if I'm re-inventing the wheel), as I've never compiled anything in Windows and don't have any of the necessary software readily available (free to download, but I don't have any seriously high speed access).? I also don't know whether it is possible that the Fedora team (or any third party) would have any interest in compiling these drivers or making them available even if someone else did the work since they are for Windows and would certainly require manual installation after download/(yum) "install".? It would be possible (though far from automated) to mount the VM partition and copy the directory tree to it, so downloading them directly to the Dom0 doesn't seem like a problem to me, but downloading them on the DomU would work as well if they were available some other way.? I would love to find out that the version of Xen doesn't matter for PV drivers (beyond being above 3.0 or whatever), that the Fedora version is standard in regards to PV, that a compiled version is available because of that, and that one can download it from URL X as such, but I am rarely so lucky. ??????????????? As an interesting aside, apparently the KVM project includes a PV driver for Windows networking, but this (not necessarily production ready) Xen GPLPV driver package includes not only networking, but also block devices and a service to enable the xm shutdown and xm restart commands.? Anyway, I welcome all input.? Thanks, ??????????????? Dustin -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Emre Erenoglu erenoglu at gmail.com From Dustin.Henning at prd-inc.com Wed May 21 15:58:56 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 21 May 2008 11:58:56 -0400 Subject: [Fedora-xen] HVM DomU on F9? References: <4832F44F.5050308@qumranet.com> <4832F752.7070300@qumranet.com> Message-ID: <002e01c8bb5b$930e8700$b92b9500$@Henning@prd-inc.com> That is probably what I will do, but Fedora has a short lifecycle, so I thought 9 would be OK if it worked. I am also considering CentOS 5.1, but CentOS 5.0 didn?t work on my hardware, so I don?t know that I?ll have any luck there. Any reason that would cause me grief (short of there not being a CentOS-Xen mailing list)? Thanks, Dustin From: Emre ERENOGLU [mailto:erenoglu at gmail.com] Sent: Tuesday, May 20, 2008 12:38 To: Avi Kivity Cc: Dustin.Henning at prd-inc.com; fedora-xen at redhat.com Subject: Re: [Fedora-xen] HVM DomU on F9? Hi Dustin, I guest you to use F8 and Xen. Emre On Tue, May 20, 2008 at 6:07 PM, Avi Kivity wrote: Dustin Henning wrote: ? ? ? ?Great information, and straight from the source! ?Can you tell me on which version of KVM support for TPR was implemented? ? kvm-58 (see http://kvm.qumranet.com/kvmwiki/ChangeLog). ?F7's rpms were stuck on kvm-36 IIRC. -- error compiling committee.c: too many arguments to function -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Emre Erenoglu erenoglu at gmail.com From Dustin.Henning at prd-inc.com Fri May 23 21:20:25 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 23 May 2008 17:20:25 -0400 Subject: [Fedora-xen] configure: error: GRUB requires a working absolute objcopy; upgrade your binutils Message-ID: I hope this isn't off topic since the bug I am trying to resolve only affects the xen kernel... I am trying to compile grub on Fedora 8 because I need to apply the patch for bug 250299. First, I downloaded and installed http://mirrors.kernel.org/fedora/releases/8/Fedora/source/SRPMS/grub-0.97-19.src.rpm Next, I extracted the included grub-0.97.tar.gz to /usr/src/ At this point, if I run configure, I will get the error mentioned in the subject, as follows: [CODE]checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for gcc... (cached) gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking dependency style of gcc... (cached) gcc3 checking for ranlib... ranlib checking whether optimization for size works... yes checking whether gcc has -fno-stack-protector... yes checking whether -Wundef works... yes checking whether -falign-loops works... yes checking for objcopy... objcopy checking if C symbols get an underscore after compilation... no checking whether objcopy works for absolute addresses... no configure: error: GRUB requires a working absolute objcopy; upgrade your binutils[/CODE] However, I am running binutils 2.17.50.0.18 which is the latest in the fedora repo, so I cannot upgrade, and I do not know how to downgrade. I saw another issue where this same error was happening, and someone suggested downloading ftp://alpha.gnu.org/gnu/grub/grub-0.97.tar.gz and using it. I tried this and determined that that is the exact file included in the srpm I had downloaded, and the error still surfaces when I try it. Additionally, if I apply the included grub-fedora-8.patch, the configure file disappears. I can get it from the tar again, but I will still get the same error, so while I need to know how I am supposed to compile after applying that patch (which I apply before the patch for the aforementioned bug), but that point is moot until I can determine how to fix this binutils issue. -------------- next part -------------- An HTML attachment was scrubbed... URL: From avg at icyb.net.ua Mon May 26 12:27:32 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon, 26 May 2008 15:27:32 +0300 Subject: [Fedora-xen] fedora 9 guest kernel panic Message-ID: <483AACB4.6030908@icyb.net.ua> We have FC6 Dom0 and recently upgraded one of DomUs to Fedora 9. After that we started to get seemingly random panics for that DomU. Below is some info about that. Any ideas of what might be wrong? Any suggestions on fixing? Kernel BUG at ffffffff80465fc0 [verbose debug info unavailable] invalid opcode: 0000 [1] CPU 0 Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss exportfs autofs4 fuse sunrpc ipv6 dm_multipath pcspkr xen_netfront dm_snapshot dm_zero dm_mirror dm_mod xen_blkfront ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd Pid: 1353, comm: automount Not tainted 2.6.25-2.fc9.x86_64.xen #1 RIP: e030:[] [] xen_failsafe_callback+0x0/0x10 RSP: e02b:ffff880007375e00 EFLAGS: 00010012 RAX: 000000000000000d RBX: ffff88000a9c2000 RCX: ffffffff80465fc0 RDX: ffffffff80627210 RSI: 0000000000000001 RDI: ffffffff80627350 RBP: ffff880007375ea0 R08: ffffffff8063d730 R09: 0000000000000000 R10: 0000003401024b21 R11: 0000000000000212 R12: ffff88001f442000 R13: ffff88000a9c2470 R14: 0000000000000000 R15: ffff88001f429c78 FS: 0000000000000000(0000) GS:ffffffff805bf000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00007f9409bd1780 CR3: 000000001dd9e000 CR4: 0000000000000660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000000 Process automount (pid: 1353, threadinfo ffff88001f428000, task ffff88001f442000) Stack: ffffffff806171aa 0000000000000212 0000000000000000 0000000000000000 0000000000000063 0000000000000000 ffffffff806171a8 000000010000e030 0000000000000012 ffff880007375e58 000000000000e02b 0000000000000000 Call Trace: Code: 0f 07 66 0f 1f 84 00 00 00 00 00 48 8b 0c 24 4c 8b 5c 24 08 48 83 c4 10 6a 00 50 48 8d 05 19 00 00 00 e9 54 fb ff ff 0f 1f 40 00 <0f> 0b 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 fc 65 ff RIP [] xen_failsafe_callback+0x0/0x10 RSP ---[ end trace ffae49894bdd5d90 ]--- BUG: soft lockup - CPU#0 stuck for 61s! [automount:1353] CPU 0: Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss exportfs autofs4 fuse sunrpc ipv6 dm_multipath pcspkr xen_netfront dm_snapshot dm_zero dm_mirror dm_mod xen_blkfront ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd Pid: 1353, comm: automount Tainted: G D 2.6.25-2.fc9.x86_64.xen #1 RIP: e030:[] [] __get_user_8+0x20/0x2c RSP: e02b:ffff880007375b50 EFLAGS: 00010206 RAX: ffffffffff516000 RBX: 0000000000000000 RCX: 000000004054e9f0 RDX: 0000000000002600 RSI: 0000000000000000 RDI: ffff88001f442000 RBP: ffff880007375ba8 R08: ffff88001f428000 R09: ffff880001760300 R10: 0000000000000006 R11: 3462646435643930 R12: ffff88001f442000 R13: 000000004054e9f0 R14: 0000000000000000 R15: ffff88001f442000 FS: 0000000000000000(0000) GS:ffffffff805bf000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 000000004054e9f0 CR3: 000000001dd9e000 CR4: 0000000000000660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000000 -- Andriy Gapon From markmc at redhat.com Mon May 26 15:36:58 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 26 May 2008 16:36:58 +0100 Subject: [Fedora-xen] fedora 9 guest kernel panic In-Reply-To: <483AACB4.6030908@icyb.net.ua> References: <483AACB4.6030908@icyb.net.ua> Message-ID: <1211816218.26257.1.camel@muff> Hi, On Mon, 2008-05-26 at 15:27 +0300, Andriy Gapon wrote: > We have FC6 Dom0 and recently upgraded one of DomUs to Fedora 9. > After that we started to get seemingly random panics for that DomU. ... > Code: 0f 07 66 0f 1f 84 00 00 00 00 00 48 8b 0c 24 4c 8b 5c 24 08 48 83 > c4 10 6a 00 50 48 8d 05 19 00 00 00 e9 54 fb ff ff 0f 1f 40 00 <0f> 0b > 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 fc 65 ff > RIP [] xen_failsafe_callback+0x0/0x10 See: https://bugzilla.redhat.com/show_bug.cgi?id=442949 Try updating to kernel-xen-2.6-2.6.25.3-1: https://admin.fedoraproject.org/updates/F9/FEDORA-2008-3980 Cheers, Mark. From gastonkeller at gmail.com Tue May 27 19:36:29 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Tue, 27 May 2008 15:36:29 -0400 Subject: [Fedora-xen] Cannot erase unsuccessfully created guests Message-ID: Hello, list. I've been playing with Xen lately and it was only until yesterday that I could successfully create a guest with Fedora 8 installed on it (the one with name _cero_). The problem is that all the previous attempts have generated _records_ that I cannot erase. The following is from the terminal: [root at alfa11 gkeller2]# virsh list Id Name State ---------------------------------- 0 Domain-0 running 10 cero blocked [root at alfa11 gkeller2]# /usr/sbin/xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1237 2 r----- 3085.3 cero 10 256 1 -b---- 728.5 fedora0 256 1 0.0 guest0 256 1 0.0 vm0 512 1 0.0 xen0 512 1 0.0 zero 256 1 0.0 [root at alfa11 gkeller2]# virsh destroy xen0 error: Failed to destroy domain xen0 [root at alfa11 gkeller2]# /usr/sbin/xm destroy xen0 [root at alfa11 gkeller2]# /usr/sbin/xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1237 2 r----- 3086.2 cero 10 256 1 -b---- 728.6 fedora0 256 1 0.0 guest0 256 1 0.0 vm0 512 1 0.0 xen0 512 1 0.0 zero 256 1 0.0 [root at alfa11 gkeller2]# It seems virsh doesn't detect those records, but xm does. Also, virsh cannot destroy them (what makes sense if it cannot see them), neither can xm. My problem is that, as far as I know, those _records_ of failed guest have memory assigned from dom0 and they affect the creation of new guests. Any suggestions? Thank you in advance, Gaston -- La ?nica verdad es la realidad. From marceldamasio at gmail.com Tue May 27 19:45:38 2008 From: marceldamasio at gmail.com (=?ISO-8859-1?Q?Marcel_Dam=E1sio?=) Date: Tue, 27 May 2008 16:45:38 -0300 Subject: [Fedora-xen] Cannot erase unsuccessfully created guests In-Reply-To: References: Message-ID: <386f83ad0805271245m6202dfc5ke42dd93168d4a273@mail.gmail.com> Hi Gast?n, First, these 512 of mem are just reserved to xen0 if when it starts. So, you don't have this memory problem. And the option 'xm destroy' is just to shutdown a cracked VM (I'm almost sure). To erase the VM you need to do 'xm delete'. Hope I helped. On Tue, May 27, 2008 at 4:36 PM, Gast?n Keller wrote: > Hello, list. I've been playing with Xen lately and it was only until > yesterday that I could successfully create a guest with Fedora 8 > installed on it (the one with name _cero_). The problem is that all > the previous attempts have generated _records_ that I cannot erase. > The following is from the terminal: > > [root at alfa11 gkeller2]# virsh list > Id Name State > ---------------------------------- > 0 Domain-0 running > 10 cero blocked > > [root at alfa11 gkeller2]# /usr/sbin/xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1237 2 r----- > 3085.3 > cero 10 256 1 -b---- > 728.5 > fedora0 256 1 > 0.0 > guest0 256 1 > 0.0 > vm0 512 1 > 0.0 > xen0 512 1 > 0.0 > zero 256 1 > 0.0 > [root at alfa11 gkeller2]# virsh destroy xen0 > error: Failed to destroy domain xen0 > > [root at alfa11 gkeller2]# /usr/sbin/xm destroy xen0 > [root at alfa11 gkeller2]# /usr/sbin/xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1237 2 r----- > 3086.2 > cero 10 256 1 -b---- > 728.6 > fedora0 256 1 > 0.0 > guest0 256 1 > 0.0 > vm0 512 1 > 0.0 > xen0 512 1 > 0.0 > zero 256 1 > 0.0 > [root at alfa11 gkeller2]# > > It seems virsh doesn't detect those records, but xm does. Also, virsh > cannot destroy them (what makes sense if it cannot see them), neither > can xm. > > My problem is that, as far as I know, those _records_ of failed guest > have memory assigned from dom0 and they affect the creation of new > guests. > > Any suggestions? > > Thank you in advance, > Gaston > > -- > La ?nica verdad es la realidad. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7106 Estagi?rio do NPD - UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From gastonkeller at gmail.com Tue May 27 20:46:16 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Tue, 27 May 2008 16:46:16 -0400 Subject: [Fedora-xen] Cannot erase unsuccessfully created guests In-Reply-To: <386f83ad0805271245m6202dfc5ke42dd93168d4a273@mail.gmail.com> References: <386f83ad0805271245m6202dfc5ke42dd93168d4a273@mail.gmail.com> Message-ID: On Tue, May 27, 2008 at 3:45 PM, Marcel Dam?sio wrote: > Hi Gast?n, > > First, these 512 of mem are just reserved to xen0 if when it starts. So, you > don't have this memory problem. I considered there was a problem because when I just created dom0, it's assigned memory was around 2000. Later on, each time I created (or tried to create) a new guest, the amount of memory assigned to dom0 was being reduced. Now, I have used the command _xm_delete_ with each of the guest without id and they were effectively removed. My only concern now is that the amount of memory of dom0 hasn't augmented accordingly. Am I misunderstanding something? > > And the option 'xm destroy' is just to shutdown a cracked VM (I'm almost > sure). > To erase the VM you need to do 'xm delete'. Thanks for this. I didn't know of the existence of that command. As far as I can tell, it is not documented in the manual pages (accessed from the terminal). Thanks again, Gaston > > Hope I helped. > > On Tue, May 27, 2008 at 4:36 PM, Gast?n Keller > wrote: >> >> Hello, list. I've been playing with Xen lately and it was only until >> yesterday that I could successfully create a guest with Fedora 8 >> installed on it (the one with name _cero_). The problem is that all >> the previous attempts have generated _records_ that I cannot erase. >> The following is from the terminal: >> >> [root at alfa11 gkeller2]# virsh list >> Id Name State >> ---------------------------------- >> 0 Domain-0 running >> 10 cero blocked >> >> [root at alfa11 gkeller2]# /usr/sbin/xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 1237 2 r----- >> 3085.3 >> cero 10 256 1 -b---- >> 728.5 >> fedora0 256 1 >> 0.0 >> guest0 256 1 >> 0.0 >> vm0 512 1 >> 0.0 >> xen0 512 1 >> 0.0 >> zero 256 1 >> 0.0 >> [root at alfa11 gkeller2]# virsh destroy xen0 >> error: Failed to destroy domain xen0 >> >> [root at alfa11 gkeller2]# /usr/sbin/xm destroy xen0 >> [root at alfa11 gkeller2]# /usr/sbin/xm list >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 1237 2 r----- >> 3086.2 >> cero 10 256 1 -b---- >> 728.6 >> fedora0 256 1 >> 0.0 >> guest0 256 1 >> 0.0 >> vm0 512 1 >> 0.0 >> xen0 512 1 >> 0.0 >> zero 256 1 >> 0.0 >> [root at alfa11 gkeller2]# >> >> It seems virsh doesn't detect those records, but xm does. Also, virsh >> cannot destroy them (what makes sense if it cannot see them), neither >> can xm. >> >> My problem is that, as far as I know, those _records_ of failed guest >> have memory assigned from dom0 and they affect the creation of new >> guests. >> >> Any suggestions? >> >> Thank you in advance, >> Gaston >> >> -- >> La ?nica verdad es la realidad. >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen > > > > -- > Marcel Dam?sio Moreira > 9? per?odo de Ci?ncia da Computa??o - UFES > (27) 8128-7106 > Estagi?rio do NPD - UFES -- La ?nica verdad es la realidad. From m3freak at thesandhufamily.ca Wed May 28 02:03:31 2008 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Tue, 27 May 2008 22:03:31 -0400 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080514185359.GO15783@redhat.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> Message-ID: <1211940211.29610.6.camel@krs.systemsaligned.com> On Wed, 2008-05-14 at 19:53 +0100, Daniel P. Berrange wrote: > Sadly that's life with Xen. Upstream Xen has basically stopped all kernel > development leaving 'official' Xen kernels stuck on 2.6.28 which is > essentially useless for any modern distro. We had the choice between trying > to finish off the paravirt_ops port, or dropping Xen entirely :-( What's this? Xen kernel development has stopped? What does that mean - is the GPL project dead? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.22.14-72.fc6 i686 GNU/Linux 22:02:27 up 31 days, 15:57, 2 users, load average: 1.03, 0.85, 0.84 From avg at icyb.net.ua Mon May 26 17:41:14 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon, 26 May 2008 20:41:14 +0300 Subject: [Fedora-xen] fedora 9 guest kernel panic In-Reply-To: <1211816218.26257.1.camel@muff> References: <483AACB4.6030908@icyb.net.ua> <1211816218.26257.1.camel@muff> Message-ID: <483AF63A.2060508@icyb.net.ua> on 26/05/2008 18:36 Mark McLoughlin said the following: > Hi, > > On Mon, 2008-05-26 at 15:27 +0300, Andriy Gapon wrote: >> We have FC6 Dom0 and recently upgraded one of DomUs to Fedora 9. >> After that we started to get seemingly random panics for that DomU. > ... >> Code: 0f 07 66 0f 1f 84 00 00 00 00 00 48 8b 0c 24 4c 8b 5c 24 08 48 83 >> c4 10 6a 00 50 48 8d 05 19 00 00 00 e9 54 fb ff ff 0f 1f 40 00 <0f> 0b >> 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 fc 65 ff >> RIP [] xen_failsafe_callback+0x0/0x10 > > See: > > https://bugzilla.redhat.com/show_bug.cgi?id=442949 > > Try updating to kernel-xen-2.6-2.6.25.3-1: > > https://admin.fedoraproject.org/updates/F9/FEDORA-2008-3980 Thank you very much! I have not seen any panics after the upgrade. I've been running for 3+ hours by now. Previously the system would panic within first 15 minutes after boot up. -- Andriy Gapon From jeremy at goop.org Wed May 28 10:32:12 2008 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Wed, 28 May 2008 11:32:12 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <1211940211.29610.6.camel@krs.systemsaligned.com> References: <70f41ba20805131608v2c086225gf549064d22bd37eb@mail.gmail.com> <20080513232131.GB8844@redhat.com> <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> Message-ID: <483D34AC.509@goop.org> Kanwar Ranbir Sandhu wrote: > On Wed, 2008-05-14 at 19:53 +0100, Daniel P. Berrange wrote: > >> Sadly that's life with Xen. Upstream Xen has basically stopped all kernel >> development leaving 'official' Xen kernels stuck on 2.6.28 which is >> essentially useless for any modern distro. We had the choice between trying >> to finish off the paravirt_ops port, or dropping Xen entirely :-( >> > > What's this? Xen kernel development has stopped? What does that mean - > is the GPL project dead? Not at all. In fact, I'd strongly disagree with Daniel's characterisation that Xen has "stopped all kernel development" Redhat need to "finish off" the paravirt_ops port. I've been working on it full time for the last couple of years, and have done the vast majority of the work needed to get paravirt_ops working. Redhat have contributed valuable work in areas like the paravirtual framebuffer device, and are working on 64-bit and dom0 support. But all of that is based on the work I've been doing on paravirt-ops infrastructure itself and the Xen implementation which uses it. I'm still actively working on pvops/Xen, and currently focusing on bringing it up to feature parity with the old 2.6.18-xen patches. In the last few weeks I've implemented balloon support, save/restore and starting work on pv-hvm driver support. Meanwhile, open source Xen is also being actively developed by the original Xen developers and anyone who wishes to contribute. J From invitation at refriendz.com Wed May 28 11:55:26 2008 From: invitation at refriendz.com (Sameer Gupta) Date: Wed, 28 May 2008 06:55:26 -0500 Subject: [Fedora-xen] I am now on Refriendz! Message-ID: <1b4b35ef04c71c297fba8423aa936fbf@www.refriendz.com> Hi! I would like to invite you to visit my Refriendz page and see my latest photos. In order to visit my space, you must go to: http://www.refriendz.com/?do=Login.Invite&rid=sam9823444029&email=fedora-xen at redhat.com (If this link does not work, please copy and paste it into your browser or go to www.refriendz.com and enter 'sam9823444029' as Invitation ID to Login to the web site.) P.S. Refriendz is Invitation-Only, so do not miss your chance to visit my page! Cheers! Sameer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Unsubscribe: to opt out of ALL future emails from Refriendz, visit: http://www.refriendz.com/?do=Login.RemoveEntry&email=fedora-xen at redhat.com Please do not reply directly to this email. This mailbox is not monitored and you will not receive a response. Refriendz Limited, PO BOX 1184, Luton, Bedfordshire, LU1 9AT, UK. From pasik at iki.fi Wed May 28 12:51:10 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 28 May 2008 15:51:10 +0300 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <483D34AC.509@goop.org> References: <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> Message-ID: <20080528125110.GE8042@edu.joroinen.fi> On Wed, May 28, 2008 at 11:32:12AM +0100, Jeremy Fitzhardinge wrote: > Kanwar Ranbir Sandhu wrote: > >On Wed, 2008-05-14 at 19:53 +0100, Daniel P. Berrange wrote: > > > >>Sadly that's life with Xen. Upstream Xen has basically stopped all > >>kernel development leaving 'official' Xen kernels stuck on 2.6.28 which is > >>essentially useless for any modern distro. We had the choice between > >>trying > >>to finish off the paravirt_ops port, or dropping Xen entirely :-( > >> > > > >What's this? Xen kernel development has stopped? What does that mean - > >is the GPL project dead? > > Not at all. > > In fact, I'd strongly disagree with Daniel's characterisation that Xen > has "stopped all kernel development" Redhat need to "finish off" the > paravirt_ops port. I've been working on it full time for the last > couple of years, and have done the vast majority of the work needed to > get paravirt_ops working. > > Redhat have contributed valuable work in areas like the paravirtual > framebuffer device, and are working on 64-bit and dom0 support. But all > of that is based on the work I've been doing on paravirt-ops > infrastructure itself and the Xen implementation which uses it. > Which reminds me that would be really nice to get a binary rpm for kernel-xen with dom0 patches in it to try it and start reporting bugs.. :) > I'm still actively working on pvops/Xen, and currently focusing on > bringing it up to feature parity with the old 2.6.18-xen patches. In > the last few weeks I've implemented balloon support, save/restore and > starting work on pv-hvm driver support. > This is really excellent news! Thanks a lot for doing this work. Hopefully we'll see these features in rawhide/F10 kernel-xen soon :) -- Pasi From berrange at redhat.com Wed May 28 13:16:11 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 28 May 2008 14:16:11 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <483D34AC.509@goop.org> References: <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> Message-ID: <20080528131610.GA25313@redhat.com> On Wed, May 28, 2008 at 11:32:12AM +0100, Jeremy Fitzhardinge wrote: > Kanwar Ranbir Sandhu wrote: > >On Wed, 2008-05-14 at 19:53 +0100, Daniel P. Berrange wrote: > > > >>Sadly that's life with Xen. Upstream Xen has basically stopped all > >>kernel development leaving 'official' Xen kernels stuck on 2.6.28 which is > >>essentially useless for any modern distro. We had the choice between > >>trying > >>to finish off the paravirt_ops port, or dropping Xen entirely :-( > >> > > > >What's this? Xen kernel development has stopped? What does that mean - > >is the GPL project dead? > > Not at all. > > In fact, I'd strongly disagree with Daniel's characterisation that Xen > has "stopped all kernel development" Redhat need to "finish off" the > paravirt_ops port. I've been working on it full time for the last > couple of years, and have done the vast majority of the work needed to > get paravirt_ops working. When I said 'stopped all kernel development' I was referring to the original 'linux-xen-2.6' tree, which is what we've been shipping in Fedora until this point. Obviously paravirt_ops Xen development is still active & increasingly so. Regards, 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 berrange at redhat.com Wed May 28 13:25:05 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 28 May 2008 14:25:05 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080528125110.GE8042@edu.joroinen.fi> References: <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> <20080528125110.GE8042@edu.joroinen.fi> Message-ID: <20080528132505.GC25313@redhat.com> On Wed, May 28, 2008 at 03:51:10PM +0300, Pasi K?rkk?inen wrote: > On Wed, May 28, 2008 at 11:32:12AM +0100, Jeremy Fitzhardinge wrote: > > Kanwar Ranbir Sandhu wrote: > > >On Wed, 2008-05-14 at 19:53 +0100, Daniel P. Berrange wrote: > > > > > >>Sadly that's life with Xen. Upstream Xen has basically stopped all > > >>kernel development leaving 'official' Xen kernels stuck on 2.6.28 which is > > >>essentially useless for any modern distro. We had the choice between > > >>trying > > >>to finish off the paravirt_ops port, or dropping Xen entirely :-( > > >> > > > > > >What's this? Xen kernel development has stopped? What does that mean - > > >is the GPL project dead? > > > > Not at all. > > > > In fact, I'd strongly disagree with Daniel's characterisation that Xen > > has "stopped all kernel development" Redhat need to "finish off" the > > paravirt_ops port. I've been working on it full time for the last > > couple of years, and have done the vast majority of the work needed to > > get paravirt_ops working. > > > > Redhat have contributed valuable work in areas like the paravirtual > > framebuffer device, and are working on 64-bit and dom0 support. But all > > of that is based on the work I've been doing on paravirt-ops > > infrastructure itself and the Xen implementation which uses it. > > > > Which reminds me that would be really nice to get a binary rpm for kernel-xen > with dom0 patches in it to try it and start reporting bugs.. :) This is intended to go into rawhide sometime in the reasonably near future, now that the critical F9 kerne-xen bugs have mostly been ironed out. 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 Dustin.Henning at prd-inc.com Wed May 28 16:31:40 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 28 May 2008 12:31:40 -0400 Subject: [Fedora-xen] configure: error: GRUB requires a working absolute objcopy; upgrade your binutils In-Reply-To: References: Message-ID: <001701c8c0e0$4f0c69c0$ed253d40$@Henning@prd-inc.com> FYI, I was able to get grub built with only the memory patch by installing compat-gcc-34 (and compat-gcc-34-c++ for good measure), and feeding CC=gcc34 as a variable to configure. So apparently that was just a compatibility issue where F7 must use an older version of gcc. I still have no clue how to build after applying grub-fedora-8.patch, though. ____________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dustin Henning Sent: Friday, May 23, 2008 17:20 To: fedora-xen at redhat.com Subject: [Fedora-xen] configure: error: GRUB requires a working absolute objcopy; upgrade your binutils I hope this isn't off topic since the bug I am trying to resolve only affects the xen kernel... I am trying to compile grub on Fedora 8 because I need to apply the patch for bug 250299. First, I downloaded and installed http://mirrors.kernel.org/fedora/releases/8/Fedora/source/SRPMS/grub-0.97-19 .src.rpm Next, I extracted the included grub-0.97.tar.gz to /usr/src/ At this point, if I run configure, I will get the error mentioned in the subject, as follows: [CODE]checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for gcc... (cached) gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking dependency style of gcc... (cached) gcc3 checking for ranlib... ranlib checking whether optimization for size works... yes checking whether gcc has -fno-stack-protector... yes checking whether -Wundef works... yes checking whether -falign-loops works... yes checking for objcopy... objcopy checking if C symbols get an underscore after compilation... no checking whether objcopy works for absolute addresses... no configure: error: GRUB requires a working absolute objcopy; upgrade your binutils[/CODE] However, I am running binutils 2.17.50.0.18 which is the latest in the fedora repo, so I cannot upgrade, and I do not know how to downgrade. I saw another issue where this same error was happening, and someone suggested downloading ftp://alpha.gnu.org/gnu/grub/grub-0.97.tar.gz and using it. I tried this and determined that that is the exact file included in the srpm I had downloaded, and the error still surfaces when I try it. Additionally, if I apply the included grub-fedora-8.patch, the configure file disappears.? I can get it from the tar again, but I will still get the same error, so while I need to know how I am supposed to compile after applying that patch (which I apply before the patch for the aforementioned bug), but that point is moot until I can determine how to fix this binutils issue. ? From pasik at iki.fi Wed May 28 18:32:34 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 28 May 2008 21:32:34 +0300 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <483D34AC.509@goop.org> References: <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> Message-ID: <20080528183234.GH8042@edu.joroinen.fi> On Wed, May 28, 2008 at 11:32:12AM +0100, Jeremy Fitzhardinge wrote: > Kanwar Ranbir Sandhu wrote: > >On Wed, 2008-05-14 at 19:53 +0100, Daniel P. Berrange wrote: > > > >>Sadly that's life with Xen. Upstream Xen has basically stopped all > >>kernel development leaving 'official' Xen kernels stuck on 2.6.28 which is > >>essentially useless for any modern distro. We had the choice between > >>trying > >>to finish off the paravirt_ops port, or dropping Xen entirely :-( > >> > > > >What's this? Xen kernel development has stopped? What does that mean - > >is the GPL project dead? > > Not at all. > > In fact, I'd strongly disagree with Daniel's characterisation that Xen > has "stopped all kernel development" Redhat need to "finish off" the > paravirt_ops port. I've been working on it full time for the last > couple of years, and have done the vast majority of the work needed to > get paravirt_ops working. > > Redhat have contributed valuable work in areas like the paravirtual > framebuffer device, and are working on 64-bit and dom0 support. But all > of that is based on the work I've been doing on paravirt-ops > infrastructure itself and the Xen implementation which uses it. > > I'm still actively working on pvops/Xen, and currently focusing on > bringing it up to feature parity with the old 2.6.18-xen patches. In > the last few weeks I've implemented balloon support, save/restore and > starting work on pv-hvm driver support. > Btw is this work available in some repository? -- Pasi From pasik at iki.fi Thu May 29 07:33:24 2008 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 29 May 2008 10:33:24 +0300 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <483DBBC3.1030902@goop.org> References: <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> <20080528183234.GH8042@edu.joroinen.fi> <483DBBC3.1030902@goop.org> Message-ID: <20080529073324.GL8042@edu.joroinen.fi> On Wed, May 28, 2008 at 09:08:35PM +0100, Jeremy Fitzhardinge wrote: > Pasi K?rkk?inen wrote: > >Btw is this work available in some repository? > > > > It's in Ingo's x86 git tree. See > http://people.redhat.com/mingo/tip.git/README for details. > Ok. Thanks. Is it 2.6.27 stuff, or is it already in 2.6.26? -- Pasi From jeremy at goop.org Wed May 28 20:08:35 2008 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Wed, 28 May 2008 21:08:35 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080528183234.GH8042@edu.joroinen.fi> References: <70f41ba20805131631j1e31db4avad0747ca432fc16f@mail.gmail.com> <20080513234041.GC8844@redhat.com> <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> <20080528183234.GH8042@edu.joroinen.fi> Message-ID: <483DBBC3.1030902@goop.org> Pasi K?rkk?inen wrote: > Btw is this work available in some repository? > It's in Ingo's x86 git tree. See http://people.redhat.com/mingo/tip.git/README for details. J From jeremy at goop.org Thu May 29 08:03:16 2008 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Thu, 29 May 2008 09:03:16 +0100 Subject: [Fedora-xen] Is pci-pasthrough enabled for F9 DomU? In-Reply-To: <20080529073324.GL8042@edu.joroinen.fi> References: <70f41ba20805131655j7daa1831rb35bb095b9f404b1@mail.gmail.com> <20080514135400.GA18846@amd.home.annexia.org> <6b4bb8650805141129o6951cf68jaeb15a412411dc85@mail.gmail.com> <70f41ba20805141148l14d7bb5ey3d2e38c8bcdf1885@mail.gmail.com> <20080514185359.GO15783@redhat.com> <20080514185359.GO15783@redhat.com> <1211940211.29610.6.camel@krs.systemsaligned.com> <483D34AC.509@goop.org> <20080528183234.GH8042@edu.joroinen.fi> <483DBBC3.1030902@goop.org> <20080529073324.GL8042@edu.joroinen.fi> Message-ID: <483E6344.9040605@goop.org> Pasi K?rkk?inen wrote: > On Wed, May 28, 2008 at 09:08:35PM +0100, Jeremy Fitzhardinge wrote: > >> Pasi K?rkk?inen wrote: >> >>> Btw is this work available in some repository? >>> >>> >> It's in Ingo's x86 git tree. See >> http://people.redhat.com/mingo/tip.git/README for details. >> >> > > Ok. Thanks. > > Is it 2.6.27 stuff, or is it already in 2.6.26? Most of it is targeted for .27. Everything that's planned for .26 is already in Linus' tree. J From gastonkeller at gmail.com Thu May 29 19:22:33 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Thu, 29 May 2008 15:22:33 -0400 Subject: [Fedora-xen] Xen Documentation Message-ID: Hello, everybody. I have been struggling with Xen's documentation lately, not finding where to look for accurate and up-to-date info. I remember having read in this list months ago someone saying that the documentation was quite outdated. For example, the xm command _delete_ does not appear in the man pages and many guides still do reference to the guest's config files being stored at /etc/xen (two days ago I discovered that now Xen works in a different way). My objective is not only to learn how to use Xen, but understand how it works. I'm doing my best looking for info in the net and going through docs in the Xen Wiki, but I might be missing something in my search. Therefore, I would really appreciate if someone could point me to some documentation I should read, or whatever else you could think of. Thanks, Gaston -- La ?nica verdad es la realidad. From erenoglu at gmail.com Thu May 29 23:53:13 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Fri, 30 May 2008 01:53:13 +0200 Subject: [Fedora-xen] Xen Documentation In-Reply-To: References: Message-ID: Hi Gaston, It's true that some documentation is outdated. However, for the "/etc/xen" isssue, my custom Xen 3.2 setup still stores ( and I do store there also) my config files there. Maybe what you're saying is "Fedora Specific" which I could understand as it's fedora mailing list. However, I never found the flexibility and control in the Fedora way of Xen implementation (all those xml stuff etc.). most probably, I'm wrong :) Emre On Thu, May 29, 2008 at 9:22 PM, Gast?n Keller wrote: > Hello, everybody. I have been struggling with Xen's documentation > lately, not finding where to look for accurate and up-to-date info. I > remember having read in this list months ago someone saying that the > documentation was quite outdated. For example, the xm command _delete_ > does not appear in the man pages and many guides still do reference to > the guest's config files being stored at /etc/xen (two days ago I > discovered that now Xen works in a different way). > > My objective is not only to learn how to use Xen, but understand how > it works. I'm doing my best looking for info in the net and going > through docs in the Xen Wiki, but I might be missing something in my > search. Therefore, I would really appreciate if someone could point me > to some documentation I should read, or whatever else you could think > of. > > Thanks, > Gaston > > -- > La ?nica verdad es la realidad. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From gastonkeller at gmail.com Fri May 30 00:06:32 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Thu, 29 May 2008 20:06:32 -0400 Subject: [Fedora-xen] Xen Documentation In-Reply-To: References: Message-ID: On Thu, May 29, 2008 at 7:53 PM, Emre ERENOGLU wrote: > Hi Gaston, > > It's true that some documentation is outdated. However, for the "/etc/xen" > isssue, my custom Xen 3.2 setup still stores ( and I do store there also) my > config files there. > > Maybe what you're saying is "Fedora Specific" which I could understand as > it's fedora mailing list. _The Fedora team has followed the Xensource model and begun to store all VM configuration details in a database, referred to as xenstore._ Source: http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ Then, you might be right. I interpreted it was a modification from Xen, not from Fedora (previously introduced by Xensource). So, what is the advantage behind this movement? Thanks, Gaston However, I never found the flexibility and control > in the Fedora way of Xen implementation (all those xml stuff etc.). most > probably, I'm wrong :) > > Emre > > On Thu, May 29, 2008 at 9:22 PM, Gast?n Keller > wrote: >> >> Hello, everybody. I have been struggling with Xen's documentation >> lately, not finding where to look for accurate and up-to-date info. I >> remember having read in this list months ago someone saying that the >> documentation was quite outdated. For example, the xm command _delete_ >> does not appear in the man pages and many guides still do reference to >> the guest's config files being stored at /etc/xen (two days ago I >> discovered that now Xen works in a different way). >> >> My objective is not only to learn how to use Xen, but understand how >> it works. I'm doing my best looking for info in the net and going >> through docs in the Xen Wiki, but I might be missing something in my >> search. Therefore, I would really appreciate if someone could point me >> to some documentation I should read, or whatever else you could think >> of. >> >> Thanks, >> Gaston >> >> -- >> La ?nica verdad es la realidad. >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen > > > > -- > Emre -- La ?nica verdad es la realidad. From erenoglu at gmail.com Fri May 30 08:29:52 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Fri, 30 May 2008 10:29:52 +0200 Subject: [Fedora-xen] Xen Documentation In-Reply-To: References: Message-ID: Hmm, On Fri, May 30, 2008 at 2:06 AM, Gast?n Keller wrote: > On Thu, May 29, 2008 at 7:53 PM, Emre ERENOGLU wrote: > > Hi Gaston, > > > > It's true that some documentation is outdated. However, for the > "/etc/xen" > > isssue, my custom Xen 3.2 setup still stores ( and I do store there also) > my > > config files there. > > > > Maybe what you're saying is "Fedora Specific" which I could understand as > > it's fedora mailing list. > > _The Fedora team has followed the Xensource model and begun to store > all VM configuration details in a database, referred to as xenstore._ > Source: > http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ > OK, I didn't know that. However, I find this xenstore thing a bit complicated. > Then, you might be right. I interpreted it was a modification from > Xen, not from Fedora (previously introduced by Xensource). > So, what is the advantage behind this movement? I think it's managegability. > > Thanks, > Gaston > > However, I never found the flexibility and control > > in the Fedora way of Xen implementation (all those xml stuff etc.). most > > probably, I'm wrong :) > > > > Emre > > > > On Thu, May 29, 2008 at 9:22 PM, Gast?n Keller > > wrote: > >> > >> Hello, everybody. I have been struggling with Xen's documentation > >> lately, not finding where to look for accurate and up-to-date info. I > >> remember having read in this list months ago someone saying that the > >> documentation was quite outdated. For example, the xm command _delete_ > >> does not appear in the man pages and many guides still do reference to > >> the guest's config files being stored at /etc/xen (two days ago I > >> discovered that now Xen works in a different way). > >> > >> My objective is not only to learn how to use Xen, but understand how > >> it works. I'm doing my best looking for info in the net and going > >> through docs in the Xen Wiki, but I might be missing something in my > >> search. Therefore, I would really appreciate if someone could point me > >> to some documentation I should read, or whatever else you could think > >> of. > >> > >> Thanks, > >> Gaston > >> > >> -- > >> La ?nica verdad es la realidad. > >> > >> -- > >> Fedora-xen mailing list > >> Fedora-xen at redhat.com > >> https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > -- > > Emre > > > > -- > La ?nica verdad es la realidad. > -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dustin.Henning at prd-inc.com Fri May 30 12:12:59 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 30 May 2008 08:12:59 -0400 Subject: [Fedora-xen] Xen Documentation In-Reply-To: References: Message-ID: <003701c8c24e$80445a60$80cd0f20$@Henning@prd-inc.com> Emre, As you may already know, I still use the config files in /etc/xen and don?t mess with the virsh stuff. It all certainly worked fine in F7, and though I haven?t fully tested, it appears that it all works fine in F8 as well. I use them for one, because I learned with them, and for two, because in the little time I have spent messing with the gui tools, I haven't found near as much control. That isn't to say that more can be done with the old way, but instead to say that I can do more with the old way. I don?t know if there are any plans to deprecate that stuff, but I hope that if there ever are, news makes the list before I end up on a version where I have no clue how to do anything! Dustin From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Emre ERENOGLU Sent: Friday, May 30, 2008 04:30 To: Gast?n Keller Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Xen Documentation Hmm, On Fri, May 30, 2008 at 2:06 AM, Gast?n Keller wrote: On Thu, May 29, 2008 at 7:53 PM, Emre ERENOGLU wrote: > Hi Gaston, > > It's true that some documentation is outdated. However, for the "/etc/xen" > isssue, my custom Xen 3.2 setup still stores ( and I do store there also) my > config files there. > > Maybe what you're saying is "Fedora Specific" which I could understand as > it's fedora mailing list. _The Fedora team has followed the Xensource model and begun to store all VM configuration details in a database, referred to as xenstore._ Source: http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ OK, I didn't know that. However, I find this xenstore thing a bit complicated. Then, you might be right. I interpreted it was a modification from Xen, not from Fedora (previously introduced by Xensource). So, what is the advantage behind this movement? I think it's managegability. Thanks, Gaston However, I never found the flexibility and control > in the Fedora way of Xen implementation (all those xml stuff etc.). most > probably, I'm wrong :) > > Emre > > On Thu, May 29, 2008 at 9:22 PM, Gast?n Keller > wrote: >> >> Hello, everybody. I have been struggling with Xen's documentation >> lately, not finding where to look for accurate and up-to-date info. I >> remember having read in this list months ago someone saying that the >> documentation was quite outdated. For example, the xm command _delete_ >> does not appear in the man pages and many guides still do reference to >> the guest's config files being stored at /etc/xen (two days ago I >> discovered that now Xen works in a different way). >> >> My objective is not only to learn how to use Xen, but understand how >> it works. I'm doing my best looking for info in the net and going >> through docs in the Xen Wiki, but I might be missing something in my >> search. Therefore, I would really appreciate if someone could point me >> to some documentation I should read, or whatever else you could think >> of. >> >> Thanks, >> Gaston >> >> -- >> La ?nica verdad es la realidad. >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen > > > > -- > Emre -- La ?nica verdad es la realidad. -- Emre From Dustin.Henning at prd-inc.com Fri May 30 12:22:23 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 30 May 2008 08:22:23 -0400 Subject: [Fedora-xen] HVM DomU on F9? In-Reply-To: <483FA905.9050005@qumranet.com> References: <000a01c8ba8c$5cc63320$16529960$@Henning@prd-inc.com> <4832F44F.5050308@qumranet.com> <001901c8ba92$cae6e420$60b4ac60$@Henning@prd-inc.com> <4832F752.7070300@qumranet.com> <002701c8c1c2$d449c640$7cdd52c0$@Henning@prd-inc.com> <483FA905.9050005@qumranet.com> Message-ID: <003801c8c24f$d0b5cf00$72216d00$@Henning@prd-inc.com> For anyone who might have been following this thread, I accidentally forgot to add fedora-xen to the recipient list before sending my last reply. It is below, along with a response from Avi. I updated my F8 box, and sure enough, kvm-60 was installed. I thought I had just done that and kvm-55 was where it stopped, but I must be crazy or something. Also, I got the gplpv drivers by James Harper installed and functional as of version 0.9.2 (I had no luck with 0.9.0 or any prior version). That said, I probably won't go any further with my quest for kvm, at least not in the near future. The stdvga emulation kvm uses (or at least used on kvm-47) was nice with the standard vesa drivers referenced on the kvm site (went higher than 1024x768), and those drivers don't work for the stdvga=1 option in xen, but I think the potential performance gain from the multiple paravirtual drivers will be more important for me. Also, as I didn't follow up on it, I did try to install CentOS 5.1 on this machine and it does not support the network card, so I am on Fedora 8 as originally recommended by Emre. Dustin -----Original Message----- From: Avi Kivity [mailto:avi at qumranet.com] Sent: Friday, May 30, 2008 03:13 To: Dustin.Henning at prd-inc.com Subject: Re: [Fedora-xen] HVM DomU on F9? [please use the list for questions like this] Dustin Henning wrote: > It doesn't look like F8 is likely to get up to kvm-58 either. F8 is up to kvm-60. > I > prefer to stick with the Fedora repositories for the machine I am working > with, as I don't want to run into compatibility issues on account of some > future update. However, I want to try to use the network driver, as I am > hopeful that it might make an apache application I am running perform > better. It is also possible that I really need disk drivers for that. > Would compiling a newer version of kvm on Fedora 8 be risky (in terms of > interoperability problems after some future update)? No. > Also, assuming the > answer to that is no, do I need to remove any certain packages first to make > sure they don't update and overwrite it? No. Do a ./configure --prefix=/opt/kvm-69 and all files will be placed there. > Finally, on the Fedora repo > versions of KVM for F7 and F8, I can't create a VM with 2 GiB of RAM. Was > this a known kvm bug at some point (or worse, is it still?), or could it be > a problem with Fedora (I can do this fine in xen)? Thanks, > For more than 2GB of RAM in a guest, you need a 64-bit hypervisor. Large guest support was added in kvm-47 (2TB guests were booted). -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. From erenoglu at gmail.com Fri May 30 12:27:50 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Fri, 30 May 2008 14:27:50 +0200 Subject: [Fedora-xen] Xen Documentation In-Reply-To: <6171190242523591268@unknownmsgid> References: <6171190242523591268@unknownmsgid> Message-ID: I totally share your view. :) I'm in the same condition. Emre On Fri, May 30, 2008 at 2:12 PM, Dustin Henning wrote: > Emre, > As you may already know, I still use the config files in /etc/xen > and don't mess with the virsh stuff. It all certainly worked fine in F7, > and though I haven't fully tested, it appears that it all works fine in F8 > as well. I use them for one, because I learned with them, and for two, > because in the little time I have spent messing with the gui tools, I > haven't found near as much control. That isn't to say that more can be done > with the old way, but instead to say that I can do more with the old way. I > don't know if there are any plans to deprecate that stuff, but I hope that > if there ever are, news makes the list before I end up on a version where I > have no clue how to do anything! > Dustin > > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of Emre ERENOGLU > Sent: Friday, May 30, 2008 04:30 > To: Gast?n Keller > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Xen Documentation > > Hmm, > On Fri, May 30, 2008 at 2:06 AM, Gast?n Keller > wrote: > On Thu, May 29, 2008 at 7:53 PM, Emre ERENOGLU wrote: > > Hi Gaston, > > > > It's true that some documentation is outdated. However, for the > "/etc/xen" > > isssue, my custom Xen 3.2 setup still stores ( and I do store there also) > my > > config files there. > > > > Maybe what you're saying is "Fedora Specific" which I could understand as > > it's fedora mailing list. > _The Fedora team has followed the Xensource model and begun to store > all VM configuration details in a database, referred to as xenstore._ > Source: > http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ > > OK, I didn't know that. However, I find this xenstore thing a bit > complicated. > > Then, you might be right. I interpreted it was a modification from > Xen, not from Fedora (previously introduced by Xensource). > > So, what is the advantage behind this movement? > > I think it's managegability. > > > Thanks, > Gaston > > However, I never found the flexibility and control > > in the Fedora way of Xen implementation (all those xml stuff etc.). most > > probably, I'm wrong :) > > > > Emre > > > > On Thu, May 29, 2008 at 9:22 PM, Gast?n Keller > > wrote: > >> > >> Hello, everybody. I have been struggling with Xen's documentation > >> lately, not finding where to look for accurate and up-to-date info. I > >> remember having read in this list months ago someone saying that the > >> documentation was quite outdated. For example, the xm command _delete_ > >> does not appear in the man pages and many guides still do reference to > >> the guest's config files being stored at /etc/xen (two days ago I > >> discovered that now Xen works in a different way). > >> > >> My objective is not only to learn how to use Xen, but understand how > >> it works. I'm doing my best looking for info in the net and going > >> through docs in the Xen Wiki, but I might be missing something in my > >> search. Therefore, I would really appreciate if someone could point me > >> to some documentation I should read, or whatever else you could think > >> of. > >> > >> Thanks, > >> Gaston > >> > >> -- > >> La ?nica verdad es la realidad. > >> > >> -- > >> Fedora-xen mailing list > >> Fedora-xen at redhat.com > >> https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > -- > > Emre > > > -- > La ?nica verdad es la realidad. > > > > -- > Emre > > > -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri May 30 12:32:41 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 30 May 2008 13:32:41 +0100 Subject: [Fedora-xen] Xen Documentation In-Reply-To: References: Message-ID: <20080530123241.GC6219@redhat.com> On Thu, May 29, 2008 at 08:06:32PM -0400, Gast?n Keller wrote: > On Thu, May 29, 2008 at 7:53 PM, Emre ERENOGLU wrote: > > Hi Gaston, > > > > It's true that some documentation is outdated. However, for the "/etc/xen" > > isssue, my custom Xen 3.2 setup still stores ( and I do store there also) my > > config files there. > > > > Maybe what you're saying is "Fedora Specific" which I could understand as > > it's fedora mailing list. > > _The Fedora team has followed the Xensource model and begun to store > all VM configuration details in a database, referred to as xenstore._ No, xenstore only holds information about active VMs. The persistent VM config is managed by XenD itself, and stored in files under /var/lib/xend. > Source: http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ > > Then, you might be right. I interpreted it was a modification from > Xen, not from Fedora (previously introduced by Xensource). This was all implemented by upstream Xen. Libvirt probes for this capability in XenD and if it finds it, it will make use of it, since libvirt wants to be able to manage inactive VMs too. Since Fedora 7 was the first to ship this capability in Xen, it was the first release where libvirt would enable this inactive domain management. > So, what is the advantage behind this movement? The key reason for this was to allow XenD the ability to manage inactive domains. So all its APIs for modifying VM configs now work for running and inactive VMs. This is impossible for XenD if using /etc/xen. This is why 'xm list' won't show you configs stored in /etc/xen. 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 erenoglu at gmail.com Fri May 30 12:39:22 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Fri, 30 May 2008 14:39:22 +0200 Subject: [Fedora-xen] Xen Documentation In-Reply-To: <20080530123241.GC6219@redhat.com> References: <20080530123241.GC6219@redhat.com> Message-ID: Yes, but I don't have the same flexibility of options in the libvirt implementation. Emre On Fri, May 30, 2008 at 2:32 PM, Daniel P. Berrange wrote: > On Thu, May 29, 2008 at 08:06:32PM -0400, Gast?n Keller wrote: > > On Thu, May 29, 2008 at 7:53 PM, Emre ERENOGLU > wrote: > > > Hi Gaston, > > > > > > It's true that some documentation is outdated. However, for the > "/etc/xen" > > > isssue, my custom Xen 3.2 setup still stores ( and I do store there > also) my > > > config files there. > > > > > > Maybe what you're saying is "Fedora Specific" which I could understand > as > > > it's fedora mailing list. > > > > _The Fedora team has followed the Xensource model and begun to store > > all VM configuration details in a database, referred to as xenstore._ > > No, xenstore only holds information about active VMs. The persistent VM > config > is managed by XenD itself, and stored in files under /var/lib/xend. > > > Source: > http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ > > > > Then, you might be right. I interpreted it was a modification from > > Xen, not from Fedora (previously introduced by Xensource). > > This was all implemented by upstream Xen. Libvirt probes for this > capability > in XenD and if it finds it, it will make use of it, since libvirt wants to > be able to manage inactive VMs too. Since Fedora 7 was the first to ship > this capability in Xen, it was the first release where libvirt would enable > this inactive domain management. > > > So, what is the advantage behind this movement? > > The key reason for this was to allow XenD the ability to manage inactive > domains. So all its APIs for modifying VM configs now work for running > and inactive VMs. This is impossible for XenD if using /etc/xen. This is > why 'xm list' won't show you configs stored in /etc/xen. > > 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 > :| > -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jackson at eu.citrix.com Fri May 30 13:51:18 2008 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Fri, 30 May 2008 14:51:18 +0100 Subject: [Fedora-xen] Xen Documentation In-Reply-To: References: Message-ID: <18496.1622.268214.259470@mariner.uk.xensource.com> Gast?n Keller writes ("Re: [Fedora-xen] Xen Documentation"): > _The Fedora team has followed the Xensource model and begun to store > all VM configuration details in a database, referred to as xenstore._ > Source: http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ I wouldn't believe everything you read on the internet :-). Open Source Xen doesn't store configuration details in a database. It uses plain text configuration files in /etc. To a limited amount information about xend-managed domains is stored in /var in what is arguably a kind of database, but not in xenstore. Xenstore is not a database containing configuration details; it is cleared out at reboot. The name is misleading; the earlier name `xenbus' is clearer: xenstore is used as an inter-component communication mechanism, for communicating between the various non-hypervisor components of a running system, and particularly for advertising devices to paravirtualised guests. As I understand it, the proprietary XenSource XenServer product does indeed keep much in a database but that database is not xenstore. (But I don't really work on the proprietary side so I may be wrong.) I don't know what, if anything, is changing in Fedora. It's difficult to tell from that blog posting. Perhaps some of the Fedora guys here on this list can enlighten us; otherwise ask on fedora-xen ? Ian. From berrange at redhat.com Fri May 30 14:11:49 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 30 May 2008 15:11:49 +0100 Subject: [Fedora-xen] Xen Documentation In-Reply-To: <18496.1622.268214.259470@mariner.uk.xensource.com> References: <18496.1622.268214.259470@mariner.uk.xensource.com> Message-ID: <20080530141148.GA31084@redhat.com> On Fri, May 30, 2008 at 02:51:18PM +0100, Ian Jackson wrote: > Gast?n Keller writes ("Re: [Fedora-xen] Xen Documentation"): > > _The Fedora team has followed the Xensource model and begun to store > > all VM configuration details in a database, referred to as xenstore._ > > Source: http://enterpriselinuxlog.blogs.techtarget.com/2007/06/07/fedora-7-xen-first-look/ > > I wouldn't believe everything you read on the internet :-). > > Open Source Xen doesn't store configuration details in a database. It > uses plain text configuration files in /etc. To a limited amount > information about xend-managed domains is stored in /var in what is > arguably a kind of database, but not in xenstore. Or it uses text files in /var/lib/xen for domain configs. > I don't know what, if anything, is changing in Fedora. It's difficult > to tell from that blog posting. Perhaps some of the Fedora guys here > on this list can enlighten us; otherwise ask on fedora-xen ? We haven't changed anything in Xen in this regard. In Xen 3.0.3 and ealier the only place to store config files was in /etc, and XenD had no concept of inactive domains. In Xen 3.0.4 or later, XenD can directly manage inactive domains, storing their configs in /var/lib/xen/. IF libvirt detects a new enough XenD it will use its inactive domain management capabilities instead of putting configs in /etc, since this gives access to a greater level of functionality. 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 Ian.Jackson at eu.citrix.com Fri May 30 14:18:57 2008 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Fri, 30 May 2008 15:18:57 +0100 Subject: [Fedora-xen] Xen Documentation In-Reply-To: <20080530141148.GA31084@redhat.com> References: <18496.1622.268214.259470@mariner.uk.xensource.com> <20080530141148.GA31084@redhat.com> Message-ID: <18496.3281.200086.388872@mariner.uk.xensource.com> Daniel P. Berrange writes ("Re: [Fedora-xen] Xen Documentation"): > On Fri, May 30, 2008 at 02:51:18PM +0100, Ian Jackson wrote: > > Open Source Xen doesn't store configuration details in a database. It > > uses plain text configuration files in /etc. To a limited amount > > information about xend-managed domains is stored in /var in what is > > arguably a kind of database, but not in xenstore. > > Or it uses text files in /var/lib/xen for domain configs. Right, that's what I meant. > > I don't know what, if anything, is changing in Fedora. It's difficult > > to tell from that blog posting. Perhaps some of the Fedora guys here > > on this list can enlighten us; otherwise ask on fedora-xen ? > > We haven't changed anything in Xen in this regard. In Xen 3.0.3 and > ealier the only place to store config files was in /etc, and XenD had > no concept of inactive domains. In Xen 3.0.4 or later, XenD can directly > manage inactive domains, storing their configs in /var/lib/xen/. IF > libvirt detects a new enough XenD it will use its inactive domain > management capabilities instead of putting configs in /etc, since this > gives access to a greater level of functionality. That sounds sensible. I'm not sure how that relates to the blog posting mentioned by the original poster. Ian. From berrange at redhat.com Fri May 30 14:24:35 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 30 May 2008 15:24:35 +0100 Subject: [Fedora-xen] Xen Documentation In-Reply-To: <18496.3281.200086.388872@mariner.uk.xensource.com> References: <18496.1622.268214.259470@mariner.uk.xensource.com> <20080530141148.GA31084@redhat.com> <18496.3281.200086.388872@mariner.uk.xensource.com> Message-ID: <20080530142435.GC31084@redhat.com> On Fri, May 30, 2008 at 03:18:57PM +0100, Ian Jackson wrote: > Daniel P. Berrange writes ("Re: [Fedora-xen] Xen Documentation"): > > On Fri, May 30, 2008 at 02:51:18PM +0100, Ian Jackson wrote: > > > Open Source Xen doesn't store configuration details in a database. It > > > uses plain text configuration files in /etc. To a limited amount > > > information about xend-managed domains is stored in /var in what is > > > arguably a kind of database, but not in xenstore. > > > > Or it uses text files in /var/lib/xen for domain configs. > > Right, that's what I meant. > > > > I don't know what, if anything, is changing in Fedora. It's difficult > > > to tell from that blog posting. Perhaps some of the Fedora guys here > > > on this list can enlighten us; otherwise ask on fedora-xen ? > > > > We haven't changed anything in Xen in this regard. In Xen 3.0.3 and > > ealier the only place to store config files was in /etc, and XenD had > > no concept of inactive domains. In Xen 3.0.4 or later, XenD can directly > > manage inactive domains, storing their configs in /var/lib/xen/. IF > > libvirt detects a new enough XenD it will use its inactive domain > > management capabilities instead of putting configs in /etc, since this > > gives access to a greater level of functionality. > > That sounds sensible. I'm not sure how that relates to the blog > posting mentioned by the original poster. That posting is mostly based on a mis-understanding of what XenD is doing, but also the fact that there is no way to get the config back out of XenD using 'xm'. ie, you can load a traditional /etc/xen style config into XenD using 'xm new CONFIG', but you can't ask XenD to generate you a traditional style cofnig for one of the VMs its managing. Not an issue if you're using libvirt for management, since it doesn't use /etc/xen style configs anyway. While, there are a few people who need to use /etc/xen configs to get access to specific features not supported in libvirt (PCI device passthrough), they are a small niche. On the whole switching to using the new inactive domain management APIs in XenD was a net-win, with the benefits far outweighing the disadvantages. 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 ametzger at silkspeed.com Fri May 30 19:09:21 2008 From: ametzger at silkspeed.com (Aaron Metzger) Date: Fri, 30 May 2008 15:09:21 -0400 Subject: [Fedora-xen] Xen Documentation In-Reply-To: <20080530142435.GC31084@redhat.com> References: <18496.1622.268214.259470@mariner.uk.xensource.com> <20080530141148.GA31084@redhat.com> <18496.3281.200086.388872@mariner.uk.xensource.com> <20080530142435.GC31084@redhat.com> Message-ID: <484050E1.10708@silkspeed.com> Daniel P. Berrange wrote: > > That posting is mostly based on a mis-understanding of what XenD is doing, > but also the fact that there is no way to get the config back out of XenD > using 'xm'. ie, you can load a traditional /etc/xen style config into XenD > using 'xm new CONFIG', but you can't ask XenD to generate you a traditional > style cofnig for one of the VMs its managing. Not an issue if you're using > libvirt for management, since it doesn't use /etc/xen style configs anyway. > While, there are a few people who need to use /etc/xen configs to get access > to specific features not supported in libvirt (PCI device passthrough), they > are a small niche. On the whole switching to using the new inactive domain > management APIs in XenD was a net-win, with the benefits far outweighing > the disadvantages. > Can we mix and match. Can we have some old style configs in "/etc/xen" for some guests while using libvirt for the rest? I'm using the new way of doing things now but wonder what will happen if some day I need PCI device passthrough for one guest. Do, I have to revert all guests back to the old style of config to have this capability for one? From Dustin.Henning at prd-inc.com Fri May 30 20:48:00 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 30 May 2008 16:48:00 -0400 Subject: [Fedora-xen] Strange mouse issue (F7 & F8 xen kernel with vncviewer running) Message-ID: <008d01c8c296$72a49210$57edb630$@Henning@prd-inc.com> I have been experiencing this (rather strange) issue for as long as I have been a member of this group, and I am curious as to whether anyone else has experienced it. The mouse will continue on in the direction I am moving it after I stop, change direction, or even suddenly reverse direction. Once this happens, the mouse inevitably ends up in one of the four corners of the screen, and will eventually stop trying to travel in that direction, at which point I can control it again. It seems like hitting some keys may cause this to happen sooner. The keys I most often go for are Esc, Alt, Ctrl, Super, Alt+F1, Arrows. Which keys usually depends on what is up in the vncviewer window, where I don't want to issue the wrong command to whatever client I may be working with. I have made the following observations regarding this behavior, though I can't say with absolute certainty that they are all 100% accurate and/or consistent: -keyboard and mouse are PS/2 -in all instances, hvm guests were running, consuming as much as 5 out of 8 GiB of memory on this machine -never experienced in standard kernel on F7 or F8 (even with multiple kvm guests and vncviewers running, though not to consume 5 of 8 GiB) -originally, in F7, vncviewer may not have been running every time it happened -now, in F8, vncviewer has definitely been running every time it happened, but not necessarily connected to anything -same issue was previously experienced on another machine with less memory (and less guests) on F7 Is this a known issue of any sort? It has recently occurred to me that I should try a different client, and I will do that at some point, but I figured it wouldn't hurt to see if there have been any other similar experiences out there in the meantime. Thanks, Dustin From Dustin.Henning at prd-inc.com Fri May 30 20:54:51 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 30 May 2008 16:54:51 -0400 Subject: [Fedora-xen] Strange mouse issue (F7 & F8 xen kernel with vncviewer running) In-Reply-To: <008d01c8c296$72a49210$57edb630$@Henning@prd-inc.com> References: <008d01c8c296$72a49210$57edb630$@Henning@prd-inc.com> Message-ID: <008e01c8c297$68011210$38033630$@Henning@prd-inc.com> I spoke too soon... I just tried krdc and the same thing happened before I could even try to connect to anything with it (or even determine if it supports vnc, I don't remember). This is a quad core, and I have, in all instances, confirmed that each of the four vcpus in dom0 is tied to a different core. Additionally, I have never had more than one DomU per core on top of Dom0 using each core. Finally, in this latest instance, only one DomU was doing anything, and it could not have been using but 100% of one core, so the other three were, for lack of a better word, bored. -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dustin Henning Sent: Friday, May 30, 2008 16:48 To: fedora-xen at redhat.com Subject: [Fedora-xen] Strange mouse issue (F7 & F8 xen kernel with vncviewer running) I have been experiencing this (rather strange) issue for as long as I have been a member of this group, and I am curious as to whether anyone else has experienced it. The mouse will continue on in the direction I am moving it after I stop, change direction, or even suddenly reverse direction. Once this happens, the mouse inevitably ends up in one of the four corners of the screen, and will eventually stop trying to travel in that direction, at which point I can control it again. It seems like hitting some keys may cause this to happen sooner. The keys I most often go for are Esc, Alt, Ctrl, Super, Alt+F1, Arrows. Which keys usually depends on what is up in the vncviewer window, where I don't want to issue the wrong command to whatever client I may be working with. I have made the following observations regarding this behavior, though I can't say with absolute certainty that they are all 100% accurate and/or consistent: -keyboard and mouse are PS/2 -in all instances, hvm guests were running, consuming as much as 5 out of 8 GiB of memory on this machine -never experienced in standard kernel on F7 or F8 (even with multiple kvm guests and vncviewers running, though not to consume 5 of 8 GiB) -originally, in F7, vncviewer may not have been running every time it happened -now, in F8, vncviewer has definitely been running every time it happened, but not necessarily connected to anything -same issue was previously experienced on another machine with less memory (and less guests) on F7 Is this a known issue of any sort? It has recently occurred to me that I should try a different client, and I will do that at some point, but I figured it wouldn't hurt to see if there have been any other similar experiences out there in the meantime. Thanks, Dustin -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From Dustin.Henning at prd-inc.com Fri May 30 20:55:12 2008 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 30 May 2008 16:55:12 -0400 Subject: [Fedora-xen] Strange mouse issue (F7 & F8 xen kernel with vncviewer running) Message-ID: <008f01c8c297$747e3ea0$5d7abbe0$@Henning@prd-inc.com> I spoke too soon... I just tried krdc and the same thing happened before I could even try to connect to anything with it (or even determine if it supports vnc, I don't remember). This is a quad core, and I have, in all instances, confirmed that each of the four vcpus in dom0 is tied to a different core. Additionally, I have never had more than one DomU per core on top of Dom0 using each core. Finally, in this latest instance, only one DomU was doing anything, and it could not have been using but 100% of one core, so the other three were, for lack of a better word, bored. -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dustin Henning Sent: Friday, May 30, 2008 16:48 To: fedora-xen at redhat.com Subject: [Fedora-xen] Strange mouse issue (F7 & F8 xen kernel with vncviewer running) I have been experiencing this (rather strange) issue for as long as I have been a member of this group, and I am curious as to whether anyone else has experienced it. The mouse will continue on in the direction I am moving it after I stop, change direction, or even suddenly reverse direction. Once this happens, the mouse inevitably ends up in one of the four corners of the screen, and will eventually stop trying to travel in that direction, at which point I can control it again. It seems like hitting some keys may cause this to happen sooner. The keys I most often go for are Esc, Alt, Ctrl, Super, Alt+F1, Arrows. Which keys usually depends on what is up in the vncviewer window, where I don't want to issue the wrong command to whatever client I may be working with. I have made the following observations regarding this behavior, though I can't say with absolute certainty that they are all 100% accurate and/or consistent: -keyboard and mouse are PS/2 -in all instances, hvm guests were running, consuming as much as 5 out of 8 GiB of memory on this machine -never experienced in standard kernel on F7 or F8 (even with multiple kvm guests and vncviewers running, though not to consume 5 of 8 GiB) -originally, in F7, vncviewer may not have been running every time it happened -now, in F8, vncviewer has definitely been running every time it happened, but not necessarily connected to anything -same issue was previously experienced on another machine with less memory (and less guests) on F7 Is this a known issue of any sort? It has recently occurred to me that I should try a different client, and I will do that at some point, but I figured it wouldn't hurt to see if there have been any other similar experiences out there in the meantime. Thanks, Dustin -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen