|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [win-pv-devel] v9.0.0 released
It's been a while since I replied on this since I've had lots of testing going
on.
I just ran these tests on a new install of Win Server 2019 fully updated with
all of the 9.0.0 drivers.
My config is this:
memory = 16384
maxmem = 16384
vcpus = 4
name = 'ec-win2019-1'
vif = [ 'ip=x.x.x.x,mac=00:16:3e:CD:0B:01,type=ioemu,model=e1000,bridge=xenbr0'
]
address = 'x.x.x.x'
netmask = '255.255.255.0'
disk =
['phy:/dev/vg_san/ec-win2019-1_img,hda,w','file:/root/en_windows_server_2019_x64_dvd_4cb967d8.iso,hdc:cdrom,r']
boot = 'dc'
on_reboot = 'restart'
on_crash = 'restart'
vnc = 1
vnclisten = "0.0.0.0"
vncunused = 1
vncpasswd = "kldwslex"
builder = "hvm"
viridian = [ 'base', 'freq', 'time_ref_count', 'reference_tsc',
'hcall_remote_tlb_flush', 'apic_assist' ]
mmio_hole = 2048
vga="stdvga"
videoram=16
pae=1
nx=1
xen_platform_pci=1
usb=1
usbdevice=['tablet']
device_model_args=[ "-trace", "events=/root/events" ]
acpi=1
acpi_s3=0
acpi_s4=0
acpi_laptop_slate=1
The VM is running on a Dell R620 2x10core 3ghz w/384gb. The drive is actually
over an 8gb FC to a R720 with SCST running as a SAN w/ Raid-6 and 12x3tb drives.
Since this works so well, I'm guessing the previous issues reported may have
been due to the config I had since merging your sample config with what I had
seems to work fine. That same VM I originally tested with now has the 8.2.2
drivers back on it but with the latest Xen kernel I have, it just power cycles
over and over. I had to move it to another server running an older kernel. I'll
have to figure that out.
I did some disk i/o tests and am curious if the attached results look
appropriate for the environment or if there's some tuning I'm missing.
Any suggestions are appreciated.
Thank you,
Steffan Cline
steffan@xxxxxxxxx
602-793-0014
On 12/11/19, 1:30 AM, "Durrant, Paul" <pdurrant@xxxxxxxxxx> wrote:
Can someone post a log of the qemu output (with xen_platform_log in the
events file) so we can see what the PV drivers are doing?
I generally do most of my testing against the latest Xen (i.e. 4.13). 4.8
should be fine though; the main differences from a Windoows PoV would be in the
viridian enlightenment code, but that's orthogonal to the PV driver interfaces.
I've trimmed out the cruft from the config I normally used and attached it.
(I also normally boot Xen with a grant frame limit of 128, i.e. 4x the default).
Paul
> -----Original Message-----
> From: win-pv-devel <win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf
> Of Steffan Cline
> Sent: 10 December 2019 21:42
> To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [win-pv-devel] v9.0.0 released
>
> Håkon, this is what prompted me to ask everyone what cfg is being used
> with these new drivers in case it's a conflict caused by a flag/option I'm
> using.
>
> Paul, since these work for you, can you please share what you're using to
> ensure we're not using something in conflict?
>
> On another note, is there a specific xen version we should be using?
>
> # rpm -qa | grep xen
> xen-libs-4.8.5.75.g4c666a7e15-1.el7.x86_64
> xen-ovmf-20160905-1.gitbc54e50e0.el7.x86_64
> xen-hypervisor-4.8.5.75.g4c666a7e15-1.el7.x86_64
> centos-release-xen-common-8-7.el7.centos.x86_64
> xen-licenses-4.8.5.75.g4c666a7e15-1.el7.x86_64
> xen-runtime-4.8.5.75.g4c666a7e15-1.el7.x86_64
> centos-release-xen-8-7.el7.centos.x86_64
> xen-4.8.5.75.g4c666a7e15-1.el7.x86_64
>
>
> Thank you,
> Steffan Cline
> steffan@xxxxxxxxx
> 602-793-0014
>
>
> On 12/10/19, 2:12 PM, "win-pv-devel on behalf of Håkon Alstadheim" <win-
> pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx on behalf of
> hakon@xxxxxxxxxxxxxxxxxx> wrote:
>
>
> Den 09.12.2019 22:20, skrev Steffan Cline:
> > Does anyone have a specific config file they'd like to share that
> performs well with these newest drivers?
> >
> > On my Win 2016 Server, I removed the 8.2 drivers, rebooted,
> installed these and rebooted. It's been loading for about 30 minutes with
> the spinning dots non-stop.
> >
> Same here. Restored disk image from backup and tried again, and got
> same
> second time. Left it for a day, still spinning. After destroying it,
> at
> some point I got "Can not access boot device" in the middle of that
> pale blue screen. Trying to roll back using recovery point fails.
> (That
> is the extent of the error message, just restore failed) . It /does/
> show me the possible points I can revert to though, so it looks like
> it
> is working until it doesen't. For the record I also uninstalled old
> drivers first. First time around I also removed the Spice-thingy,
> leaving only Qemu. Second time around I left both the Qemu and Spice
> stuff in.
>
> Going back to that image is rather painful, as the disk image takes
> forever to copy to a new partition, and the backup I have is several
> windows-updates old, and insist on running a backup first thing when
> it
> gets moving :-/ .
>
> Did a chkdsk from the installation-iso (which boots nicely with the
> same
> config, except for "boot='dc'"). Found some minor nits w\chkdsk. Am
> now
> trying to boot into safemode minimal. Not even a spinner showing,
> "Times" column in the "xl list" display increases by about 0.4 every
> second, so it is doing /something/ ...
>
>
>
> _______________________________________________
> win-pv-devel mailing list
> win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/win-pv-devel
>
>
>
> _______________________________________________
> win-pv-devel mailing list
> win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/win-pv-devel
Attachment:
Screen Shot 2020-03-02 at 12.36.58 AM.png _______________________________________________ win-pv-devel mailing list win-pv-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/win-pv-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |
