RU2690415C1 - Technology of automatic start of an operating system on a hardware platform with elements not supported by operating system modules when the computer is turned on - Google Patents

Abstract

FIELD: computer equipment.SUBSTANCE: invention relates to computer operating system start-up methods. Physical hardware platform hardware platform physical device unit is used to install software tools for emulating another hardware platform, based on which a separate section of this physical block device is installed guest operating system, containing modules that do not support hardware platform elements of a physical computer, without creating in this section a separate partition table. Software platform hardware emulation hardware is configured to transmit all packets corresponding to the open system interaction model network layer from the physical computer hardware to the guest operating system. Software platform hardware emulation hardware is configured to provide access to all computer input/output devices in the guest operating system. A configuration script is created in software tools for emulating a hardware platform for providing access in a guest operating system to devices connected via a universal serial bus. Software platform hardware emulation hardware is configured to automatically start the guest operating system when the computer is turned on.EFFECT: technical result is shorter time for launching a guest operating system on a hardware platform with elements not supported by guest operating system modules in a software platform hardware emulation environment.7 cl, 2 tbl

Description

The invention relates to the field of computing, and more precisely to methods of launching the operating system of the computer.

In the prior art a method for processing a resource, an operating system and a device (patent RU invention No. 2639693), the launch of the root operating system; the discovery through the root operating system of many physical resources; running through the root operating system hypervisor; Reception by the hypervisor from the root operating system of information representing a variety of physical resources; running through the hypervisor a virtual machine instance for the root operating system; initialization of the virtual machine using the state consistent with the information; resuming the operation of the root operating system so that the root operating system interacts indirectly with the mentioned plurality of physical resources through a virtual machine instance. The disadvantage of this technical solution is the impossibility of automatically starting the operating system on a hardware platform with elements that are not supported by the modules of the operating system when the computer is turned on.

The technical task of the claimed invention is to provide the ability to automatically start the operating system on a hardware platform with elements that are not supported by the modules of the operating system when the computer is turned on.

The solution of the technical problem is ensured by the fact that emulation software of another hardware platform is installed on the physical block device of the hardware platform of a physical computer, on the basis of which a guest operating system is installed on a separate partition of this physical block device; , without creating a separate partition table in this section; then, software emulation of the hardware platform is configured to transfer all packets corresponding to the network layer of the open systems interaction model from the physical computer hardware to the guest operating system; after that, software emulation of the hardware platform is configured to provide access to all computer I / O devices in the guest operating system; then a configuration script is created in the hardware emulation software of the hardware platform to provide access to the guest operating system to devices connected via a universal serial bus; then the software is configured for the guest operating system, setting the resolution of the virtual graphics adapter to match the recommended resolution of the computer display; further, it prohibits the use of key combinations that switch virtual desktops of the hardware emulation software of the hardware platform to prevent switching the operation of input-output devices from the guest operating system to the hardware emulation software of the hardware platform; then the hardware platform emulation software is configured to automatically start the guest operating system when the computer is turned on.

To extend the functionality of using the technology, the installation of a guest operating system containing modules that do not support elements of the physical computer's hardware platform can be performed on a separate partition of the physical block device of the computer with installed software emulating the computer's hardware platform with the creation of a separate partition table in this section.

To extend the functionality of using technology, the installation of a guest operating system containing modules that do not support elements of the hardware platform of a physical computer can be performed on a partition of a separate physical block device of a computer without software emulation software installed on it, creating a separate partition table in this section .

To extend the functionality of using the technology, the installation of a guest operating system containing modules that do not support elements of the hardware platform of a physical computer can be performed on a partition of a separate physical block device of a computer without software installed on it emulating the hardware platform of a computer without creating a separate partition table in this partition .

To extend the functionality of using the technology, the installation of a guest operating system that contains modules that do not support elements of the hardware platform of a physical computer can be performed on a separate physical block device of a computer without software installed on it that emulates a computer hardware platform and creates a separate partition table.

To extend the functionality of using the technology, the installation of a guest operating system that contains modules that do not support elements of the hardware platform of a physical computer can be performed on a separate physical block device of a computer without software installed on it emulating the hardware platform of the computer without creating a separate partition table.

To extend the functionality of using technology, the installation of a guest operating system containing modules that do not support elements of the physical computer's hardware platform can be performed on a virtual hard disk.

Technical result achieved is a reduction in the launch time of the guest operating system on a hardware platform with elements that are not supported by the guest operating system modules in the hardware emulation software environment.

Description of the invention

The principle of operation:

1) The hardware emulation of another hardware platform is installed on the hardware platform of the physical computer with elements not supported by the modules of the operating system;

2) In the emulation software of another hardware platform, a guest operating system is installed that cannot be installed on the physical computer hardware platform with elements not supported by the operating system modules by the usual method due to incompatibility;

3) The installed emulation software of another hardware platform and the guest operating system installed in it are configured so that the end user does not notice the layer between the hardware platform of the physical computer with elements not supported by the operating system modules and the guest operating system in the face of emulation software of another hardware platform and works with a ready-made solution as with a normal computer with an operating system installed on it directly, as well as spends time on the separate execution of necessary components.

• The hardware platform of a physical computer with elements not supported by the modules of the operating system is a computer in which there are elements (chips, devices) that are not supported by the modules of certain operating systems.

An example of such elements:

Intel Core 6 generation processors;

Intel 100th series chipsets;

Intel UHD 630 integrated graphics.

• The guest operating system is an operating system, usually more than 6 years old, not having modules for supporting specific equipment, and also not being able to upgrade for any reason.

An example of such operating systems:

MSVS 3.0 rev. 04;

MSVS 3.0 rev. 06;

Astra Linux Special Edition 1.2.

• emulation software of another hardware platform is a solution to provide emulation services running under its control, emulating real (physical) hardware of a specific computer and managing these emulated machines, allocating and freeing resources for them.

An example of such emulation software is another hardware platform:

Horizon-Sun 1.0.

Automatic launch of the operating system on the hardware platform of a physical computer with elements not supported by the operating system modules, when the computer is turned on, it is necessary when it is necessary to start the operating system on a hardware platform with elements that are not supported by the modules of the operating system so that the user does not waste time on a separate launch of the necessary components.

Also, the invention solves the problem of incompatibility of outdated operating systems with chipsets of modern motherboards. Example:

MSVS 3.0 rev. 04 is not compatible with Intel chipsets from the 7th series inclusive.

MSVS 3.0 rev. 06 is not compatible with Intel chipsets starting from the 9th series inclusive.

Or another OS is incompatible with any element of the computer on which its operation is required.

An example implementation of the invention

As an example, step-by-step implementation of the invention is provided using the following components:

• hardware platform of a physical computer with elements not supported by operating system modules (hereinafter referred to as hardware platform):

a computer with an Intel Core 6 generation processor and Intel 100th series chipset;

• guest operating system (hereinafter referred to as the operating system or OS):

MSVS 3.0 rev. 04;

• software emulation of another hardware platform (hereinafter referred to as the Hypervisor):

Horizon-Sun 1.0.

1.1. Install Horizon-Sun 1.0.

- Drive breakdown:

For example, a hard disk size of 256GB.

The disk is broken by the GParted utility, the following structure is created:

MBR table

1.2. Installing MSVS (or another OS) on a hard disk partition (/ dev / sda and not / dev / sdaX). Perform only after paragraph 1.6.

For example, MSVS and Horizon vl

In VM manager, select ready VM

Create a RAW disk and install the MASS into it, the size is not important, you can choose 8GB. It is not necessary to install with only one partition - /, neither swap, nor / home.

Connect ready RAW image with installed MSWS in Horizon. For this:

Install via qemu-nbd:

# modprobe nbd max_part = 63

# qemu-nbd -c / dev / nbd0 image_raw_im.img

# partprobe / dev / nbd0

You can view the sections on the / dev / nbd0 disk as follows:

# fdisk -1 / dev / nbd0

The output will be something like:

/ dev / nbd0p1 ... - this is our partition where the / MAWS was installed

Perform sector-by-sector copying of the nbd0p1 partition to the required partition, we have / dev / sda3:

# dd if = / dev / nbd0p1 of = / dev / sda3 bs = 4M

Wait until copying is completed and install / dev / sda3 to / mnt:

