search for: neugebauer

Commit 501db511397f ("virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too, fixing this by adding a hint (has_data_valid) and set it only on the receiving path. Cc: Rolf Neugebauer <rolf.neugebauer at docker.com> Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/net/macvtap.c | 2 +- drivers/net/tun.c | 2 +- drivers/net/virtio_net.c | 2 +- include/linux/virtio_net.h | 6 +++++- net/packet/af_packet.c | 4 ++-- 5 files changed, 1...

Commit 501db511397f ("virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too, fixing this by adding a hint (has_data_valid) and set it only on the receiving path. Cc: Rolf Neugebauer <rolf.neugebauer at docker.com> Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/net/macvtap.c | 2 +- drivers/net/tun.c | 2 +- drivers/net/virtio_net.c | 2 +- include/linux/virtio_net.h | 6 +++++- net/packet/af_packet.c | 4 ++-- 5 files changed, 1...

...> Commit 501db511397f ("virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on >> xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too, >> fixing this by adding a hint (has_data_valid) and set it only on the >> receiving path. >> >> Cc: Rolf Neugebauer<rolf.neugebauer at docker.com> >> Signed-off-by: Jason Wang<jasowang at redhat.com> >> --- >> drivers/net/macvtap.c | 2 +- >> drivers/net/tun.c | 2 +- >> drivers/net/virtio_net.c | 2 +- >> include/linux/virtio_net.h | 6 +++++-...

...> Commit 501db511397f ("virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on >> xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too, >> fixing this by adding a hint (has_data_valid) and set it only on the >> receiving path. >> >> Cc: Rolf Neugebauer<rolf.neugebauer at docker.com> >> Signed-off-by: Jason Wang<jasowang at redhat.com> >> --- >> drivers/net/macvtap.c | 2 +- >> drivers/net/tun.c | 2 +- >> drivers/net/virtio_net.c | 2 +- >> include/linux/virtio_net.h | 6 +++++-...

dear folks, when I run smbclient -L <hostname>, I've got the problem ; Added interface ip=10.1.1.32 bcast=10.1.7.255 nmask=255.255.248.0 Server time is Thu Jul 9 15:30:47 1998 Timezone is UTC+7.0 Domain=[AIFILE] OS=[Unix] Server=[Samba 1.9.16p9] SMBtconX failed. ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the

...;virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on > > > xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too, > > > fixing this by adding a hint (has_data_valid) and set it only on the > > > receiving path. > > > > > > Cc: Rolf Neugebauer<rolf.neugebauer at docker.com> > > > Signed-off-by: Jason Wang<jasowang at redhat.com> > > > --- > > > drivers/net/macvtap.c | 2 +- > > > drivers/net/tun.c | 2 +- > > > drivers/net/virtio_net.c | 2 +- > > > in...

...Jason Wang wrote: > Commit 501db511397f ("virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on > xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too, > fixing this by adding a hint (has_data_valid) and set it only on the > receiving path. > > Cc: Rolf Neugebauer <rolf.neugebauer at docker.com> > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > drivers/net/macvtap.c | 2 +- > drivers/net/tun.c | 2 +- > drivers/net/virtio_net.c | 2 +- > include/linux/virtio_net.h | 6 +++++- > net/packet/af_packet...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

Chris, le Wed 19 Dec 2007 10:19:53 -0500, a écrit : > Members of the team > created a domain builder separate from dom0 (conceptually similar to > Derek Murray''s recent project based on Rolf Neugebauer''s "initial > domains" patch) that accepts grub modules as input. So, your > suspicion is correct that the comments don''t belong in this patch and > are related to modifications used to accommodate several modules and > command line arguments. Ok. Si...

> -----Original Message----- > From: Ian Pratt [mailto:Ian.Pratt@cl.cam.ac.uk] > Sent: 15 May 2004 09:59 > To: Kip Macy > Cc: Neugebauer, Rolf; Ian Pratt; Keir Fraser; xen- > devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk > Subject: Re: [Xen-devel] telnet xend > > > > I now have secondary domains up and running with iSCSI luns as the root > > device. DOM1 doesn''t appear to have any difficulty...

On Thu, 11 Nov 2004 11:19:25 -0800, "Romain Neugebauer" <romain at berkeley.edu> wrote : >Dear Duncan Murdoch, > >I just posted the following message to the R-help mailing list in >response to your email of October 29th (see below). Unfortunately it >looks like my new message was not correctly posted, i.e. it does not >a...

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

On Tue, Jan 17, 2017 at 04:20:49PM +0000, Rolf Neugebauer wrote: > Commits: > > fd2a0437dc33 virtio_net: introduce virtio_net_hdr_{from,to}_skb > e858fae2b0b8 virtio_net: use common code for virtio_net_hdr and skb > GSO conversion > > introduced a subtle (but unexplained) difference in how virtio_net > flags are derived from skb-...

Thank you very much for your help. I was able to figure out a way to make this simple package work and was able to build a more useful and complex package as well. I am however left with one problem when building that more complex package. Before I go on with this issue, here is how I solved my initial problem: After creating an R package directory structure, I included in the \src directory

Commits: fd2a0437dc33 virtio_net: introduce virtio_net_hdr_{from,to}_skb e858fae2b0b8 virtio_net: use common code for virtio_net_hdr and skb GSO conversion introduced a subtle (but unexplained) difference in how virtio_net flags are derived from skb->ip_summed fields on transmit from the guest to the host/backend. Prior to the patches the flags would be set to VIRTIO_NET_HDR_F_NEEDS_CSUM if

Commits: fd2a0437dc33 virtio_net: introduce virtio_net_hdr_{from,to}_skb e858fae2b0b8 virtio_net: use common code for virtio_net_hdr and skb GSO conversion introduced a subtle (but unexplained) difference in how virtio_net flags are derived from skb->ip_summed fields on transmit from the guest to the host/backend. Prior to the patches the flags would be set to VIRTIO_NET_HDR_F_NEEDS_CSUM if

Hi, I''m curious about how you guys deal with big virtualization installations. To this date we only dealt with a small number of VM''s (~10)on not too big hardware (2xquad xeons+16GB ram). As I''m the "storage guy" I find it quite convenient to present to the dom0s one LUN per VM that makes live migration possible but without the cluster file system or cLVM

Maybe this question is a little stupid, but please help me. I am a newbie to Xen. When I tried to create a new domain "domain 1", I followed the Yan-Ching CHU''s guide on :installing quick file systems for new domains in Xen 1.2". But when I do "xc_dom_create.py -Dvmid=1", Xen seems to start to boot with some normal bootup information, but right after several

Hello all, I was able to create R packages under windows XP in the past using the dynamic NAG C library for windows XP (Mark 6). Recently, I changed computers and I am now using the static NAG C library for windows XP (Mark 7) to create a simple R package (called "test") which simply returns random numbers simulated using repetitive calls to a NAG C routine (uniform random

Is there a way to prevent other users from being able to map a drive from windoww95/NT to anyother user directory on the system. For example I can map to anyone's account on the system and have read only access, is there a way to stop this in either the global or share level? Thanks