Date: Fri, 15 Jan 2021 15:38:57 +0100 From: "Lizbeth Mutterhunt, PhD" <lizbethmutterhunt@gmail.com> To: freebsd-xen@freebsd.org Subject: Fwd: Re: either xen or custom Message-ID: <5536984.Zv9zXsTiuT@freebsd-current>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --nextPart2518611.TYJnH3iKXO Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Op Donnerstag, 14. J=E4nner 2021 09:21:09 CET schreef u: > On Sun, Dec 13, 2020 at 12:11:40AM +0100, lizbethmutterhunt@gmail.com wro= te: > > to make a long story short: either I get a lock (hard to avoid, not to = be > > unlimited with ulimit -l unlimited) or a boot of xen and a blank screen > > with reboot after a 10 seconds with vga=3Dcurrent. > > Hello, Hello Roger,=20 > Sorry for the delay on the reply. I'm afraid I will need more info in > order to help diagnose your issue. no matter, was occupied other ways; using VirtualBox at the moment, slow an= d=20 the hypervisor tends to make long waiting-times...=20 > How do you get the lock that you mention? Is it booting Xen, or just > plain FreeBSD? It's booting XEN, but not the CURRENT-kernel afterwards or it boots the=20 CURRENT but not xen. I have in /boot/loader.conf xen_kernel=3D"/boot/xen" xen_cmdline=3D"dom0_mem=3D4048M dom0_max_vcpus=3D4 dom0=3Dpvh com1=3D115200= ,8n1=20 guest_loglvl=3Dall loglvl=3Dall" iommu=3D"force,no-intremap" if_tap_load=3D"YES" console=3Dvga,com1 boot_multicons=3D"YES" boot_serial=3D"YES" console=3D"comconsole,vidconsole" vmm_load=3D"YES" vga=3Dcurrent and in /etc/rc.conf: xencommons_enable=3D"YES" cloned_interfaces=3D"bridge0" ifconfig_bridge0=3D"addm bge0 SYNCDHCP" ifconfig_bge0=3D"up" sudo ulimit -l unlimited sudo uname -a =46reeBSD freeBSD-CURRENT 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r368997: Tue= Jan=20 12 13:46:33 CET 2021 lizbeth@freeBSD-CURRENT:/usr/obj/usr/src/amd64.amd= 64/ sys/LIZBETH amd64 it's a no-debug kernel! /etc/ttys xc0 "/usr/libexec/getty Pc" xterm on secure when booting without XEN I get the following with 'xl dmesg' xencall: error: Could not obtain handle on privileged command interface /de= v/ xen/privcmd: No such file or directory libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle: No suc= h=20 file or directory cannot init xl context a normal boot without xen is on pastebin (VERBOSE_SYSINIT=3D2) https://pastebin.com/RN1SYXdW > Do you have a serial console attached to the box so that we could > see the log of Xen and FreeBSD booting? how to? every time I boot into xen I have to zpool import -f and mount it f= rom=20 rescue CD. Is there a log from the last boot somewhere? I duckduckgo'd a bi= t=20 but couldn't find anything else than the dmesg. As it is not a kernel crash= =20 there's nothing in /var/crash and on /var/run I have the running boot insid= e.=20 Maybe you tell me how to show the log from the serial console; btw, I tried= =20 both ways, only serial, only bios or both --- no matter, xen's booting,=20 screen's blanking for the "normal" kernel but nothing happens but a sudden= =20 reboot. Is it on the /var/* somewhere when booting from resucue? btw, the=20 current images from beginning 2021 don't boot, turning root sign but blank= =20 screen, no boot menue but steady access to USB-stick.=20 I thought that the XEN-log should be somewhere in the boot-directory but it= 's=20 empty but asking for IUMMO support when using both consoles, when serializi= ng=20 xen boots successfully but rebooting afterwards.=20 =20 > Thanks, Roger. I have to tell you thank you.=20 byebye,=20 lizbeth --nextPart2518611.TYJnH3iKXO Content-Type: message/rfc822; name="Re: either xen or custom" From: "Lizbeth Mutterhunt, PhD" <lizbethmutterhunt@gmail.com> To: Roger Pau =?ISO-8859-1?Q?Monn=E9?= <roger.pau@citrix.com> Cc: port-xen@netbsd.org Subject: Re: either xen or custom Date: Thu, 14 Jan 2021 14:49:26 +0100 Message-ID: <7599180.bYQgcRI8ro@freebsd-current> X-Face: jLp,#|qe`P=tm$C@l^;H-:@l=wrh`EUh90+Zq8&japTr{$pA+r^:ne~/Tml>0T8#5?+o&^ zKe%^Q*b52{qhsO_kOj/P.vmm:r`teihTj)qZi]u{qX=h=MhLU%OXcDp])XtYFLu?PS In-Reply-To: <20210114082109.scxr2xwkrzvpb4qn@Air-de-Roger> References: <2345596.0dHE6SNnxz@freebsd-current> <20210114082109.scxr2xwkrzvpb4qn@Air-de-Roger> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Op Donnerstag, 14. J=E4nner 2021 09:21:09 CET schreef u: > On Sun, Dec 13, 2020 at 12:11:40AM +0100, lizbethmutterhunt@gmail.com wro= te: > > to make a long story short: either I get a lock (hard to avoid, not to = be > > unlimited with ulimit -l unlimited) or a boot of xen and a blank screen > > with reboot after a 10 seconds with vga=3Dcurrent. >=20 > Hello, Hello Roger,=20 > Sorry for the delay on the reply. I'm afraid I will need more info in > order to help diagnose your issue. no matter, was occupied other ways; using VirtualBox at the moment, slow an= d=20 the hypervisor tends to make long waiting-times...=20 > How do you get the lock that you mention? Is it booting Xen, or just > plain FreeBSD? It's booting XEN, but not the CURRENT-kernel afterwards or it boots the=20 CURRENT but not xen. I have in /boot/loader.conf xen_kernel=3D"/boot/xen" xen_cmdline=3D"dom0_mem=3D4048M dom0_max_vcpus=3D4 dom0=3Dpvh com1=3D115200= ,8n1=20 guest_loglvl=3Dall loglvl=3Dall" iommu=3D"force,no-intremap" if_tap_load=3D"YES" console=3Dvga,com1 boot_multicons=3D"YES" boot_serial=3D"YES" console=3D"comconsole,vidconsole" vmm_load=3D"YES" vga=3Dcurrent and in /etc/rc.conf: xencommons_enable=3D"YES" cloned_interfaces=3D"bridge0" ifconfig_bridge0=3D"addm bge0 SYNCDHCP" ifconfig_bge0=3D"up" sudo ulimit -l unlimited sudo uname -a =46reeBSD freeBSD-CURRENT 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r368997: Tue= Jan=20 12 13:46:33 CET 2021 lizbeth@freeBSD-CURRENT:/usr/obj/usr/src/amd64.amd= 64/ sys/LIZBETH amd64 it's a no-debug kernel! /etc/ttys xc0 "/usr/libexec/getty Pc" xterm on secure when booting without XEN I get the following with 'xl dmesg' xencall: error: Could not obtain handle on privileged command interface /de= v/ xen/privcmd: No such file or directory libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle: No suc= h=20 file or directory cannot init xl context a normal boot without xen is on pastebin (VERBOSE_SYSINIT=3D2) https://pastebin.com/RN1SYXdW > Do you have a serial console attached to the box so that we could > see the log of Xen and FreeBSD booting? how to? every time I boot into xen I have to zpool import -f and mount it f= rom=20 rescue CD. Is there a log from the last boot somewhere? I duckduckgo'd a bi= t=20 but couldn't find anything else than the dmesg. As it is not a kernel crash= =20 there's nothing in /var/crash and on /var/run I have the running boot insid= e.=20 Maybe you tell me how to show the log from the serial console; btw, I tried= =20 both ways, only serial, only bios or both --- no matter, xen's booting,=20 screen's blanking for the "normal" kernel but nothing happens but a sudden= =20 reboot. Is it on the /var/* somewhere when booting from resucue? btw, the=20 current images from beginning 2021 don't boot, turning root sign but blank= =20 screen, no boot menue but steady access to USB-stick.=20 I thought that the XEN-log should be somewhere in the boot-directory but it= 's=20 empty but asking for IUMMO support when using both consoles, when serializi= ng=20 xen boots successfully but rebooting afterwards.=20 =20 > Thanks, Roger. I have to tell you thank you.=20 byebye,=20 lizbeth --nextPart2518611.TYJnH3iKXO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5536984.Zv9zXsTiuT>