similar to: State of GPLPV and Windows 8

Thanks, the whole iSCSI LUN have been passed to the VM. But I test it with scsicmd, and found that the driver may be not support SPC-3, but if i use this by microsoft iscsi initiator, I can pass all the scsi3_test tests. Tool can be found here: http://www.symantec.com/business/support/index?page=content&id=TECH72086 It's this means that the scsi passthrough windows driver does not

Hello Jeremy & Keir, sorry to be persistent, but the problem that pvops0 kernel 2.6.32.x still does not boot if x > 18 on my machines (and on many other machines, see this mailing list) is not solved yet. Shouldn''t this be a great focus of debugging and fixing? What is the point of having releases for 4.0.2 or 4.1 if I don''t have a dom0 kernel? The last time I tried

''cat /proc/interrupts'' in a Linux PV domain shows interrupts starting at 256 and labelled as ''Dynamic-irq''. Are these available in a HVM domain, eg under Windows? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

In the spirit of ''release early, release often'', here''s another binary release... http://www.meadowcourt.org/WindowsXenPV-0.8.8.zip The only thing that''s changed since 0.8.7 is that xennet should work under amd64 again. James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

In the spirit of ''release early, release often'', here''s another binary release... http://www.meadowcourt.org/WindowsXenPV-0.8.8.zip The only thing that''s changed since 0.8.7 is that xennet should work under amd64 again. James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, Sometimes, seemingly randomly, long-running Xen domains, using clocksource xen, have their clock shift by ~3000 or ~36000 seconds, often with the dom0 complaining about clocksource tsc. The number changes if the hypervisor is explicitly told to use clocksource=pit, but it still happens. It doesn''t seem to be particularly hardware-specific. See also http://bugs.debian.org/599161 I

Does anyone know if the ABIOSDSK service in XP would "find" and a HDD image pushed to ram by MEMDISK?? ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

> On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: >>> On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: >>>> 1) tell which devices can be configured >>> Not sure that I fully understated

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

Hi Stefan, Michael, Jason and everyone, Several days ago, I discussed with jason about "Vsock over Virtio-net". This idea has two advantages: First, it can use many great features of virtio-net, like batching, mergeable rx buffer and multiqueue, etc. Second, it can reduce many duplicate codes and make it easy to be maintained. Before the implement, I want to discuss with everyone

Hi Stefan, Michael, Jason and everyone, Several days ago, I discussed with jason about "Vsock over Virtio-net". This idea has two advantages: First, it can use many great features of virtio-net, like batching, mergeable rx buffer and multiqueue, etc. Second, it can reduce many duplicate codes and make it easy to be maintained. Before the implement, I want to discuss with everyone

The way we patch the Windows registry in order to allow it to boot off a virtio-blk drive was initially conceived by comparing the state with virtio-blk driver properly installed, to that without. However, we don't want to replicate the Windows PnP system; rather we need to apply just enough edits to make the system boot, and then let the Windows PnP manager figure out the rest. This series

On Mon, 2015-11-09 at 18:08 +0300, Roman Kagan wrote: > On Sun, Nov 08, 2015 at 10:15:31AM +0200, Yan Vugenfirer wrote: > > > > > On 06 Nov 2015, at 08:51, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: > > > > > > On Thu, 2015-11-05 at 21:46 +0000, Richard W.M. Jones wrote: > > >> On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld

On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > On Wed, 2015-10-28 at 14:53 +0300, Roman Kagan wrote: > > 1) tell which devices can be configured > Not sure that I fully understated your question. but if you are going to > create some sort of off-line automatic virtio-win drivers update > utility, then it shouldn't be too complicated. Firs of all you will

On Thu, 30 Sep 2010 14:02:34 +0800, gang.wei@intel.com wrote: > I am the original developer of HPET broadcast code. > > First of all, to disable HPET broadcast, no additional patch is required. > Please simply add option "cpuidle=off" or "max_cstate=1" at xen cmdline in > /boot/grub/grub.conf. > > Second, I noticed that the issue just occur on

Tony Brian Albers writes: > On 11/27/2017 05:28 PM, Benjammin2068 wrote: > > Thanks for the reply. > > > > IIRC, I've even rebooted the system (host as well) with no success... but > maybe not. I'll try your suggestions again if I have an issue. > > > > I really thought it was updates. I also don't use any VirtIO stuff either. > As plain and

Tony Brian Albers writes: > >> Hmm.. could this somehow be related to the fast startup thing in win10? > >> I mean, if fast startup is disabled, will that help? > >> > >> Just a thought. > > > > Fast startup does not get utilized for reboots, only for regular > > shutdowns. The actual option in Windows settings reads: > > > >

Hello All, I took a break from trying to get Tinc working and have come back to it now with the release of 1.0.11. I have 2 Windows computers connected behind firewalls and everything seems to be correct, except I cannot seem to get any data past the server TAP interface. I can ping the Server TAP interface from the client, but no data will move through the TAP interface to the Internet. I have

[Partly using the mailing list as a backup again ...] This commit changes virt-v2v to make registry changes to all ControlSets, not just the CurrentControlSet. Not sure what difference if any this would make. Rich.

I''ve recently noticed that my windows crash dumps fail at around 40-50% under GPLPV. ''xm dmesg'' shows the following: (XEN) grant_table.c:350:d0 Iomem mapping not permitted ffffffffffffffff (domain 865) At first I thought that the cause was just a bug in my grant ref code but it just occurred to me that this could be happening when Windows tries to write out the