Description of problem:
python-virtinst and virt-manager don't work when creating FC4 para-virtual guests, but they only can create FC5/FC6 (x86_64) on my 64bit machine. I looked into some codes, and I found it looks for "images/xen" which is not in FC4 tree. (/usr/lib/python2.4/site-packages/virtinst/ParaVirtguest.py). I think it also looks for host's OS version to decide which version (32/64bit) will be installed.
[Wed Apr 18 16:15:45 2007] [error] [client 192.168.2.128] File does not exist: /var/www/html/fedora/core/4/i386/os/images/xen
[Wed Apr 18 16:47:58 2007] [error] [client 192.168.2.128] (70014)End of file found: mod_mime_magic: read failed from uncompress of /var/www/html/fedora/core/5/i386/os
/images/xen/vmlinuz
Version-Release number of selected component (if applicable):
python-virtinst-0.98.0-1.fc6
How reproducible:
Always
Steps to Reproduce:
1. launch virt-install or virt-manager
2. follow the instructions
3. it stops installation
Monday, July 02, 2007
Bugzilla Bug 237143
Description of problem:
virt-manager can install full-virtual guests by using CDROM mode, but cannot by using .iso file.
It can generate image file and config file, but stop at below:
HVMAssist BIOS, 1cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (5000 MBytes)
ata0 slave: Unknown device
ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
ata1 slave: Unknown device
CDROM boot failure code : 0004
Boot from CD-ROM failed
FATAL: Could not read the boot disk
My macheine is a Dell PE2950 (16G RAM)
Version-Release number of selected component (if applicable):
virt-manager-0.2.6-3.fc6
How reproducible:
Always
Steps to Reproduce:
1. launch virt-manager
2. follow the instruction of making full-virtual guest
3. after generating image file, it stops.
virt-manager can install full-virtual guests by using CDROM mode, but cannot by using .iso file.
It can generate image file and config file, but stop at below:
HVMAssist BIOS, 1cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (5000 MBytes)
ata0 slave: Unknown device
ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
ata1 slave: Unknown device
CDROM boot failure code : 0004
Boot from CD-ROM failed
FATAL: Could not read the boot disk
My macheine is a Dell PE2950 (16G RAM)
Version-Release number of selected component (if applicable):
virt-manager-0.2.6-3.fc6
How reproducible:
Always
Steps to Reproduce:
1. launch virt-manager
2. follow the instruction of making full-virtual guest
3. after generating image file, it stops.
Thursday, May 03, 2007
Supplement for FedoraXenQuickstartFC5/6
When we want to use "xm console vm-name/id" on fully-virtualized VMs, we can find solution on http://fedoraproject.org/wiki/FedoraXenQuickstartFC6. However, it doesn't work if you don't do some changes in the guest.
Beside above information from Fedora, we have to do below changes:
Fullyvirt guest serial console access
Fully-virtualized guest OS will automatically have a serial console configured, but the guest kernel will not be configured to use this out of the box. To enable the guest console in a Linux fully-virt guest, edit the /etc/grub.conf in the guest and add 'console=ttyS0 console=tty0'. This ensures that all kernel messages get sent to the serial console, and the regular graphical console. The serial console can then be access in same way as paravirt guests:
# xm console
Alternatively, the graphical virt-manager program can display the serial console. Simply display the 'console' or 'details' window for the guest & select 'View -> Serial console' from the menu bar.
Beside above information from Fedora, we have to do below changes:
# vi /etc/inittab
add
0:2345:respawn:/sbin/mingetty tty0
S0:2345:respawn:/sbin/mingetty ttyS0
in that file.
# init q
# vi /etc/securetty
add tty0 and ttyS0 in that file.
Tuesday, February 06, 2007
Get Linux Information
sysctl - configure kernel parameters at runtime
-a Display all values currently available.
-A Display all values currently available in table form.
getconf - get configuration values
help: help [-s] [pattern ...]
Display helpful information about builtin commands. If PATTERN is
specified, gives detailed help on all commands matching PATTERN,
otherwise a list of the builtins is printed. The -s option
restricts the output for each builtin command matching PATTERN to
a short usage synopsis.
# ulimit
unlimited
# umask
0022
-a Display all values currently available.
-A Display all values currently available in table form.
getconf - get configuration values
help: help [-s] [pattern ...]
Display helpful information about builtin commands. If PATTERN is
specified, gives detailed help on all commands matching PATTERN,
otherwise a list of the builtins is printed. The -s option
restricts the output for each builtin command matching PATTERN to
a short usage synopsis.
# ulimit
unlimited
# umask
0022
Monday, February 05, 2007
Koha on Fedora Core 6
Koha-2.2.7 works on LAMP, but we have to do some manual modification on a recent Linux distribution.
Firstly, you have to install enough Perl modules in terms of installation manual. On Fedora Core 6, you have to install some modules, such as ZOOM, Data::Random, etc., from the CPAN source code.
Secondly, you have to create some tables by yourself which are defined in koha.mysql, because they would not be created during the installation process, such as Koha.items, Koha.systempreference, etc. Especially you have to modify the create script of Koha.issues, because it uses a MySQL 5.0 reserved word "return" (it is not a reserved word in MySQL 4.1 and previous versions). According to , "reserved words are permitted as identifiers if you quote them". "MySQL allows some keywords to be used as unquoted identifiers because many people previously used them. Examples are those in the following list: ACTION BIT DATE ENUM NO TEXT TIME TIMESTAMP", so you only need to quote the `return`, and leave the "timestamp" unquoted.
Firstly, you have to install enough Perl modules in terms of installation manual. On Fedora Core 6, you have to install some modules, such as ZOOM, Data::Random, etc., from the CPAN source code.
Secondly, you have to create some tables by yourself which are defined in koha.mysql, because they would not be created during the installation process, such as Koha.items, Koha.systempreference, etc. Especially you have to modify the create script of Koha.issues, because it uses a MySQL 5.0 reserved word "return" (it is not a reserved word in MySQL 4.1 and previous versions). According to , "reserved words are permitted as identifiers if you quote them". "MySQL allows some keywords to be used as unquoted identifiers because many people previously used them. Examples are those in the following list: ACTION BIT DATE ENUM NO TEXT TIME TIMESTAMP", so you only need to quote the `return`, and leave the "timestamp" unquoted.
Friday, February 02, 2007
A Typo In SSHD Man Page
OPENSSH 4.3p2 in Fedora Core 6 said:
However I found it does work with ~/.ssh/authorized_keys2 when you don't setup "AuthorizedKeysFile" in /etc/ssh/sshd_config.
AUTHORIZED_KEYS FILE FORMAT
~/.ssh/authorized_keys is the default file that lists the public keys that are permitted for RSA authentication in pro-tocol version 1 and for public key authentication (PubkeyAuthentication) in protocol version 2. AuthorizedKeysFile may be used to specify an alternative file.
However I found it does work with ~/.ssh/authorized_keys2 when you don't setup "AuthorizedKeysFile" in /etc/ssh/sshd_config.
Monday, January 22, 2007
How to Set a Linux Host Name in Office
We have a Microsoft dynamic DNS server in the office, so you can dynamically register your host name when you get the dhcp IP address. Your Windows system can get it automatically, while your Linux system should do some configuration.
For Debian you need add some items in /etc/interfaces. For more info in Debian, see "man interfaces" and scroll down to "The dhcp Method".
For Fedora Core you will do something below:
Then restart your network, it should be ok.
For Debian you need add some items in /etc/interfaces. For more info in Debian, see "man interfaces" and scroll down to "The dhcp Method".
For Fedora Core you will do something below:
/etc/sysconfig/network
HOSTNAME=YourLinuxHostName
/etc/sysconfig/networking/devices/ifcfg-eth0
DHCP_HOSTNAME=YourLinuxHostName
Then restart your network, it should be ok.
Thursday, January 18, 2007
Argument list too long
When I execute the command:
Q: What's the problem?
A: "The UNIX operating system traditionally has a fixed limit for the amount of memory that can be used for a program environment and argument list combined."
If I include "/media/dvd/Fedora" in the list, it would exceed 131072. Reducing PATH name or using Shell script can run those commands correctly.
# ls /media/dvd/Fedora/RPMS/*.rpm
bash: /bin/ls: Argument list too long
Q: What's the problem?
A: "The UNIX operating system traditionally has a fixed limit for the amount of memory that can be used for a program environment and argument list combined."
# getconf ARG_MAX
131072
# cd /media/dvd/Fedora/
# ls RPMS/*.rpm|wc
2931 2931 116609
If I include "/media/dvd/Fedora" in the list, it would exceed 131072. Reducing PATH name or using Shell script can run those commands correctly.
Subscribe to:
Posts (Atom)