New virt-manager release v0.2.0
by Daniel P. Berrange
I'm pleased to announce the availabilty of another snapshot / development
release of virt-manager, version 0.2.0. The major new capabilities in this
release include:
* First cut of a wiziard for creating both paravirt & fullyvirt
guest VMs. aka the gui equivalent of xenguest-install.py
You can find out more about this in the new screenshots section:
http://virt-manager.et.redhat.com/screenshots/install.html
* An embedded serial console viewer - no need to go to the shell and
use 'xm console' anymore. This is actually used for the paravirt
guest instllation if your XenU kernel does not support the new VNC
framebuffer (not yet in xen-unstable)
* Hooked up the config dialog for adjusting vcpus & memory for active
domains
* Extended RFB protocol handler code to support the 'desktop resize'
extensions in the VNC widget - so the graphical console has correct
size when the guest switches screen resolutions
The tar.gz for the release can be found on the download page:
http://virt-manager.et.redhat.com/download.html
NB, I'm not providing RPMs in my people.redhat.com YUM repo because we're
intending to build this release straight into Fedora rawhide. I'll send
a followup message when they're avaiable there.
NB-2. there is a dependnacy on the 'xeninst' python library which is a
new library built from re-factoring xenguest-install.py You can get this
from rawhide in the python-xeninst RPM, or direct from the mercurial
repository
http://hg.et.redhat.com/virt/applications/xeninst--devel
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
17 years, 8 months
XENBUS_PATH
by MJang
Folks,
I'm trying to get Xen working on FC5. I get some way through the
xenguest-install.py script, and realize that Networking isn't working.
I've tried setting via DHCP and manually, and can't ping to it. Key log
messages include:
/var/log/messages:
Aug 24 11:11:17 Enterprise5a logger: /etc/xen/scripts/vif-bridge: brctl
addif xenbr0 vif3.0 failed
/var/log/xen-hotplug.log:
./vif-common.sh: line 52: XENBUS_PATH: parameter null or not set
I'm guessing that I need to set XENBUS_PATH somewhere, but don't have a
clue where - or to what. Haven't found it in any of the docs that I've
searched.
I'm also guessing that my problem may be related to the two network
cards that I have on this AMD x86_64 system, but that's a wild guess.
Thanks,
Mike
17 years, 8 months
virt-manager
by Daniel Rindt
Hello,
Yesterday i Setup the Repo for the virt-manager. Today i would like to
Setup this Repo on another Machine and i cant find the Repo file again
at the Homepage of the Developer.
Can anyone please give me a Hint where i can find the rpm files from
virt-manager?
Thanks in Advance
Daniel
17 years, 8 months
ati-driver and xen kernel --> black screen
by Thomas von Steiger
Hi,
I can testing HP Notebooks nw8440 and nc8430 with VT enabled CPU's
(T2500/T2600) and fc5 to have fullvirtualitation on a notebook.
With the latest smp kernel 2.6.17-1.2174 and
ati-driver-installer-8.27.10-x86.run (generate rpm's) everything is working.
If I try to boot the latest xen kernel 2.6.17-1.2174 in runlevel 5 with the
same ati driver I get a black screen, no display, no console.
The same xen kernel can boot without problem in runlevel 3 and then I have a
console.
Has anybody a solution for this problem ?
Reagards
Thomas
17 years, 8 months
RE: [Fedora-xen] Newbie question regarding Xen traps
by Alex Tomic
Hey Rik (reply to list)
I forgot to thank you for this response. I had planned to buy a serial cable
if I had any more instability after upgrading.
After doing the full-blown yum update for my stock FC5_x86_64 boxes (to
kernel 2.6.17-1.2157_FC5xen0 and Xen-3.0.2-3), I have had no such crashes
after 13 days. I really wish I had the stack traces so you could at least
identify a fixed bug, but I don't have the luxury of being able to go back
to an old code release and reproduce the problem, at least not now.
If anyone on this list experiences instability when stressing mysql on a
x86_64 VM, especially with a stack that has mask_IO_APIC_irq or
mask_and_ack_level_ioapic_irq in it (not sure exactly what these do), I
would suggest doing an upgrade to the latest Xen on Dom0; I did not upgrade
the guest OSes, they are still on the stock FC5 guest kernel
(2.6.15-1.2054_FC5xenU)
-Alex
---------------------------------------------
Alex Tomic
Database Administrator, Gifts.com
8833 Sunset Blvd, 3rd Floor
West Hollywood, CA 90069
Phone: (310) 360-4332
-----Original Message-----
From: Rik van Riel [mailto:riel@redhat.com]
Sent: Tuesday, August 08, 2006 4:20 PM
To: Alex Tomic
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] Newbie question regarding Xen traps
Alex Tomic wrote:
> My question is, how do I retain the trap output that is printed to the
> console when the machine dies?
Serial console.
The easiest thing is to buy two serial cables and have both
systems act as serial console server for the other, using
the excellent ttywatch program from Fedora Extras.
If one crashes, the other will log all the crash output.
Don't forget to also configure the hypervisor for serial
console output. Your grub.conf will look like this:
title Fedora Core (2.6.17-1.2488.fc6xen)
root (hd0,0)
kernel /xen.gz-2.6.17-1.2488.fc6 com1=38400,8n1
module /vmlinuz-2.6.17-1.2488.fc6xen ro root=LABEL=/
console=ttyS0,38400 mem=2000M panic=180 debug 3
module /initrd-2.6.17-1.2488.fc6xen.img
When you get a backtrace, please file a bugzilla and feel
free to add me to the CC: list. I have a very strong
personal interest in fixing x86-64 Xen bugs, since I want
to get rid of a (noisy, warm) server at home and move that
workload into a virtual machine on my new desktop system :)
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
17 years, 8 months
FC5-DOM0 and FC6T2-DOMU
by Roger Grosswiler
Hey,
tried today to run a installation of FC6T2 on a FC5 machine with Dom0.
As i remarked, it was not possible to install, I got after the start of
installation the error, that the Domain was not found.
Btw. xenguest-install.py did work well. Do i have to do something
special to install FC6T2 as DomU und Fc5?
Thanks,
Roger
17 years, 8 months
Ubuntu Dapper Drake as guest on Fedora Core 5
by plottygat
Hello,
I'm running a Fedore Core 5 as domain0 on Xen 3.0. I could quite easily install another FC5 as guest OS, following the quickstart guide.
Now I'd like to run a different OS as domU, in particular Ubuntu 6.06. I can't understand if the kernel-xenU that must be specified in the domU configuration file is the Fedora's one (vmlinuz-2.6.17-1.2174_FC5xenU) or a kernel-xenU specific to the guest distro.
Is there a howto for starting an ubuntu or debian guest on Fedora?
Thanks to all in advance
Moreno T
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
17 years, 8 months
Re: [Fedora-xen] fc5 kernel-xen0 w/ pae
by Jason Tower
that's what i tried already (reread my original post). but xend doesn't
start properly when booting kernel-xen (it starts fine with kernel-xen0).
thanks for answering my question, the next problem is to figure out why xend
isn't happy with that particular kernel.
unfortunately circumstances beyond my control have forced me to put this box
in production my monday am so i can't troubleshoot things at this time.
hopefully i can scrounge up a similar box w/ 6gb ram so i can work this out.
jason
On 8/13/06, Andrew Cathrow <acathrow(a)redhat.com> wrote:
>
> Try the kernel-xen package - I believe the system is kernel-xen0 = non
> pae and kernel-xen = pae.
>
> Aic
>
>
> On Sat, 2006-08-12 at 22:20 -0400, Jason Tower wrote:
>
> is there an "official" xen0 kernel for fc5 that includes pae support? i
> have a 32bit system w/ 6gb ram that works fine with
> kernel-xen0-2.6.17-1.2174_FC5 (from yum) although it only sees 4gb. i
> installed kernel-xen-2.6.17-1.2174_FC5 which says it was built with pae,
> it sees the full 6gb but fails to bring up the bridge devices when xend
> starts. if anyone can point me in the right direction i'd appreciate it.
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
17 years, 8 months
How to enable "pciback.hide" in standard xen 3.0.2 kernels
by Wolfgang Schleicher
Or how to delegate special PCI devices from domain-0 to dom(u)
Hi,
I tried to manage some pci devices for dom(u) domains, using the fedora core 5 (xen0/u) and 6-test2 (xen) i686 kernel-xen and kernel-xen-devel rpms:
In domain-0 lspci shows the pci device 00:04.01 which should be delegated to dom(u)
In dom(u) lspci does not show any information (this seems to be ok)
lsmod in dom(u) gives:
xennet
ipv6
dm_mirror
dm_mod
parport_pc
lp
parport
pcspkr
ext3
jbd
xenblk
Following the official XEN Documentation, I modified the grub.conf with the following kernel option:
"module /vmlinuz-2.6.17-1.2566.fc6xen ro root=LABEL=/1 selinux=0 rhgb quiet pciback.hide=(00:08.0)"
or
"module /vmlinuz-2.6.17-1.2566.fc6xen ro root=LABEL=/1 selinux=0 rhgb quiet pciback.hide=(0000:00:08.0)"
After having booted into Domain-0, I noticed in the message log:
"kernel: Kernel command line: ro root=LABEL=/1 selinux=0 rhgb quiet pciback.hide=(00:08.0)"
"kernel: Unknown boot option `pciback.hide=(00:08.0)': ignoring"
So this kernel option does not seem to be supported by default.
Btw, I also tried the xen-binaries packages (the testing ones) from xensource with the same results
Adding the pci option to /etc/xen/config-file
"pci = [ '0000:00:08.0' ]"
or
"pci = [ '00:08.0' ]"
or
"pci = [ '00,08,00' ]"
and trying to start the guest domain fails:
"Error: pci: failed to locate device and parse itŽs ressources
- [Errno 2] No such file or directory: '/sys/bus/pci/devices/0000:00:08.0/driver' "
I donŽt understand why the pci backend option is not included as a default kernel option and I wonder why this kernel option (slots) is mentioned in nearly every xen documentation (I know this option was missed in xen 3.0.0/3.0.1)
I would like prefer the latest fc6-t2 kernel packages as there seems to be no longer smaller xenU kernels which might give a better support when trying to compile different kernel modules (e.g. avm fritzcard).
What I did (Hardware x86, PIII)
I downloaded the latest fedora core 6t2 src.rpm kernel-packages and tried to rebuild but was unsecure [e.g. marked with (?)] about the correct kernel-xen options.
Then I would do the following:
-install fedora-buildrpmtree
-install kernel-2.6.17-1.2564.fc6.src.rpm
-switching to non root user:
-rpmbuild -bp --target i686 ~/rpmbuild/SPECS/kernel-2.6.spec
-cd ~/rpmbuild/BUILD/kernel-2.6.17/linux-2.6.17.i686/
-make mrproper
-cp ~/rpmbuild/SOURCES/kernel-2.6.17-i686.config .config
-make oldconfig
-cd ~/rpmbuild/BUILD/kernel-2.6.17/linux-2.6.17
-vi Makefile:
change EXTRAVERSION = -1.2566.fc6xen
to EXTRAVERSION = -1.2566.fc6xen-wsc
#make menuconfig (not working for me)
- make xconfig
#make config (accepting all settings)
##
#not sure about this, having red this in another FC kernel-howto#
-echo >config.fix "# i386"
-cat .config >>config.fix
-cp -f config.fix ~/rpmbuild/SOURCES/kernel-2.6.17-i686.config
##
-rpmbuild --target i686 -ba ~/rpmbuild/SPECS/kernel-2.6.spec
Before doing the steps as listed above, I`m not sure what different settings should be used for a new kernel-built.
Current (orginal default FC6t2) kernel-xen config file: /usr/src/kernels/2.6.17-1.2566.fc6-xen-i686/build/.config
...
# XEN
#
CONFIG_XEN_PRIVILEGED_GUEST=y
# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
CONFIG_XEN_PRIVCMD=y (?)
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=m
CONFIG_XEN_BLKDEV_TAP=m
CONFIG_XEN_NETDEV_BACKEND=m
# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_NETDEV_LOOPBACK=m
CONFIG_XEN_PCIDEV_BACKEND=m (?)
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set (?)
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set (?)
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_FRAMEBUFFER=m
CONFIG_XEN_KEYBOARD=m
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_DISABLE_SERIAL is not set
CONFIG_XEN_SYSFS=y
CONFIG_XEN_COMPAT_030002_AND_LATER=y
# CONFIG_XEN_COMPAT_LATEST_ONLY is not set
CONFIG_XEN_COMPAT_030002=y
CONFIG_HAVE_ARCH_ALLOC_SKB=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
CONFIG_NO_IDLE_HZ=y
CONFIG_XEN_UTIL=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_DEVMEM=y
CONFIG_XEN_SKBUFF=y
CONFIG_XEN_REBOOT=y
CONFIG_XEN_SMPBOOT=y
...
Please, can anyone provide a detailed "rebuilding kernel-xen" tutorial, regarding the relevant xen options for the pci backend/pci frontend settings?
Anyone to point me to location where pci backend precompiled fedora kernel-xen packages are provided?
Any help would be appreciated!
Thanks
Wolfgang
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
17 years, 8 months
XENBUS: Device with no driver: device/vbd/51712
by Ricardo Ariel Gorosito
I was installed a rawhide domain using xenguest-install.py .
Installation was successful, but when I try to start the domain, it die
with a kernel panic (guest)
The full output from the console in guest domain is in the attachment.
the following lines make me think that initrd is not generated correctly
during the installation of guest domain:
XENBUS: Device with no driver: device/vbd/51712
...
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Any hint?
Going to boot Fedora Core (2.6.17-1.2548.fc6xen)
kernel: /vmlinuz-2.6.17-1.2548.fc6xen
initrd: /initrd-2.6.17-1.2548.fc6xen.img
Started domain xuxa
Linux version 2.6.17-1.2548.fc6xen (brewbuilder(a)hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20060802 (Red Hat 4.1.1-14)) #1 SMP Thu Aug 10 23:10:42 EDT 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
Using x86 segment limits to approximate NX protection
ACPI in unprivileged domain disabled
Built 1 zonelists. Total pages: 67584
Kernel command line: ro root=/dev/VolGroup00/LogVol00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0728000 soft=c0708000
PID hash table entries: 2048 (order: 11, 8192 bytes)
Xen reported: 1908.934 MHz processor.
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB disabled
vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000
Memory: 250368k/270336k available (2043k kernel code, 11520k reserved, 850k data, 176k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4775.27 BogoMIPS (lpj=9550546)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 4377k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
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 driver usbfs
usbcore: registered new driver hub
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: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 327680 bytes)
TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
IA-32 Microcode Update Driver: v1.14-xen <tigran(a)veritas.com>
audit: initializing netlink socket (disabled)
audit(1155423080.036:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 9E1464B61C97F3AB
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver libusual
usbcore: registered new driver hiddev
usbcore: registered new 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
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Processor cpuid 6a0 not supported
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 176k freed
Red Hat nash version 5.1.2 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading xenblk.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mod.ko module
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel(a)redhat.com
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Making device-mapper control node
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
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 /proc/bus/usb
ERROR unmounting old /proc/bus/usb: No such file or directory
forcing unmount of /proc/bus/usb
unmounting old /sys
switchroot: mount failed: No such file or directory
4gb seg fixup, process nash-hotplug (pid 219), cs:ip 73:080addd1
4gb seg fixup, process nash-hotplug (pid 219), cs:ip 73:08159148
4gb seg fixup, process init (pid 1), cs:ip 73:080addd1
4gb seg fixup, process init (pid 1), cs:ip 73:08159148
Kernel panic - not syncing: Attempted to kill init!
17 years, 8 months
