search for: debvm

...the domU run suffers from unstable NFS mount. Since this is a NFS root, the domU just appear to be freezed. The log from both end of the NFS mount shows that the connection is broken: Note that the client time stamp is about 20 seconds ahead of server. From the domU (client end): Jan 4 23:31:16 debvm kernel: [ 371.008142] nfs: server 192.168.1.8 not responding, still trying //(once) Jan 4 23:31:25 debvm kernel: [ 379.928142] nfs: server 192.168.1.8 not responding, still trying //(28 times within the same second) Jan 4 23:31:26 debvm kernel: [ 381.396143] nfs: server 192.168.1.8 not respond...

...the domU run suffers from unstable NFS mount. Since this is a NFS root, the domU just appear to be freezed. The log from both end of the NFS mount shows that the connection is broken: Note that the client time stamp is about 20 seconds ahead of server. From the domU (client end): Jan 4 23:31:16 debvm kernel: [ 371.008142] nfs: server 192.168.1.8 not responding, still trying //(once) Jan 4 23:31:25 debvm kernel: [ 379.928142] nfs: server 192.168.1.8 not responding, still trying //(28 times within the same second) Jan 4 23:31:26 debvm kernel: [ 381.396143] nfs: server 192.168.1.8 not respond...

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that