Re: HEADS UP: Imported Xen 4.7: no blkback

[Marcin Cieslak]

On Fri, 3 Jun 2016, Roger Pau Monné wrote:

> One of the more relevant changes in 4.7 regarding FreeBSD is the support for 
> block hotplug scripts. This means that we now have the option to use 
> backends different than simple block or regular files, provided that someone 
> writes the proper hotplug scripts to attach them (I've heard there are some 
> iSCSI hotplug scripts around). This however requires changes in blkback, so 
> if you plan to use the Xen 4.7 port, please make sure that you are running a 
> kernel that contains revision r301269 (or any later version). The same also 

I am running it with r301685 and the HVM guests have some trouble with
block devices.

SeaBIOS does not find /dev/zvol/zroot/freebsd1,raw,xvda,w to boot FreeBSD
from, after chaging to "hda" I get up to the kernel mountroot prompt
(Xen block devices seem to be detected in dmesg).

What used to be Windows 2016 domU with /dev/zvol/zroot/windows0,raw,hda,w
ends up in the Tianocore UEFI shell. Block devices seem to be available,
I can even list the fs0: partition, but no booting further possible.

Marcin

# more freebsd.cfg 
builder = "hvm"
name = "FreeBSD"
disk = [
'/dev/zvol/zroot/freebsd1,raw,xvda,w',
'/dev/zvol/zroot/freebsd2,raw,xvdb,w'
]
boot = "c"
#usbdevice = 'tablet'
#nographics = 1
serial = [ "file:/tmp/boot.log" ]
vnc = 1
#vnclisten = '0.0.0.0'
vif = ['bridge=bridge0,mac=00:02:04:08:fd:f0']
memory=2048
vcpus=1
vga = "cirrus"
videoram = 16

# more windows-run.cfg 
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'
on_crash = 'destroy'
acpi = 1
bios = 'ovmf'
vif = [ 'bridge=bridge0,mac=00:16:3e:5d:0d:48' ]
videoram=16
vga = "stdvga"
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261

--- Comment #24 from Sydney Meyer  ---
FWIW, i have applied the three patches to r301515M and on a dom0 running Xen
4.4.1 with Linux 4.5.1, and a Xen 4.5.3 / NetBSD 7.0.1 host i was able to ping,
connect via ssh, scp a file and nc some data between two FreeBSD VMs connected
trough a third VM, all running this revision, on the same Linux, respective
NetBSD dom0 host.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Re: HEADS UP: Imported Xen 4.7 and blkback changes - domU respawning on_crash

[Marcin Cieslak]

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:

Windows2016211  4079 1 --p---   0.0
Windows2016213  4096 1 --psc-   0.0
(disappears)
Windows2016221  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
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261

--- Comment #23 from Roger Pau Monné  ---
(In reply to kpielorz from comment #22)
Thanks for the traces, I will try to prepare a debug patch for you either this
afternoon or tomorrow morning.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261

--- Comment #21 from Roger Pau Monné  ---
(In reply to kpielorz from comment #20)
Yes, I think I know what the issue is. What OS are the other DomUs on the same
host using?

If you can provide me with complete tcpdump traces on both interfaces
(xn0/xn1), that would help me quite a lot, the following rune should get you
the traces:

# tcpdump -n -i  -s0 -w .pcap

The resulting pcap files are going to be quite big, so you will probably have
to upload them somewhere. Just 10s of capture while trying to route traffic is
probably fine.

Thanks, Roger.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"