On 4 March 2019 4:21:46 PM GMT+05:30, "Mathew, Cherry G." wrote:
>Thank you both. Its unclear to me if the xl dmesg belongs to the
>hypervisor under which the shutdown malfunction occurred or not.
>
>Many Thanks.
In other words, how do I reproduce this bug ?
--
Sent from my phone. Please excuse
Thank you both. Its unclear to me if the xl dmesg belongs to the hypervisor
under which the shutdown malfunction occurred or not.
Many Thanks.
--
Sent from my phone. Please excuse my brevity.
It is almost identical, here is the full 'xl dmesg' output if it may
be of interest:
-
__ ___ _ _ __
\ \/ /___ _ __ | || | |___ / /_
\ // _ \ '_ \ | || |_ / / '_ \
/ \ __/ | | | |__ _| / /| (_) |
/_/\_\___|_| |_||_|(_)_/(_)___/
(XEN) [0.00] Xen
On Fri, 1 Mar 2019, Chavdar Ivanov wrote:
On 3/1/19 в 1:02 AM, Mathew, Cherry G.:
Would be could to know the dom0 versions it broke under, please.
The DOMU is tCentOS 7.6, the virtualizer is XCP-NG v.7.6.
That's not what Cherry's asking for.
Try the output of xl dmesg on XCP-NG. Near the to
On 3/1/19 в 1:02 AM, Mathew, Cherry G.:
Would be could to know the dom0 versions it broke under, please.
The DOMU is tCentOS 7.6, the virtualizer is XCP-NG v.7.6.
On 1 March 2019 6:32:26 AM GMT+05:30, "Mathew, Cherry G." wrote:
>Would be could to know the dom0 versions it broke under, please.
And also the hypervisor version please.
Many thanks ,
Cherry
--
Sent from my phone. Please excuse my brevity.
Would be could to know the dom0 versions it broke under, please.
--
Sent from my phone. Please excuse my brevity.
I tried with the overnight build, it seems to be OK now, works on at
least two -current XEN3_DOMU guest. There were a few XCP-NG patches in
between, though.
On Wed, 20 Feb 2019 at 03:26, Cherry G.Mathew wrote:
>
> Chavdar Ivanov writes:
>
> > Yes, it is. This happens on:
> > ...
> > uname -a
>
Chavdar Ivanov writes:
> Yes, it is. This happens on:
> ...
> uname -a
> NetBSD nbuild.lorien.lan 8.99.34 NetBSD 8.99.34 (XEN3_DOMU) #0: Tue
> Feb 19 13:23:54 GMT 2019
> sysbu...@nbuild.lorien.lan:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOMU
> amd64
>
>
Thank
Yes, it is. This happens on:
...
uname -a
NetBSD nbuild.lorien.lan 8.99.34 NetBSD 8.99.34 (XEN3_DOMU) #0: Tue
Feb 19 13:23:54 GMT 2019
sysbu...@nbuild.lorien.lan:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOMU
amd64
On Tue, 19 Feb 2019 at 16:39, Cherry G. Mathew
On 19 February 2019 11:31:37 PM MYT, Martin Husemann wrote:
>On Tue, Feb 19, 2019 at 03:28:23PM +, Chavdar Ivanov wrote:
>> Any bells ringing?
>
>I think this already has been fixed by Cherry?
>
>Martin
I believe so.
Chavdar, I'd be interested to know if this is happening in -current.
Than
On Tue, Feb 19, 2019 at 03:28:23PM +, Chavdar Ivanov wrote:
> Any bells ringing?
I think this already has been fixed by Cherry?
Martin
Hi,
I run a few NetBSD VMs under XCP-NG in PV mode, booting unmodified
XEN3_DOMU of their respective releases. One is an amd64 8_STABLE from
december 2018 vintage, which continues to properly
shutdown/poweroff/reboot. The others closely follow -current, right
now running a kernel and userland from
13 matches
Mail list logo
