From: Marcin Cieslak <saper@saper.info>
To: "Roger Pau Monné" <royger@FreeBSD.org>
Cc: freebsd-xen@FreeBSD.org, freebsd-virtualization@freebsd.org,
xen-devel@lists.xenproject.org
Subject: Re: HEADS UP: Imported Xen 4.7 and blkback changes - domU respawning on_crash
Date: Wed, 8 Jun 2016 22:35:22 +0000 [thread overview]
Message-ID: <alpine.BSF.2.11.1606082229190.2130__46478.8757883527$1465425407$gmane$org@z.fncre.vasb> (raw)
In-Reply-To: <alpine.BSF.2.11.1606082204080.2130@z.fncre.vasb>
On Wed, 8 Jun 2016, Marcin Cieslak wrote:
> On Fri, 3 Jun 2016, Roger Pau Monné wrote:
>
> > Hello,
> >
> > First of all, this message is only relevant to those that use FreeBSD as
> > Dom0 (host), not as a DomU (guest), so don't panic.
> >
> > I've imported the latest Xen version (4.7-rc4) into the ports tree, it's
> > still not the final version, but it's quite close, so we better start
> > testing it to make sure it works fine with FreeBSD.
One issue maybe unrelated to FreeBSD:
This domain:
builder = "hvm"
memory = 4096
vcpus = 2
name = "Windows2016"
disk = [
'/dev/zvol/zroot/windows0,raw,hda,w',
'/dev/zvol/zroot/vs2013,raw,hdb,w',
# '/root/win/install.iso,raw,hdc:cdrom,r'
]
boot = "c" # Boot to hard disk image
vnc = 2
#vnclisten = "0.0.0.0"
usbdevice = 'tablet'
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
acpi = 1
bios = 'ovmf'
vif = [ 'bridge=bridge0,mac=00:16:3e:5d:0d:48' ]
videoram=16
vga = "stdvga"
crashes because I didn't have ovmf image:
(d203) HVM Loader
(d203) Detected Xen v4.7.0-rc
(d203) Xenbus rings @0xfeffc000, event channel 1
(d203) Unknown BIOS ovmf, no ROM image found
(d203) *** HVMLoader bug at hvmloader.c:229
(d203) *** HVMLoader crashed.
But I seem unable to kill it with "xl destroy" - it keeps
respawning again:
Windows2016 211 4079 1 --p--- 0.0
Windows2016 213 4096 1 --psc- 0.0
(disappears)
Windows2016 221 4096 1 --psc- 0.0
(null) 221 147 1 --psc- 0.0
...
...
I have finally managed to snatch it by issuing this a few times, after
changing the "on_crash" to 'destroy':
# xl config-update Windows2016 xen/windows-run.cfg
WARNING: xl now has better capability to manage domain configuration, avoid using this command when possible
setting dom243 configuration
Marcin
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-08 22:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160603120921.y5l362zgrhf4fdcb@mac>
2016-06-08 22:18 ` HEADS UP: Imported Xen 4.7 and blkback changes Marcin Cieslak
[not found] ` <alpine.BSF.2.11.1606082204080.2130@z.fncre.vasb>
2016-06-08 22:35 ` Marcin Cieslak [this message]
2016-06-09 7:40 ` Roger Pau Monné
[not found] ` <alpine.BSF.2.11.1606082229190.2130@z.fncre.vasb>
2016-06-09 7:44 ` HEADS UP: Imported Xen 4.7 and blkback changes - domU respawning on_crash Roger Pau Monné
[not found] ` <20160609074021.uqtjio2vn7wo5h4m@mac>
2016-06-10 21:41 ` HEADS UP: Imported Xen 4.7 and blkback changes Marcin Cieslak
[not found] ` <alpine.BSF.2.11.1606102140290.2130@z.fncre.vasb>
2016-06-13 9:22 ` Roger Pau Monné
2016-06-09 0:16 ` HEADS UP: Imported Xen 4.7: no blkback Marcin Cieslak
[not found] ` <alpine.BSF.2.11.1606090010280.2130@z.fncre.vasb>
2016-06-09 8:03 ` Roger Pau Monné
[not found] ` <20160609080343.44rvpda4hskiy3ge@mac>
2016-06-09 9:07 ` Wei Liu
2016-06-10 21:38 ` Marcin Cieslak
[not found] ` <alpine.BSF.2.11.1606102124330.2130@z.fncre.vasb>
2016-06-13 9:10 ` Roger Pau Monné
[not found] ` <20160613091003.cejnbuqepp25zanc@mac>
2016-06-13 9:44 ` Marcin Cieslak
2016-06-13 19:26 ` Marcin Cieslak
[not found] ` <alpine.BSF.2.11.1606131922240.2130@z.fncre.vasb>
2016-06-16 15:29 ` Roger Pau Monné
[not found] ` <20160616152919.3nelncwerh3nir27@mac>
2016-06-16 17:05 ` Marcin Cieslak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='alpine.BSF.2.11.1606082229190.2130__46478.8757883527$1465425407$gmane$org@z.fncre.vasb' \
--to=saper@saper.info \
--cc=freebsd-virtualization@freebsd.org \
--cc=freebsd-xen@FreeBSD.org \
--cc=royger@FreeBSD.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).