server migration
by jm-ml
aloa list,
i have an existing fedora core 1 machine and want to convert this
machine to a xen-domU on a fc6(7) dom0.
i tried the following:
- create an imagefile and format it.
- rsync the existing machine to the xen-dom0 into the mounted image file
- then i took the existing kernel of a fc6 domU and copied it to the
fc1-domU
there is a problem during the systemboot and so i think there should be
better ways to convert the fc1 machine to a xen-domU.
what way would you suggest?
thanks and greetings
jm
16 years, 11 months
[patch] GUI for spacifying additional kernel parameters
by Alexander Todorov
Hello list,
I needed to use additional kernel parameters when installing a Xen
guest. I was testing modifications of anaconda.
This patch provides a page where the user can supply any parameters that
should be passed to the kernel. Write the parameters as you would do it
on the command line for a physical machine.
The new page is shown after settings for paravirtualized install.
Changes are in vmm-create.glade and virtManager/create.py.
Q: Why there is an option to pass additional kernel parameters only for
paravirtualized installs? Is this possible for fully virtualized installs?
NB: I have tested this with a backported changes for the version I have
installed on my system but it should be working in devel version too.
Greetings,
Alexander.
16 years, 11 months
BUG at arch/x86_64/mm/../../i386/mm/hypervisor.c:185!
by Naoki
Is this one known? Didn't see in BZ.
May 21 12:03:20 localhost kernel: ------------[ cut here ]------------
May 21 12:03:20 localhost kernel: kernel BUG at
arch/x86_64/mm/../../i386/mm/hypervisor.c:185!
May 21 12:03:20 localhost kernel: invalid opcode: 0000 [1] SMP
May 21 12:03:20 localhost kernel: last sysfs
file: /devices/pci0000:00/0000:00:00.0/irq
May 21 12:03:20 localhost kernel: CPU 0
May 21 12:03:20 localhost kernel: Modules linked in: i915 drm bridge
netbk blktap blkbk autofs4 eeprom hidp rfcomm l2cap bluetooth sunrpc
nf_conntrack_ftp nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4
xt_state nf_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables
x_tables video sbs i2c_ec dock button battery asus_acpi backlight ac
ipv6 lp loop tg3 snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_dummy
snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_mixer_oss snd_pcm i2c_i801 i2c_core snd_timer iTCO_wdt
iTCO_vendor_support serio_raw serial_core pcspkr snd soundcore
snd_page_alloc parport_pc parport shpchp sr_mod cdrom sg dm_snapshot
dm_zero dm_mirror dm_mod ata_piix ata_generic libata sd_mod scsi_mod
ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
May 21 12:03:20 localhost kernel: Pid: 16222, comm: evolution Not
tainted 2.6.20-2925.8.fc7xen #1
May 21 12:03:20 localhost kernel: RIP: e030:[<ffffffff80276c16>]
[<ffffffff80276c16>] xen_pgd_pin+0x51/0x5a
May 21 12:03:20 localhost kernel: RSP: e02b:ffff8800591e7dd8 EFLAGS:
00010282
May 21 12:03:20 localhost kernel: RAX: 00000000ffffffea RBX:
ffff880065aaa480 RCX: 000000000005fe0a
May 21 12:03:20 localhost kernel: RDX: 0000000000000000 RSI:
0000000000000001 RDI: ffff8800591e7dd8
May 21 12:03:20 localhost kernel: RBP: ffff880065aaa518 R08:
0000000000075700 R09: ffff880037e27008
May 21 12:03:20 localhost kernel: R10: 0000000000007ff0 R11:
0000000022159000 R12: ffff8800375b6810
May 21 12:03:20 localhost kernel: R13: ffff880065aaa480 R14:
0000000000000000 R15: ffff880065aaa480
May 21 12:03:20 localhost kernel: FS: 00002aaaaaac5af0(0063)
GS:ffffffff80579000(0000) knlGS:0000000000000000
May 21 12:03:20 localhost kernel: CS: e033 DS: 0000 ES: 0000 CR0:
000000008005003b
May 21 12:03:20 localhost kernel: CR2: 0000000000000000 CR3:
0000000008432000 CR4: 0000000000000660
May 21 12:03:20 localhost kernel: Process evolution (pid: 16222,
threadinfo ffff8800591e6000, task ffff88004fc76040)
May 21 12:03:20 localhost kernel: Stack: ffffffff00000003
000000000001dc0a ffff880065aaa518 0000000022159000
May 21 12:03:20 localhost kernel: 000000000005fe0b ffffffff80276667
ffff880065aaa480 ffff8800112b37c8
May 21 12:03:20 localhost kernel: 0000000000000000 ffffffff8021f583
00000000414019d0 0000000000000000
May 21 12:03:20 localhost kernel: Call Trace:
May 21 12:03:20 localhost kernel: [<ffffffff80276667>] mm_pin
+0x182/0x1f1
May 21 12:03:20 localhost kernel: [<ffffffff8021f583>] copy_process
+0xc8f/0x18a2
May 21 12:03:20 localhost kernel: [<ffffffff80231389>] do_fork
+0x69/0x15a
May 21 12:03:20 localhost kernel: [<ffffffff802a8048>]
audit_syscall_entry+0x141/0x174
May 21 12:03:20 localhost kernel: [<ffffffff8025b300>] tracesys
+0xb2/0xb7
May 21 12:03:20 localhost kernel: [<ffffffff8025b4fd>]
ptregscall_common+0x3d/0x70
May 21 12:03:20 localhost kernel:
May 21 12:03:20 localhost kernel:
May 21 12:03:20 localhost kernel: Code: 0f 0b eb fe 48 83 c4 28 c3 48 83
ec 28 48 c1 ef 0c 80 3d b4
May 21 12:03:20 localhost kernel: RIP [<ffffffff80276c16>] xen_pgd_pin
+0x51/0x5a
May 21 12:03:20 localhost kernel: RSP <ffff8800591e7dd8>
16 years, 11 months
fc6xen kernel panic after yum update
by Tauren Mills
Hello,
I used yum update on a newly installed dual cpu i386 FC6 system a
couple days ago. My system was updated from Fedora Core
2.6.18-1.2798.fc6xen to 2.6.20-1.2948.fc6xen. The update went fine.
After reboot, I got the following kernel panic:
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumnes
Volume group "vg0" not found
Creating root device.
Mounting root filesystem.
mount: could not fine 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 failed: No such file or directory
setuproot: error mounting /sys failed: 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
Kernel panic - not syncing: Attempted to kill init!
If I'd boot into the original kernel, it booted just fine.
So, today I took a spare system and installed FC6 fresh from
installation disks. The very first thing I did after the installation
was completed was do a yum update. After reboot, the exact same
problem. Both systems don't work with the latest XEN kernel.
For reference, the only packages installed from the graphical
installer were these:
Applications/Editors:
vim-enhanced
Applications/Text-based Internet:
lynx
Base System/Base:
finger
gnupg
man-pages
mdadm
mlocate
nfs-utils
openssh-clients
oopenssh-server
rsync
sudo
telnet
wget
which
yum
Base System/Virtualization:
virt-manager
Since the errors indicate LVM problems, here's info about my disk
layout. I'm configured using two 72GB scsi disks using raid1, then lvm
on top. Disk partitioning:
/dev/sda (72GB)
/dev/sda1 (102MB)
/dev/sda2 (69.9GB)
/dev/sdb (72GB)
/dev/sdb1 (102MB)
/dev/sdb2 (69.9GB)
/dev/sda1 & /dev/sdb1 are mirrored to /dev/md0
used by /boot partition (102MB)
/dev/sda2 & /dev/sdb2 are mirrored to physical volume /dev/md1
used in VolGroup00
/dev/md1 is LVM VolGroup00 and contains these logical volumes
/dev/VolGroup00/lvdom0 (root) 3GB
/dev/VolGroup00/lvswap0 (swap) 4GB
The rest of the space was left empty for xen guest partitions.
I've edited grub.conf to use /dev/mapper vs /dev/VolGroup00, but
nothing has booted with the new kernel.
Is there a problem with the new kernel? Where should I go for a
solution? Should I just run the old kernel for now? If I'm not in the
best forum for this, where should I go for help?
Any help would be appreciated!
Thanks!
16 years, 11 months
Intel VT and paravirtualized Guests?
by Christian Reiter
Hi!
Is there any advance in using a CPU which supports Intel VT
when having only paravirtualized domUs?
Or does VT only help when there are fully virtualized Guests?
How do i enable the usage of VT in FC6's Xen?
Kind Regards,
Christian Reiter
--
Christian Reiter ||| c.reiter(a)gmx.net
16 years, 11 months
PXE boot with Xen
by Alexander Todorov
Hello,
Is it possible to create a xen guest than will use PXE boot for initial
installation?
16 years, 11 months
380MB memory in Dom-0 enough to support 6 Dom-U guest
by Ma wai ming
any people try and know this configuration workable ?
Total mem : 3GB
6 x Dom-U Guest with 430MB memory each
remaining arround 380MB memory in Dom-0
is there any min memory requirement for Dom-0 ?
Thanks
Regards,
16 years, 11 months