Fedora HVM install - text console

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Fedora HVM install - text console

G Crowe
Hi,
    I am trying to install Fedora into a HVM without needing VNC. This
would entail completing the entire installation process via "virsh
console".

    I have managed to convert a running HVM to use the xen console for
both grub and bootup so that I can use "virsh console". I have been
able to install paravirtualised linux using the "virt-install" utility
which completes the installation without use of VNC.

As far as installing a HVM, the closest I have managed to get is by
setting up a VNC window, booting from the install ISO image and altering
the GRUB command line to add "console=ttyS0". This allows me to then close
the VNC window and progress through the rest of the install via "virsh
console" (it even adds the "console=ttyS0" to the installed version, and
sets up grub for serial as well).

Is there any way to get the initial install ISO's grub menu to appear on
ttyS0 so that I can install without needing VNC at all? Preferably without
having to modify the ISO, as it is the one downloaded from Fedora's
website).


Thanks

GC



_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fedora HVM install - text console

George Dunlap-4
On Sun, Oct 25, 2015 at 8:43 AM, G Crowe <[hidden email]> wrote:

> Hi,
>     I am trying to install Fedora into a HVM without needing VNC. This
> would entail completing the entire installation process via "virsh
> console".
>
>     I have managed to convert a running HVM to use the xen console for
> both grub and bootup so that I can use "virsh console". I have been
> able to install paravirtualised linux using the "virt-install" utility
> which completes the installation without use of VNC.
>
> As far as installing a HVM, the closest I have managed to get is by
> setting up a VNC window, booting from the install ISO image and altering
> the GRUB command line to add "console=ttyS0". This allows me to then close
> the VNC window and progress through the rest of the install via "virsh
> console" (it even adds the "console=ttyS0" to the installed version, and
> sets up grub for serial as well).
>
> Is there any way to get the initial install ISO's grub menu to appear on
> ttyS0 so that I can install without needing VNC at all? Preferably without
> having to modify the ISO, as it is the one downloaded from Fedora's
> website).

This is really a question about the Fedora installer -- your best bet
is to ask on a fedora-specific list.

 -George

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Xen died - Fedora upgrade from 21 to 26

G Crowe
In reply to this post by G Crowe
Hi,
     I am trying to upgrade my Xen host (Dom0) and are having troubles
getting it to work.

I think that it has booted into a kernel that supports Xen (running 'xl
info' does list some Xen capabilities), but I have three problems (that
I have found so far).

Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result
all 'virsh' commands fail). It is set to auto-start (systemctl enable
libvirtd), and can be manually started (systemctl start libvirtd), but
it will not auto-start on reboot.

Secondly, Once I have manually started libvirtd, when I try to define a
domain it gives me an error "could not find capabilities for arch=x86_64
domaintype=xen" and I haven't yet been able to define any domains. This
domain type works fine on Fedora 21.

Thirdly, I am unable to convert to/from xml config format, it gives me
the error "error: invalid argument: unsupported config type xen-xl"
however the format "xen-xl" works fine on the Fedora 21 machine.

I had these same issues when I tried to upgrade to Fedora 25 and assumed
that something had been broken and so abandoned further attempts to
upgrade, however since Fedora 26 is the same I am now assuming that I
have stuffed something up myself (or missed something).

Fedora 21 uses kernel 3.19.3 and xen 4.4.1
Fedora 26 uses kernel 4.11.8 and xen 4.8.1

I have tried following the info on
https://wiki.xen.org/wiki/Fedora_Host_Installation but it appears to be
out of date now (I used this site when I started using Xen under Fedora
19, and when I upgraded to Fedora 21)

Does anyone have any suggestions? outputs from "xl info" and the domain
config are below. I have also tried disabling SELinux, but it made no
difference.


Thanks

GC

-----------------------------------------------
On the fedora 26 box.....
# xl info
host                   : family.mydomain.mytld
release                : 4.11.8-300.fc26.x86_64
version                : #1 SMP Thu Jun 29 20:09:48 UTC 2017
machine                : x86_64
nr_cpus                : 4
max_cpu_id             : 3
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2712
hw_caps                :
b7ebfbff:77faf3bf:2c100800:00000121:0000000f:009c67af:00000000:00000100
virt_caps              : hvm hvm_directio
total_memory           : 8072
free_memory            : 128
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 8
xen_extra              : .1
xen_version            : 4.8.1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          :
xen_commandline        : placeholder
cc_compiler            : gcc (GCC) 7.0.1 20170421 (Red Hat 7.0.1-0.15)
cc_compile_by          : mockbuild
cc_compile_domain      : [unknown]
cc_compile_date        : Wed May  3 21:23:49 UTC 2017
build_id               : 1c6e5a40165e05837303942b54757ae1f2d5033d
xend_config_format     : 4

---------------------------------------------------
# cat vmtest.xml
<domain type='xen' id='21'>
   <name>testVM</name>
   <memory unit='KiB'>2097152</memory>
   <currentMemory unit='KiB'>2097152</currentMemory>
   <vcpu placement='static'>1</vcpu>
   <os>
     <type arch='x86_64' machine='xenfv'>hvm</type>
     <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader>
     <boot dev='network'/>
   </os>
   <features>
     <acpi/>
     <apic/>
     <pae/>
   </features>
   <clock offset='variable' adjustment='0' basis='utc'/>
   <on_poweroff>destroy</on_poweroff>
   <on_reboot>restart</on_reboot>
   <on_crash>restart</on_crash>
   <devices>
     <interface type='bridge'>
       <mac address='02:02:00:03:00:00'/>
       <source bridge='enp1s0'/>
       <script path='vif-bridge'/>
     </interface>
     <serial type='pty'>
       <target port='0'/>
     </serial>
     <console type='pty'>
       <target type='serial' port='0'/>
     </console>
     <input type='mouse' bus='ps2'/>
     <input type='keyboard' bus='ps2'/>
     <graphics type='vnc' port='5901' autoport='no' listen='192.168.131.54'>
       <listen type='address' address='192.168.131.54'/>
     </graphics>
   </devices>
</domain>

--------------------------------------


_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Xen died - Fedora upgrade from 21 to 26

Fajar A. Nugraha-4
On Sun, Jul 23, 2017 at 4:59 PM, G Crowe <[hidden email]> wrote:
Hi,
    I am trying to upgrade my Xen host (Dom0) and are having troubles getting it to work.

I think that it has booted into a kernel that supports Xen (running 'xl info' does list some Xen capabilities), but I have three problems (that I have found so far).

Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result all 'virsh' commands fail). It is set to auto-start (systemctl enable libvirtd), and can be manually started (systemctl start libvirtd), but it will not auto-start on reboot.

Secondly, Once I have manually started libvirtd, when I try to define a domain it gives me an error "could not find capabilities for arch=x86_64 domaintype=xen" and I haven't yet been able to define any domains. This domain type works fine on Fedora 21.

Thirdly, I am unable to convert to/from xml config format, it gives me the error "error: invalid argument: unsupported config type xen-xl" however the format "xen-xl" works fine on the Fedora 21 machine.


All of those are libvirt related. You might have better luck asking on libvirt list.

Xen has its own domU configuration format, which you did not use.


    <type>hvm</type>

... as opposed to what you wrote

    <type arch='x86_64' machine='xenfv'>hvm</type>

... so that might be relevant. In any case, You might have better luck asking on libvirt list.

-- 
Fajar

_______________________________________________
Xen-users mailing list
[hidden email]
https://lists.xen.org/xen-users
Loading...