similar to: Unable to see network printer on domu

Hi folks, I''m new to Xen so apologies if this is a stupid question. Setup is as follows: Dom0 and DomU''s running Hardy Heron Kernel 2.6.24-16-xen Xen version 3.0 My problem is I want to run TShark on DomU to see packets sent to eth0 on Dom0. TShark on Dom0 can see packets sent to DomU on eth0 but DomU cannot see packets sent to Dom0 on eth0. I know the eth0 on DomU is a

Hello! I have two problems. One is, that I cannot ping a DomU from Dom0 (or any other host in my local network) and the second one is, that I cannot ping the same site (eg. www.suse.com) from two DomU''s at the same time. I have a fresh installation of openSuse 11.0 with Kernel 2.6.25.20-0.1-xen and my box has two physical ethernet cards. As far as I have investigated, eth0 is the one

We have several suse 10.3 guests running in paravirtualization, however all the guests boot with the following messages: Loading keymap Couldnt open /dev/tty1 Loading /usr/share/kbd/keymaps/i386/qwerty/us.map.gz failed Loading compose table latin1.add failed Start Unicode mode Couldnt open /dev/tty1 Couldnt open /dev/tty2 Couldnt open /dev/tty3 Couldnt open /dev/tty4 Couldnt open

Hi all Ive just installed an XP and a 2003 server hvm instances. They way I read the docs, a ps2 mouse will automatically map to ps2 in the domU. The problem I having however is that the mouse ''flicks'' off the screen as soon as i activate the window and move the mouse. Just like an incorrect mouse driver was installed. If I look at the windows mouse configuation its using the

All, Just wanted to check one last time before letting this thread die. I am curious if anyone has gotten CentOS 8 to work in a PV Xen environment. Thanks. <9f9dcad3f78905b03201 at bcirpg.com> wrote: >All, > >I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running. > >Hardware does not support

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

We tried to get CentOS 8 domU working in PV mode as well but did not have any success and ended up deploying it in HVM mode. The reason OP have was lack of hardware support for HVM. This wasn't our rationale for wanting to run in PV mode. Our rationale was that we prefer to deploy CentOS 7 VMs on LVs which are formatted and deployed from an image on dom0 and don't have any partition

the fastest/best mode is still pvh... use the kernel from elrepo it supports the mode --- ------ Greetz Am 19.09.2020 19:08, schrieb Rados?aw Piliszek: > Hi, > > In general, PV tends not to be supported in newer distribution > releases. > This is mostly due to HVM performance and flexibility nowadays, which > just was not the case back in the days when PV ruled. > > I am

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

Hi guys, I''ve seen this post regarding "lvm resize" and this contains all the information I need to resize a disk inside domU : http://lists.xensource.com/archives/html/xen-users/2006-11/msg00019.html >From this post: "With this I can extend the LVs in the Dom0, and either shutdown the DomU and resize2fs from Dom0 or even (tested on test VMs and low-use

All, I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running. Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate. My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently

Xen-system AMD x64 2GB Memory installed with Domain 0 Linux Fedora 7 + Xen 3.1 + 2.6.18-xen i386 Domain 0 Linux Fedora 7 + Xen 3.1 + 2.6.18-xen x64 HVM - Vista 32 Ultimate + xenbus Vista 64 Ultimate + xenbus The DTM studio/controller was based on microsoft WLK 1.0c + update fileter patch (MS logo kit filter update every day) for more detail please

I'm running CentOS 6 x86_64 domU on CentOS 5 x86_64 dom0 The host is running 2.6.18-238.19.1.el5xen The guest is 2.6.32-220.2.1.el6.x86_64 'xm list' on the host shows 512mb memory allocated. 'free -m' in the guest shows 224mb memory. 'xm mem-set 21 1024' (21 being the domU ID), 'xm list' now shows 1024mb, but in the guest I now see 736mb. Anyone else seeing

Hi, I am experiencing a strange network problem. It looks like some packets get lost on the way from frontend network device in domU to the backend vifx.x in dom0. But first my configuration: - Xen 3.4.0 from the gentoo ebuild and the pvops dom0 kernel from jeremy/xen.git - The system has two physical network interfaces called gblan (Gigabit Ethernet) and felan (Fast Ethernet) - Two network

I''ve seen a lot of threads w/ similar problems, but none have posted a resolution. I am using Debian 4.0r1 (Etch). I was using the xen packages from stable, but have tried w/ testing as well and the problem persists. http://pastie.caboo.se/95144 Host is 10.0.0.20 on network 10.0.0.0/24. Dom0 is thus 10.0.0.20 DomU is 10.0.0.30 When the bridge is enabled, DomU can ping everything.

hi there all, I''m seeing some odd things with my networking (I''ll bet noone has ever read that before!): * My domU can access the outside world and download whatever I like from within the domain * Nothing from the outside can access the domU''s services despite the fact they''re running * I can access the domU''s services from the domU via eth0 or

Package: xen-utils-common Version: 3.0+hg11624-2 Severity: normal Hi, Problem shutting down Xen when DomU name contains more than 17 characters. I use fully qualified domain names in DomU names (example: long-domu-name.domain.com) Here's results when i attempt to run the following command: /etc/init.d/xendomains stop long-domname.doma(save)...Error: the domain 'in.com' does

Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only

----- "Thomas Jensen" <tom.jensen@digitaltoolbox-inc.com> ha scritto: > [ 2242.157407] Fatal DMA error! Please use ''swiotlb=force'' > [ 2242.157438] ------------[ cut here ]------------ > [ 2242.157446] kernel BUG at I''ve had the same situation (usb printer to domu) working until few days ago when I shut down the server to install more ram.

I am trying to get a USB printer to work in a Linux domU. I am using Xen 3.0.3 and the Xen Linux kernel 2.6.16.40. I have hidden the USB controller''s PCI devices from dom0 and exported them to domU, and build the domU kernel with the necessary device support. When I boot the xenU kernel, it lists an error from the USB printer class code that allocating a write buffer failed. This is an 8k