Re: Status of bhyve

2017-02-17 Thread Alexander Nusov 
Hello,

Do have plans for Suspend/Resume? 
I'm really waiting for this feature.

--
Alexander

> On Feb 16, 2017, at 4:07 AM, Shane Ambler  wrote:
> 
> 
> CC'ing to freebsd-virtualization as a better place to ask this.
> 
> On 16/02/2017 05:11, Andrea Venturoli wrote:
>> Hello.
>> 
>> I've been searching the web for a while, but the info I got is sparse
>> (many howtos, little on the big picture) and it's not always clear what
>> is current and what is outdated.
>> 
>> I might be in need to permanently run a Windows 64b VM (with SQL server)
>> on a new FreeBSD box, so...
> 
> Permanently as in a development environment or production?
> 
>> What's the current status of bhyve?
>> I mean, it is it production ready (meaning no critical feature is
>> missing and I can count on this VM to behave properly nearly as much as
>> the host)?
>> Any difference between 10.3 and 11.0? (I got the idea the former will be
>> supported for longer and I'd have to upgrade my poudriere in order to
>> install the latter).
> 
> 11.0 includes a "VNC accessible framebuffer driver" which is not in 10.x
> This will allow you to vnc into the bhyve instance during boot to
> install/repair windows.
> 
> You will need to run poudriere on an 11 host to build 11 packages,
> while you can sometimes have success building newer systems than the
> host, building 11 packages on a 10 host does fail for many ports.
> 
>> 
>> How well does it run Windows?
>> Would I better run W7 instead of W10 (or the other way round)?
>> What's the maximum amount of RAM I can dedicate to a VM?
>> 
>> 
>> How does it compare to VirtualBox wrt to stability and performance?
>> (I know I can find benchmarks, but, again, it's hard to tell whether
>> they can be trusted or considered current).
>> 
>> 
>> Should I use a dedicated disk (or disk mirror) for better speed?
>> Or should I use a dedicated partition on the host's disk/disk mirror?
>> Will a ZFS volume perform as good as a partition?
>> 
>> 
>> 
>> Any caveat or hint?
>> 
>> 
>> 
>> bye & Thanks
>>av.
> 
> 
> 
> -- 
> FreeBSD - the place to B...Sharing Devices
> 
> Shane Ambler
> 
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"


___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

2017-01-23 Thread Alexander Nusov 
Hello,

I'm trying to launch a HVM DomU guest from QCOW2 image by using PV driver on 
FreeBSD 11.0-RELEASE.
The issue is that guest cannot connect to the device/vbd and requires to wait 
for 4 minutes to proceed, it goes through the countdown and starts fine (disk, 
networking)

[6.684115] XENBUS: Waiting for devices to initialise: 
25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
[  271.591403] XENBUS: Timeout connecting to device: device/vbd/51712 (local 
state 3, remote state 1)
[  271.599963] XENBUS: Device with no driver: device/vkbd/0
[  271.604249]   Magic number: 1:453:334
...
login: 


Unlike Linux It's impossible to boot FreeBSD 11 guests from QCOW2 
(xenbusb_nop_confighook_cb timeout)

Steps to reproduce:
1. Download qcow2 cirros image (small linux) 
http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img 

# file cirros-0.3.4-x86_64-disk.img 
cirros-0.3.4-x86_64-disk.img: QEMU QCOW Image (v2), 41126400 bytes
2. create DomU from config bellow xl create -c config.cfg

builder = "hvm"
memory = 512
vcpus = 2
name = "cirros"
disk = [ 'file:qcow2:/root/cirros-0.3.4-x86_64-disk.img,xvda,w' ]
boot = "c" 
vnc = 1
vnclisten = "0.0.0.0"
usbdevice = 'tablet'
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
acpi = 1
serial = 'pty'

I've also tried multiple configurations like tap:qcow2:. tap2:qcow2:, aio:, 
switching from xen bus to ide. didn't work.
The only driver that had no issues was PHY but it supports only RAW images.

Is that a bug or I'm missing something?

# pkg info | grep xen
xen-4.7.0_2Xen Hypervisor meta port
xen-kernel-4.7.1_3 Hypervisor using a microkernel design
xen-tools-4.7.1_1  Xen management tool, based on LibXenlight

# cat /boot/loader.conf 
hw.pci.mcfg=0
xen_kernel="/boot/xen"
xen_cmdline="dom0_mem=8192M dom0_max_vcpus=8 dom0pvh=1 com1=115200,8n1 
guest_loglvl=all loglvl=all"

# xenstore-ls -p
  4 = "" . . . . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
   vm = "/vm/94b147df-e15d-11e6-a685-002590d7eca6" . . . . .  (n0,r4)
   name = "cirros" . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
   cpu = ""  . . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
0 = "" . . . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
 availability = "online" . . . . . . . . . . . . . . . .  (n0,r4)
1 = "" . . . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
 availability = "online" . . . . . . . . . . . . . . . .  (n0,r4)
   memory = "" . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
static-max = "4194304" . . . . . . . . . . . . . . . . .  (n0,r4)
target = "4186112" . . . . . . . . . . . . . . . . . . .  (n0,r4)
videoram = "8192"  . . . . . . . . . . . . . . . . . . .  (n0,r4)
   device = "" . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
suspend = "" . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
 event-channel = ""  . . . . . . . . . . . . . . . . . .  (n4)
vbd = "" . . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
 51712 = ""  . . . . . . . . . . . . . . . . . . . . . .  (n4,r0)
  backend = "/local/domain/0/backend/qdisk/4/51712"  . .  (n4,r0)
  backend-id = "0" . . . . . . . . . . . . . . . . . . .  (n4,r0)
  state = "3"  . . . . . . . . . . . . . . . . . . . . .  (n4,r0)
  virtual-device = "51712" . . . . . . . . . . . . . . .  (n4,r0)
  device-type = "disk" . . . . . . . . . . . . . . . . .  (n4,r0)
  ring-ref = "8" . . . . . . . . . . . . . . . . . . . .  (n4,r0)
  event-channel = "18" . . . . . . . . . . . . . . . . .  (n4,r0)
  protocol = "x86_64-abi"  . . . . . . . . . . . . . . .  (n4,r0)
vkbd = ""  . . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
 0 = ""  . . . . . . . . . . . . . . . . . . . . . . . .  (n4,r0)
  backend = "/local/domain/0/backend/vkbd/4/0" . . . . .  (n4,r0)
  backend-id = "0" . . . . . . . . . . . . . . . . . . .  (n4,r0)
  state = "1"  . . . . . . . . . . . . . . . . . . . . .  (n4,r0)
   control = ""  . . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
shutdown = ""  . . . . . . . . . . . . . . . . . . . . .  (n4)
platform-feature-multiprocessor-suspend = "1"  . . . . .  (n0,r4)
platform-feature-xs_reset_watches = "1"  . . . . . . . .  (n0,r4)
   hvmloader = ""  . . . . . . . . . . . . . . . . . . . . .  (n0,r4)
bios = "seabios" . . . . . . . . . . . . . . . . . . . .  (n0,r4)
allow-memory-relocate = "0"  . . . . . . . . . . . . . .  (n0,r4)
   data = "" . . . . . . . . . . . . . . . . . . . . . . . .  (n4)
   drivers = ""  . . . . . . . . . . . . . . . . . .