I was talking about the Hyper-V problem with a guy from MS, and he
followed up on it for me. It seems this is a known issue, which
should be fixed in the latest version of Hyper-V (i.e. the RC of
Windows Server 2008 R2 that was released on TechNet last week).
David.
On Tuesday 14 April 2009 8:46:51 pm Sergey Babkin wrote:
John Baldwin wrote:
Your printf() probably isn't in the right place. pci_add_map() uses
PCIB_READ_CONFIG() directly and doesn't use pci_read_config(), so if your
printf is in pci_read_config_method() in pci.c it won't see them. Try
John Baldwin wrote:
On Tuesday 07 April 2009 9:14:26 pm Sergey Babkin wrote:
John Baldwin wrote:
On Monday 06 April 2009 11:12:33 pm Sergey Babkin wrote:
Anyway, as far as I can tell, it's only the base register of
the simulated DEC21140 device that has this issue, so it's
On Tuesday 07 April 2009 9:14:26 pm Sergey Babkin wrote:
John Baldwin wrote:
On Monday 06 April 2009 11:12:33 pm Sergey Babkin wrote:
Anyway, as far as I can tell, it's only the base register of
the simulated DEC21140 device that has this issue, so it's
quite possible that the bug
On Monday 06 April 2009 11:12:33 pm Sergey Babkin wrote:
John Baldwin wrote:
On Monday 06 April 2009 1:07:38 pm Ivan Voras wrote:
2009/4/6 John Baldwin j...@freebsd.org:
On Sunday 05 April 2009 12:23:39 pm Sergey Babkin wrote:
Hmm, the problem is we need to be able to write to
On Tue, Apr 7, 2009 at 9:21 AM, John Baldwin j...@freebsd.org wrote:
On Monday 06 April 2009 11:12:33 pm Sergey Babkin wrote:
John Baldwin wrote:
On Monday 06 April 2009 1:07:38 pm Ivan Voras wrote:
2009/4/6 John Baldwin j...@freebsd.org:
On Sunday 05 April 2009 12:23:39 pm Sergey
(Let's see if I've figured yet another workaround for the web
interface= ).
The address space used by the card I think is actually 0x80 bytes= ,
in the I/O port space. The card has it located at the port 0xEC00.
Yester= day I've had all the values and addresses written to this
John Baldwin wrote:
On Monday 06 April 2009 11:12:33 pm Sergey Babkin wrote:
Anyway, as far as I can tell, it's only the base register of
the simulated DEC21140 device that has this issue, so it's
quite possible that the bug is in that device's simulator.
I've attached a modified
On Sunday 05 April 2009 12:23:39 pm Sergey Babkin wrote:
Apr 4, 2009 02:10:23 PM, ivo...@freebsd.org wrote:
Can someo=ne please review and commit (if appropriate) the tweak for
Hyper-V shu=tdown issue at
http://shell.peach.ne.jp/aoyama/archives/40
?
=The problem is:
2009/4/6 John Baldwin j...@freebsd.org:
On Sunday 05 April 2009 12:23:39 pm Sergey Babkin wrote:
Hmm, the problem is we need to be able to write to BARs to size them. Any OS
needs to be able to do this to know what address space regions are being
decoded by devices. We can't avoid writing
In message: 200904061154.19601@freebsd.org
John Baldwin j...@freebsd.org writes:
: On Sunday 05 April 2009 12:23:39 pm Sergey Babkin wrote:
:
: Apr 4, 2009 02:10:23 PM, ivo...@freebsd.org wrote:
: Can someo=ne please review and commit (if appropriate) the tweak for
:
On Monday 06 April 2009 1:07:38 pm Ivan Voras wrote:
2009/4/6 John Baldwin j...@freebsd.org:
On Sunday 05 April 2009 12:23:39 pm Sergey Babkin wrote:
Hmm, the problem is we need to be able to write to BARs to size them. Any
OS
needs to be able to do this to know what address space
John Baldwin wrote:
On Monday 06 April 2009 1:07:38 pm Ivan Voras wrote:
2009/4/6 John Baldwin j...@freebsd.org:
On Sunday 05 April 2009 12:23:39 pm Sergey Babkin wrote:
Hmm, the problem is we need to be able to write to BARs to size them. б
Any
OS
needs to be able to do this
Apr 4, 2009 02:10:23 PM, ivo...@freebsd.org wrote:
Can someo= ne please review and commit (if appropriate) the tweak for
Hyper-V shu= tdown issue at
http://shell.peach.ne.jp/aoyama/archives/40
?
= The problem is: the VM appears to hang on shutdown without it
(hanging
14 matches
Mail list logo