# mount / dev / sda3 / mnt

The mount should succeed, and in the / mnt directory there will be / transferred to MAWS.

Fix it in / mnt / ... / etc / fstab (change hda1 to hda), / etc / lilo (the path should point to the current disk, this is hda).

In the VM manager, replace the RAW disk with the physical partition / dev / sda3, connect the installation MSVS. Turn on the VM and boot from the installation disk, go to the disk selection stage, do not select it, otherwise the partition table will be overwritten, which we do not need. Switch to another console via Ctrl + Alt_F2. Create a folder / 1 (it is important to create a directory, and not to use ready, for example / mnt). Mount to / 1 disk / dev / hda, and execute:

# mount --bind / proc / 1 / proc

# mount --bind / dev / 1 / dev

# mount --bind / sys / 1 / sys (in MSVS / sys not, but if you do for another OS, you will need it)

Go to / 1 and execute chroot. Run bash:

# / bin / bash

Run lilo:

# / sbin / lilo

The output should not contain errors.

Disconnect the installation disk from the VM and reboot.

To check, turn off the VM and mount / dev / sda3 in / mnt in Horizon. Mounting should occur successfully and in / mnt will be observed / from MSWS.

Unmount / mnt and perform the FS expansion for the whole partition:

# resize2fs / dev / sda3

A message may appear that you must first execute fsck ... Execute and repeat resize2 ... It should complete successfully.

To check if the VM with MSVS is enabled and execute df -h, the entire available partition size of / dev / sda3 (MSWS sees it as / dev / hda) should be displayed, and not the previously allocated 8GB that were in the RAW image.

1.3. Network configuration:

- Network br0:

Create the file / etc / sysconfig / network-scripts / ifcfg-br0:

ONBOOT = yes

BOOTPROTO = static

DEVICE = br0

TYPE = Bridge

MTU = 1500

NOZEROCONFIG = no

USERCTL = yes

DELAY = 0

IPADDR = 10.238.38.10 # any untrusted address, so as not to overlap with popular subnets

NETMASK = 255.255.255.0

This interface does not have to "see" other networks / nodes, as long as it is configured.

Create the / etc / sysconfig / network-scripts / ifcfg-eth0 file:

DEVICE = eth0

ONBOOT = yes

BRIDGE = br0

- Network br1:

Create the / etc / sysconfig / network-scripts / ifcfg-br1 file:

ONBOOT = yes

BOOTPROTO = static

DEVICE = br1

TYPE = Bridge

MTU = 1500

NOZEROCONFIG = no

USERCTL = yes

DELAY = 0

IPADDR = 10.238.38.11 # any untrusted address, so as not to overlap with popular subnets

NETMASK = 255.255.255.0

Create the / etc / sysconfig / network-scripts / ifcfg-eth0 file:

DEVICE = eth0

ONBOOT = yes

BRIDGE = br0

This interface does not have to "see" other networks / nodes, as long as it is configured.

Run:

/etc/init.d/networking restart

Check, it should be like “br0 8000.08608ee7dc58 no eth0”:

brctl show

1.4. Enabling the ability to run third-party scripts:

ATTENTION! Scripts, like any other files, should not be added to the / usr directory

In the /etc/rc.d/rc.sysinit file, comment out all lines starting with:

# --------------- IMA start ----------------

and ending with:

--------------- IMA end ------------------

Reboot host

1.5. Setting up the touchpad to work in the guest VM:

Bring the file /etc/udev/rules.d/99-mouse-power-on.rules to the form:

ACTION == "add", SUBSYSTEM == "usb", ENV {ID_CLASS} == "mouse", TEST == "power / control", ATTR {power / control} = "off ''

ATTENTION! Without this setting, the touchpad is guaranteed not to work. But even with it, the touchpad may sometimes appear inoperable, to fix it, you need to restart the host

1.6. Creating a virtual machine:

Run the command:

virt-install --connect qemu: /// system -n msvs2 --ram 4096 --arch = i586 --vcpus = 2 --cpu core2duo --os-type linux --boot cdrom, hd, menu = on - -disk pool = vm_store, cache = none, size = 50, format = qcow2 --network = bridge: br0, model = e1000 --graphics spice, listen = 0.0.0.0, keymap = en --noautoconsole --watchdog default, action = reset --virt-type = kvm --autostart -cdrom = / dev / cdrom

