Op 23-10-14 om 18:00 schreef James B. Byrne:
At the moment none I guess. The message is that the client cannot find a
driver. I have virtio-win-0.1-74.iso and virtio-win-0.1-81.iso on the
hypervisor host. How do I get the driver from there into the guest? Does the
client have access to the hy
On Mon, October 27, 2014 03:57, Patrick Bervoets wrote:
>
> Op 23-10-14 om 18:00 schreef James B. Byrne:
>> At the moment none I guess. The message is that the client cannot find a
>> driver. I have virtio-win-0.1-74.iso and virtio-win-0.1-81.iso on the
>> hypervisor host. How do I get the drive
On Mon, October 27, 2014 09:08, James B. Byrne wrote:
>
> On Mon, October 27, 2014 03:57, Patrick Bervoets wrote:
>>
>> (if your client already has more than 2 drives attached, change target dev
>> hdc to hdd or ...)
>>
>> You can switch your storages to virtio too, I did it in the past but fail
OK. We are golden with respect to getting the network reactivated on the
Windows guest. One down, infinity to go. Thanks for the help.
There was one wrinkle in all this. I had to log on to the guest as a local
administrator to configure the nic driver. Windows explorer (not IE) reported
a ser
Ted Miller wrote:
> I have gotten in the habit of either creating or leaving unused some space
> on any disk that might be used as a boot disk, rather than committing all
> the space to LVM. That way I have something to work with if I need "yet
> another" boot partition.
A bit ignorant of me, bu
Ted Miller wrote:
> I have not tried an upgrade, but it sounds like they put the work into
> making server upgrades easier, but did not (or could not) make it as easy
> for desktop installations. Most people paying license fees are covering
> servers.
I got the impression that the CentOSUpgradeT
Hi All,
I am switching from Fedora20 to CentOS7 since I now run all my Linux
development in a VM and I get a more robust feature set (i.e. shared
folders with the host that "just work", etc)
The only issue I have thus far is VPN connections. Looking at what's
installed on my old Fedora insta
Hello listmates,
Somehow or other my DNS services that are part of
the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup.
When I then start them up using systemctl:
systemctl start dnscache
systemctl start tinydns
they start just fine.
>From the log I got the following for t
I'm trying to extend a logical volume and I'm doing as follow:
1- Run `fdisk -l` command and this is the output:
Disk /dev/sda: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track,
10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512
Hello again,
I think I have resolved this issue by adding the following line to my
relevant service startup files:
RestartSec=60s
I presume the line forces a restart within 60 seconds (or with the time
allowance of 60 seconds). Actually according to this source:
http://www.dsm.fordham.edu/cgi-b
OK, on the second take, even 5 seconds has proved to be enough of a sleep
period in my case.
Just FYI.
Boris.
On Mon, Oct 27, 2014 at 4:07 PM, Boris Epstein wrote:
> Hello again,
>
> I think I have resolved this issue by adding the following line to my
> relevant service startup files:
>
> Res
On 10/27/2014 01:13 PM, CS DBA wrote:
> Hi All,
>
> I am switching from Fedora20 to CentOS7 since I now run all my Linux
> development in a VM and I get a more robust feature set (i.e. shared
> folders with the host that "just work", etc)
>
> The only issue I have thus far is VPN connections. L
Rebooting your system, then run fdisk /dev/sda
Then run
P
N
P
3
8e
..so on
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of
reynie...@gmail.com
Sent: Monday, October 27, 2014 12:57 PM
To: centos@centos.org
Subject: [CentOS] "No fre
It'd be nice if you reported this upstream.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Boris Epstein"
> To: "CentOS mailing list"
> Sent: Monday, 27 October, 2014 20:14:29
> Subject: Re: [CentOS] tinydns exceeds "holdoff
On Mon, Oct 27, 2014 at 3:54 PM, Zhang, Jonathan
wrote:
> Rebooting your system, then run fdisk /dev/sda
>
> Then run
> P
> N
> P
> 3
>
Can't pass from here, it says:
Partition number (1-4): 3
No free sectors available
Why?
___
CentOS mailing list
C
On Mon, Oct 27, 2014 at 3:56 PM, reynie...@gmail.com
wrote:
> I'm trying to extend a logical volume and I'm doing as follow:
> 1- Run `fdisk -l` command and this is the output:
>
This is for actual partitions, not LVM which seems to be what you want per
the rest of your message.
>
> 2- Run `
Hi SilverTip nice answer and very helpful, I'll try to get some more help
here since as I said in the main post I'm not an expert on Linux or a
Administrator I'm just a developer trying to setup a development enviroment
so ...
It's telling you the truth.
> Sounds like you want another Logical Volu
On 10/27/2014 07:42 PM, reynie...@gmail.com wrote:
Hi SilverTip nice answer and very helpful, I'll try to get some more help
here since as I said in the main post I'm not an expert on Linux or a
Administrator I'm just a developer trying to setup a development enviroment
so ...
It's telling you t
On 10/27/2014 10:31 AM, Timothy Murphy wrote:
Ted Miller wrote:
I have gotten in the habit of either creating or leaving unused some space
on any disk that might be used as a boot disk, rather than committing all
the space to LVM. That way I have something to work with if I need "yet
another"
On 10/27/2014 10:35 AM, Timothy Murphy wrote:
Ted Miller wrote:
I have not tried an upgrade, but it sounds like they put the work into
making server upgrades easier, but did not (or could not) make it as easy
for desktop installations. Most people paying license fees are covering
servers.
I
Uppsss I think this goes more and more advanced all the time but here I go
more doubts
On Mon, Oct 27, 2014 at 9:20 PM, Ted Miller wrote:
> If I were in your position, I think I would:
> * Create a new, 80GB disk using VMWare
>
Not problem at all
> * Partition that disk into your /boot a
On 10/27/2014 02:56 PM, reynie...@gmail.com wrote:
I also check the free available space using vgdisplay and watching the Free
PE / Size part near the end and seems like I've free space available (Free
PE / Size 7670 / 29.96 GiB) so I tried to extend the LV by using the
command:lvextend -L+29G /d
On Mon, Oct 27, 2014 at 11:21 PM, Robert Nichols wrote:
> Those I/O errors are alarming. They suggest that you have a disk that is
> failing. Does anything about disk sda appear in /var/log/messages when
> you do that? You should indeed have 29GB available for growing lv_root,
> but perhaps th
what do you get from the commands:
pvs -v
vgs -v
lvs
and, if pvs shows any /dev/mdXX devices, the output of mdadm --detail
/dev/mdXX
?example output...
# pvs -v
Scanning for physical volume names
PV VG Fmt Attr PSize PFree DevSize PV UUID
/dev/md
24 matches
Mail list logo
