I'm testing some kickstarts on xen. Everything's OK, but I'm stuck on one part.
I've researched my question well, and I'm just not getting one piece.
The pw set during install is intentionally bogus. I now want to go to my grub
menu, go single-user and set it via 'passwd'. ( Which we typically do on
non-virtual installations. )
On RHEL, where I have much more experience, I can just "xm create -c mydomain"
to get an immediate attach and see the grub menu.
It looks like this newer xen/libvirt on FC8 is setup to use virsh, and it has
the XML configs over in /var/lib/xend/domains/, etc.
So, how do I get to the grub menu using virsh, since xm seems to want to work
with plaintext configs in /etc/xen, which I do not have? Or, how would you
suggest I change the bogus root pw, that no one knows?
Thanks and have a fine day.
# rpm -q xen
# rpm -q libvirt
I read other entries about this subject but none
explain why it is not possible to boot from a floppy
image with XEN even though it is possible to do so
Under dom0(2.6.21-6.fc7xen) I issue the command:
qemu -boot a -fda <my-floppy-image> -hda
and I get to boot from the floppy image, whereas when
I use xen whose config file contains
in the <disk> clause, I get the following message in
the booting window:
Booting from Floppy...
Boot from Floppy failed: could not read the boot
FATAL: No bootable device.
The QEMU monitor shows that, while disk-C image was
taken into consideration as such, the equivalent
<file> command for the floppy disk was completely
Furthermore, it expects the floppy media to be present
in the drive, as the following lines from the
<info block> command show:
hda: type=hd removable=0 file=<my-disk-C-image>
hdb: type=cdrom removable=1 locked=0 [not
fda: type=floppy removable=1 locked=0 [not
Can somebody explain whether that behaviour was the
result of a design choice or error?
Let me emphasize the importance to have this feature.
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
I'm sure its not a bios setting, because when I boot into Vista it sees 2 cpus.
----- Original Message ----
From: Lamont Peterson <lamont(a)gurulabs.com>
To: Fedora Xen <fedora-xen(a)redhat.com>
Sent: Tuesday, December 18, 2007 2:55:21 AM
Subject: Re: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core
On Monday 17 December 2007 10:41:26 pm Darryl Bowler wrote:
> I have an ACER AM3100-UD5200A which uses an AMD 64 X2 5200.
> Xen only detects one of two cores
Have you checked your BIOS config? I've heard of (though none of my
multi-core systems have such) support in some BIOSes to enable/disable
he 'extra' cores.
Lamont Peterson <lamont(a)gurulabs.com>
Guru Labs, L.C. [ http://www.GuruLabs.com/ ]
NOTE: All messages from this email address should be digitally signed
0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver
well as other keyservers that sync with MIT's.
Never miss a thing. Make Yahoo your home page.
[this is a message that I sent to xen-users yesterday, but I guess this
list may be better - this looks like a problem either in Xen, or in the
packaging of 2.6.21-2952.fc8xen].
I've just installed Fedora 8 / xen-2.6.21 on a headless server, but I
can't get a serial console login on the Xen version of the kernel.
1 - If I boot into 220.127.116.11-63.fc8, the serial console login works as
2 - If I boot into 2.6.21-2952.fc8xen instead, I get all the expected
serial output up to the end of the boot process, but no login.
When I boot into the xen kernel, inittab is modified, and the
modification removes the agetty on ttyS0. If I compare the old inittab
with the new inittab, I get:
< # co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav
< co:12345:respawn:/sbin/agetty ttyS0 115200 vt100
> co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav
In other words, a commented entry was uncommented, and the following
line was deleted, which explains why I can't log in. This is so bizarre
that it almost looks like it was done on purpose (was it ? :))
Anyone seen this? Any ideas?
Thanks to everyone who sent me responses on my original issue. I got it resolved and it's humming along! =)
I've been doing some benchmarking on my Windows-on-Xen instance and the numbers are pretty low for certain kinds of tests. Is there a general assumption about the performance that one can expect from a Xen-instance (i.e. 70% of the speed of a real system, etc.)? I've got my virtual machine running with 1 virtual cpu and 2gb of RAM, running windows xp.
in the virt-manager's new VM wizard there is a small alignment
inconsistency on the "Locating installation media" page for
paravirtualized machine. The second and third label are right aligned,
while the first (Install Media URL) is not. The included patch fixes