All the options here are clear.

Further actions will be described for working with port 5900, which is assigned automatically.

For the machine, you can configure a specific port. For this you need to edit it.

config in /etc/libvirt/qemu/msvs2.xml: <graphics type = 'spice' port = '5938' autoport = 'no' listen = '0.0.0.0'

To install the MAWS under clause 1.2. Add the created domain to virsh autoload. In the virtual machine manager, connect all network interfaces (network bridges), they may not be detected immediately and you will have to restart the host before.

1.7. Setting graphics inside the guest VM.

Inside the guest VM, edit the /etc/X11/xorg.conf file:

In the section "Monitor" fix:

HorizSync at 31.5-90

VertRefresh at 50-180

Add the line Option "PrefferedMode" "1920x1080_60.0"

comment out Option "dpms"

In the section "Device" fix:

comment out the Identifier lines

Driver

Vendorname

BoardName

add Identifier "Device0"

Add Driver "vmware"

In the "Screen" section fix:

comment out the Device lines

DefaultDepth

Depth

Modes

add Device "Device0"

Add DefaultDepth "16"

add Depth 16

Add Modes "1920x1080"

Save changes and turn off VM. Also turn off the VM in virsh. After that, start changing the VM config, to do this, edit the file /etc/libvirt/qemu/msvs2.xml (make a copy in advance):

Change the video card in the domain:

In file

/etc/libvirt/qemu/msvs2.xml

change section

<video>

on:

<video>

<model type = 'vmvga' vram = '65536' heads = '1' />

<address type = 'pci' domain = '0x0000' bus = '0x00' slot = '0x02' function = '0x0' />

</ video>

1.8. Setting up automatic probros USB devices from the host to the guest VM:

ATTENTION! This feature will work only after turning on the host. All USB devices connected to the host before it is turned on will not be forwarded to the VM.

All USB devices connected after switching on the host and the VM will be forwarded to the VM.

There is a feature - different USB devices with the same PID and VID will not be connected at the same time, they should be connected in turn.

Create a UDEV rule /etc/udev/rules.d/97-udev-kvmusbattach.rules:

ACTION == "add", SUBSYSTEM == "usb", ENV {DEVTYPE} == "usb_device", RUN + = "/ etc / udev / attach.sh $ env {ID_VENDOR_ID} $ {ID_MODEL_ID}"

Create a UDEV rule /etc/udev/rules.d/97-udev-kvmusbdetach.rules:

ACTION == "remove", SUBSYSTEM == "usb", ENV {DEVTYPE} == "usb_device", RUN + = "/ etc / udev / detach.sh $ env {ID_VENDOR_ID} $ {ID_MODEL_ID}"

Create a script in /etc/udev/attach.sh:

#! / bin / bash

touch /root/usbdev_${l}:${2}.xml

cat << EOF> /root/usbdev_${l}:${2}.xml

<hostdev mode = 'subsystem' type = 'usb'>

<source>

<vendor id = '0x $ {l}' />

<product id = '0x $ {2}' />

</ source>

</ hostdev>

EOF

/ usr / bin / virsh attach-device msvs2 /root/usbdev_${ll\\\:${2}.xml

exit 0

Create a script in /etc/udev/detach.sh:

#! / bin / bash

virsh detach-device msvs2 /root/usbdev_${l}\:${2}.xml

rm /root/usbdev_${ll\\\:${2}.xml

exit 0

After that, all USB devices connected after turning on the host and the VM will be forwarded to the VM.

1.9. Configure forwarding COM ports from host to guest VM:

In the virtual machine manager, go to the msvs2 domain settings and select:

Add hardware -> serial port -> type physical host character device, then specify ttySX

It is possible to determine the list of COM ports using the command:

dmesg | grep tty

In the output ports will be labeled ttySX

1.10. Sound settings in the guest VM.

In the virtual machine manager, go to the msvs2 domain settings and select:

Sound card -> Select AC97

In the guest VM, reboot and agree to auto-tune the new equipment. After that, run alsaconf and agree with the proposed.

After that in alsamixer select the desired volume level.

On the host, configure the audio redirection from the application to the physical device (using pulseaudio):

ATTENTION! Built-in sound card is not supported in Horizon-Sun. It is proposed to use a USB sound card and external speakers / headphones.

In this case, you should connect a USB sound card before turning on the host.

In the / etc / xdg / lxsession / LXDE / autostart file add the line:

@pactl move-sink-input 1 0

Reboot host

1.11. Configuring the automatic launch of the guest VM:

ATTENTION! After applying this setting, you will not be able to access the host without a tool stick.

This setting will allow launching the guest VM to full screen without launching the host graphical table. An automatic shutdown of the host will also be added after shutting down the guest VM.

Create a /etc/xdg/lxsession/LXDE/auto.sh script with the contents:

#! / bin / bash

remote-viewer spice: //0.0.0.0: 5900 -f

poweroff

exit 0

Bring the file /etc/X11/xinit/xinitrc.d/60windowmanager to the form:

export LANG = en_RU.UTF-8

# / bin / startlxde

/etc/xdg/lxsession/LXDE/auto.sh

1.12. Disable Ctrl + Alt + FX:

Open / create the file /etc/X11/xorg.conf using the following command:

sudo -i gedit /etc/X11/xorg.conf

and add the following lines inside:

Section "ServerFlags"

Option "DontVTSwitch" "true"

Endsection

1.13. Change key combination to go to the host system:

In the VM manager, apply the appropriate setting.

Use LCtrl + LAlt + h

Achievable technical result - reducing the startup time of the operating system on a hardware platform with elements that are not supported by the modules of the operating system when the computer is turned on - is confirmed by the test results (Table 2).

Claims (7)

1. The method of launching the operating system on the hardware platform of a physical computer with elements not supported by the modules of the operating system, consisting in that the physical block device of the hardware platform of the physical computer installs software emulation of another hardware platform, on the basis of which a separate section of this physical block device is installed guest operating system containing modules that do not support elements of the hardware platform of the physical computer , without creating a separate partition table in this section; then, software emulation of the hardware platform is configured to transfer all packets corresponding to the network layer of the open systems interaction model from the physical computer hardware to the guest operating system; after which the software emulation hardware platform is configured to provide access to all computer I / O devices in the guest operating system; then a configuration script is created in the hardware emulation software of the hardware platform to provide access in the guest operating system to devices connected via a universal serial bus; then the software of the guest operating system is configured, which sets the resolution of the virtual graphics adapter to the recommended resolution of the computer display; further, it prohibits the use of key combinations that switch virtual desktops of the hardware emulation software of the hardware platform to prevent switching the operation of input-output devices from the guest operating system to the hardware emulation software of the hardware platform; then the hardware platform emulation software is configured to automatically start the guest operating system when the computer is turned on. 2. The method according to p. 1, characterized in that the installation of a guest operating system containing modules that do not support elements of the hardware platform of the physical computer is performed on a separate section of the physical block device of the computer with installed software emulating the hardware platform of the computer with creating in this section a separate partition tables. 3. The method according to p. 1, characterized in that the installation of a guest operating system containing modules that do not support elements of the hardware platform of the physical computer is performed on the partition of a separate physical block device of the computer without software installed on it emulating the hardware platform of the computer with the creation of section of a separate partition table. 4. The method according to p. 1, characterized in that the installation of a guest operating system containing modules that do not support elements of the hardware platform of the physical computer is performed on a partition of a separate physical block device of the computer without software installed on it emulating the hardware platform of the computer without creating this section of a separate partition table. 5. The method according to p. 1, characterized in that the installation of a guest operating system containing modules that do not support elements of the hardware platform of the physical computer is performed on a separate physical block device of the computer without software installed on it emulating the hardware platform of the computer with the creation of a separate partition table . 6. The method according to claim 1, wherein installing a guest operating system containing modules that do not support elements of the hardware platform of the physical computer is performed on a separate physical block device of the computer without software installed on it emulating the hardware platform of the computer without creating a separate partition table . 7. The method according to p. 1, characterized in that the installation of a guest operating system containing modules that do not support elements of the hardware platform of the physical computer, is performed on a virtual hard disk.